National public services
I take many separate government platforms and turn them into one simple system that has to work for everyone in the country.
The problem
Government services grow one portal at a time. A citizen ends up facing dozens of different sites, each with its own login, its own layout, its own idea of what matters. For someone on an old phone, on a weak signal, using the internet for the first time, that sprawl is not an inconvenience. It is the difference between getting help and giving up.
What I did
I unify sprawling public-sector platforms into single, coherent systems, and build the shared design and component foundations used across national e-governance services, so common features are built once and reused everywhere. The client stays unnamed because the work requires it. The named, verifiable Tata Neu work is why you can believe this.
The hardest part
The hard part is never can we design it. It is getting many owners to agree that the user's priority outranks each team's priority. Every organisation wants its section first, framed its way. Unifying them means telling each one that its corner is changing for the good of the person actually using it. That fight is political, not visual, and it is most of the job.
What I design first
The error state. Everyone designs the happy path. I start with what the screen says when something breaks on a slow connection, because on a public service that is the moment a citizen decides whether to trust it or walk away. Built for old phones, low literacy and absolute trust.