Feedzai
Rule Strategy Builder
Whether Analysts are monitoring fraudulent transactions or possible money laundry schemes, the software they use needs to have a well fleshed out strategy to ensure it catches sketchy behaviour.
Problem
Currently users have to set up the risk strategy on multiple environments and workflows, which might result in dangerous and unwanted activity.
Solution
Design a solution on a single platform that allows users to create and maintain a stretegy.
Context
The Rule Strategy Builder and other related projects emerged after Feedzai's products were unified into the RiskOps Studio. With this unification it became important to start improving key journeys with the first one being redesigning the risk strategy.
What are rules?
Rules are a core component when it comes to defining a risk strategy. They are a mechanism that enables teams to define specific “and/or” conditions based on certain behaviours or attributes of the entities captured by our system (such as transactions with exaggerated amounts or customers from high-risk countries, etc.).
What is a Rule Strategy?
Setting up a strategy allows users to define how rules should interact with each other, in other words, users define the priority between rules.
In the current solution this was identified as one of the most important but also one of the most cumbersome tasks.
The Problem
Currently users need to set up the strategy on multiple environments and workflows, which might result in dangerous and unwanted activity. This might cause fraudulent transactions to fly off the radar.
User Story Mapping
To create a good MVP, the Senior UX Designer and I spent some time with the PM and a Data Scientist to define the project's requirements. We started out with a big list, but managed to break it down into the necessary requirements to make up a functional MVP.
User flow
After spending some time creating the user flow and reviewing it with the senior designer we landed on the version below. There were a lot of layers to consider when creating the user flow. Does the manager work for a parent company with several subsidiaries?; or does the user need to edit some rules or the entire strategy? These are just 2 of a dozen other questions to take into considerations.
Ideation and
design explorations
Together with the Senior UX Designer, we ran an internal ideation workshops using the Crazy 8s exercise with 3 groups, 11 people in total.
UX Considerations
Have a clear indication of the outcomes
Have a system that automatically suggests rules to the table
Have a toggle button to enable and disable rules
Use human language that is easy to read and code-free
Having filters based on some entities from the transaction
Wireframes
The wireframes were created based on the results of the ideation workshop.
We designed a rule strategy builder dashboard for both Fraud and AML, although Fraud was deemed as higher priority.
We then ran usability sessions with 7 users in total:5 Fraud users and 2 AML users
Use Case: Fraud
Open the image to view the full prototype.
Use Case: Anti-Money Laundry
Open the image to view the full prototype. Wireframes for this use case were created and tested, but later deprioritised.
Validation Sessions Outcomes
Before being shown the new wireframes, users were asked to rate the current experience and after exploring it, we asked them for a new rating.
In general, the new version saw a huge improvement in both user needs and usability.
The improvement percentage gave us the confidence needed to proceed with wireframes updates and start designing the Hi-Fi Prototypes.
Wireframes updates
based on the outcomes
With the feedback from all 7 usability testing sessions we managed to improve the experience significantly – clearer journeys
Final Designs #1:
Rule Strategy Dashboard
The final solution was designed for users to have their decisions prioritised in a linear sequence and be able to write/add rules directly linked to a decision, meaning directly linked to a priority. This would cut down steps and simplify the overall journey.
One of the methods that contributed to the success of the solution was to analyse why users would do tasks in a certain way. Then, look into whether that method could be changed into a simpler solution that would continue to support users in their end goal but make the path ahead more straightforward.
Final Designs #2:
Customise the strategy
Given that building an entire strategy is a big job that could break the entire strategy, only Analyst Managers who knows how to work with the rule strategy builder have access to the edit mode.
Reorder rule group – path #1
Reorder by changing the numbers on the indicators.
Reorder rule group – path #2
Reorder by dragging and dropping rule groups
New rule group – path #1
Add a rule group between the existing groups.
New rule group – path #2
Add trailing rule groups.
New rule group – path #3
Add a rule group with the primary CTA, which will then appear at the end of the strategy.