Steady’s management portal is the internal tool used by the case workers and programme managers who review income reports submitted through the Income Passport. When a gig worker submits their income verification, it enters a queue — and someone on the Steady team has to review it, validate it, and process it.
The existing process was fragmented. Case workers were navigating between multiple screens and tools to complete what should have been a straightforward review workflow. The full portal was redesigned.
The portal had to serve two roles with genuinely different needs — and getting the balance right was the central design challenge:
Case workers review individual income reports. Their primary need is an efficient queue they can move through quickly and accurately — open a report, review the income data, validate it, mark it complete or flag it for follow-up. Speed and clarity matter because they’re doing this repeatedly throughout the day.
Programme managers need aggregate visibility — not the detail of individual reports, but an overview of how the team is performing. How many reports are pending, how many processed, where are bottlenecks forming, which case workers need support. They’re managing throughput rather than doing the reviews themselves.
The tension: the same interface needs to support both heads-down individual review work and the oversight perspective of a manager. Interviews were run with both roles before designing anything, and the personas that came out shaped every layout decision.
The dashboard serves both user types through customisation — case workers configure it to show their personal queue and pending items; managers configure it to show team throughput, queue depth, and workload distribution. Neither has to work around the other’s view.
The dashboard surfaces:
The income report format case workers review was restructured around how they actually move through a review — not how the data was stored in the system:
The portal serves multiple programmes with different data access requirements. A role management system was designed, giving administrators control over which case workers access which programme’s reports, what level of data each user can see, and manager vs. case worker permissions within each programme.
This was an MVP engagement. The complete design, Figma handoff documentation, and design system were delivered for the development team to build from. The product was at an early stage, and the engagement ended before it was deployed to users. The design gave the engineering team a well-documented, complete foundation — rather than the common alternative where development starts from sketches and design decisions get made during implementation.
Projects
Six months across the full product — student, teacher and admin flows, adaptive testing, research experiments, and a broader UX restructure.
Redesigned the full interface to cover small package, freight, and international shipping, plus a new standalone mode and design system.
Redesigned the platform twice across four user types and built the design system from scratch as the only embedded design resource on the account.
Designed the question bank, exam builder, Crew Evaluation Test, proctoring system, course reporting, and student test interface.
Joined before any UX decisions were made and designed the complete product — form builder, workflow engine, API library, brand, and design system.
Audited the full application and redesigned the verification flow, report submission, deposit loading, and error handling throughout.
Your senior AI Product designers think about the products strategically, catching issues before they reach you, and making sure the work holds up under scrutiny.
Flexible subscription. Start in 48h.
✦ Start with a conversation ✦
20 minutes, no pitch. I'll tell you honestly if I'm the right fit for what you're building.