Skip to main content
Meytal Dahan
Back to insights

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.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Government & Public Sector
FoundersFrom MVP to Full Version

Why GovTech MVPs Don't Look Like Startup MVPs

Founders are taught to ship the scrappiest MVP and iterate in public. In govtech, that instinct can sink you. A citizen service that looks like a beta — or breaks for a screen reader user — loses trust you may never win back. So I redefine 'minimum': not a thin slice of everything, but one complete, accessible, end-to-end path a real person can finish with dignity. Narrow the use cases brutally. Never narrow the quality. Then grow in concentric circles — keep the simple core intact, layer depth around it. Your launch version should be something you'd defend in a public hearing. That's the bar.

Read
Government & Public Sector
CEOsPersonalization & Tailored Models

Personalization That Survives Public Scrutiny

When CEOs hear 'personalization' they picture a consumer feed that learns you. In a public service, that's a liability — citizens didn't opt into being profiled, and any hint of differential treatment invites fairness questions you don't want to answer in public. So I reframe it as relevance, not prediction. Not a model guessing what you want — a service showing each person only what actually applies to them, driven by their situation, not surveillance. A parent sees the parent path. Someone who already applied sees status, not a fresh form. That cuts confusion and call volume, and every tailoring decision stays explainable. The efficiency of personalization, without the consumer-playbook downside.

Read
Government & Public Sector
Project ManagersUsability Testing

Usability Testing as Schedule Insurance for Public Services

Usability testing isn't a threat to your timeline — it's insurance on it. The costly defects aren't the ones found in a session; they're the ones found after launch when the fix means re-planning everyone's quarter. Test early, test on the worst device, and label every finding by whether it blocks the core task. A PMO can schedule around that. It can't schedule around surprises.

Read
Meytal Dahan

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.