Project
True Anomaly Mosaic C2 System
Reinvigorating the OODA Loop
Details
About
C2 systems are meant to provide surgical precision and accurate decision making under pressure. There are no KPIs around profit margins, click traffic, checkout rates, or time spent on the app — in fact, it's quite the contrary. Dark UX/UI patterns are not just frowned upon, they're completely prohibited from this use case. It's a completely utilitarian way of thinking that focuses on functionality and performance, both for the operator and the vehicle(s).
The core emphases of mission ops UX are: getting the operator the right data at the right time, presenting it in an intuitive way that prioritizes cognitive bandwidth, and enabling the operators to make the best decisions possible in the shortest amount of time — aka, implementing the OODA loop decision-making framework to software. In addition, as Product Designer, my role is to follow this industry-standard best practice through the lens of design thinking and assess the deltas as they come up. If and when they do, my responsibility is to decide how to harmonize these two frameworks to create the optimal mission ops experience.
Mosaic is no exception to this rule.
Impact
Learn more about how my contributions enabled mission success here.
Company
True Anomaly
Timeframe
August 2025 - January 2026
Tools
Figma, Project Management Tools
Problem
Space defense operations demand software that translates complex mission objectives into reliable, usable tools. Oftentimes, the experience proves fragmented, inconsistent, and high cognitive load. Mosaic needed to support high-stakes C2 workflows while meeting usability, mission and engineering constraints.
Questions
How might we translate complex product and mission requirements into clear, functional interfaces?
How might we support C2 and other related workflows while reducing operator friction?
How might we design a ground software system that supports complex C2 workflows without overwhelming operators?
How might mission needs, product requirements, and engineering realities be aligned in a single interface?
How might accessibility and UX best practices be embedded from the start?
My Contributions
Led the end-to-end design lifecycle for Mosaic, owning planning, execution, and delivery
Translated mission and product requirements into functional design specifications aligned with engineering capabilities.
Collaborated cross-functionally to resolve complex technical challenges through high-performance interface solutions.
Embedded UX research, iterative testing, and accessibility compliance into the product lifecycle.
Drove continuous iteration and contributed to Mosaic’s evolving design system.
Skillset
Product Strategy, UX Research, Interaction Design, Design Systems, Accessibility, Cross-Functional Leadership, Product Development, Product Design
Process
Research
Partner with operators and stakeholders to understand mission workflows
Enhance workflows to reduce unnecessary cognitive burden on operators
Identify and create standardized personas, as part of a larger coordinated UX Research effort for Mosaic
Feature Engineering
Based on mission requirements, create product requirements that satisfy both user needs and engineering constraints
Use iterative prototyping to communicate feasibility and implementation to both operators and engineers
Create workflows for ideal process flows with each iterative build
Design
Design and iterate mockups
Design high-fidelity mockups and prototypes
Design scalable interaction patterns and mission workflows
Develop
Collaborate with engineers to ensure smooth implementation
Launch
Deliver Mosaic as an operational, mission-critical platform
Highlights
Led design for a mission-critical space defense system
Bridged mission, product, and engineering domains
Embedded accessibility practices into defense software
Contributed to a scalable, multi-use case design system
Conclusion
Mosaic as a C2 system follows industry best practice — and then some.
About
C2 systems are meant to provide surgical precision and accurate decision making under pressure. There are no KPIs around profit margins, click traffic, checkout rates, or time spent on the app — in fact, it's quite the contrary. Dark UX/UI patterns are not just frowned upon, they're completely prohibited from this use case. It's a completely utilitarian way of thinking that focuses on functionality and performance, both for the operator and the vehicle(s).
The core emphases of mission ops UX are: getting the operator the right data at the right time, presenting it in an intuitive way that prioritizes cognitive bandwidth, and enabling the operators to make the best decisions possible in the shortest amount of time — aka, implementing the OODA loop decision-making framework to software. In addition, as Product Designer, my role is to follow this industry-standard best practice through the lens of design thinking and assess the deltas as they come up. If and when they do, my responsibility is to decide how to harmonize these two frameworks to create the optimal mission ops experience.
Mosaic is no exception to this rule.
Impact
Learn more about how my contributions enabled mission success here.
Company
True Anomaly
Timeframe
August 2025 - January 2026
Tools
Figma, Project Management Tools
Problem
Space defense operations demand software that translates complex mission objectives into reliable, usable tools. Oftentimes, the experience proves fragmented, inconsistent, and high cognitive load. Mosaic needed to support high-stakes C2 workflows while meeting usability, mission and engineering constraints.
Questions
How might we translate complex product and mission requirements into clear, functional interfaces?
How might we support C2 and other related workflows while reducing operator friction?
How might we design a ground software system that supports complex C2 workflows without overwhelming operators?
How might mission needs, product requirements, and engineering realities be aligned in a single interface?
How might accessibility and UX best practices be embedded from the start?
My Contributions
Led the end-to-end design lifecycle for Mosaic, owning planning, execution, and delivery
Translated mission and product requirements into functional design specifications aligned with engineering capabilities.
Collaborated cross-functionally to resolve complex technical challenges through high-performance interface solutions.
Embedded UX research, iterative testing, and accessibility compliance into the product lifecycle.
Drove continuous iteration and contributed to Mosaic’s evolving design system.
Skillset
Product Strategy, UX Research, Interaction Design, Design Systems, Accessibility, Cross-Functional Leadership, Product Development, Product Design
Process
Research
Partner with operators and stakeholders to understand mission workflows
Enhance workflows to reduce unnecessary cognitive burden on operators
Identify and create standardized personas, as part of a larger coordinated UX Research effort for Mosaic
Feature Engineering
Based on mission requirements, create product requirements that satisfy both user needs and engineering constraints
Use iterative prototyping to communicate feasibility and implementation to both operators and engineers
Create workflows for ideal process flows with each iterative build
Design
Design and iterate mockups
Design high-fidelity mockups and prototypes
Design scalable interaction patterns and mission workflows
Develop
Collaborate with engineers to ensure smooth implementation
Launch
Deliver Mosaic as an operational, mission-critical platform
Highlights
Led design for a mission-critical space defense system
Bridged mission, product, and engineering domains
Embedded accessibility practices into defense software
Contributed to a scalable, multi-use case design system
Conclusion
Mosaic as a C2 system follows industry best practice — and then some.