05 — Case study
All workCommand Centre
The operator side of a payment orchestration platform — where payment traffic is watched and controlled rather than transacted. Add what is actually configured and monitored here: routing between providers, failures and retries, reconciliation, settlement. Its counterpart is the Client Portal, and the two are designed as one system.
01
The problem
For the business
What was wrong before — payments spread across providers with no single place to see or steer them.
For the people using it
What the people using it were actually struggling to do.
02
Constraints
What limited us
- A real constraint — provider APIs, latency, what the platform could report on
What we were aiming at
- Goal one
- Goal two
03
My scope
What I owned
- Designed and built both portals — the only designer on the platform, and the front end is mine too
- Name the command-centre areas that were yours: routing, monitoring, reconciliation
- Kept the operator and client views consistent, since they describe the same payments
What I didn’t
- Did not build the back end — the payment engine and provider integrations are engineering’s
- 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 — 06