Skip to main content
Meytal Dahan
Back to insights

Digital Transformation in the Public Sector: How Does Good Design Reduce the Load on Service Centers?

CEOs of public bodies - government ministries, local authorities, public infrastructure companies - face a fundamental business-and-public challenge: their service centers are overloaded. Citizens call in, wait on hold for hours, and often need a simple action that could have been completed independently in a few clicks. Every call to the center costs the organization in operational expenses and hurts citizen satisfaction. On the government project, the strategy was clear: digitize processes to create Self-Service for citizens. Good user-experience design is critical here. If the digital system is clunky or unclear, citizens will give up on it and go back to the call center. If it's clear and efficient, they'll finish the action in minutes and save both themselves and the center valuable time. The numbers speak for themselves. An improvement in the user experience of a government system translates into a significant drop in calls to the service center. Every percentage point of decline in calls translates into millions of shekels saved in operational costs, and into a significant improvement in citizen-satisfaction metrics. For CEOs of public bodies, the insight is this: investing in digital user-experience design isn't a "pretty face" - it's an operational and budgetary lever. The return on investing in a senior product designer for a government project shows up directly in reduced call-center costs and an improved organizational reputation with the public.

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.