CONCEPT CASE STUDY · SPACE OPERATIONS UX

One operator, 25 satellites, one night shift. Designing an AI teammate that can be trusted.

A concept for on-the-loop anomaly resolution: automation detects, diagnoses and plans, and a single operator supervises. The interface shows the mission rather than the machines, hides what doesn't need a human, and proves what it's hiding.

Play the 4-minute demo Read the walkthrough
RoleConcept, UX direction and design. Prototyped with AI assistance.
DomainCrosslinked Earth-observation constellation (fictional)
ScenarioSingle-operator 12-hour shift, intermittent ground contact

Why a concept piece

For the past six years I've designed mission-critical software for space operations: constellation management, space object tracking, commanding, mission management and AI-assisted anomaly resolution. That work can't be shown. This piece rebuilds how I approach those problems from public principles, with a fictional commercial operator, invented data and no real program's workflows. I set the problem, the principles and the scenario, directed the design and reviewed every screen; an AI assistant did much of the production.

THE PROBLEM

Constellations are always connected now. People can't be.

Older operations waited for a ground pass, and the next contact window set the tempo. Satellites linked by optical crosslinks are in contact continuously, so automation can act in seconds. The operator's job shifts from planning contacts to supervising decisions made at machine speed, across many vehicles, alone, for a whole shift.

Scale One person can't watch 25 satellites' telemetry for 12 hours. Watching everything means noticing nothing.
Ripple effects In a mesh, one satellite's problem reroutes traffic and tasks for its neighbors. Anomalies are network events, not box-level faults.
Trust Operators either rubber-stamp automation or ignore it. Both fail. The design has to calibrate trust, not just ask for it.
THE CORE TENSION Being on the loop requires transparency. One operator over a 12-hour shift requires abstraction. The design has to deliver both.
SEVEN PRINCIPLES

Abstraction you can always peel back.

{{p.n}}
{{p.title}} {{p.body}} See it: {{p.screen}}
BEFORE AND AFTER · SAME ANOMALY

From 14 alarms and a 37-step checklist to one situation and one decision.

BEFORE · VEHICLE-CENTRIC Everything on screen
10 telemetry panels and 19 tabs 47 unacknowledged events in the log 14 alarms to acknowledge one by one before commanding is allowed The operator works out the cause and the fix
Open the legacy console →
AFTER · INTENT-CENTRIC The mission, and what needs you
"On track. One situation needs you." 14 alarms grouped into one situation with a probable cause A ready plan, a deadline, and a stated default if no one responds Every claim can be peeled back to raw telemetry
Open the mission view →
THE WALKTHROUGH · HOUR 7 OF 12

A crosslink starts failing while the operator is on a break.

RAD-07's optical terminal is drifting off target as it heats up. Every screen below is playable; open any of them, or play the demo from the start.

  1. {{b.n}}
    {{b.title}} {{b.body}}
    Open
KEY DECISIONS

Small choices that decide whether people trust the system.

{{d.title}} {{d.body}}
VALIDATION PLAN

Can someone with minimal training make the right call?

The hypothesis is that this design cuts training time. It hasn't been tested yet. The plan is a small study with people who have no space background, running the same anomaly on the legacy console and on the new design.

Measure How
Time to the right decisionFrom the briefing to approving the plan, legacy console vs. new design
ErrorsWrong approvals, missed twist, approving without opening details
Situation awarenessFreeze-and-ask questions: which satellite, what is the default, how long is left
Trust calibrationDo participants catch a planted wrong automatic action in the ledger?
Time to competenceMinutes of instruction before a first unassisted run succeeds
Play the demo Or go straight under the hood →