Mansoor Majidi
Case study 01ABANK · 2025
ABANK

From payroll file to final signature.

Designing multi-signatory banking for businesses—so complex signing rules, permissions, and next actions stay visible across mobile and desktop.

Final ABANK desktop signing protocol
Final ABANK mobile signing protocol
Role
Lead Product Designer
Scope
Corporate & Shared Banking
Platforms
Mobile app · Desktop web
Year
2025
01 · ContextThe problem

One payment could involve many people, permissions, and stages.

ABANK primarily served individual customers. The new corporate experience had to support how real businesses prepare, sign, and execute payments.

The challenge was making multiple stages, signatories, thresholds, sequence, permissions, rejection, editing, and failed destination recovery understandable.

01

Prepare

An accountant or finance teammate creates the payment order.

02

Approve

The order moves through the company’s signing stages and thresholds.

03

Execute

After the required signatures, the payer completes the transfer.

02 · EvidenceResearch and testing

We tested the logic with the people who prepare the orders.

We interviewed payment order preparers from three companies, reviewed Kilid, and tested the primary prototype flows with the same three participants.

  • Long destination lists made manual entry slow and risky.
  • Signatories needed a notification when their turn arrived.
  • The next responsible actor was not always clear.
  • Failed destinations needed visible tracking and retry.
  • The priority-based signing model remained difficult to understand.
Bank Ayandeh Kilid high, medium, and low signing priority interface
03 · IterationPriority → Stage

More explanation could not fix the mental model.

The intermediate design separated configuration and display, but users still had to reconstruct the signing structure in their heads.

Initial priority-based model
Initial ABANK priority-based signing protocol screen
Design decision

When a mental model itself is confusing, don’t just add instructions; redesign the interaction so the logic becomes visible.

04 · Final modelMobile + Desktop

One product logic, adapted to both platforms.

Each group became one approval stage. Signatories became draggable cards and the minimum required signatures stayed visible inside every stage.

Connected mobile and desktop screens were reviewed side by side so terminology, statuses, thresholds, and next actions remained aligned.

05 · My roleHands-on + Leadership

I designed the core interaction and aligned product logic across platforms.

Hands-on

Final signing protocol model and flow, protocol UI, corporate home widget, payment order detail, and signatories bottom sheet.

Leadership

Reviewed connected mobile and web screens side by side to align terminology, statuses, logic, and next actions.

The revised model was retested, received positive qualitative feedback, and was handed off. The product was paused before launch.

Back to selected work