Command & Control Operating Picture

Commanders needed a real-time picture of operational status across air, land, maritime, and cyber domains. The existing approach: operators manually aggregated data from separate classified systems and briefed commanders verbally or with static slides. Latency and human error, baked into high-stakes decisions.

The project ran under Controlled Unclassified Information (CUI) handling requirements, which constrained everything from where design files lived to which collaboration tools we could touch. My normal cloud-based workflow was off the table.

Research in defense is inherently constrained — I couldn't observe real operations or access classified data. Instead I worked with SMEs who had operational experience and could describe workflows, decision points, and failure modes in declassified terms.

Structured interviews with 12 operators across three command levels revealed the core design problem: each level needs fundamentally different information from the same underlying data. A tactical operator needs granular unit positions in real time. A strategic commander needs trends, readiness scores, and decision-relevant summaries. I also studied existing military interface conventions closely — those patterns persist for reasons, and breaking them without understanding why erodes trust fast.

Wireframing started with information hierarchy: what does a commander need to see first when they walk into a command center? Working with operators, I established a visual priority framework — critical alerts on top, status overview center, detail panels on demand.

The tension in mid-fi was density versus scannability. Military operators are trained to parse dense interfaces, but trained tolerance isn't the same as effectiveness. I pushed for cleaner layouts than the team was comfortable with, and testing settled the argument: operators found critical information 25% faster in the cleaner designs.

Color was the most sensitive call. Red, yellow, and green carry specific operational meanings in defense contexts that can't be redefined for aesthetics. We worked inside the established semantics and modernized everything around them.

The dashboard uses a three-tier architecture: a persistent status bar for critical alerts and overall readiness, a configurable main panel (map, timeline, or matrix view), and collapsible detail panels for drill-down.

Designing under security constraints forced discipline that improved the work. When you can't casually screenshot a prototype into Slack, you plan review sessions carefully. When files can't live in the cloud, you get serious about versioning and documentation.

The hardest part was balancing innovation against muscle memory. Every deviation from convention needed a defensible rationale — not "it looks better" but "operators identify threats 25% faster in testing." Data-driven arguments carried weight that aesthetic arguments never would.