06 — Case study
All workClient Portal
The client side of the same payment orchestration platform — where the businesses using it see their own payment activity and manage their own account. Add what they can do here: transactions, refunds, payouts, reports, keys and settings. Designed alongside the Command Centre so an operator and a client are looking at the same truth from two sides.
01
The problem
For the business
What was costing the business money or momentum, stated plainly.
For the people using it
What the people using it were actually struggling to do.
02
Constraints
What limited us
- Constraint that shaped the design
- Another real constraint
What we were aiming at
- Goal one
- Goal two
03
My scope
What I owned
- Designed and built both portals — the design and the front end are both mine
- Name the client-facing flows that were yours
- Decided how much of the operational picture a client should see, and in what language
What I didn’t
- Did not build the back end
- Anything else outside your scope
04
Research
What we found
- A finding that changed your mind
- A finding with a number behind it
Where it hurt
- Pain point
- Pain point
05
Decisions
Decision 01
The specific problem this decision solved
Chosen
What you shipped
Rejected, and why
The alternatives you considered and why each lost
Decision 02
The specific problem this decision solved
Chosen
What you shipped
Rejected, and why
The alternatives you considered and why each lost
06 — The work
02 screens
desktopScreen name — what it does, and the decision it reflects
07
What happened
Measured
- Measured change, with the before and after
Knock-on effects
- What it unlocked for the business or team
08
In hindsight
I’d do differently
- What you would do differently
What it taught me
- What this project taught you
Next — 07