Skip to main content
Meytal Dahan
Back to insights

Typography Is How Citizens Find the One Thing They Came For

Most people land on a public service page stressed, on a phone, mid-task — renewing a license, checking a benefit, filing something before a deadline. As a PM, your conversion metric is really comprehension: did they find and complete the one action they came for? Typography and visual hierarchy are the levers that decide that, far more than copy length. I design around a single, unmistakable primary path. The core task sits at the top of the hierarchy with generous size and weight; everything else — eligibility caveats, edge cases, legal detail — recedes into a calmer, optional layer. That's Layered Complexity expressed in type: a simple surface, with depth available to those who need it. This also serves accessibility directly. Real heading structures, not just big bold text, let screen-reader users navigate by hierarchy, and dynamic type scaling means low-vision users aren't punished with broken layouts. The practical PM win is call-center load. When the next step is visually obvious, fewer citizens give up and phone in. Clear hierarchy is cheaper than a support queue — and it's the most measurable thing typography buys you.

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.