Skip to main content
Meytal Dahan
Back to insights

Personalization That Survives Public Scrutiny

When CEOs hear personalization, they picture a consumer feed that learns you and sells better. In a public service, that framing is a liability. Citizens didn't opt into being profiled, the data is often sensitive by law, and any whiff of differential treatment invites fairness questions you do not want to answer publicly. So I reframe personalization here as relevance, not prediction. The goal isn't a model that guesses what you want — it's a service that shows each person only what actually applies to them. That's mostly driven by their situation and the answers they give, not by behavioral surveillance: a parent sees the parent path, a small business sees the business path, someone who already submitted sees status, not a fresh form. This is the layered-complexity principle again — a clean core for everyone, with the right depth surfaced for the right person. Done this way, personalization cuts confusion and call volume, because people stop wading through options that were never meant for them. And it stays defensible: every tailoring decision is explainable and consistent, never a black box. For a CEO, that's the version that delivers the efficiency upside of personalization without the reputational downside of the consumer playbook.

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
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
Government & Public Sector
Product ManagersFirst-Run Onboarding

The First Run Is Where Public Trust Is Won or Lost

Consumer onboarding sells value. Govtech onboarding has a harder job: convince a wary first-timer they're in the right place and can finish without calling anyone. So I skip the product tour — they came to do one thing, not learn a tool. Tell them what they'll need, the steps, the time, then get out of the way. The metric is completion on first attempt. If people finish without help, it worked — quietly.

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.