Introduction
It’s 2 p.m., the waiting room is full, and your scheduling system just froze. Or a patient in the lobby is in real distress. Or insurance flags something wrong right as a patient’s being walked back. Whatever it is, there’s no time to think it through — someone has to act in the next thirty seconds, and whatever happens next depends entirely on whether anyone actually knows what to do.
Two real flights, decades apart, show exactly what separates a crisis that gets handled from one that doesn’t. The difference wasn’t luck, and it wasn’t which pilot was more skilled. It was whether a process built beforehand actually got followed under pressure — and whether anyone was allowed to speak up when it wasn’t.
One Crew Followed the Process. The Other Crew Had One Person Who Wouldn’t Be Questioned.
In January 2009, a flock of geese took out both engines of an Airbus just after takeoff from LaGuardia. The pilot had seconds to decide there was no way back to any runway. What actually got 155 people out alive wasn’t a single heroic decision — it was a crew that had run through their emergency checklist together before the flight even started, so that when the moment came, everyone already knew their role and executed it without hesitation. The co-pilot worked through every restart option in the manual while the captain focused entirely on the landing. Nobody was improvising. Everybody had already rehearsed this.
Compare that to a runway in Tenerife decades earlier, where a respected, experienced pilot misheard clearance from air traffic control and began takeoff with another plane still on the runway ahead of him. His co-pilot voiced concern — once — and was overruled. He didn’t push back a second time, because the pilot in that seat was too well-regarded to question twice. 583 people died. The failure wasn’t a lack of skill. It was a process that depended entirely on one person’s judgment being correct, with no real mechanism for anyone else to stop it if it wasn’t.
Your Front Desk Runs on One of These Two Models — You Just Might Not Know Which One Yet
Most practices think they’re closer to the first story. In practice, a lot of them are quietly closer to the second, without anyone intending it. It shows up in small ways: a scheduling conflict that everyone defers to the most senior person to sort out, even when they’re wrong. A new hire who notices something off about how a chart was handled, but doesn’t say anything because it’s not really their place. A front-desk emergency — the 2 p.m. moment — where there’s no agreed-on process, just whoever’s most confident in the room making the call under pressure.
The Sully flight worked because the emergency response wasn’t invented in the moment — it existed beforehand, everyone had trained on it, and the structure of the crew meant multiple people could act and speak up simultaneously instead of waiting on one person’s authority. The Tenerife flight failed because none of that existed — there was one authority, no real mechanism to challenge a bad call, and a co-pilot who tried once and stopped.
What This Actually Looks Like Off a Runway
You don’t need an emergency response plan as dramatic as either of these stories, but you need the same two ingredients: a process that exists before the bad moment happens, and a culture where the person who notices something’s wrong is expected to say so — not just once, quietly, and then defer.
That means having an actual, written response for the situations that do happen at a front desk under pressure — a patient having a medical event in the waiting room, a system outage mid-day, an insurance issue discovered right as a patient’s about to be seen — so nobody’s improvising the first response from scratch. And it means making it explicit, out loud, that if your front desk or your newest hire notices something’s off, they’re expected to say so more than once if the first attempt gets brushed aside — the same gap that turned a misheard instruction into the worst crash in aviation history.
Try This
Pick one real 2 p.m. moment that’s happened at your practice in the last year — even something as ordinary as a patient having a reaction in the waiting room or the system going down during a full schedule — and write down, step by step, what actually should happen next time, before it happens again. Then ask your newest or most junior staff member directly: if you noticed something was about to go wrong, would you feel comfortable saying so twice? If the honest answer is no, that’s the gap worth closing before the next bad moment, not after it.
