Pause for a second and picture your most reliable frontline supervisor — the one you’d send into a fire if you only had one to send.
Now picture the last problem they walked into your office with.
What did they actually ask you?
If you’re like most senior operations leaders I talk to, they didn’t bring you a recommendation. They didn’t bring you a structured set of alternatives. They didn’t even necessarily bring you a clearly framed problem. What they brought you was some version of: “Boss, what do you want me to do?”
You answered. They went and did it. The shift kept moving. Nobody noticed.
But something quiet just happened in your operation, and it happens dozens of times a day across the floor. A decision that should have been made three layers down was just made one layer up. The supervisor who needed the rep to grow into the role didn’t get one. The leader who needed the time to lead the operation just gave that time away. And the cycle that defines most struggling operations got a little more entrenched.
This week, I sat down with Christopher Seifert — a global manufacturing executive, author of Enabling Empowerment, and a former U.S. Navy submariner who spent his early career operating inside one of the most demanding decision-making cultures in the military. Chris isn’t just an expert on decision-making; he’s an expert on developing decision-makers in some of the most high-pressure environments.
The Micromanagement Doom Loop
The most expensive misread in operations leadership is the one that frames micromanagement as a personality flaw.
It almost never is.
The vast majority of leaders who micromanage do not want to. They are running the operation the only way they know how to keep it from breaking. Chris named the pattern they get stuck in the Micromanagement Doom Loop:
A senior leader decides their team needs to start owning more decisions. They announce it. They mean it. The team — never coached on how to actually think through a decision under pressure — makes a series of bad calls. The bad calls produce bad results. The senior leader catches heat for the bad results. The senior leader pulls back into command-and-control to stabilize the operation. And the team, already shaky, now reads the entire arc as confirmation that the leader never really wanted them to make the call in the first place.
The next attempt is harder than the first. The one after that is harder than the second. Eventually, leadership stops trying.
What looks like a micromanagement problem is almost always a development problem in disguise.
Why Your Supervisors Default to Asking Instead of Deciding
When a supervisor walks into your office with a problem and no recommendation, three things are usually true at once.
- The first is that they have never been taught a process for thinking through a decision. Not in school. Not in onboarding. Not in any program your organization has ever run. Decision-making, despite being one of the most consequential skills in any operating role, almost never appears on a development curriculum.
- The second is that asking is safer than recommending. If they ask and you answer, the outcome is your problem. If they recommend and the outcome goes sideways, the responsibility is theirs. In an operation that has historically punished bad outcomes more than it has rewarded good thinking, the math gets very predictable very fast.
- The third is that the leader above them is, often unconsciously, optimizing the same way. It is faster — in the moment — to give the answer than to walk a supervisor through the framework of arriving at one. The cost of that shortcut is invisible the day you take it, but it compounds quietly into a culture where nobody three layers down is ever expected to think.
That is not a culture anybody intended to build, yet is unknowingly formed time and time again.
The Cognitive Biases Already Working Against You
Before any framework can land, frontline leaders have to understand that the brain they’re bringing to the decision is not neutral. It is a pattern-matching machine, optimized for speed, with several failure modes that hit hardest in exactly the situations that matter most.
Three of them show up daily on a manufacturing floor.
The framing trap. Most supervisors accept the problem as it’s presented to them. “We need to fix this machine” leads to a different solution set than “we need this line producing again by 2pm.” Reframing the problem is the single most underused move in frontline decision-making.
Anchoring bias. The first piece of information given carries more weight than it should. The first idea proposed in a huddle quietly becomes the gravity well every other idea has to fight against. Anyone who has ever led an emergency response knows this — the loudest first idea usually gets defended, even when it is not the best one.
Hindsight bias. After the fact, every leader tends to believe they could have known more than they actually did. So decisions get judged on outcomes rather than on the quality of the analysis that produced them. Chris’s example sticks: drive home drunk, make it home safe, and you did not just make a good decision. You got a good outcome from a bad one. Until an organization can separate the two, it cannot coach its leaders to make better calls.
A real decision framework is not just a thinking aid. It is an active push against these defaults.
A Framework Built for the Floor and the Boardroom
Chris teaches a seven-step decision framework deliberately built to scale up or down based on the stakes of the call. The steps are simple. The discipline of using them is not.
First, frame the problem — and ask whether the way it has been framed is the best way to frame it.
Second, brainstorm a range of alternatives before defending any of them.
Third, identify the key drivers — the one or two variables that have to go right for this decision to succeed.
Fourth, think through the best case and the worst case for those drivers, and what would have to be true for each.
Fifth, do the math on the alternatives against those drivers.
Sixth, make the call.
Seventh, show your work — write down the alternatives considered, the drivers, the best and worst case, and the choice. The next decision-maker who has to read it gets a coaching artifact. The one who wrote it gets a reference point that makes hindsight bias harder to play.
The most important sentence in that framework is the first one: the rigor with which you apply this should match the stakes. A 20% production loss does not require what a life-safety call requires. The framework is the same; the application scales.
What Changes When the Recommendation Replaces the Question
Inside an operation, the most powerful version of this is also the simplest.
Stop accepting “What do you want me to do?” as a valid opening line.
Start requiring “Here is my recommendation” — delivered in the structure above. Frame. Alternatives. Drivers. Best and worst case. Recommendation, with reasoning.
Two things change immediately. The supervisor making the recommendation now owns it — they cannot fall back on “I just did what you told me.” And the senior leader hearing it gets a coaching surface. You are no longer reacting to a problem; you are evaluating a process. The question shifts from “Did this go well?” to “Was the thinking sound?” That is the only question that produces leaders who get better over time.
Why Process Beats Data Every Time
One of the most counterintuitive points Chris made in the conversation: when you study what actually correlates with good decision-making across organizations, the discipline of the process tends to outweigh the quality of the data. The reason is intuitive once you sit with it. A disciplined decision-making process surfaces the data you don’t have. Better data inside a sloppy process tends to get swallowed by the very biases the framework was designed to defeat.
For senior operations leaders, that is the case for treating decision-making as a core competency of the organization — not a personality trait of a few good supervisors. It is teachable. It is coachable. It scales. And the longer it goes uninstalled, the more decisions you’ll keep making three layers up that should have been made three layers down.
Where to Start This Week
Pick one direct report. The next time they walk into your office with a problem, do not answer the question. Hand them the four-line structure: Frame. Alternatives. Drivers. Recommendation. Tell them to come back in twenty minutes.
When they come back, do not grade the recommendation. Coach the thinking. If a key alternative is missing, name it. If the drivers are wrong, ask why. If the worst case is unaccounted for, work it through together.
Do that ten times and you will have built something most operations never bother to build: a leader who can think. Do it across the team and you will have built the start of an operating system.
The frontline stops being your bottleneck the moment your frontline leaders stop bringing you the questions and start bringing you the calls.
Let’s Lead,
Craig
