Cairo International Airport - Command Hub

A dashboard concept that organizes terminal activity, operational issues and alerts.

Transcript
View Live Project

RoleUX & Data Visualization Designer

Designed dashboard hierarchy, warning states and interactions.

Web dashboard conceptDashboard concept

Problem

An operational display needs to show where an issue is, how urgent it is and whether the data is current. I explored that hierarchy in an airport dashboard concept.

Key decisions

I established terminal scope before showing detail, then placed active issues ahead of routine flight information. Warning and connection states sit beside the relevant data so the viewer can interpret them in context.

Solution

I designed the information hierarchy, warning states and interactions, then translated them into a responsive web demonstration. Demo data connects terminal navigation, operational summaries and flight details.

Cairo International Airport - Command Hub interface preview
Terminal scope, operational summaries and warning states establish what needs attention. Demo data is shown.
Explore screens & design details

A closer look at the features, interface and evidence behind the work.

Key Design Decision

I placed configurable warnings beside the operational information they explain.

Trade-off: Combining signals increases density. Operational reviewers need to test whether priorities and full warning messages remain clear.

Figma Dashboard UX Real-Time Telemetry Information Architecture Design Systems WCAG 2.2 informed

A closer look at the design

Explore three decisions in the interface. Open a numbered detail to highlight its place in the screen.

Terminal 3 map beside active issues, flight details, and an offline status label.
Annotated interface overview
01 · Establish the operational scope

The terminal selector sits above the map and highlights Terminal 3. Establishing scope before presenting detail helps explain which part of the airport the overview refers to.

Terminal tabs with Terminal 3 selected between Terminal 2 and Support Services.
Enlarged screenshot detail. The explanation above is its text equivalent.
02 · Bring exceptions into view

The area overview places active issues before the flight list. This hierarchy gives exceptions a clear place beside the map. Long issue labels still need validation for readability and access to the full message.

Terminal 3 area overview with an Active Issues section and a truncated gate issue label.
Enlarged screenshot detail. The explanation above is its text equivalent.
03 · Make data freshness visible

The flight card shows an OFFLINE label alongside flight and status text. Showing the connection state helps people question data freshness. The public concept demonstrates this presentation; it does not establish a live airport feed.

Incoming flights with an OFFLINE label and text statuses including On time and Landing.
Enlarged screenshot detail. The explanation above is its text equivalent.

Why this approach

Terminal scope gives each signal a location. Prioritizing exceptions and showing connection status helps a viewer decide which details to inspect and whether the information needs checking.

What I learned

Translating the Figma layout into a working dashboard exposed how information density changes across screen sizes.

Next validation task

Use a simulated delayed-flight scenario. Ask operational reviewers to locate the issue, explain the warning and choose an action. Compare interpretation and task time across screen sizes.

Evidence includes designs, live demos, and documented decisions. Business outcomes require sourced measurements.

Recordings & transcripts

Prefer to read along? Explore the audio library and the words behind each recording.

Explore recordings