Designing GovTech Products: How Do You Spec a System for Citizens Across Every Extreme of Age, Language, and Digital Literacy?
Product managers on government projects face one of the most diverse product challenges in the digital world: their target audience is every single citizen of the country. Unlike commercial products that get to pick a focused persona for themselves, a government system has to serve the 18-year-old filing their first application, the 80-year-old calling in to update their details, and the new immigrant still learning the language - all at the same level of quality, through the same interface.
On the government project, the central insight was that designing "for Everyone" is not the same as designing "for the Average User." Instead of building a generic experience that talks to everyone at a mediocre level, we broke the user experience down into layers. The base layer - the critical steps of the process - is as simple as possible, with clear, plain language, a clear progress indicator, and microcopy that explains every decision.
The deeper layers offer additional information, detailed explanations, and links to regulations. A citizen who needs the details can open them up, and a citizen who just wants to finish the process can finish fast. This approach, known as "Layered Complexity," makes it possible to serve diverse audiences without compromising any one of them.
For product managers working on GovTech products, public education, or public health systems, the insight is this: don't try to design for the "average" user. They don't exist. Design flexible layers that let every user tailor the experience to themselves, and respect the fact that your audience is an entire spectrum of human diversity.
Related articles

About
Making complicated into easy for users.
Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.