Falcon is an AI-based which was used to detect any kind of malicious transaction
or any anti-money laundering transaction on the system.

About the project





My Role

I was the product designer for the project, I was responsible for the overall product design, UX design, wireframing, UI design, Information Architecture, and prototyping. I also collaborated with the marketing team and management of the project in establishing the brand guidelines and in project management.

Project Summary

Anti-money laundering (AML) transaction monitoring software allows banks and other financial institutions to monitor customer transactions daily or in real-time for risk. By combining this information with analysis of customers’ historical information and account profile, the software can provide financial institutions with a “whole picture” analysis of a customer’s profile, risk levels, and predicted future activity, and can also generate reports and create alerts to suspicious activity.

The transactions monitored can include cash deposits and withdrawals, wire transfers, and ACH activity. Providing software to analyze transactions in an attempt to identify transactions or patterns of transactions is a completely different industry where the data and the information architecture plays a crucial role.

Falcon used patterns of the users and the patterns of the transactions made on the platform. Falcon is used to monitoring bank customer transactions daily and, using customer historical information and account profile, provide a “whole picture” to bank management. Transaction monitoring can include cash deposits and withdrawals, wire transfers, and ACH activity. In the bank circles, these applications are known as “AML software”.


The Challenge

Falcon was the application, which was designed for the banking professionals, the major challenges while designing the application was the application had a lot of information, which was required to be shown on the screen at a single instance.


If dealing with the heavy data was one part, the challenge that we were facing the major challenge was making the application intuitive and efficient for the users while performing the tasks. While designing such transaction monitoring application picking of the right colors, icons, and maintaining a proper visual language played a vital role. Along with these, the kind of data the users were looking at was the most important factor to decide the kind of emotions that were invoked.

We wanted to use more statistics in the form of plain graphs or tables or pie charts to make it easy to summarize the information that was required to be scanned. Another major challenge was coming up with the right environment and a more intuitive user experience that would help the users to perform the tasks in a better way. These users had to work on the application daily; we had to ensure that the application has a seamless navigation process that would allow the users to go back and forth in the application.

The Solution

The major goal while designing falcon was to increase the efficiency and the productivity of the Anti-money laundering team while checking the banking applications. Falcon is an enterprise application that contains sensitive data about the company. The biggest challenge while designing falcon was The complex nature of the application and the lack of examples of patterns that work or do not work in specific scenarios.

We started the project by setting the right goals for the project, to understand the goals, and to set a clear boundary we initially started with the stakeholder interviews, the stakeholder interviews helped us a lot in understanding the problem that needs to be solved. After speaking with the stakeholder we had a deep 1:1 session with our key user audience in understanding what are the problems in the current tools that they were using to detect the malicious transactions, Along with 1:1 interviews we also performed a survey in understanding their typical workday. Later we realized that there were too many options on one screen and most of these features were not used most of the time, This helped us to conclude that the new tool that we’re about to design should be a very simple tool which has to be adaptable and most importantly it should be efficient and easy to adapt to. While understanding the common issues we also started looking into the technologies which were used by popular banks to prevent fraud, ProcessGene, AML check, and SAAS AML tool were some popular tools that most companies used to check their malicious transaction. The Interviews and focus group session helped us in structuring our research, outlining our product requirements, and defining use cases.


Once we understood what we wanted to solve the next important phase to get an idea on how we could solve the specific problem, We started researching more about the user, and based on research findings we started fleshing out multiple user personas. We started building user personas of unique backgrounds, behaviors, values, and expectations. Our research and based on the user personas we could carve out the problem and helped us a lot in understanding more about how money laundering works and gave a clear foundation for the solution we wanted to build. Then we proceeded further in making the user scenarios and listed out the different situations where our audience could use the product and how they would interact with the machine.

The next phase of design was to crave out the user scenarios and then we started brainstorming on the various ideas and laid out a set of features that have to place in the current release, we ensure that we looped in various teammates so that we all were on the same page, these sessions helped us in understanding what we wanted to build and then we divided various features in a complete product roadmap and established a clear idea on what every individual team was supposed to work on. Once we had a clear idea of what we were building we started creating the information architecture of the entire features, the Information Architecture gave us a clear understanding and idea of the pages that we wanted to build. After building the overall Information Architecture we proceeded further and started sketching out the ideas and built a low-level wireframe of the overall project. we ensured that our wireframe gave a high-level idea about the product and it also helped the developers to do initial research. post that we made a high-level wireframe using the sketch and made a clickable prototype using the Invision app. This helped us in presenting our idea in a much better state and gave a high-level idea to everyone how our platform is going to look like.


One of the common myths while designing internal banking applications was banking applications cannot be visually appealing and most of the banks used legacy UI systems which were quite outdated, this was something which I wanted to avoid. I wanted to come up with a modern design system and something which a professional would use for 9 long hours at a stretch. In short, I wanted to make the job easy and interesting for these banking professionals. so we started our Visual design by collecting the right mood boards and started building a design system that is modern and fresh. We used Sketch to develop our overall UI design system. We wanted to use a common tool to design the overall visual design and as well as design system hence sketch was the best choice for us. After designing the Design system we started our visual designs and started mockup of the screens. The most exciting part of designing the User interface for a platform like FALCON was colorful graphs and the subtle usage of icons whenever required.


Once we are clear about how the UI, We prototyped the overall version, we used canvas flip for the analytics, and then to get a better insight we wanted to go with the A/B testing, since most of our users were available for use inside the office it wasn’t a huge concern for us. We started our A/B testing with various hypotheses. We gave 2 different Prototypes for the users to test and based on the quantitative results and after interviewing the users after the testing we started. We had 2 options for the flows, and once we spoke to the users the most of the professionals reported the flow which helped them and, then we proceeded further and started our coding for the flow. Finally implementing and running the test cases helped us to gain the right in-house solutions and it was faster and easy to conduct, but the only concern was some of our assumptions proved to be wrong and it’s after the user testing we understood what works best for us.

falcon_styke guide


Soon after the launch of the product, we performed a user testing where we used tools and heat maps to user stand where the users are spending most of the time and ensured that we smoothen the specific module of the application, We performed A/B testing and user interviews to understand the efficiency of the application. After working on the product we understood that the potential customer’s actions and emotions, and how we capture plays a vital role in designing the experience for the customer-centric applications.

Next case study

Previous case study