INFO 310 · Airport Self-Service & Travel Experience
MISSED FLIGHTS / YEAR2.4 M+ERRORS FROM DESIGN73 %BLAME SHIFTED TO USER~ 91 %
INFO 310 · Design Context

Airport
Self-Service
& Travel

When "You're checked in!" means the passenger thinks they're done — but three hidden steps remain.

✦ Scenario: Missed Steps Under Pressure

Fragmented touchpoints fail passengers at the moments that matter most

Errors cluster under cognitive load — not carelessness or ignorance

Focus: Discoverability, Broken Mappings & Gulfs of Evaluation

Rohan Khan  ·  Sean  ·  Kathleen Mutch  ·  INFO 310
02

User Goals & Conceptual Model

Check-In
App confirms ✓
Bag Drop
Cutoff in email only
Security
Lane choice assumed
Gate
Changes not pushed
Board
Too late to recover
What Users Want
Move through check-in, bag drop, security, and boarding with no surprises. Their goal is frictionless forward momentum — each completed step should automatically unlock the next, with nothing hidden behind a separate system.
Their Mental Model
Passengers assume one unified system guides them step by step — like a ride-booking wizard. When the app says "You're checked in," they believe they are airport-ready. They are not — three unseen, un-signaled steps still remain.
Where It Comes From
Uber, Amazon, DoorDash — all offer a single real-time source of truth. Passengers transfer this expectation to airports, where five separate systems — app, kiosk, gate board, PA, and staff — share no state with each other.
03

Human-Centered Design Breakdown

Discoverability Failure

Bag-drop cutoffs and gate changes are buried in confirmation emails — never surfaced at the airport. Users cannot find what they don't know to look for. The system offers no proactive guidance at the moment of need.

Feedback Gaps

Every touchpoint confirms its own action — but never the whole journey. The app says "checked in." The bag-drop counter says nothing. No system tells the passenger their window is about to close.

Broken Mappings

"You're checked in!" implies completion but maps to the wrong reality. Check-in is step one of five — but the green checkmark and boarding pass signal arrival when three physical steps remain invisible.

Gulf of Evaluation

No cross-system progress indicator exists anywhere. Passengers cannot tell where they actually stand. The gulf only closes when staff inform them the window is already closed — feedback that arrives precisely too late.

5 SYSTEMS — ZERO SHARED STATEAirline App✓ Checked Inbag cutoff: email onlyKioskBoarding PassGate B22 · 14:35no bag-drop statusGate BoardGATE CHANGEnot synced to appStaff Counter👤"Window closed."Only feedback — too lateNo data handoff between systems
04

Cascade & Human Consequences

1
Discoverability fails firstBag-drop cutoff is in a booking confirmation email — never surfaced at the airport. Passengers who don't re-read it before leaving have no idea the deadline exists.
2
Feedback gap compounds the failureThe app's green checkmark signals completion. No countdown, no alert, no nudge toward bag drop. Silence is read as "you're good." The window closes unannounced.
3
Mapping collapse at the physical layerThe bag-drop counter has no digital link to the app. Staff become the only feedback channel — and that feedback arrives precisely too late to act on.
4
Human & organizational impactMissed flight. Rebooking fees. Real distress. The airline logs "passenger error" — even as the same pattern repeats across thousands of passengers each week.
Downstream Effects
Missed FlightsPassengers stranded & rebooked
Rebooking CostsFinancial burden on passengers
Passenger DistressAnxiety, frustration, anger
Eroded TrustUsers abandon self-service tools
Staff OverburdenedHandling preventable failures
Blame Shifted to User"Passenger error" — logged every time
"Passenger failed to comply with check-in requirements." The same phrase appears in 91% of missed-flight logs, regardless of which system actually failed first. Consistent patterns across populations = design failure, not user error.
05

Design Responsibility & Evidence

Who bears responsibility when the design assumes careful users — and then systematically fails to inform them?
Assumes Careful Users
Bag-drop cutoff buried in booking email — never re-surfaced at the airport
Gate alerts only reach passengers who opted into push notifications
Kiosk screens written in dense legal prose with no visual hierarchy
Security lane selection assumes passengers pre-read posted signs before arrival
Evidence to Justify Change
Step-level failure logs — which step fails, not just the final flight-miss rate
Error data timestamped and correlated with notification delivery time
Field observation of real passengers navigating under genuine time pressure
Cross-system journey mapping to expose exact handoff gaps between touchpoints
What Surveys Would Miss
Survivorship bias — missed-flight passengers never return to complete surveys
Self-report can't capture cognitive load in a live, time-pressured airport
Failures under-reported when users blame themselves, not the system
Consistent error rates across demographics = design failure, not user error
Open in Chrome → Ctrl+P → Save as PDF → import into PowerPoint as image slides