Five systems, one way of deciding.
Government onboarding, an outpatient service, a team workspace, an enterprise reporting portal and the design system underneath a national product. Each one is written as an argument, not a gallery.
- Case 01Onboarding architectureAn institute isn't a user — so I removed the account entirely.
Registration asked every institution to set up three near-identical identities, then wait weeks for a human to verify them. Two-thirds got stuck and could only finish with the PhD Cell's help — and the most common support call was simply “has my verification gone through yet?”
Read the re-architecture - Case 02Service & system designEvery counter optimises itself. Nobody owns the sequence.
Parking is chaotic, wayfinding is confusing, waiting is long. Three complaints invite three features. They share one cause — nobody owns the sequence between counters, so the patient carries the plan in their head.
Read the system - Case 03Product UXPeople don't think in conversations. They think in files.
Teams on a chat-first collaboration product kept re-asking for files they had already been sent. Every shared document was buried in the thread it arrived in.
Explore the workspace - Case 04Enterprise workflowA report goes before Parliament. The data behind it was assembled by hand.
Public-sector enterprises file an annual return that ends up before Parliament. Finance teams built it in Excel, then retyped it into a portal — for three to four weeks, every year.
Read the rebuild - Case 05Design systemsA design system that makes accessibility impossible to skip.
Four modules of a public platform, designed by different teams — every one a fresh chance to drift a component at a time, and to relitigate every contrast decision in review.
See the system