Skip to main content
Meytal Dahan
Back to insights

A DefenseTech Startup: How Do You Design a Product That Passes the Acceptance Rules of Defense Organizations?

Ministry of DefenseFoundersDefenseTech / Government
Ministry of Defense — A marketing platform
Founders in DefenseTech and Critical Infrastructure face a unique challenge: their target market is the hardest in the world to break into. Defense organizations, power companies, transportation systems — they all demand lengthy approval processes, high technical standards, and information security requirements that don't exist in other industries. A founder who arrives with an excellent product but a UI that doesn't meet those standards — gets rejected before anyone even looks at the technology. In my work with the Ministry of Defense, I learned exactly what those standards are and what these organizations look for in product design. They look for: methodical rigor (every design decision is documented), consistency (the same component behaves the same way everywhere), operational accessibility (even a user with an unusual cognitive shift can operate the system intuitively), and visual credibility (the design conveys seriousness, not "startup-iness"). For founders launching a DefenseTech startup or trying to break into this market, my experience is a powerful competitive tool. I deeply understand the visual communication language of these organizations, and I know how to design a product that not only works technically, but signals in every corner "we understand your world." That's the difference between a startup that gets a first meeting and a startup that wins a contract.

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.