MERIDIAN Mission Telemetry: a concept UX prototype

Design rationale, panel by panel

Portfolio note

You are looking at a concept piece

This is a simulated mission telemetry dashboard I designed to demonstrate UX for multi-asset monitoring systems. All telemetry below is randomly generated for this demo. No real vehicles or data are involved. Click Next for the design thinking behind it, then a walkthrough of each panel.

Design principles

The thinking behind this

A few decisions shaped everything you are about to see, not tied to any single panel.

1. Fleet Overview

Every asset, at a glance

Operators see status for the whole fleet at once, sorted by severity so anything needing attention rises to the top automatically.

Sorting by severity, not alphabetically or by call sign, means an operator scanning under pressure sees what matters first without having to search for it.

2. Tactical Map

Where everything is, right now

A stylized tactical map keeps geographic context visible at all times.

It stays dark in both light and dark mode on purpose, matching how real sensor and radar displays are built to reduce glare and preserve night vision adaptation. Matching real-world convention mattered more here than matching my own theme toggle.

3. Asset Detail

Click any asset to drill in

Selecting an asset from the list or the map surfaces its live telemetry, a simulated sensor feed, and mission elapsed time, without ever leaving the fleet-wide view.

This is progressive disclosure in practice. Depth is one click away but never forced on you, so the default view stays scannable instead of overwhelming.

4. Alert Feed

Anomalies surface themselves

Instead of making operators watch every metric on every asset, the system detects anomalies and pushes them here: chronological, severity-tagged, and acknowledgeable. Watch this panel for a scripted incident shortly after load.

This is recognition over recall, one of the oldest usability heuristics for a reason. An operator should never have to remember to check something. The system should tell them.

5. Trend

Supports root-cause thinking

A quick history of the selected metric, not just its current value.

A single number cannot tell you if something is a spike or a trend. This exists so an operator investigating an alert can judge urgency before reacting to it.

6. Controls

Panels, tutorial, and theme

The grid icon shows or hides any panel, close one from its header and bring it back here. The question mark replays this walkthrough any time. The sun and moon icon switches between light and dark mode.

None of this is required to use the dashboard. It exists because different operators and different shifts have different preferences, and forcing one fixed layout on everyone is its own usability problem.

That is the tour

Feel free to explore

Drag the thin dividers between panels to resize them, and click any asset to see it update live. Thanks for taking the walkthrough.

MD
MERIDIAN
Mission Telemetry
Back to Portfolio Ground Control Station
MONITOR MODE
LINK NOMINAL
00:00:00 UTC
AC
Fleet Overview
6 ASSETS
Tactical Map
GRID REF 34.7Q
SCAN RADIUS 40NM
REFRESH 1.0s
Nominal
Warning
Critical
Asset Detail
Select an asset from the fleet list
or tactical map to view telemetry.
Alert Feed
0
Trend
-
Welcome
Design rationale