signing
rules
alfa-bank
product designer
2022-2023
signing
rules
alfa-bank
product designer
2022-2023
signing
rules
alfa-bank
product designer
2022-2023
signing
rules
alfa-bank
product designer
2022-2023
signing
rules
alfa-bank
product designer
2022-2023
about
project
Flexible signing rules for approvals in business banking
The Signing Rules feature helps businesses set up approval flows: who signs each operation, under what conditions, and in which order. It reduces manual checks and makes signing logic clear across the team, so operations stay secure and predictable.
VOC score (3,6 → 4,43 out of 5)
4,43
Time to audit rules
−80%
Successfully created rules
87%
Rule creation time
x3 faster
my role
I identified UX issues in the signing rules product and redesigned its structure and main flows to improve clarity and prepare the interface for future features.
problems
• The homepage was overloaded and hard to navigate • Users could not understand where to create or edit signing rules • The rule setup flow lacked structure, which caused confusion and slowed down work • Users could not review rule logic from the homepage without opening each rule • Primary actions (“Create rule” and “Edit”) were easy to miss, blocking the start of the workflow
business goals
• Reduce time spent on configuring signing rules to speed up operations • Decrease user mistakes during operation signing and rule setup • Strengthen security through a more transparent and controlled signing flow • Reduce support load and manual reviews by making rules easier to audit • Improve customer satisfaction with a clearer and more reliable signing process
actions
• Identified key UX issues and success metrics for the redesign • Ran interviews and usability walkthroughs with SMB users • Reworked the core flows to make rule setup faster and more predictable • Aligned design with product, QA, and engineers to ensure correct implementation • Validated impact post-release using product analytics and VOC tracking
results
• 87% first-time success rate for creating valid rules • −80% time to audit complex rule • ×3 faster median time to create and validate a rule • +13% VOC score (3.6 → 4.43) • +37% rule builder usage growth
about
project
Flexible signing rules for approvals in business banking
The Signing Rules feature helps businesses set up approval flows: who signs each operation, under what conditions, and in which order. It reduces manual checks and makes signing logic clear across the team, so operations stay secure and predictable.
VOC score (3,6 → 4,43 out of 5)
4,43
Time to audit rules
−80%
Successfully created rules
87%
Rule creation time
x3 faster
my role
I identified UX issues in the signing rules product and redesigned its structure and main flows to improve clarity and prepare the interface for future features.
problems
• The homepage was overloaded and hard to navigate • Users could not understand where to create or edit signing rules • The rule setup flow lacked structure, which caused confusion and slowed down work • Users could not review rule logic from the homepage without opening each rule • Primary actions (“Create rule” and “Edit”) were easy to miss, blocking the start of the workflow
business goals
• Reduce time spent on configuring signing rules to speed up operations • Decrease user mistakes during operation signing and rule setup • Strengthen security through a more transparent and controlled signing flow • Reduce support load and manual reviews by making rules easier to audit • Improve customer satisfaction with a clearer and more reliable signing process
actions
• Identified key UX issues and success metrics for the redesign • Ran interviews and usability walkthroughs with SMB users • Reworked the core flows to make rule setup faster and more predictable • Aligned design with product, QA, and engineers to ensure correct implementation • Validated impact post-release using product analytics and VOC tracking
results
• 87% first-time success rate for creating valid rules • −80% time to audit complex rule • ×3 faster median time to create and validate a rule • +13% VOC score (3.6 → 4.43) • +37% rule builder usage growth
about
project
Flexible signing rules for approvals in business banking
The Signing Rules feature helps businesses set up approval flows: who signs each operation, under what conditions, and in which order. It reduces manual checks and makes signing logic clear across the team, so operations stay secure and predictable.
VOC score (3,6 → 4,43 out of 5)
4,43
Time to audit rules
−80%
Successfully created rules
87%
Rule creation time
x3 faster
my role
I identified UX issues in the signing rules product and redesigned its structure and main flows to improve clarity and prepare the interface for future features.
problems
• The homepage was overloaded and hard to navigate • Users could not understand where to create or edit signing rules • The rule setup flow lacked structure, which caused confusion and slowed down work • Users could not review rule logic from the homepage without opening each rule • Primary actions (“Create rule” and “Edit”) were easy to miss, blocking the start of the workflow
business goals
• Reduce time spent on configuring signing rules to speed up operations • Decrease user mistakes during operation signing and rule setup • Strengthen security through a more transparent and controlled signing flow • Reduce support load and manual reviews by making rules easier to audit • Improve customer satisfaction with a clearer and more reliable signing process
actions
• Identified key UX issues and success metrics for the redesign • Ran interviews and usability walkthroughs with SMB users • Reworked the core flows to make rule setup faster and more predictable • Aligned design with product, QA, and engineers to ensure correct implementation • Validated impact post-release using product analytics and VOC tracking
results
• 87% first-time success rate for creating valid rules • −80% time to audit complex rule • ×3 faster median time to create and validate a rule • +13% VOC score (3.6 → 4.43) • +37% rule builder usage growth
about
project
Flexible signing rules for approvals in business banking
The Signing Rules feature helps businesses set up approval flows: who signs each operation, under what conditions, and in which order. It reduces manual checks and makes signing logic clear across the team, so operations stay secure and predictable.
VOC score (3,6 → 4,43 out of 5)
4,43
Time to audit rules
−80%
Successfully created rules
87%
Rule creation time
x3 faster
my role
I identified UX issues in the signing rules product and redesigned its structure and main flows to improve clarity and prepare the interface for future features.
problems
• The homepage was overloaded and hard to navigate • Users could not understand where to create or edit signing rules • The rule setup flow lacked structure, which caused confusion and slowed down work • Users could not review rule logic from the homepage without opening each rule • Primary actions (“Create rule” and “Edit”) were easy to miss, blocking the start of the workflow
business goals
• Reduce time spent on configuring signing rules to speed up operations • Decrease user mistakes during operation signing and rule setup • Strengthen security through a more transparent and controlled signing flow • Reduce support load and manual reviews by making rules easier to audit • Improve customer satisfaction with a clearer and more reliable signing process
actions
• Identified key UX issues and success metrics for the redesign • Ran interviews and usability walkthroughs with SMB users • Reworked the core flows to make rule setup faster and more predictable • Aligned design with product, QA, and engineers to ensure correct implementation • Validated impact post-release using product analytics and VOC tracking
results
• 87% first-time success rate for creating valid rules • −80% time to audit complex rule • ×3 faster median time to create and validate a rule • +13% VOC score (3.6 → 4.43) • +37% rule builder usage growth
about
project
Flexible signing rules for approvals in business banking
The Signing Rules feature helps businesses set up approval flows: who signs each operation, under what conditions, and in which order. It reduces manual checks and makes signing logic clear across the team, so operations stay secure and predictable.
VOC score (3,6 → 4,43 out of 5)
4,43
Time to audit rules
−80%
Successfully created rules
87%
Rule creation time
x3 faster
my role
I identified UX issues in the signing rules product and redesigned its structure and main flows to improve clarity and prepare the interface for future features.
problems
• The homepage was overloaded and hard to navigate • Users could not understand where to create or edit signing rules • The rule setup flow lacked structure, which caused confusion and slowed down work • Users could not review rule logic from the homepage without opening each rule • Primary actions (“Create rule” and “Edit”) were easy to miss, blocking the start of the workflow
business goals
• Reduce time spent on configuring signing rules to speed up operations • Decrease user mistakes during operation signing and rule setup • Strengthen security through a more transparent and controlled signing flow • Reduce support load and manual reviews by making rules easier to audit • Improve customer satisfaction with a clearer and more reliable signing process
actions
• Identified key UX issues and success metrics for the redesign • Ran interviews and usability walkthroughs with SMB users • Reworked the core flows to make rule setup faster and more predictable • Aligned design with product, QA, and engineers to ensure correct implementation • Validated impact post-release using product analytics and VOC tracking
results
• 87% first-time success rate for creating valid rules • −80% time to audit complex rule • ×3 faster median time to create and validate a rule • +13% VOC score (3.6 → 4.43) • +37% rule builder usage growth
terminology
Product context
We built Flexible Signing Rules so companies can configure custom signing flows instead of relying on fixed templates. In corporate banking, signing logic often depends on amount, product, or company structure, so complex operations stay safe and consistent.
terminology
Product context
We built Flexible Signing Rules so companies can configure custom signing flows instead of relying on fixed templates. In corporate banking, signing logic often depends on amount, product, or company structure, so complex operations stay safe and consistent.
terminology
Product context
We built Flexible Signing Rules so companies can configure custom signing flows instead of relying on fixed templates. In corporate banking, signing logic often depends on amount, product, or company structure, so complex operations stay safe and consistent.
what are signing rules?
Signing rules define who must approve an operation and in what order. A rule can include multiple signers, limits, conditions, and sequential or parallel signing logic. Rules are applied automatically based on operation parameters.
who is a signer?
A signer is a user with a role that allows approving specific operations. A signer can participate in a signing process only if their role meets the rule conditions and they have permission to sign the selected product.
what makes a rule flexible?
A flexible signing rule is a configurable approval logic that replaces default signing templates. It allows companies to define custom signer sets, limits, and sequences for different products and scenarios without rigid constraints.
discovery
Validating how teams set signing rules for real operations
Together with a UX research team, I ran user research to see how companies configure signing rules for operations and where complexity breaks the flow.
discovery
Validating how teams set signing rules for real operations
Together with a UX research team, I ran user research to see how companies configure signing rules for operations and where complexity breaks the flow.
discovery
Validating how teams set signing rules for real operations
Together with a UX research team, I ran user research to see how companies configure signing rules for operations and where complexity breaks the flow.
discovery
Validating how teams set signing rules for real operations
Together with a UX research team, I ran user research to see how companies configure signing rules for operations and where complexity breaks the flow.
discovery
Validating how teams set signing rules for real operations
Together with a UX research team, I ran user research to see how companies configure signing rules for operations and where complexity breaks the flow.
methodology:
• 4 participants from small and medium businesses (owners and accountants) • In-depth interviews combined with usability walkthroughs (30–40 min each) • Internal review with product and QA teams to validate flow logic
research goals:
• Understand how users create and apply flexible signing rules across different products • Identify unclear steps and usability issues during the setup process • Define opportunities to simplify and automate signing rule configuration
key tasks:
• Observe how users set up rules, assign signers, and manage limits • Collect feedback on difficulties and confusing parts of the flow • Propose UX improvements to make the process faster, clearer, and more consistent
methodology:
• 4 participants from small and medium businesses (owners and accountants) • In-depth interviews combined with usability walkthroughs (30–40 min each) • Internal review with product and QA teams to validate flow logic
research goals:
• Understand how users create and apply flexible signing rules across different products • Identify unclear steps and usability issues during the setup process • Define opportunities to simplify and automate signing rule configuration
key tasks:
• Observe how users set up rules, assign signers, and manage limits • Collect feedback on difficulties and confusing parts of the flow • Propose UX improvements to make the process faster, clearer, and more consistent
methodology:
• 4 participants from small and medium businesses (owners and accountants) • In-depth interviews combined with usability walkthroughs (30–40 min each) • Internal review with product and QA teams to validate flow logic
research goals:
• Understand how users create and apply flexible signing rules across different products • Identify unclear steps and usability issues during the setup process • Define opportunities to simplify and automate signing rule configuration
key tasks:
• Observe how users set up rules, assign signers, and manage limits • Collect feedback on difficulties and confusing parts of the flow • Propose UX improvements to make the process faster, clearer, and more consistent
methodology:
• 4 participants from small and medium businesses (owners and accountants) • In-depth interviews combined with usability walkthroughs (30–40 min each) • Internal review with product and QA teams to validate flow logic
research goals:
• Understand how users create and apply flexible signing rules across different products • Identify unclear steps and usability issues during the setup process • Define opportunities to simplify and automate signing rule configuration
key tasks:
• Observe how users set up rules, assign signers, and manage limits • Collect feedback on difficulties and confusing parts of the flow • Propose UX improvements to make the process faster, clearer, and more consistent
methodology:
• 4 participants from small and medium businesses (owners and accountants) • In-depth interviews combined with usability walkthroughs (30–40 min each) • Internal review with product and QA teams to validate flow logic
research goals:
• Understand how users create and apply flexible signing rules across different products • Identify unclear steps and usability issues during the setup process • Define opportunities to simplify and automate signing rule configuration
key tasks:
• Observe how users set up rules, assign signers, and manage limits • Collect feedback on difficulties and confusing parts of the flow • Propose UX improvements to make the process faster, clearer, and more consistent
Research insights
Usability tests and short interviews showed that users struggled with navigation and rule setup. They had trouble finding key actions, creating rules, and understanding the signing logic:
Research insights
Usability tests and short interviews showed that users struggled with navigation and rule setup. They had trouble finding key actions, creating rules, and understanding the signing logic:
Research insights
Usability tests and short interviews showed that users struggled with navigation and rule setup. They had trouble finding key actions, creating rules, and understanding the signing logic:
Research insights
Usability tests and short interviews showed that users struggled with navigation and rule setup. They had trouble finding key actions, creating rules, and understanding the signing logic:
Research insights
Usability tests and short interviews showed that users struggled with navigation and rule setup. They had trouble finding key actions, creating rules, and understanding the signing logic:
"I had no idea how to create a rule. The interface doesn't guide you at all, so I just kept clicking around trying to figure out where to start."
"I had no idea how to create a rule. The interface doesn't guide you at all, so I just kept clicking around trying to figure out where to start."
"I had no idea how to create a rule. The interface doesn't guide you at all, so I just kept clicking around trying to figure out where to start."
"I had no idea how to create a rule. The interface doesn't guide you at all, so I just kept clicking around trying to figure out where to start."
"I had no idea how to create a rule. The interface doesn't guide you at all, so I just kept clicking around trying to figure out where to start."
"The page is too cluttered to navigate. Everything feels mixed together and out of order, so finding what I need takes forever."
"The page is too cluttered to navigate. Everything feels mixed together and out of order, so finding what I need takes forever."
"The page is too cluttered to navigate. Everything feels mixed together and out of order, so finding what I need takes forever."
"The page is too cluttered to navigate. Everything feels mixed together and out of order, so finding what I need takes forever."
"The page is too cluttered to navigate. Everything feels mixed together and out of order, so finding what I need takes forever."
"There's no clear structure to any of the sections. I keep getting lost and have to start over every time."
"There's no clear structure to any of the sections. I keep getting lost and have to start over every time."
"There's no clear structure to any of the sections. I keep getting lost and have to start over every time."
"There's no clear structure to any of the sections. I keep getting lost and have to start over every time."
"There's no clear structure to any of the sections. I keep getting lost and have to start over every time."
"Important actions are hidden or placed where you'd never think to look. You end up hunting for everything instead of just doing the work."
"Important actions are hidden or placed where you'd never think to look. You end up hunting for everything instead of just doing the work."
"Important actions are hidden or placed where you'd never think to look. You end up hunting for everything instead of just doing the work."
"Important actions are hidden or placed where you'd never think to look. You end up hunting for everything instead of just doing the work."
"Important actions are hidden or placed where you'd never think to look. You end up hunting for everything instead of just doing the work."
"It's basically a wall of operations with no structure. Every time I try to set up a rule it feels like more of a struggle than it should be."
"It's basically a wall of operations with no structure. Every time I try to set up a rule it feels like more of a struggle than it should be."
"It's basically a wall of operations with no structure. Every time I try to set up a rule it feels like more of a struggle than it should be."
"It's basically a wall of operations with no structure. Every time I try to set up a rule it feels like more of a struggle than it should be."
main page
Where signing rules start
The main page is the starting point for managing signing rules. Users should quickly see which rules are set up, where they apply, and the key parameters, without opening each rule one by one.
main page
Where signing rules start
The main page is the starting point for managing signing rules. Users should quickly see which rules are set up, where they apply, and the key parameters, without opening each rule one by one.
main page
Where signing rules start
The main page is the starting point for managing signing rules. Users should quickly see which rules are set up, where they apply, and the key parameters, without opening each rule one by one.
main page
Where signing rules start
The main page is the starting point for managing signing rules. Users should quickly see which rules are set up, where they apply, and the key parameters, without opening each rule one by one.
main page
Where signing rules start
The main page is the starting point for managing signing rules. Users should quickly see which rules are set up, where they apply, and the key parameters, without opening each rule one by one.
Before redesign
The previous signing rules screen lacked structure, making it difficult for users to understand the current setup. Usability testing showed that key actions were hidden and the dense text layout forced users to read every line just to find what they needed.
Before redesign
The previous signing rules screen lacked structure, making it difficult for users to understand the current setup. Usability testing showed that key actions were hidden and the dense text layout forced users to read every line just to find what they needed.
Before redesign
The previous signing rules screen lacked structure, making it difficult for users to understand the current setup. Usability testing showed that key actions were hidden and the dense text layout forced users to read every line just to find what they needed.
Problems
The screen was overloaded with dense text and lacked visual hierarchy making it nearly impossible for users to scan the content and locate specific rules without reading every line.
Users consistently overlooked the «Create rule» button because it blended into the page, blocking the start of the workflow.
The operations list did not show which operations were covered by rules, so users could easily miss gaps in their signing setup.
Interaction patterns were inconsistent across sections, which made complex setups harder to complete and increased the chance of errors.
Problems
The screen was overloaded with dense text and lacked visual hierarchy making it nearly impossible for users to scan the content and locate specific rules without reading every line.
Users consistently overlooked the «Create rule» button because it blended into the page, blocking the start of the workflow.
The operations list did not show which operations were covered by rules, so users could easily miss gaps in their signing setup.
Interaction patterns were inconsistent across sections, which made complex setups harder to complete and increased the chance of errors.
Problems
The screen was overloaded with dense text and lacked visual hierarchy making it nearly impossible for users to scan the content and locate specific rules without reading every line.
Users consistently overlooked the «Create rule» button because it blended into the page, blocking the start of the workflow.
The operations list did not show which operations were covered by rules, so users could easily miss gaps in their signing setup.
Interaction patterns were inconsistent across sections, which made complex setups harder to complete and increased the chance of errors.
After redesign
I unified all rules into a single categorized table. This created a clear starting point for management and made key actions like «Create rule» instantly discoverable.
After redesign
I unified all rules into a single categorized table. This created a clear starting point for management and made key actions like «Create rule» instantly discoverable.
After redesign
I unified all rules into a single categorized table. This created a clear starting point for management and made key actions like «Create rule» instantly discoverable.
Problem and solution
Problem: Key rule details were hidden inside nested pages, so users had to open each rule one by one just to understand the current setup. This made reviews slow and increased the chance of configuration errors.
Solution: I consolidated all rules into a single table with key parameters visible at a glance — limits, signer sequences, and applied accounts. This removed the need to drill into each rule for a basic review.
Problem and solution
Problem: Key rule details were hidden inside nested pages, so users had to open each rule one by one just to understand the current setup. This made reviews slow and increased the chance of configuration errors.
Solution: I consolidated all rules into a single table with key parameters visible at a glance — limits, signer sequences, and applied accounts. This removed the need to drill into each rule for a basic review.
Problem and solution
Problem: Key rule details were hidden inside nested pages, so users had to open each rule one by one just to understand the current setup. This made reviews slow and increased the chance of configuration errors.
Solution: I consolidated all rules into a single table with key parameters visible at a glance — limits, signer sequences, and applied accounts. This removed the need to drill into each rule for a basic review.
Problem and solution
Problem: The previous signer list was ambiguous. It showed names but hid the actual approval logic, making it impossible to distinguish between parallel signing (anyone can sign) and sequential signing (strict order). This created compliance risks, as users couldn't verify if the approval flow was secure without opening every rule.
Solution: I designed a structured signer row that visualizes the exact signing sequence and role dependencies. This makes the approval workflow transparent and ensures the signing order is visible at a glance, preventing setup errors.
Problem and solution
Problem: The previous signer list was ambiguous. It showed names but hid the actual approval logic, making it impossible to distinguish between parallel signing (anyone can sign) and sequential signing (strict order). This created compliance risks, as users couldn't verify if the approval flow was secure without opening every rule.
Solution: I designed a structured signer row that visualizes the exact signing sequence and role dependencies. This makes the approval workflow transparent and ensures the signing order is visible at a glance, preventing setup errors.
Problem and solution
Problem: The previous signer list was ambiguous. It showed names but hid the actual approval logic, making it impossible to distinguish between parallel signing (anyone can sign) and sequential signing (strict order). This created compliance risks, as users couldn't verify if the approval flow was secure without opening every rule.
Solution: I designed a structured signer row that visualizes the exact signing sequence and role dependencies. This makes the approval workflow transparent and ensures the signing order is visible at a glance, preventing setup errors.
Problem and solution
Problem: Users could not verify rule logic without opening details. With new limits and account scopes, the list lacked context, making review slow and prone to errors.
Solution: To make rule behavior clear at a glance, I surfaced the most important new parameters directly in the list. I extended the rule row to show limits and applied accounts, so users can immediately understand where and under what conditions a rule works, without drilling into its details.
Problem and solution
Problem: Users could not verify rule logic without opening details. With new limits and account scopes, the list lacked context, making review slow and prone to errors.
Solution: To make rule behavior clear at a glance, I surfaced the most important new parameters directly in the list. I extended the rule row to show limits and applied accounts, so users can immediately understand where and under what conditions a rule works, without drilling into its details.
Problem and solution
Problem: Users could not verify rule logic without opening details. With new limits and account scopes, the list lacked context, making review slow and prone to errors.
Solution: To make rule behavior clear at a glance, I surfaced the most important new parameters directly in the list. I extended the rule row to show limits and applied accounts, so users can immediately understand where and under what conditions a rule works, without drilling into its details.
Problem and solution
Problem: The interface was fragmented. Custom and Standard rules lived in separate, disconnected blocks. This forced users to switch contexts constantly and made the configuration difficult to scan.
Solution: I unified both rule types into a single table with collapsible sections. Custom rules are prioritised at the top while Standard templates stay accessible below, so everything is in one place without the clutter.
Problem and solution
Problem: The interface was fragmented. Custom and Standard rules lived in separate, disconnected blocks. This forced users to switch contexts constantly and made the configuration difficult to scan.
Solution: I unified both rule types into a single table with collapsible sections. Custom rules are prioritised at the top while Standard templates stay accessible below, so everything is in one place without the clutter.
Problem and solution
Problem: The interface was fragmented. Custom and Standard rules lived in separate, disconnected blocks. This forced users to switch contexts constantly and made the configuration difficult to scan.
Solution: I unified both rule types into a single table with collapsible sections. Custom rules are prioritised at the top while Standard templates stay accessible below, so everything is in one place without the clutter.
Problem and solution
Problem: Users struggled to find the main actions. “Create rule” and “Edit” were pushed to the right side and visually blended into the page, so people missed them and had to scan the screen to start the key flow.
Solution: I moved the primary actions to the top, right under the page header, so the next step is obvious immediately. I grouped “Create rule” and “Edit” into a single, consistent action area aligned with the title, making the entry point faster and removing unnecessary visual search.
Problem and solution
Problem: Users struggled to find the main actions. “Create rule” and “Edit” were pushed to the right side and visually blended into the page, so people missed them and had to scan the screen to start the key flow.
Solution: I moved the primary actions to the top, right under the page header, so the next step is obvious immediately. I grouped “Create rule” and “Edit” into a single, consistent action area aligned with the title, making the entry point faster and removing unnecessary visual search.
Problem and solution
Problem: Users struggled to find the main actions. “Create rule” and “Edit” were pushed to the right side and visually blended into the page, so people missed them and had to scan the screen to start the key flow.
Solution: I moved the primary actions to the top, right under the page header, so the next step is obvious immediately. I grouped “Create rule” and “Edit” into a single, consistent action area aligned with the title, making the entry point faster and removing unnecessary visual search.
Results
After the redesign, we saw clear improvements across navigation and rule management. Results were measured through task-based usability testing and product analytics.
Results
After the redesign, we saw clear improvements across navigation and rule management. Results were measured through task-based usability testing and product analytics.
Results
After the redesign, we saw clear improvements across navigation and rule management. Results were measured through task-based usability testing and product analytics.
time to task
Median time from homepage to starting rule creation
3x faster
First-click success rate on «Create rule» button
77%
Accuracy
First-time success rate for creating valid rules
87%
time to task
Median time from homepage to starting rule creation
3x faster
First-click success rate on «Create rule» button
77%
Accuracy
First-time success rate for creating valid rules
87%
time to task
Median time from homepage to starting rule creation
3x faster
First-click success rate on «Create rule» button
77%
Accuracy
First-time success rate for creating valid rules
87%
creating rules
Smart Rule Builder
Configuring signing rules requires precision, but the previous form had no structure and allowed users to create conflicting logic. I redesigned it as a guided flow with separate sections for accounts, limits, and signers, so every rule is complete and consistent by the time it is saved.
creating rules
Smart Rule Builder
Configuring signing rules requires precision, but the previous form had no structure and allowed users to create conflicting logic. I redesigned it as a guided flow with separate sections for accounts, limits, and signers, so every rule is complete and consistent by the time it is saved.
creating rules
Smart Rule Builder
Configuring signing rules requires precision, but the previous form had no structure and allowed users to create conflicting logic. I redesigned it as a guided flow with separate sections for accounts, limits, and signers, so every rule is complete and consistent by the time it is saved.
creating rules
Smart Rule Builder
Configuring signing rules requires precision, but the previous form had no structure and allowed users to create conflicting logic. I redesigned it as a guided flow with separate sections for accounts, limits, and signers, so every rule is complete and consistent by the time it is saved.
creating rules
Smart Rule Builder
Configuring signing rules requires precision, but the previous form had no structure and allowed users to create conflicting logic. I redesigned it as a guided flow with separate sections for accounts, limits, and signers, so every rule is complete and consistent by the time it is saved.
Before redesign
The legacy creation form was designed as a static checklist. It treated signing rules as simple permissions rather than flexible logic preventing users from configuring specific limits, account scopes, or strict signing orders.
Before redesign
The legacy creation form was designed as a static checklist. It treated signing rules as simple permissions rather than flexible logic preventing users from configuring specific limits, account scopes, or strict signing orders.
Before redesign
The legacy creation form was designed as a static checklist. It treated signing rules as simple permissions rather than flexible logic preventing users from configuring specific limits, account scopes, or strict signing orders.
Problems
The form did not support transaction limits or specific conditions, forcing businesses to use the same approval chain for both small and critical payments.
The interface treated signers as a simple group without defining the order, making it impossible to enforce strict sequential approvals for security.
Rules applied to the entire company context by default. Users could not restrict high-risk rules to specific bank accounts, creating potential security gaps.
All settings were presented as a long uniform list of checkboxes, which made it difficult to focus on building a secure scenario.
Problems
The form did not support transaction limits or specific conditions, forcing businesses to use the same approval chain for both small and critical payments.
The interface treated signers as a simple group without defining the order, making it impossible to enforce strict sequential approvals for security.
Rules applied to the entire company context by default. Users could not restrict high-risk rules to specific bank accounts, creating potential security gaps.
All settings were presented as a long uniform list of checkboxes, which made it difficult to focus on building a secure scenario.
Problems
The form did not support transaction limits or specific conditions, forcing businesses to use the same approval chain for both small and critical payments.
The interface treated signers as a simple group without defining the order, making it impossible to enforce strict sequential approvals for security.
Rules applied to the entire company context by default. Users could not restrict high-risk rules to specific bank accounts, creating potential security gaps.
All settings were presented as a long uniform list of checkboxes, which made it difficult to focus on building a secure scenario.
After redesign
Based on research, I rebuilt the rule creation flow from scratch. The new structure separates each decision into its own section, so users configure rules step by step without getting lost in a single overloaded form.
After redesign
Based on research, I rebuilt the rule creation flow from scratch. The new structure separates each decision into its own section, so users configure rules step by step without getting lost in a single overloaded form.
After redesign
Based on research, I rebuilt the rule creation flow from scratch. The new structure separates each decision into its own section, so users configure rules step by step without getting lost in a single overloaded form.
Problem and solution
Problem: Creating a rule felt like filling out a “wall of settings.” Everything was packed into one block, so users had to scan a long mixed list, constantly losing track of what each parameter means and whether it’s already set. This made configuration slower and increased the chance of missing a critical setting.
Solution: I completely rebuilt the page into a modular structure so rule setup feels controlled and predictable. Each parameter group became its own section (operation, signers, accounts, conditions) with a consistent layout, so users move step by step, instantly understand what they’re editing, and can review the rule without hunting through a single overloaded block.
Problem and solution
Problem: Creating a rule felt like filling out a “wall of settings.” Everything was packed into one block, so users had to scan a long mixed list, constantly losing track of what each parameter means and whether it’s already set. This made configuration slower and increased the chance of missing a critical setting.
Solution: I completely rebuilt the page into a modular structure so rule setup feels controlled and predictable. Each parameter group became its own section (operation, signers, accounts, conditions) with a consistent layout, so users move step by step, instantly understand what they’re editing, and can review the rule without hunting through a single overloaded block.
Problem and solution
Problem: Creating a rule felt like filling out a “wall of settings.” Everything was packed into one block, so users had to scan a long mixed list, constantly losing track of what each parameter means and whether it’s already set. This made configuration slower and increased the chance of missing a critical setting.
Solution: I completely rebuilt the page into a modular structure so rule setup feels controlled and predictable. Each parameter group became its own section (operation, signers, accounts, conditions) with a consistent layout, so users move step by step, instantly understand what they’re editing, and can review the rule without hunting through a single overloaded block.
Problem and solution
Problem: The previous checklist allowed mixing different operations in a single rule, which prevented setting specific limits or unique signing logic for each transaction type
Solution: I changed the logic to one operation per rule to ensure granular control and allow users to configure precise security settings for each specific process.
Problem and solution
Problem: The previous checklist allowed mixing different operations in a single rule, which prevented setting specific limits or unique signing logic for each transaction type
Solution: I changed the logic to one operation per rule to ensure granular control and allow users to configure precise security settings for each specific process.
Problem and solution
Problem: The previous checklist allowed mixing different operations in a single rule, which prevented setting specific limits or unique signing logic for each transaction type
Solution: I changed the logic to one operation per rule to ensure granular control and allow users to configure precise security settings for each specific process.
Problem and solution
Problem: Signing rules were applied globally with no way to restrict them to specific accounts. This created compliance risks and made it impossible to apply stricter controls where they were actually needed.
Solution: I introduced a dedicated account binding block that allows businesses to set different approval rules for different accounts, so high-risk accounts get stricter controls without affecting standard operations.
Problem and solution
Problem: Signing rules were applied globally with no way to restrict them to specific accounts. This created compliance risks and made it impossible to apply stricter controls where they were actually needed.
Solution: I introduced a dedicated account binding block that allows businesses to set different approval rules for different accounts, so high-risk accounts get stricter controls without affecting standard operations.
Problem and solution
Problem: Signing rules were applied globally with no way to restrict them to specific accounts. This created compliance risks and made it impossible to apply stricter controls where they were actually needed.
Solution: I introduced a dedicated account binding block that allows businesses to set different approval rules for different accounts, so high-risk accounts get stricter controls without affecting standard operations.
Problem and solution
Problem: Signing rules were applied globally with no way to restrict them to specific accounts. This created compliance risks and made it impossible to apply stricter controls where they were actually needed.
Solution: I introduced a dedicated account binding block that allows businesses to set different approval rules for different accounts, so high-risk accounts get stricter controls without affecting standard operations.
Problem and solution
Problem: Signing rules were applied globally with no way to restrict them to specific accounts. This created compliance risks and made it impossible to apply stricter controls where they were actually needed.
Solution: I introduced a dedicated account binding block that allows businesses to set different approval rules for different accounts, so high-risk accounts get stricter controls without affecting standard operations.
Problem and solution
Problem: Signing rules were applied globally with no way to restrict them to specific accounts. This created compliance risks and made it impossible to apply stricter controls where they were actually needed.
Solution: I introduced a dedicated account binding block that allows businesses to set different approval rules for different accounts, so high-risk accounts get stricter controls without affecting standard operations.
Problem and solution
Problem: The product had no support for amount-based rules. Businesses could not set different approval conditions for different transaction sizes, so the same signing logic applied to both small and large payments.
Solution: I designed a limit engine that allows users to create and manage custom payment thresholds from scratch. This filled a significant gap and gave companies the ability to build more precise signing logic based on transaction size.
Problem and solution
Problem: The product had no support for amount-based rules. Businesses could not set different approval conditions for different transaction sizes, so the same signing logic applied to both small and large payments.
Solution: I designed a limit engine that allows users to create and manage custom payment thresholds from scratch. This filled a significant gap and gave companies the ability to build more precise signing logic based on transaction size.
Problem and solution
Problem: The product had no support for amount-based rules. Businesses could not set different approval conditions for different transaction sizes, so the same signing logic applied to both small and large payments.
Solution: I designed a limit engine that allows users to create and manage custom payment thresholds from scratch. This filled a significant gap and gave companies the ability to build more precise signing logic based on transaction size.
Results after 6 months
After the redesign, rule creation became faster and more reliable. By separating complex decisions into clear blocks (operation, signers, accounts, conditions), the setup became easier to complete and less prone to errors, even as the product gained more flexibility and parameters.
Results after 6 months
After the redesign, rule creation became faster and more reliable. By separating complex decisions into clear blocks (operation, signers, accounts, conditions), the setup became easier to complete and less prone to errors, even as the product gained more flexibility and parameters.
Results after 6 months
After the redesign, rule creation became faster and more reliable. By separating complex decisions into clear blocks (operation, signers, accounts, conditions), the setup became easier to complete and less prone to errors, even as the product gained more flexibility and parameters.
Builder completion
Rule creation conversion (builder start → rule saved)
68%
Share of users who successfully save a rule on their first attempt
74%
Quality
Rules saved without validation errors
87%
VOC score (3.6 → 4.43)
4,43
Builder completion
Rule creation conversion (builder start → rule saved)
68%
Share of users who successfully save a rule on their first attempt
74%
Quality
Rules saved without validation errors
87%
VOC score (3.6 → 4.43)
4,43
Builder completion
Rule creation conversion (builder start → rule saved)
68%
Share of users who successfully save a rule on their first attempt
74%
Quality
Rules saved without validation errors
87%
VOC score (3.6 → 4.43)
4,43
scroll on top
scroll on top
scroll on top