Supervisors who push every call upward or who freeze when one lands in their lap haven’t failed at their job, they were simply never handed a process for deciding quickly. The fix is a repeatable approach built on three variables: how much time is genuinely available, what’s being risked against what could be gained, and where a supervisor’s authority begins and ends — run through a four-part sequence originally developed by a fighter pilot studying aerial combat. Once a supervisor can run that sequence, the calls that used to stall a shift start moving again, with nothing climbing the chain unnecessarily.
Why Good Supervisors Either Kick Everything Upstairs or Freeze
Most operations hand someone a supervisor title because they were outstanding at the job underneath it; a fair basis for promotion and not where things go wrong. The mistake is what happens next: that person suddenly fields instant judgment calls with no framework for making any of them. Predictably, two patterns take over. Either everything gets sent up the ladder regardless of whether it belongs there backing up every leader above, or the supervisor hesitates hoping the problem resolves itself before someone else has to own it.
Neither pattern says anything about character. Both are what happens when someone is handed real decision-making responsibility with no way to exercise it. There’s a subtler cost underneath, too: a supervisor who defaults to escalating starts to read that habit as evidence her judgment can’t be trusted, an erosion with nothing to do with whether her judgment was actually sound.
The First Variable: What the Clock Actually Allows
Sizing up any decision starts with a question most people skip: how much runway is genuinely there before this has to be settled? That single question reshapes everything that follows. It echoes a line often attributed to General Patton — that an imperfect plan, acted on immediately, beats a flawless one that arrives too late. A sound decision made too slowly can turn into a bad one on its own, and an unnecessarily rushed call creates problems that were entirely avoidable.
Setting a firm deadline on your own decision isn’t limiting — it’s liberating. It gives you something concrete to work against instead of drifting inside open-ended uncertainty, exactly where stalling and paralysis both thrive. Left without a deadline, a decision rarely improves while it waits. It just arrives later than it needed to.
There’s a useful layer here from military planning: leaders are taught to claim only a fraction of the available window for their own thinking, leaving the larger share for the people who’ll actually carry the decision out. It’s a built-in check against hoarding the clock — a reminder that most decisions aren’t the finish line. They’re the starting gun for someone else’s work.
The Second Variable: Weighing What’s at Stake
At its core, deciding well means holding what you might gain against what you could lose — a principle that sounds obvious right up until you notice how rarely anyone actually stops to do it. Most poor calls on a shop floor aren’t the result of a supervisor who didn’t care. They happen because nobody paused to name the trade-off before acting on instinct.
The complication is that not every risk announces itself. Cost and schedule impacts tend to be visible from a mile away; opportunity cost, flexibility, and long-range consequences are easier to miss, which is exactly why they get missed. And one part of this variable isn’t about risk at all — it’s emotional intelligence. People often latch onto whichever idea comes to mind first, regardless of whether it’s actually the strongest option — a tendency researchers call anchoring bias. Every so often, the real liability in a call is less about the choice and more about the state of mind of whoever’s making it.
The Third Variable: Knowing What’s Yours to Decide
Strong decision-makers never operate in a vacuum. Understanding exactly what falls inside your authority, and what doesn’t, is what lets a supervisor act with speed and confidence on the calls that are genuinely theirs, and pull in whoever actually owns the ones that aren’t. When those boundaries stay fuzzy, everything slows down because everyone is burning energy just figuring out whether they’re even permitted to act.
But authority only gets a supervisor partway there. The other piece is intent — the bridge between a stated mission and the judgment calls it actually requires. Authority defines what a supervisor is allowed to decide; intent shapes how she decides it well, particularly on calls no procedure ever anticipated. A supervisor fluent in both isn’t only asking whether something is permitted, she’s asking whether it serves the larger goal. That gap is what separates a decision that’s merely allowed from one that’s actually good.
The Framework: Compressing Three Variables Into Seconds
Time, risk against reward, and authority paired with intent show up inside every decision a supervisor makes. But simply naming those variables doesn’t tell anyone what to do with them in the moment — and solving exactly that puzzle became the life’s work of a fighter pilot and military strategist named John Boyd.
In the early 1950s, American-flown F-86 Sabres squared off against Soviet-built MiG-15s over Korea. Spec for spec, the MiG was the stronger machine on paper — quicker to climb, tighter in a turn. Even so, American pilots won the large majority of those engagements. Boyd’s explanation had nothing to do with the hardware; it came down to tempo. American pilots cycled through a mental loop faster than their opponents — absorb, interpret, choose, act, repeat — consistently outpacing the other side’s ability to keep up. Boyd distilled what he’d found into a four-part model now known by its initials: Observe, Orient, Decide, Act.
The three variables slot neatly inside it. The observing stage is where a supervisor takes stock of the situation and clocks the real time window. The orienting stage is where they interpret what they’re seeing through the lens of risk-and-reward and through intent — and a supervisor already fluent in that intent starts this stage from a head start rather than reading the situation cold. Deciding means committing against the deadline already set, rather than chasing an open-ended search for certainty. And acting means executing, communicating within the bounds of your authority, and looping in whoever else needs to know. A decision nobody hears about isn’t finished yet.
Putting It to Work: The Flagged-Part Scenario
Let’s return to the situation we opened on: forty units headed for a customer’s line, one flagged during final inspection for a bore that’s slightly out of tolerance, with the truck due to leave in two hours.
Observing: the supervisor confirms the flag. That single nonconforming unit is already routed into the standard quality process and won’t clear in the available window — that part of the problem is out of her hands. The real question in front of her is narrower: what happens to the other thirty-nine parts while the flagged one works its way through a process she doesn’t control?
Orienting: she checks her read against what’s actually true — the customer’s line isn’t casually waiting on this shipment, it’s stopped because of it. Holding back all forty penalizes them for an issue confined to a single unit.
Deciding: she sets herself a fifteen-minute window to confirm logistics can split the load, then commits — ship the thirty-nine good units on the truck as scheduled and hold the one flagged part back to move separately once it’s cleared.
Acting: she signs off on splitting the shipment, flags the held-back unit as a priority with quality so it doesn’t stall in line, then picks up the phone and tells the customer herself, ahead of any delay they might otherwise notice. The question of how the defect slipped through goes into her notes for the next process review, not something that needs solving before the truck pulls out.
Two hours spent standing over one flagged part turns into a clean, well-documented call inside her own authority — one that keeps the customer’s operation moving instead of halting it a second time.
The Real Cost of Never Building This Skill
Skip installing this skill on purpose and the costs stack up both ways. Supervisors who escalate everything climb the chain out of reflex, not need — pulling senior leaders away from work only they can do while signaling to your strongest people that their own judgment isn’t trusted. Supervisors who freeze hand you a floor that moves only as fast as their hesitation and every pause carries a real cost in output and quality.
Neither outcome says much about the individual supervisor; it says something about what they were never handed in the first place. An organization that keeps assigning decision-heavy roles without ever building the underlying skill is asking its strongest performers to carry a gap that was never theirs to close.
Four Prerequisites for Making This Stick
Building this comes down to four things.
First, make authority genuinely explicit — defined and communicated, so supervisors know which calls belong to them.
Second, keep intent something a supervisor can restate in her own words, not something buried in a strategy document; if she can’t say what her shift is trying to get done this week, orienting collapses before it starts.
Third, grant clear permission to decide without defaulting to escalation — if every call still travels up the chain out of habit, nothing has actually changed except how your supervisors feel.
Fourth, build in repetition: debriefs, scenario rehearsals, a standing habit of asking to talk through how they read the situation, not just what they decided. Reflexes that hold up under real pressure get built ahead of time, in the calm stretches between decisions — never in the decision itself.
What Changes When Supervisors Can Own the Call
Picture a floor several months into this work: a flagged part shows up and the supervisor standing over it doesn’t wait for you to weigh in. She’s already sizing up her real time window, weighing what’s genuinely at stake, and acting inside authority she understands — because someone built that capability on purpose instead of hoping it would show up on its own.
Escalations start reflecting genuine judgment calls instead of habit. Senior leaders get their time back for decisions that are actually theirs. And your strongest supervisors stop quietly second-guessing themselves every time a call lands in their lap.
If you’re watching good people escalate everything or freeze, three or four levels deep in your organization, that’s the gap our system is built to close. Learn more at operationlead.com.
Let’s Lead,
Craig
