Intelligence Operations

SPECTRA

Unified Intelligence Operations Platform. Real-time situational awareness, intelligence fusion, and operational decision-making through a single integrated interface designed for mission-critical environments.

Role
Lead UX/UI Designer
Scope
15+ Screens
Deliverables
UX, UI, Design System, IA
Status
Active Deployment

On this page: OverviewChallengeUsersProblemsPrinciplesIADesign System

Industry
Intelligence Operations
Users
Operators, Analysts, Commanders
Platform
Web Application
Scope
15+ Screens
Role
Lead Product Designer
Deliverables
UX, UI, Design System, IA
SPECTRA Hero Image

SPECTRA unified multiple operational workflows into a single intelligence platform with a consistent interaction model. Operators, analysts, and commanders access their domain-specific view through a common system.

Unifying fragmented operations

Problem

Operators worked across 4–6 disconnected tools with different workflows, alert models, and navigation patterns. Cognitive switching cost slowed real-time decision-making.

Solution

Built a unified platform bringing signal monitoring, intelligence analysis, air traffic, and command workflows into one consistent experience. 15+ screens with a single cognitive language.

Outcome

Delivered a production-ready design system and interface architecture supporting three user types simultaneously while maintaining persistent operational situational awareness.

Designing for real-time operations

Business Challenge

Fragmented tooling across 4–6 specialist applications
Context switching cost during active operations
Multiple user types with conflicting needs
Real-time data from multiple intelligence sources

Design Challenge

Extreme information density across 15+ screens
Persistent operational awareness without overload
Cognitive language consistent across all modules
Speed from signal detection to command action

Three simultaneous roles

EW Operator

Signal Detection

Goal
Detect anomalies and respond rapidly
Needs
Speed, visibility of exceptions, immediate action
Time
Detection to response: under 60 seconds
Analyst

Intelligence Fusion

Goal
Correlate multi-source intelligence
Needs
High-density information without overload
Task
Build Electronic Order of Battle
Commander

Threat Assessment

Goal
Understand situation and decide action
Needs
Synthesized status, threat visualization
Time
Assessment to decision: under 2 minutes

Four structural challenges

01

Persistent Situational Awareness

An analyst drilling into deep screens must not lose awareness of the live operational picture. Alerts firing while focused on detail work are a real operational risk.

02

Consistent Cognitive Language

15 screens with different visual logic create mental overhead. Operators needed one coherent system learned once and applied everywhere.

03

Data Density Without Paralysis

Every screen carries significant information. The challenge was never simplifying by removing data—it was structuring complexity to prevent overload.

04

Detection-to-Action Speed

Every design decision had to shorten the path from "I see something" to "I have responded." Observation without clear action is a failure state.

Before vs. After

Before

Before Image
4–6 disconnected systems
Different visual languages
Multiple alert systems
Heavy context switching
Fragmented workflows

After

After Image
Single unified platform
Consistent cognitive language
Centralized intelligence picture
Reduced navigation friction
Shared operational workflow

Five core operational principles

1

Status First, Detail Second

Every screen opens with critical status information visible before interaction. An operator with 10 seconds gets essential context.

2

The Right Panel Never Leaves

Persistent right column showing live alerts and operational picture on every screen. The operator's peripheral vision is always active.

3

Color Means Operational Status

Red = critical threat. Amber = high/suspect. Cyan = monitoring. Green = safe. This semantic system is fixed across the entire platform.

4

Every Data Point Has Action

Nothing is pure observation. Every threat has Investigate and Acknowledge. Every intercept has Analyze and Record. The interface is a decision instrument.

5

AI as an Instrument

The AI terminal feels like a command interface integrated into operations—not a chatbot. Structured responses, classification labels, authority.

Unified operational structure

SPECTRA

Single unified intelligence operations platform

Operations
Live Map
COMINT
ELINT
ADS-B
AIS
Command
Alerts
JADOPS-AI
Situational Awareness
Analysis
Threat Fusion
Reports
Intelligence Correlation
Defense Loop
Detect
Identify
Monitor
Respond

Built before screen work began

Color Tokens

JADOPS uses a compact semantic palette: core surfaces (--bg, --panel), operational accents (--acc2: blue for primary, --warn: amber, --red, --green, --teal), and text hierarchy (--txtb: bright, --txt: muted, --dim: secondary). All colors mapped to CSS variables for consistency.

--bg
#07101e
--panel
#0d1a2b
--acc2
#3b82f6
--red
#ef4444
--warn
#f59e0b
--teal
#00c896

Typography

Monospace-first (JetBrains Mono) at 11.5px base. Headers 12–13px, labels 8–9px. High x-height ensures legibility at small sizes. Letter-spacing ±0.5px used for hierarchy. No anti-aliasing penalties at compact scales.

Module Title — 12px
Body Text — 11.5px (base)
Label — 10px
CAPTION — 9px

Button / Action System

Compact module buttons (`.mod-btn`): transparent default, 1px border with var(--border), hover→--acc2. Primary variant adds subtle bg rgba(37,99,235,.15). Padding 3px 10px, border-radius 2px, font-size 9px, zero shadow.

Card Patterns

KPI cards and panel cards use var(--panel) background, 1px solid var(--border), border-radius 4px, padding 10–12px. Task cards add left border accent for severity. No shadow; subtle contrast achieved through borders and background opacity.

KPI Label
42
Task Title
Active state

Badges & Severity

Status badges use minimal borders + subtle bg: `.badge-green`, `.badge-warn`, `.badge-red`, `.badge-blue`. Padding 1px 6px, border-radius 2px, font-size 8px. Applied to tables, alerts, and inline status. Semantic color hierarchy baked in.

badge-green badge-warn badge-red badge-blue

Layout & Spacing

Grid-based with compact spacing: sidebar 200px, collapsed 56px, right panel 280px, header 44px. Content padding 12px. Card gaps 8px, module padding 12px, row padding 6–10px. Flex and CSS grid align items. No margin collapse.

56px
Content area
280px

Alert States

Critical High Monitor
Use for system-level severity indicators.

Action Buttons

Module-level actions matching JADOPS design system.

Status Chips

Connected Loading… Error
Compact status indicators for row-level data.

Entity Tags

Aircraft #3245 Emitter RADAR Threat CONFIRMED
Compact labelled tags for entities and classifications.

Confidence Levels

95%
72%
41%
Visual confidence indicator for automated detections.

Form Elements

Compact inputs with 2px radius, var(--line) borders, and JADOPS token colors.

Key screen showcase

Common Operating Picture

Common Operating Picture

Unified dashboard showing live tactical picture. All operators, analysts, and commanders access the same intelligence view with role-specific detail levels.

Primary Users
All roles simultaneously
Key Design Decision
Persistent right panel with live alerts ensures operators never lose situational awareness
Operational Outcome
Single source of truth for all personnel. Commanders have decision-ready picture at all times.
COMINT Dashboard

COMINT Dashboard

Dedicated communications intelligence workspace. Deep analysis capabilities with spectrum visualization, frequency hop detection, and transcription management.

Primary User
COMINT Analyst
Key Design Decision
Waterfall display replaces simple log, enabling pattern recognition at a glance
Operational Outcome
Analysts spot frequency anomalies instantly. Threat confidence increases through visual pattern matching.
Threat Fusion

Threat Fusion

AI-powered intelligence correlation. Automated threat assessment combining SIGINT, ELINT, and tactical data. Machine confidence paired with analyst judgment.

Primary User
Senior Analyst / Commander
Key Design Decision
Confidence indicators and source attribution paired with threat severity for decision authority
Operational Outcome
Analysts make higher-confidence threat assessments faster. AI handles heavy correlation lifting.
JADOPS-AI Terminal

JADOPS-AI Terminal

Conversational intelligence interface. Analysts query the system in natural language. AI returns structured threat assessments with confidence levels and source attribution.

Primary User
All analysts
Key Design Decision
Positioned as primary navigation item, signaling AI is core workflow not optional
Operational Outcome
Analysts skip manual correlation. AI terminal becomes primary intelligence production method.
EW Planning

EW Planning

Electronic Warfare planning and execution. Mission design, frequency allocation, and real-time adjustment. Coordinates with COMINT and air traffic operations.

Primary User
EW Operator / Planner
Key Design Decision
Seamless context switch from planning to operations. Same interaction language across modules.
Operational Outcome
Planners execute missions without context switching. Real-time data informs live mission adjustments.

Tradeoffs and rationale

Design Decision 1

Persistent Right Panel

Alternative

Full-bleed content with notification overlays

Decision

Always-visible right panel with live alerts

Tradeoff

280px content space cost per screen vs. uninterrupted awareness

Problem
Operators drilling into analysis screens could miss critical live alerts. Polling for alerts or modal interruptions caused friction in focused workflows.
Why Rejected
Notification overlays cause cognitive interruption. Checking a separate alerts view breaks operational momentum.
Expected Outcome
Operators maintain operational picture while engaged in deep analysis. 280px space trade is acceptable for mission-critical awareness.
Design Decision 2

AI Terminal as Primary

Alternative

Floating widget, supplementary feature

Decision

Primary navigation item in Command group

Tradeoff

Signals AI-assisted analysis is core workflow, not optional

Problem
AI capabilities were positioned as a secondary tool. Analysts treated it as backup, not primary intelligence fusion method.
Why Rejected
Floating widgets create inconsistent access patterns. Supplementary positioning signals limited trust in AI capabilities.
Expected Outcome
AI becomes first-class citizen in operational workflow. Analysts use it as primary correlation method, with visual intelligence as validation.
Design Decision 3

Waterfall Display vs. Log

Alternative

Simple chronological intercept log

Decision

Live spectrum waterfall showing frequency behavior

Tradeoff

Higher implementation complexity vs. pattern visibility

Problem
Chronological logs obscure frequency hopping patterns. Operators needed to visualize spectrum behavior over time.
Why Rejected
Text logs require active scanning. Visual waterfall enables pattern recognition at a glance.
Expected Outcome
Operators spot frequency patterns instantly. Implementation complexity is acceptable for operational intelligence value.
Design Decision 4

Flat Navigation

Alternative

Grouped hierarchy with expandable sections

Decision

Flat single-level sidebar, all modules always visible

Tradeoff

Vertical sidebar space vs. predictable one-click access

Problem
Hierarchical navigation requires two-step access (expand, then select). In operational context, this friction is unacceptable.
Why Rejected
Expand/collapse adds cognitive overhead. Operators need immediate access to any module.
Expected Outcome
Single-click access to all modules. Sidebar uses vertical space efficiently via scrolling. Operational speed is optimized.
Design Decision 5

Bilingual Transcription

Alternative

Source language only, separate translation view

Decision

Arabic and English side-by-side with threat tags below

Tradeoff

Layout complexity vs. seamless conversation reading

Problem
Analysts switch between source and translation, breaking conversation context. Threat classification was separate from content.
Why Rejected
Separate views require context switching. Analysts need full conversation + classification in single view.
Expected Outcome
Analysts read full conversation with translation and threat tags. No context switching. Layout complexity is justified.

From operational brief to production system

1
Requirements
2
Architecture
3
Wireframes
4
Validation
5
High Fidelity
6
Design System

Requirements arrived as operational briefs written in military domain language. Translated into design problems and presented back to stakeholders as annotated wireframes before moving to high fidelity. Client stakeholders validated structure before visual decisions were locked. Maintained living Figma component library for development handoff with exact specifications for spacing, color tokens, interaction states, and responsive breakpoints.

What was delivered

📐

Design System

Complete component library with 40+ elements, all states, and interaction specifications

🎯

15+ Screens

High-fidelity operational interfaces ready for development handoff

📋

Interaction Specifications

Detailed interaction patterns, animations, and state transitions documented

🏗️

Information Architecture

Complete navigation structure, user flows, and task mapping across all roles

⚠️

Edge Case Documentation

Failure states, error handling, and exceptional operational scenarios

🎨

Figma Component Library

Production-ready design tokens, responsive components, and developer handoff assets

What the platform enables

One Unified Platform

Replaces 4–6 specialist tools with a single integrated system. Operators access SIGINT, ELINT, ADS-B, AIS, and EW planning through one consistent interface.

Consistent Operational Language

Same interaction patterns, color semantics, and navigation logic across all 15 screens. Operators learn once and apply everywhere, reducing cognitive overhead.

Reduced Context Switching

Moving from COMINT to EW planning to threat analysis requires no interface relearning. Seamless task transitions enable sustained operational focus.

AI-Assisted Intelligence

JADOPS-AI terminal enables analysts to produce threat assessments through natural queries. Automation handles heavy correlation lifting while analysts maintain decision authority.

Production-Ready Design System

Complete Figma component library with 40+ elements, interaction specifications, responsive patterns, and developer handoff assets ready for immediate implementation.

Command-Level Situational Awareness

Commanders have persistent common operating picture updated in real-time. Highest-confidence threat correlations surface automatically without active polling.

Why This Project Matters

SPECTRA was a complex systems design challenge that required balancing information density, operational awareness, and decision-making speed across multiple user groups operating under time pressure and mission-critical constraints.

The project reinforced fundamental principles about designing for demanding environments: information architecture is not decoration—it directly impacts operational effectiveness. Cognitive consistency matters more when stakes are high. And design systems are not overhead—they're force multipliers that enable operators to maintain focus on the mission, not the interface.

The greatest satisfaction came from designing a platform used by highly trained specialists who have absolute clarity about what they need. Building for experts means no room for compromise. Every decision is tested against operational reality. The work reminds us why thoughtful, rigorous design is essential—not for aesthetic reasons, but because it translates directly into operational capability.

Interested in complex operational design?