Skip to main content
Meytal Dahan
Back to insights

Why a Trust-First Portal Says No to Flashy AI

Ministry of Defense — A marketing platform
The reflex right now is to put AI somewhere visible in every product. On the Ministry of Defense communications portal, the more disciplined strategy was to keep it out of the citizen-facing experience entirely. The brief was trust: a public institution projecting authority and seriousness to citizens, partners and press. A chatbot speaking on behalf of a ministry, or AI-generated answers presented as official communication, is a trust liability, not a feature - the failure mode isn't a bad UX, it's an institution appearing to say something it didn't. So my AI strategy here was about where it belongs: behind the curtain, in how the work gets made, not in front of the citizen as a gimmick. Generated drafts and explorations can accelerate the design and content process, but the public surface stays deliberate, edited and accountable. For founders, that's the harder strategic call. The pressure is to show AI to prove you're modern. But strategy is as much about what you withhold as what you ship. Match the technology to the trust the product is built on - and when the entire product is trust, the most forward-thinking move can be keeping AI invisible.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Ministry of Defense
Engineering LeadersR&D Collaboration

Designing a public face for serious engineering

The MoD public portal tells citizens about real strategic and security advancements - so the collaboration that mattered most was with the technical side that owns the substance. My constraint as a designer: present serious work credibly, never overclaim it. R&D partners weren't a sign-off gate; they were the source of truth for what 'forward-thinking' could honestly say. The win wasn't agreed pixels - it was a shared standard for representing rigorous work publicly without distortion. Fidelity to the truth is a design requirement, not just an engineering one.

Read
Ministry of Defense
Product ManagersUser Research

Researching a portal that speaks to a whole nation

On the Israel MoD public portal, the research question wasn't 'who is the user' - it was 'who are ALL of them, and where do their needs collide.' Citizens, partners, press, one set of pages. The instinct to pick one persona and optimize would have broken trust with the others. We researched by intent, not demographics. The real deliverable wasn't insights - it was a model that let the roadmap say no with confidence. Research earns its keep when it makes prioritization defensible, not just informed.

Read
Ministry of Defense
Project ManagersDelivery & Handoff to Development

A handoff built to survive the ministry's scrutiny

Handoff on the MoD public portal had high stakes: a public-facing government record where accessibility is an expectation, not a bonus. My PMO-minded goal was simple - kill ambiguity before it becomes rework. Not a Figma dump over the wall, but a sequenced package: responsive system, reusable components, documented states, WCAG-minded specs. Foundations first, so build starts on solid ground. A good handoff doesn't just transfer files - it transfers intent. That's what keeps a high-visibility delivery on schedule.

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.