Partners Let's talk

Back to products

Government

Ministry of Defense

A public-facing communications portal for Israel's Ministry of Defense - the record of strategic milestones, framed to project authority, trust and forward-thinking leadership.

Type

B2C

Role

Product Designer

Scope

Marketing site UX
Visual system
Responsive web

The Ministry of Defense portal is the public face of the ministry's communications - the place its achievements, milestones and security advancements get told to citizens, partners and press. The design brief was a tone problem first and a content problem second: project authority and seriousness without slipping into bureaucratic dryness, signal innovation without losing institutional weight.

01 · Section

The brief

A central hub for the ministry to communicate strategic milestones and national-security advancements to a broad public audience. The interface had to feel authoritative, professional and forward-thinking - a visual language that read as both gravity and momentum. Government communications platforms tend to drift toward one of two failures: austere to the point of unreadable, or marketing-bright to the point of untrustworthy. The portal had to sit deliberately between those - a site that looks like a ministry that takes itself, and its audience, seriously.

Next product

Designed the Risk Engine - the platform's most complex surface, where all system logic and high-risk thresholds are defined - into a visual decision system compliance teams could actually own.

Insights

More on Ministry of Defense.

View all insights

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.

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.

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.

Ministry of Defense

CEOsPersonalization & Tailored Models

When the Right Move Is One Voice for Everyone

Personalization is sold as an automatic win. On the Ministry of Defense public portal, one consistent voice for everyone was the stronger play. A government portal that silently reshapes itself per visitor trades credibility for cleverness. I designed clear paths for citizens, partners and press to find what's relevant - segmented audiences, but the same truth for all of them. Personalization pays off when relevance is the bottleneck. When trust is the product, consistency wins.

Ministry of Defense

Product ManagersTypography & Visual Hierarchy

Typography as the Tone of Voice

The Ministry of Defense portal brief was a tone problem first: authority without dryness, leadership without marketing-brightness. Typography carried most of that load. For PMs, hierarchy is really prioritization made visible — type size and contrast decide what a citizen reads first, no explanation needed. And it had to hold in Hebrew and on a phone. Good hierarchy tells people what matters before they read a single word.

Ministry of Defense

FoundersAI Strategy in the Product

Why a Trust-First Portal Says No to Flashy AI

Everyone wants AI somewhere visible in the product. On the Ministry of Defense public portal, the smarter strategy was to keep it out of the citizen-facing surface entirely. When a product's whole job is institutional trust, an AI speaking on a ministry's behalf isn't a feature - it's a liability. Use it behind the curtain to make the work; keep the public surface deliberate and accountable. Strategy is as much what you withhold as what you ship.

Ministry of Defense

Why Do Private Companies Specifically Benefit From Working With Experts Who Have Worked in the Defense System?

CEOs, looking for a product designer for critical projects? Look for someone who has already passed the Stress Test of defense organizations. Experience designing systems for the Ministry of Defense means methodical rigor, precise documentation, and meeting demanding standards. You're not paying for an "opportunity to grow" — you're paying for deliverables from day one.

Ministry of Defense

Product Managers

Designing Command and Control Systems: How Do You Balance Volume of Information Against Speed of Decision?

Product managers in command and control systems, your users don't need "All Information All The Time" — they need "Right Information Right Now." Working with the Ministry of Defense, we built a Contextual UI that shifts dynamically between a calm state and an alert state. Information overload = slow decisions. Contextual design = saving critical seconds.

Ministry of Defense

Engineering LeadersInternationalization (i18n)

Designing a Portal That Doesn't Assume One Direction

For an Israeli government portal, i18n isn't just a translation table - it's a direction problem. The Ministry of Defense site had to hold its institutional authority in Hebrew's right-to-left layout, not just the left-to-right conventions designers default to. So I described spacing and alignment in logical start/end terms rather than fixed left/right, so the visual system doesn't quietly break when direction flips. The lesson for any R&D team: make direction-awareness a property of the design system from the first screen, because retrofitting it later is expensive and visible.

Ministry of Defense

Project Managers

Managing a Design Project in a Classified Environment: Working Within Information Security Constraints Without Slowing the Pace

Project managers in classified environments, information security constraints aren't a "problem" — they're a structure for the work. In projects for the Ministry of Defense, we built a hybrid methodology: intensive work in the classified environment at key points, and independent work on generic elements. Detailed upfront planning = saving months down the road.

Ministry of Defense

Studio & Agency

Your Studio Won a Defense Tender? Why It's Worth Bringing In an External Expert Who Has Already Worked in This Environment

Studio leaders, won a defense tender and not sure how to approach the classified project? Don't give up on this market — bring in an expert. My experience designing systems for the Ministry of Defense lets me start functioning from day one, and gives your studio a professional "seal of approval" in front of the client.

Ministry of Defense

Product ManagersFirst-Run Onboarding

The First Thirty Seconds of a Government Portal

On the Ministry of Defense public portal, onboarding wasn't a tour or a sign-up — most people arrive once and leave. So 'first run' was really the first thirty seconds: feel the authority, find the path, no friction. There's no second screen to fix a weak first one. PMs — when users land cold, your onboarding is just whatever the homepage communicates instantly. Earn trust and orientation there, because for many users there is no later.

Ministry of Defense

CEOsSpecific Feature ROI

Where a Government Portal's ROI Actually Lives

On the Ministry of Defense public portal, ROI wasn't measured in revenue - it was measured in trust. Every feature I argued for had to change how citizens and press read the institution. The milestone storytelling earned its place. Decorative motion didn't. When you can't count conversions, the discipline gets harder, not easier: you defend each feature by the perception it moves. On a public-facing government site, perception is the product.

Ministry of Defense

FoundersFrom MVP to Full Version

An MVP That Couldn't Look Like an MVP

Some MVPs aren't allowed to look like MVPs. The Ministry of Defense public portal had to project institutional authority on day one - 'ship rough, polish later' would have read as untrustworthy, and trust was the whole brief. So we shrank the surface, not the quality: fewer pages, full-fidelity visual system from launch. The design system made every later page inherit that weight for free. Decide which axis you're allowed to compromise on before you start building.

Ministry of Defense

Product ManagersMicro-interactions & Animation

Motion That Signals Composure

A Ministry of Defense portal could've been stone-static. But the brief wanted forward-thinking leadership — and motion signals that, if it's disciplined. Every animation is a tiny promise about how the institution behaves. So: calm hover states, purposeful transitions, media that reveals with intent. No springy bounce, no jank. Composed motion reads as competent AND current. PMs — treat motion as a tone instrument, not decoration.

Ministry of Defense

Engineering Leaders

Working Under Classification With Communication Gaps: How Do You Design Systems in Environments Where Not Everything Can Be Shown?

Engineering leaders in classified systems, the secret is to work with "Abstracted Information." Working with the Ministry of Defense, we built a methodology where the technical team describes needs at the concept level, and the designer creates generic UI that fits any content. The result: meeting security requirements + a modular, flexible product that functions in any scenario.

Ministry of Defense

Engineering LeadersDesign Systems

A Design System That Carries Institutional Weight

On the Ministry of Defense public portal, the design system wasn't about velocity first — it was about credibility. Inconsistent UI on a government communications site quietly undermines the authority it's meant to project. Tokenized type, color and spacing meant every new milestone page inherited institutional weight for free. The real win for engineering: less drift, fewer judgment calls, easier handovers. A small, well-named system beats a sprawling one nobody trusts.

Ministry of Defense

Project ManagersDocumentation & Organizational Handoff

Documentation so the portal outlives the project

A government portal is never 'finished' - the MoD keeps publishing milestones long after a project phase ends. So the real test of the work isn't launch day; it's whether their own teams can extend it without eroding tone, accessibility, or the visual system. From a PMO view, that's continuity risk - and documentation is how you retire it. I treated the design system as a living reference: components, rules, and the rationale behind the tone, so future updates inherit decisions instead of reinventing them. Good documentation makes the right decision the easy one for whoever comes next.

Ministry of Defense

Engineering LeadersProject-Specific Data Visualization

Visualizing Milestones the Public Can Trust

On the Ministry of Defense public portal, the moments a milestone or timeline gets visualized are the moments credibility is most at stake. Not a real-time dashboard — communication. So the engineering constraints led: accessible (not color-alone), legible on mobile, and graceful degradation so a failed chart never blanks out a government page. Clarity over flourish. On a public-record site, accuracy and accessibility ARE the features.

Ministry of Defense

FoundersColor & Psychology

The Color of Trust

Building the Ministry of Defense public portal, color had one job: project trust and authority without going stale-grey or marketing-bright. The move was restraint — deep institutional tones, accent used sparingly so the few highlights feel deliberate. Founders: color isn't your logo, it's the emotional posture of the whole product. Pick the feeling first, then earn it with discipline, not volume. And on a public-record site, contrast is part of the trust contract.

Ministry of Defense

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

Founders in DefenseTech, your market is the hardest in the world to break into. Defense organizations reject excellent products because of a UI that doesn't meet their standards. My experience designing systems for the Ministry of Defense ensures your product conveys seriousness in every corner. Don't lose a contract over unnecessary startup-iness in your design.

Ministry of Defense

Engineering LeadersIndustry-Specific Accessibility

Accessibility Is the Baseline for a Public Institution

On a government portal, accessibility isn't best practice - it's the floor. The Ministry of Defense site is public by definition, so it has to work for every citizen: screen readers, keyboard, high contrast. The trap is that the easy version of 'looks authoritative' - low-contrast greys, motion-heavy reveals - is exactly what fails WCAG and fails real users. I built contrast, focus states and reduced-motion into the component library itself. The most credible interface has to also be the most usable one.

Ministry of Defense

Project ManagersUsability Testing

Testing trust, not just task completion

Usability testing on the MoD public portal had an unusual pass/fail bar: not just 'can they complete the task,' but 'do they trust what they're reading.' Tone was a testable risk, not a taste debate. As anyone running delivery knows, ambiguity is schedule risk. So we ran fixed rounds - test, triage by severity, fix, retest - and turned 'is it good enough?' into a closed, evidenced list. Testing protects the timeline most when it converts subjective doubt into a finite backlog.