Skip to main content
Meytal Dahan
Back to insights

The First Run Is Where Public Trust Is Won or Lost

In consumer products, onboarding sells value. In govtech, the first run does something harder: it has to convince a wary, often first-time user that they're in the right place, that this is official, and that they can finish the task without phoning anyone. As a PM, I treat the first session as the moment that determines both completion rate and downstream call-center load. So I resist the tutorial reflex. A multi-step product tour assumes engagement the user didn't sign up for — they came to do one thing. Instead I design onboarding as the simplest viable core path: tell them plainly what they'll need (documents, references), what the steps are, and roughly how long it takes, then get out of the way. Layered Complexity carries the rest — optional help and detail sit one tap away for the people who need them, invisible to those who don't. Accessibility shapes this too: progress and instructions must work for screen readers, low digital literacy, and many languages, because the first run is exactly where excluded users abandon. The metric I watch is task completion on first attempt. If people finish without help, the onboarding worked — quietly, which is the point.

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.