Travel··4 min read

Lessons from Airports

Airports are designed to make time disappear. What they actually do is remove every distraction you normally use to avoid thinking. I've had more useful conversations and clearer thoughts in airports than in most offices. The environment people most want to escape might be the one most worth paying attention to.

travelairportsobservationbusiness

Manas Majhi
Manas Majhi

Founder, Majhi Group & Majhi OS

Lessons from Airports

The most useful airport heuristic I have learned happened in Singapore. My flight was delayed. The queue at the gate desk was forty people long. I called the airline's rebooking line instead, while walking, and was rebooked in four minutes. The people at the gate desk waited another forty. Same situation. Different approach. That gap is what eight years of frequent flying has actually taught me: the system you can see is not the only system available.

The system you can see is not the only system available.

Here is what else airports have taught me.

What airports reveal about process design

Airports are among the most observed and analyzed process environments in the world. Every major hub has teams of engineers and operations researchers studying queue lengths, throughput rates, bottleneck identification, and wait time reduction. The information systems are sophisticated. The feedback loops are faster and more legible than in most operational environments.

And yet airports are reliably frustrating, in ways that are consistent enough across different airports and different operators to suggest that the problem is not local.

The frustration usually concentrates at the handoffs: the moments when one system passes responsibility to another. Security checkpoint to gate. International arrival to immigration to customs to baggage to exit. These are the points where queue dynamics are least predictable, where information is least reliable, and where the experience of the traveler degrades most sharply.

What airports taught me about operational design: your average performance across the stable segments of a process is less important than your performance at the handoffs. The handoffs are where complexity concentrates, where things go wrong, and where the experience of the people in the process is most sharply determined.

This applies directly to hiring, the thing I work on. The stalls in executive search are almost always at the handoffs: between sourcing and screening, between screening and presentation, between presentation and decision. Improving the stable segments does not help much if the handoffs are broken.

What the regulars understand that first-timers do not

Frequent flyers develop heuristics that are genuinely different from the default behavior of travelers who navigate airports rarely.

Not the obvious ones: sign up for priority queue, get to the gate early. The less obvious ones: when a delay is announced, do not join the queue at the gate desk. Call the airline's rebooking line while walking, because the queue you can see is not the only queue. When your bag is late to baggage claim, go to the office first rather than waiting at the carousel: the bag may already be there.

These heuristics are not documented anywhere. They are learned through iteration and failure, through watching other regulars and understanding what they are doing differently. They are the kind of knowledge that is specific enough to be highly valuable and general enough to be broadly applicable to anyone who moves through the same system.

This is what domain expertise looks like in most fields: not the textbook knowledge, which is available to everyone, but the accumulated heuristics about how the system actually behaves versus how it is supposed to behave. The gap between those two things is where most of the practical value lives.

The sociology of waiting

Airports are one of the few environments where people of significantly different backgrounds and circumstances are regularly placed in proximity and subjected to the same constraints. The business traveler and the family relocating across continents are in the same queue, experiencing the same delay, with the same lack of information about what is happening.

What this reveals, repeatedly, is the enormous variance in how people relate to uncertainty and loss of control. Some people treat airport disruption as a logistical problem to be solved: calling airlines, checking alternatives, making decisions without complete information. Some people treat it as an injustice being done to them: escalating emotionally, directing their frustration at the nearest available target. Some people read a book and wait.

These are not random responses. They correlate with dispositions that show up in other contexts. The person who responds effectively to airport uncertainty is often the same person who responds effectively to business uncertainty. The behavior is consistent enough to be diagnostic.

I have learned to watch how people respond to small, uncontrollable inconveniences. It tells you more about how they will handle larger, more consequential uncertainty than most formal assessments.

See also: Travel as a Learning System, What Travel Has Taught Me, Why Food Matters More Than We Think

Frequently Asked Questions

What is the most transferable operational lesson airports have produced?

That the system you can see is not the only system available. The visible queue, the gate desk with forty people waiting: these are the default path, not the only path. There is almost always a parallel option with a different queue length, and finding it requires refusing to assume that the most visible option is the only one. This transfers directly to most operational situations.

Why do airports produce consistent frustration despite being among the world's most engineered process environments?

Because the frustration concentrates at the handoffs, where one system passes responsibility to another, and handoffs are where information, incentives, and accountability belong fully to neither system. Each part of the airport optimises for its own metrics. The gap between them is where the traveler's experience degrades most sharply, and it is precisely the gap that no single operator owns.

What does the enforced waiting of transit produce that ordinary work time does not?

A different quality of attention. Transit removes the default structure, the meeting schedule, the task queue, the ambient pressure of the next thing, and in that removal a different kind of thinking becomes available. Not necessarily better, but different. The thinking happens not because transit is generative but because it eliminates the structures that make certain thoughts inaccessible during ordinary working time.

Did this land? Push back? Add something I missed?

Reply to Manas →