ELINT Mission Prep Tool for SIGINT Reprogrammers
SRC Threat Emulation — Electronic Warfare Database UX
Details shared with permission. Visuals and process shown; client name, sensitive system details, and classified aspects omitted.
- Client
- src-inc
- My Role
- Lead UX Designer
- Team
-
- Large cross-functional team — Various stakeholders, SMEs, developers
- Year
- 2022
- Timeframe
- 24 months
- Platform
- desktop-web
- Deliverables
- ui-designs, infographic
The SRC ELINT mission prep tool designed a database-driven workflow for SIGINT reprogrammers — specialists who maintain radar files and electronic warfare libraries to support ELINT missions. The reprogramming OODA loop is lengthy, intricate, and data-intensive; operators range from entry-level reprogrammers to expert EW analysts, and the tool needed to serve both without compromise. As Lead UX Designer over 24 months at Visual Logic, I drove UX from information architecture through three rounds of validated user testing. Young SIGINT reprogrammers responded positively — the simple-by-default design proved intuitive while preserving full complexity for advanced operators.
This was a 24-month engagement for SRC Inc., sourced through Visual Logic, where I served as Lead UX Designer on a large cross-functional team including SMEs, developers, and stakeholders. The platform was a desktop web application. Deliverables included UI designs and scope infographics for team alignment. Visuals are shown with permission; sensitive system details are omitted.
Overview
SRC specializes in radars and electronic warfare (EW). This tool prepares radar files for ELINT missions — supporting SIGINT reprogrammers in maintaining spectrum dominance. The electromagnetic spectrum represents a complex, contested domain where “spectrum dominance” is a highly sought objective for nation states.
The Challenge
The reprogramming OODA loop involves lengthy, intricate, data-intensive processes. Creating tools for this workflow presents inherent difficulties.
Reprogrammers work in a domain that demands sophisticated databases and specialized workflows. Understanding their roles — and the tool’s position within the larger OODA loop — required substantial investigation before any design work could begin.
Challenges
Complex Domain Signal intelligence demands sophisticated databases and workflows. Understanding user roles required substantial investigation. The tool’s position within the larger OODA loop was difficult to communicate clearly to the team.
Ambiguous Scope Broad, unclear project parameters created team misalignment and disagreement. Multiple visuals and strategic plans were developed to establish clarity and facilitate progress. The reprogramming landscape was articulated and feature inclusions/exclusions were explicitly defined.
Strategic Misalignment Contrasting viewpoints between senior leadership and junior team members created friction throughout. Progressive disclosure methodology helped bridge these disagreements.
Designing for Technical Users Reprogrammers required functionality serving both inexperienced and expert operators. Progressive disclosure satisfied users across expertise levels without sacrificing capability for power users.
Data Challenges Launch involved incomplete datasets; future versions faced data abundance concerns. The solution accommodated both sparse and data-rich environments.
Process
Success emerged through aligning team understanding of scope trade-offs and immediate priorities. As with many complex projects with large teams, the initial emphasis involved establishing shared comprehension of the problem domain and value proposition.
Stakeholder and Technical Research
- Worked with teams to establish timeframes, goals, priorities, and technical constraints
- Examined SIGINT-specific public and private resources
UX Artifacts and Frameworks
- Generated personas, journey maps, and mental models contextualizing user requirements
- Produced information architecture diagrams and sitemaps for prioritizing tasks amid ambiguous scope
Design and Iteration
- Established foundational macro design framework with progressive refinements
- Designed widgets, graphs, and data visualizations suited for signal intelligence operations
- Produced low-fidelity wireframes; high-fidelity designs finalized with SRC’s design system
Collaboration and Validation
- Engaged with subject matter experts and technical teams during weekly 1.5-hour sessions
- Conducted three rounds of user testing; iterated designs until positive feedback emerged
Solution
A simplified database concatenation tool delivered optimal outcomes without sacrificing capability.
- Engineered an intuitive tool matching reprogrammers’ requirements, prioritizing simplicity and usability
- Produced thorough information architecture and scope diagrams directing project efforts
- Delivered user-focused designs supporting technical workflows with progressive disclosure
- New reprogrammers gained required functionality; experienced reprogrammers accessed expected complexity through supplementary views
Results
Young SIGINT reprogrammers responded positively during user testing. The simple-by-default solution proved intuitive while permitting complexity scaling.
- Positive User Feedback — Three rounds of user testing validated the design robustly
- Improved Clarity and Usability — The tool established a foundation for efficient reprogramming and scalable data integration
- Progressive Complexity — New reprogrammers gained required functionality; experienced reprogrammers accessed expected capability
FAQ
What did you design for SRC?
An ELINT mission prep tool — a database concatenation and management application for SIGINT reprogrammers who maintain radar files and EW libraries to support electronic warfare missions.
What is the SIGINT reprogramming domain, and why is it hard to design for?
Reprogrammers manage complex signal databases within a national-security OODA loop where "spectrum dominance" is a strategic objective. The domain requires deep technical understanding before a single screen can be designed — and the tool's position within the larger EW workflow is not obvious from the interface alone.
How did you resolve team misalignment on scope?
Through IA artifacts and scope diagrams — visualizing the full reprogramming OODA loop and explicitly mapping feature inclusions and exclusions. Making the invisible scope visible created alignment at every level, from junior developers to senior leadership.
What were the user testing outcomes?
Three rounds with young SIGINT reprogrammers validated the design. The simple-by-default approach was confirmed intuitive. Progressive disclosure provided the complexity pathway for experienced operators without exposing it to those who didn't need it.
How does progressive disclosure apply at the military domain level?
By separating "need to know" from "good to know" at the interface level. Novice reprogrammers see exactly what they need to complete a mission prep task. Expert operators reach deeper functionality through deliberate reveals — never confronted with full complexity by default.