Migrating a legacy admin console to the platform's current design system, while shipping its first dashboard, scoped to what the data could actually support on day one.
The admin console for managing user accounts, roles and authentication was still running on the platform's older design system, years after most other applications had migrated to the current one. It also had no dashboard at all. Every question, how many invitations went out, how many accounts were active, how authentication was split, meant digging through individual records with no single view of any of it.
I joined the project mid-way, inheriting an interface migration already underway from another designer, and took ownership of the dashboard feature end to end, a capability that didn't exist in the product before.
The dashboard shipped as an MVP, not its full intended shape.
Populating every planned metric would have needed new APIs that were one to two years out. Rather than wait, the first release shipped three widgets that existing data could already support: Invitation Status, User Account Summary and User Auth Info. The plan was to add one additional metric group at a time as backend support caught up, rather than blocking a real, if partial, dashboard behind a much longer data project.
{{ screen.desc }}
No hard metrics captured yet; the impact here is described qualitatively.
Real visibility for the first time, scoped honestly to what could actually be delivered immediately, rather than a dashboard that shipped once and stalled.
A clear, designed path to grow the dashboard as backend support caught up, instead of an all-or-nothing bet on a much longer data project.