Skip to main content
Meytal Dahan
Back to insights

Why Public-Sector Color Has to Feel Boring on Purpose

Founders instinctively want a brand that pops — a signature gradient, an energetic palette that signals momentum. In govtech, that instinct is a liability. Citizens don't choose a public service; they're often required to use it, sometimes warily. Color here does a different psychological job: it has to earn trust by feeling calm, established, and impartial. A palette that looks like a consumer startup quietly tells people 'this might not be official, this might not be safe to enter my data into.' So I lean into restraint — sober, institutional tones, with saturated color reserved almost entirely for meaning rather than decoration. Status colors do heavy lifting: success, warning, error, and 'action required' must be instantly legible and never the only signal, because color-blind users and WCAG both demand a text or icon backup. For a founder, the reframe is this: maturity is the brand. A service that feels steady survives public scrutiny, press, and a skeptical citizen's first impression. Excitement isn't the goal — confidence is. The best compliment a public service can get is that nobody thought twice before trusting it.

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.