Quorra · Shipped 2026
Order processing with zero room for error
- Role
- Product Designer
- Timeline
- 2026
- Status
- Shipped 2026
Scope
- Flow Optimization
- Screen Consolidation
- Market Maker Mode
- Wallets
- Design System
Quorra is a stand-in name, and every screen here is a concept recreation. The company and the shipped design stay under NDA, so the screens were built from scratch for the portfolio, with invented names, people and values.
Overview
An order queue where funds move, and mistakes don’t get a second try.
Quorra is a crypto exchanger running regulated flows, KYC and AML among them. Its admin panel is an internal tool with 60+ users, and at its core is the finance team that processes exchange orders: scan the order, gather every relevant piece of data, process it and send the funds to the end user.
Funds move, so the work has zero tolerance for error. That makes the panel a different product from the consumer app, with a different mental model and a different measure of success.
Every decision mine
No studio on this project: product design was mine end to end.
A view for every order
A dense table replaced by a space built around the order in hand.
Shipped step by step
Rolled out in stages instead of one big switch.
Problem
A dense table, and orders that took too long.
Orders were worked from a dense table. There was no space to look at a single order on its own, and the information inside it had no clear hierarchy, so finding the right data took time.
Watching the finance team at work showed where that time went, and the product metric confirmed it: time to completion was long.
Approach
A new way to handle an order, introduced step by step.
I redesigned how an order gets handled. Instead of a row in a table, each order now opens in its own view, with its information regrouped so the hierarchy finally makes sense. It shipped in stages rather than as one big redesign, for two reasons.
The team knew the old view
They were used to it, and switching everything at once would have slowed them down.
Sensitive sections came first
Each one was understood before it changed, so the finance team made no mistakes along the way.
Order processing
One order, one screen: client, payout, incoming transfer and checks together
Confirm payout
Speed everywhere else, one deliberate pause where funds leave
Design decisions
The table they asked for, and the order view I pushed for instead.
The finance team’s first request was a table, so that’s where I started. Working through it showed the limit: a better table still left no room for a single order and no clear hierarchy inside it. A dedicated order view solved both, so I dropped the table and pushed back on the request.
From table to order view
A dedicated space for the order in hand, not a row among dozens.
A hierarchy that reads
Information regrouped and reordered, so the next thing to check is where you look.
Pushback
The finance team wasn’t happy with the new core flow.
The redesign changed the core flow, the part of the panel the team relied on most, and they pushed back on it. I defended it from the UX side and proposed a test instead of a debate: run it with a group of users for a while, then decide.
A month of metrics settled it.
Outcome
Orders completed about 35% faster within a month.
Time to completion covers an order from start to finish: taken into work, every check done, funds sent correctly. Over the first month it came down by about 35% against the pre-launch baseline, measured through the product metric and backed by feedback from the finance team.
~35% faster completion
Against the pre-launch baseline, from taking an order into work to sending the funds.
Fewer complaints
Qualitative: fewer complaints from the finance team about the panel.
Tuned after launch
Small changes made a few sections easier to spot.
