Picture a 19-year-old Sailor. Let’s call her Seaman Smith.

Smith grew up as a digital native. Before she even walked into a Navy recruiting station, she lived in an ecosystem where information was instantaneous, interfaces were intuitive, and software worked seamlessly across devices. If an app on her phone took more than three seconds to load, she deleted it. If a website required a manual read of a 40-page standard operating procedure (SOP) just to figure out how to reset a password, she abandoned it.
Then, she graduates from boot camp, is handed a Common Access Card (CAC), and arrives at her first command on a guided-missile destroyer. She sits down at a computer to do something incredibly basic—perhaps submit a leave request, check her training requirements, or review her pay stub.
She inserts the CAC. She types her PIN. She waits. The page times out. She refreshes. She clicks “I Agree” on a DoD warning banner. She selects her email certificate instead of her ID certificate by mistake. The portal crashes. She starts over. Twenty minutes later, she finally accesses the system, only to find an interface that looks like it was designed in 1998, filled with dead links and incomprehensible acronyms.
To accomplish a single morning of administrative and operational tasks, Seaman Smith will have to log into MyNavy Portal, NSIPS, FLTMPS, NFAAS, DTS, eLeave, and half a dozen other siloed, disjointed websites.
We are killing our Sailors with a thousand portals.
For too long, the Department of the Navy has treated User Experience (UX) as a luxury—a nice-to-have feature that gets cut the moment a program runs over budget. But in a fast-paced, high-stakes military environment, poor UX is not an inconvenience; it is a massive, systemic readiness failure. It drains millions of man-hours, destroys morale, and imposes a heavy cognitive load on a workforce that should be focused on warfighting, not fighting their computers.
In an age where we seem to love to vex about storage, compute, and other real capacity issues, we have to stop admiring the problem. We must fundamentally tear down the fragmented Navy portal landscape and build an experience for Sailors across their entire digital battle rhythm that actually makes sense.
Why Do We Have So Many Portals?
To solve the portal problem, we first have to understand why the Navy’s digital landscape looks like a chaotic strip mall rather than a unified digital headquarters.
The root cause is not a lack of technical talent; it is the bureaucratic architecture of our funding and acquisition systems. In the Navy, software is rarely bought as an enterprise. It is bought by individual program offices to solve individual problems.
When OPNAV N2/N6 identifies a requirement for a new maintenance tracking system, they fund a specific program office to build it. That office, often working through NAVWAR for technical authority and PEO Digital for acquisition, goes out and hires a defense contractor. That contractor builds a bespoke database, wraps it in a proprietary user interface, and stands it up on its own unique web address.
Meanwhile, a completely different program office is doing the exact same thing for a medical readiness tracking system. Because these program offices have different budgets, different leadership, and different timelines, they have absolutely no incentive to collaborate.
The result? The burden of integration is pushed entirely onto the end user. We force the 19-year-old Sailor to act as the “human API,” manually transcribing data from one disconnected portal to another, navigating a maze of wildly different interfaces, authentication protocols, and design languages.
We do not have an enterprise IT architecture; we have a collection of independent software fiefdoms, and the Sailor is forced to pay the toll at every single border.
The Edge Computing Reality: UX When the Network Goes Dark
Fixing the portal problem in a Pentagon cubicle with a fiber-optic connection is hard enough. But out on the deckplates, we face an entirely different beast: the physical reality of the contested edge.
We are preparing for a fight in a DDIL environment—Denied, Degraded, Intermittent, and Limited use of the electromagnetic spectrum. When a carrier strike group operates under heavy electromagnetic emission control (EMCON) or faces active jamming from a near-peer adversary, that fat SATCOM pipe disappears.
Right now, our monolithic web portals are built with a fatal flaw: they assume a persistent, high-bandwidth connection back to a server farm in Norfolk or a centralized cloud. When a Sailor on a destroyer in the Philippine Sea tries to load a training portal or a logistics database, and the satellite link is choked to a few kilobits per second, the portal doesn’t just load slowly—it breaks. The authentication times out. The session drops. The UX goes from “frustrating” to “non-existent.”
We cannot build a modern UX that relies exclusively on a persistent umbilical cord to the shore. If we are serious about supporting the defense end user, we must embrace edge computing as a fundamental UX requirement. This means shifting how we engineer software for the warfighter:
- Offline-First Architecture. Think about how modern civilian applications work. You can type a document or draft an email on an airplane without Wi-Fi, and the second you land and reconnect, the app silently syncs your data in the background. Navy software must do the same. A Sailor should be able to fill out a maintenance form, digitally sign it, and hit “submit” even if the ship is completely disconnected. The local shipboard server (the edge) holds that data and automatically pushes it to the shore enterprise the moment connectivity is restored. The Sailor should never see a “Page Not Found” error.
- Microservices at the Tactical Edge. Instead of relying on heavy web applications hosted thousands of miles away, NAVWAR must prioritize networks that push lightweight, containerized microservices down to the ship level. A platform needs enough localized compute power to run its own essential applications natively, completely independent of the broader internet.
- Bandwidth Triage and “Low-Bandwidth Mode.” UX in a DDIL environment means designing interfaces that understand their environment. PEO Digital should require software that intelligently recognizes a degraded connection and automatically switches to a “low-bandwidth mode.” It should strip out heavy graphics, unnecessary CSS, and bloated code, serving only raw text, critical data fields, and essential forms to the user.
If a piece of software requires a gigabit connection just to load the login screen, it is worse than useless in a contested spectrum—it is a combat liability. True user experience means building tools that fight through the friction of the real world, empowering the Sailor whether they have a 5G connection or are operating in total electromagnetic silence.
Specific Ways to Change
We cannot train our way out of bad design, and we cannot mandate our way out of a fractured architecture. OPNAV, NAVWAR, and PEO Digital must force a structural shift in how we acquire and deploy software. Here are the specific actions we must take right now.
1. Mandate API-First, Not Portal-First
We need to stop buying monolithic web portals. OPNAV N2/N6 must mandate that every single piece of software the Navy buys or builds must be API-first (Application Programming Interface).
An API allows different software programs to talk to each other silently in the background. If a vendor builds a new training database, they should not be allowed to build a standalone portal for it. They should build the database and provide secure APIs so that the data can be pulled into a single, unified “pane of glass”—a centralized digital workspace where a Sailor logs in once and sees all their necessary actions, from maintenance tags to pay discrepancies, in one feed. PEO Digital must act as the gatekeeper here: if a vendor’s software cannot seamlessly integrate into a unified frontend via APIs, the Navy shouldn’t buy it.
2. Implement True Identity, Credential, and Access Management (ICAM)
The CAC is a critical piece of public key infrastructure (PKI), but relying on it for every single user action across fifty different websites is causing authentication fatigue.
PEO Digital must aggressively expand modern ICAM solutions. We need a true Single Sign-On (SSO) ecosystem. When a Sailor logs into their workstation at 0700, that authentication should securely token-ize their identity for their entire session. They should be able to seamlessly jump from their email to an unclassified intelligence database to an HR system without ever having to re-select a certificate or enter a PIN again during that session. Commercial industry solved this a decade ago with providers like Okta and Ping Identity. We must adapt these commercial models to our security enclaves.
3. Make UX a Key Performance Parameter (KPP)
In defense acquisition, a Key Performance Parameter (KPP) is a metric that a system must meet to be fielded. If a ship doesn’t meet its speed KPP, the Navy doesn’t buy it. OPNAV N2/N6 needs to make User Experience a KPP for all software.
We must require vendors to utilize Human-Centered Design (HCD). Before a line of code is written, developers should be sitting on the deckplates with actual Sailors, observing their workflows. Software must pass rigorous, timed usability tests by lay-users (not engineers). If a Petty Officer cannot figure out how to use a new supply-ordering tool within five minutes without consulting a manual, the software fails its KPP and is sent back to the vendor.
4. Adopt a Unified Design System
Why does an Air Force website look different from a Navy website, which looks different from an Army website? We are reinventing the digital wheel every day. PEO Digital should enforce the use of a strict design system—similar to the U.S. Web Design System (USWDS) used by modern federal agencies. A unified design system means that buttons, navigation menus, fonts, and layouts are standardized. When a Sailor learns how to navigate one Navy application, they immediately know how to navigate all of them because the visual language is identical.
Where We’ve Gotten It Right
It is easy to be cynical about defense IT, but there are powerful examples of what happens when we prioritize the user and cut through the bureaucracy. We have to look at these successes not as anomalies, but as the blueprint for the future.
The Flank Speed Revolution
Perhaps the greatest IT victory the Navy has achieved in the last decade was the rapid rollout of Flank Speed. For years, the Navy suffered under the NMCI (Navy Marine Corps Intranet) webmail ecosystem—a notoriously slow, portal-heavy, and frustrating experience.
When the COVID-19 pandemic hit, the Navy was forced to act. PEO Digital, working at breakneck speed, pushed the fleet into a cloud-native Microsoft 365 environment. Suddenly, Sailors had access to modern tools: Teams for chat, OneDrive for cloud storage, and a robust web-based email client.
It worked because we didn’t try to have NAVWAR build a proprietary Navy chat app. We didn’t admire the problem. PEO Digital bought a commercial, industry-leading product that already had billions of dollars of UX research poured into it, and we adapted our security posture to fit the commercial model, rather than forcing the commercial model to conform to legacy DoD architecture. Flank Speed proved that we can deliver consumer-grade UX to the warfighter if we get out of our own way.
MyNavy HR Transformation
For decades, a Sailor’s personnel and pay records were scattered across dozens of archaic databases running on mainframe computers. To fix an issue, a Sailor had to bounce between physical PSD (Personnel Support Detachment) offices and an array of terrible web portals.
The ongoing MyNavy HR transformation is a massive step in the right direction. By working to collapse legacy systems like NSIPS and FLTMPS into a more unified, cloud-based architecture, the Navy is slowly building a centralized digital experience. The MyNavy Portal (MNP), while still a work in progress, represents a conscious effort by OPNAV and PEOs to consolidate the user experience.
It is working because leadership recognized that “pay and personnel” is a single user journey, not twenty separate databases. By aligning the funding and the program management under a unified vision, they are slowly killing off the legacy portals and pulling that functionality into a more modernized, single-point-of-entry system.
The Kessel Run Blueprint (A Joint Lesson)
While this is an Air Force example, the DoD-wide gold standard for fixing the UX crisis is the Kessel Run software factory. When the Air Force realized their Air Operations Center (AOC) software was a bloated, unusable mess of portals and legacy code, they didn’t write another 10-year requirements document.
They stood up a DevSecOps environment, paired actual software developers side-by-side with the Airmen doing the job, and coded solutions in real-time. If an Airman said, “This button is in the wrong place and takes too long to click,” the developer moved the button that afternoon.
Kessel Run succeeded because they destroyed the barrier between the engineer and the end-user. NAVWAR and PEO Digital are beginning to adopt these “software factory” concepts (like the Black Pearl initiative), bringing continuous integration and continuous delivery (CI/CD) to the fleet. When the developer and the warfighter look at the same screen at the same time, the “thousand portals” problem vanishes, replaced by streamlined, purpose-built workflows.
Stop Admiring, Start Delivering
The UX crisis in Navy IT is not an unsolvable technical mystery. It is a choice we make every day through our acquisition strategies, our funding lines, and our tolerance for legacy bureaucracy.
Every time a Sailor spends forty-five minutes fighting a login loop, we are degrading our lethality. Every time a division officer spends her Friday night manually transferring data from a training portal to a readiness portal, we are wasting the intellectual capital of our force.
OPNAV N2/N6, NAVWAR, and PEO Digital have the talent and the budget to fix this. The commercial tools, the cloud infrastructure, and the design frameworks already exist. We just need the institutional courage to stop funding fragmented program silos and giant systems integrators and start demanding a unified, seamless, and dignified digital experience for our warfighters.
It is time to close the portals. It is time to open the door to a modern digital experience for Seaman Smith and all Navy end users.







