Ninety minutes on the ground doesn’t have to be wasted time between flights. Treated correctly, it’s one of the more productive blocks in a business traveler’s day.
Most people look at a 90-minute connection and see a countdown clock. I look at it and see a meeting room that happens to have jet bridges attached. A connection at a hub like Charlotte, if you plan around it instead of just enduring it, is genuinely one of the more productive 90-minute blocks in my week. No commute to get there. No one walking into my office to ask a quick question that isn’t quick. Just a chair, a charger, and a deadline built into the departure board.
That only works if you treat it like a scheduled block of work rather than a gap you’ll figure out once you land. I plan connections the same way I plan meetings: what needs to happen, in what order, and what I’m explicitly not going to attempt.
The First Five Minutes Off the Jet Bridge
The instinct after a flight is to relax for a minute. I don’t. The first five minutes after deplaning are for orientation, not decompression: check the gate for the next flight, note the walk time, and glance at whether the inbound aircraft for my connection is already at the gate. That single data point tells me more about my real time budget than the app does. If the incoming plane isn’t there yet, I’ve probably got more room than the schedule suggests. If it’s already parked and deboarding, I tighten my plan.
Only after that do I decide where to actually work. Two options, and I choose deliberately rather than defaulting to whichever is closer.
Gate Versus Lounge: How I Actually Decide
If the connection is under an hour, I stay near the gate. The walk to a club and back eats time I don’t have, and a bad boarding announcement while you’re mid-espresso in a lounge two concourses away is a bad way to start the next leg. I’ll find a quiet stretch of seating away from the boarding line, put my back to a wall so I can see the departure monitor, and get to work exactly where I am.
If I’ve got seventy-five minutes or more and the club is a reasonable walk, I’ll use it. Not for the food — for the noise floor. A gate area is a wall of announcements, rolling suitcases, and someone’s speakerphone call. A club gives me maybe twenty real minutes of quiet before I need to start heading back, and that’s often enough to finish the one task that actually requires concentration rather than just responsiveness.
The connection isn’t dead time between two flights. It’s a scheduled block with a hard deadline, which is more focus than most of my actual office hours get.
What Gets Done, and in What Order
I work in a fixed sequence, because deciding what to do next is its own kind of wasted time. First, anything time-sensitive: a call that has to happen before end of business, a decision someone is blocked waiting on, an email that unlocks someone else’s afternoon. Second, inbox triage — not answering everything, just clearing anything that takes under two minutes and flagging what doesn’t. Third, whatever single piece of real work benefits most from an uninterrupted hour. That third item only gets attention if the first two didn’t eat the whole window, which they often do.
How I Structure a 90-Minute Window
I split it roughly 45 minutes for calls and anything time-sensitive, 25 minutes for real focused work, and a firm 20-minute buffer at the end before boarding starts. The buffer is not optional. It’s the difference between calmly finding my seat and jogging down a concourse with a laptop bag banging against my hip.
Protecting the Buffer
The whole plan depends on one honest habit: building in a real buffer against a late inbound flight, not an optimistic one. If my connecting flight is scheduled to board 20 minutes before my outbound leaves, I don’t trust that number. I watch the inbound aircraft’s actual status, not just my own itinerary, because a connection is really a bet on someone else’s on-time performance. The moment a delay shows up anywhere upstream, I stop new work and shift into “close everything out cleanly” mode — send what’s drafted, note what’s pending, and get moving toward the gate. Losing ten minutes of a work session is a minor inconvenience. Missing a connection because I wanted to finish one more email is an afternoon I don’t get back.
What I Deliberately Don’t Try to Do
Ninety minutes is enough for meaningful work. It is not enough for everything, and pretending otherwise is how people end up frazzled at the gate instead of prepared for it. I don’t try to start anything that requires more than about 40 uninterrupted minutes to reach a stopping point — those tasks get worse, not better, when you have to abandon them mid-thought to board. I don’t try to eat a real meal; a protein bar and coffee at the gate beats a sit-down lunch that leaves me watching the clock instead of the work. And I don’t try to squeeze in a call that runs long by nature — a real negotiation or a sensitive personnel conversation doesn’t belong in a concourse, no matter how good the connection window looks on paper.
The goal isn’t to maximize every possible minute. It’s to be honest about what a connection is actually good for, use it well, and not let ambition about the layover put the flight itself at risk.
A genuinely distraction-light block of time with a hard deadline — more focused than most conference rooms.
It only works if you’re honest about the buffer; optimism about a tight connection is how the whole plan falls apart.
Yes — a well-timed connection at a hub is often more productive than the same 90 minutes spent at my desk.
Business travelers who can treat a layover as a scheduled work block instead of downtime to be endured.
A 90-minute connection, planned deliberately, is a legitimate piece of the workday rather than a gap in it. The traveler who treats it that way lands at the next gate already caught up, not scrambling.
Leave A Comment