Modernizing a Legacy Command & Control Interface
Northrop Grumman | 2019–2024 | UX Designer

Context

I was embedded as the UX designer on a U.S. Army air and missile defense program, working within a multidisciplinary team of systems engineers and software developers. The program operated under strict security requirements, so while I can't share screens or system details, I can speak to my design process and the challenges I navigated.

The Problem

The operator-facing interface had been built on legacy standards that no longer reflected how users worked or what current usability guidelines required. Operators — soldiers working under significant cognitive load in time-critical environments — were using a system that hadn't kept pace with modern interface conventions. The goal was to bring the interface up to current standards while meaningfully reducing the mental effort required to complete core tasks.

My Process

I began with a research phase focused on understanding how operators actually used the existing system — what workflows were most common, where friction points existed, and what the legacy interface got right that we needed to preserve. Conducting research in a classified environment meant working within constraints most UX teams don't face: limited access to users, controlled observation settings, and documentation requirements that differed from typical research ops. I adapted standard methods accordingly.

From there I worked iteratively with engineering, translating findings into interface updates that aligned with current design standards while staying within the technical constraints of the system. A significant part of my work was advocating for the user within a team where design was not always the primary lens.

Constraints & What I Learned

Working in a highly regulated, security-cleared environment taught me how to do rigorous UX work with limited access, compressed timelines, and stakeholders who spoke the language of systems engineering rather than design. I learned to communicate design decisions in terms of operator performance and risk reduction — a translation skill I use constantly.

Due to the nature of the program, post-deployment outcomes were not available to me. I'm happy to discuss my process and decision-making in depth.