What is the sterile cockpit rule and how does it apply to work?

It's an aviation regulation (14 CFR 121.542) that bars flight crews from any non-essential activity during "critical phases of flight"—taxi, takeoff, landing, and everything below 10,000 feet. Applied to work, the sterile cockpit rule means naming your team's high-stakes, attention-critical phases (incidents, deploys, deep-work blocks) and making non-essential interruptions off-limits during exactly those windows—then reopening the channel the moment the phase ends.

Does a sterile cockpit rule mean no Slack or no talking at all?

No, and that's the most common misreading. Even in a real cockpit, pilots talk freely at cruise—the restriction is phase-specific, not a vow of silence. NASA itself calls expecting constant silence "unrealistic." For a team, it means full availability between critical phases and protection only during them. You're not banning communication; you're scheduling it around the moments where an interruption does real damage.

How much does one interruption actually cost?

Far more than the seconds it takes. University of California research by Gloria Mark found it takes roughly 25 minutes to fully return to an interrupted task, and that average attention on a single screen has dropped to about 47 seconds. That gap between the 30-second question and the 25-minute recovery is the true context switching cost—and the reason protecting focus is worth a formal rule rather than a vague aspiration.

How do you protect focus without making people unreachable?

You keep the break-glass open. A sterile cockpit still has a radio for genuine emergencies; your version needs a clearly defined escalation path—a page, a call, or an agreed "real emergency" signal—that everyone trusts is reserved for true blockers. Bounded async availability plus a respected emergency channel lets people go heads-down without anyone fearing a real fire will go unseen.

How is this different from just having no-meeting blocks?

No-meeting blocks remove scheduled meetings; the sterile cockpit rule removes all non-essential interruptions—pings, "got a sec?" DMs, drive-by questions—during defined critical phases, and it ties the protection to a visible phase rather than a fixed calendar slot. No-meeting blocks are one tool inside it. The rule is the broader norm: protect the phase, name what's allowed to break it, and call "cruise" when it's over.

The Sterile Cockpit Rule for Remote Teams

There is a federal regulation that makes it illegal for an airline pilot to talk about their weekend. Below 10,000 feet—during taxi, takeoff, and landing—U.S. flight crews are legally barred from any conversation that isn't about flying the plane. It's called the sterile cockpit rule, and the regulation that defines it is blunt: "No flight crewmember may engage in, nor may any pilot in command permit, any activity during a critical phase of flight which could distract any flight crewmember from the performance of his or her duties."

That rule was written in blood. And your team has critical phases too—the deploy, the incident, the two hours of deep work a hard problem actually needs—except almost nothing protects them. Meanwhile, focus is collapsing. The workplace-analytics firm ActivTrak reported in 2025 that as AI spread through the workday, "AI users show consistently longer workdays (+8 mins) and lower focus time (-27 mins)." We handed everyone a faster engine and quietly paved over the runway.

This piece is about borrowing aviation's fix. You'll see what the sterile cockpit rule actually means (it is not "be quiet"), why "always be available" is the wrong default, and a step-by-step way to install the sterile cockpit rule on a distributed team.

What the sterile cockpit rule actually means

Most people who borrow the phrase get it backwards. They hear "sterile cockpit" and picture grim pilots in total silence, white-knuckling their concentration through sheer discipline. That's not it at all.

The rule is not about silence. It's about phase. The regulation applies only during "critical phases of flight"—defined as "all ground operations involving taxi, takeoff and landing, and all other flight operations conducted below 10,000 feet, except cruise flight." At cruise, pilots can talk about used cars all they want. The rule doesn't demand constant focus. It draws a bright line around the moments that can kill you and protects only those.

It's also not about willpower. NASA's Aviation Safety Reporting System, in a classic analysis of sterile-cockpit violations, is refreshingly human about it: "It's unrealistic to expect a crew to fly together for several days and never discuss anything except items related to flying the aircraft." The point was never to turn pilots into robots. It was to make protection automatic during the windows that matter, so no individual has to decide, mid-approach, whether now is a good time to bring up the oil crisis.

And it exists because people died. On September 11, 1974, Eastern Air Lines Flight 212 went down on approach to Charlotte, killing 72 of the 82 people aboard. The cause wasn't weather or a mechanical failure. As the accident record puts it, "both flight crews became engrossed in other conversations unrelated to the flight operation, ranging from politics to used cars, particularly focusing on the 1973 oil crisis." The NTSB's probable cause was "the flight crew's lack of altitude awareness at critical points during the approach due to poor cockpit discipline." Seven years later, the FAA made the rule federal law. The most habitually cited offense in those NASA reports, for the record, was something thoroughly ordinary: "extraneous conversation between cockpit crew members."

So strip it down. The sterile cockpit rule is not silence, and it is not grit. It's a phase-gated norm: identify the windows where attention is load-bearing, then make non-essential interruptions structurally off-limits during exactly those windows—and only those.

Your team flies below 10,000 feet more than you think

On a plane, the dangerous phases are obvious and visible to everyone: the runway, the climb, the approach. On a distributed team, the critical phases are invisible. There's no landing gear thunking down to tell the cabin that someone is in the middle of something fragile. The engineer untangling a race condition, the writer holding a whole argument in their head, the on-call responder reading a stack trace—each is flying an approach, and the rest of the company has no idea.

So you get pinged. And the brutal part is that the cost of the interruption is almost never the interruption. The University of California's Gloria Mark, who has logged knowledge workers' attention for two decades, found that after being pulled off a task "it takes about 25 and a half minutes to pick up that original interrupted project." Her data also shows average attention on any one screen has fallen to "about 47 seconds." A "quick question" is not quick. It detonates the next half hour.

Engineers have always known this in their bones. As one put it on Hacker News: tapping someone in flow "leads not only to immediate destruction of mental state"—the lucky version is when "you get an IM along the lines of 'Got a sec?' and you can gracefully swap that mental state out to disk and address the question." The mental state is expensive to load and easy to lose. That's the real context switching cost, and it is exactly what aviation decided was too dangerous to leave to chance.

The trouble is that a remote workday is one long invitation to break the phase. Every Slack ping, every "@here," every calendar nudge is a hand reaching into the cockpit. Left unmanaged, notification overload turns every critical phase into Flight 212: a competent crew, a working aircraft, and a conversation that should have waited. (For the deeper economics of the switch itself, see our breakdown of the cost of context switching; the sterile cockpit rule is the upstream fix—it stops the switch from happening during the windows you can least afford it.)

Why "always be available" is the wrong rule

Let me steelman the default first, because it isn't dumb. Responsiveness is a real virtue on a distributed team. When you can't lean over a desk, being reachable is how you unblock a teammate in another time zone, how you keep async work from stalling for a day over a one-line answer. "Always be available" grew out of a genuine good: don't be the bottleneck.

But here's the trap. Availability is the right setting between critical phases and a hazard during them. The rule quietly mutates from "be reachable when it helps" into "be interruptible at all times," and at that point you've banned cruise-altitude chatter from happening and mandated it on every approach. An interruption during a critical phase isn't collaboration. It's the used-cars conversation—well-meaning, perfectly normal, and landing at the exact wrong moment.

This is why async availability has to be bounded, not absolute. The most counterintuitive part of the aviation answer is that protecting the window makes the team more collaborative overall, not less—because the alternative is a workforce that never actually finishes the approach. The numbers bear this out. When researchers studied protected time in MIT Sloan Management Review, cutting meetings by 40% made "productivity to be 71% higher because employees felt more empowered and autonomous," and deeper cuts dropped the "risk of stress" by 57%. Guarding the phase doesn't cost you cooperation. It buys it.

None of this means going dark. A sterile cockpit still has a radio—the tower can always reach the crew about something that actually matters. The skill isn't choosing between "always on" and "never reachable." It's the same judgment a pilot makes flying on instruments: trust the protected procedure during the critical phase, and keep one channel open for the genuine emergency. Real deep work for remote teams depends on that distinction, not on heroics. It's also the difference between a sterile cockpit and a squelch threshold—squelch filters low-level noise continuously, all day; the sterile cockpit rule is binary and time-boxed: full protection during the phase, full openness after it.

How to install the sterile cockpit rule on your team

A cockpit doesn't stay sterile through good intentions. It stays sterile because the rule is explicit, shared, and tied to a phase everyone can see. Here's how to translate that into a distributed team.

Define your "below 10,000 feet"

Pilots don't argue, in the moment, about whether this counts as a critical phase—the altitude decides for them. Your team needs the same pre-agreed list. Write down the handful of states where attention is genuinely load-bearing: an active incident, a production deploy, the final day before a launch, and individual deep-work blocks for work that requires sustained focus. If everything is critical, nothing is—keep the list short and real. This is the foundation of protected focus time: a phase has to be named before it can be defended.

Signal the phase, not the person

The single biggest mistake is making this about individuals ("leave me alone") instead of phases ("we're below 10,000 feet right now"). A status of "heads-down until 11" or an incident channel marked in approach is a phase signal—it's temporary, it's legible, and it doesn't read as "this person is unfriendly." Remote teams fail here because the cockpit is invisible: in a room you can see someone is wrecked, but on Slack you can't tell an engineer has been on final approach for two hours. Make the phase show up where the work happens, so the next person sees the gear is down before they reach for the channel.

Write the "essential only" list

The regulation works because it names what's allowed: duties "required for the safe operation of the aircraft," and nothing else. Do the same. Decide, in advance, what is permitted to break a critical phase—prod is down, a customer-facing outage, a true blocker with a hard deadline—and agree that everything else waits for cruise. The goal is to minimize interruptions for a remote team without anyone having to adjudicate each one live. When the rule is written, "could this have waited?" stops being a personal judgment and becomes a shared standard.

Keep the break-glass open

A sterile cockpit is not radio silence, and your version can't be either. The fastest way to kill the rule is to make people afraid that a real emergency will sit unseen. Define the escalation path explicitly: a page, a phone call, an "@here—genuine emergency" convention that everyone trusts is reserved for exactly that. When the break-glass is real and respected, people stop pinging "just in case," because they know the true signal will always get through.

Call "cruise" out loud

The rule has an end as much as a beginning. A phase that never officially closes becomes a person who is simply never reachable—and that's how you breed resentment and quiet quitting of the rule itself. End the block out loud: "out of the deploy, back online," "incident resolved, channel open." This is where no-meeting blocks and focus windows earn their keep instead of curdling into permanent unavailability. Protect the approach, then genuinely reopen the cabin.

It helps to run all of this where the work already lives. A shared canvas that shows the team's current "altitude"—what phase each piece of work is in and who owns it—paired with AI that follows both the board and the conversation, the way Coommit is built to, means the moment a phase ends, the next person can pick it up with full context instead of a cold start. Practitioners reinvent this constantly; one manager's entire prescription on Hacker News was "no meetings/standups in the morning — no email/slack/phones in the morning. Try to create an environment where people can work 3-4h without stupid interruptions and do some deep work." That's a sterile cockpit. They just didn't have the name for it. (And when the phase is recovery rather than focus, the same discipline is what makes a real safety stop after crunch actually restful instead of fake.)

What the cockpit knows that your calendar doesn't

Your calendar shows you meetings and free slots. It does not show you altitude. It can't see that the empty hour you're about to fill with a "quick sync" is someone's final approach—or that the back-to-back day you scheduled is one uninterrupted descent with no protected phase anywhere in it, the kind of fragmentation that makes Parkinson's law swallow your meetings whole.

Aviation figured this out the hard way, and then it made the fix a law. The sterile cockpit rule isn't about working harder or talking less. It's a single, structural idea: name the phases that can hurt you, protect them automatically, and open everything back up the moment they're over. As AI keeps making every individual faster while shredding their focus time, the teams that win won't be the ones who are always on. They'll be the ones who learned to call a sterile cockpit—and mean it. Name your "below 10,000 feet" this week, signal one phase where your team isn't to be disturbed, and watch how much of the approach you were quietly crashing.