The Certainty Trap
Why organisations stop learning precisely when they need it most
You can feel it the moment you walk into a boardroom that’s about to break. Not long ago, Jason L Zimmerman sat with a Board of Directors that had less than 48 hours to secure a massive cash injection to cover payroll. Without it, hundreds of employee wages would bounce, institutional creditors would call in debts, and an enterprise that had spent thirty years building market trust would start collapsing.
The crisis wasn’t driven by inferior service or bad frontline delivery. This was a pure liquidity stranglehold.
In moments like that, the pressure is felt in the gut. It’s the sudden realisation that you are carrying the weight of hundreds of families who rely on that money, alongside customers (patients, in this case) whose care is hanging in the balance. It’s a tangled mess of competing priorities, and the sheer ambiguity of it can feel suffocating. When the conversation starts to spiral, the natural knee-jerk reaction is simply to act, because action feels non-negotiable.
However, complex situations hide secondary dangers. Acting decisively on what you can see does nothing about what you cannot, and the visible problem is rarely the whole of it. The craving for a clear answer is itself part of the trap, because it makes the partial picture in front of you feel like the full one.
When you reach that level of duress, pressure does something dangerous to human cognition: it destroys the capacity to see clearly.
Speed pulls against accuracy, while anxiety narrows what leaders can see. So leaders begin making high-velocity decisions based on partial truths, unintentionally creating second- and third-order consequences that amplify the original disaster.
In that specific event, board members personally advanced the funds to bridge the immediate payroll gap. It bought them three weeks. But it also fired the starting gun on a deeper investigation: discovering how they could lose sight of a multi-million-dollar pillar of stability so fast.
The crisis in that room was treated as a financial one. In reality, it was an epistemic crisis: a total breakdown in the organisation’s ability to know what was actually happening inside its own walls.
The pressure dial
Pressure doesn’t simply switch from “normal operations” to “catastrophe.” In our work with leadership teams, we view pressure as a fluid dial from 1 to 10. For example:
Dial 3 (tense project review): A missed milestone leads to filtering of uncomfortable details.
Dial 5 (customer churn): Declining performance causes teams to protect their own functions; silos begin to optimise for survival.
Dial 7 (acute cash strain): Board scrutiny increases, authority centralises, and meeting rooms shrink.
Dial 10 (imminent collapse): Total operational or solvency crisis. Dissent is reclassified as delay.
As the dial turns, curiosity slowly becomes a luxury, which is a predictable behavioural response. The structural research of Barry Staw and the cognitive insights of Karl Weick show us exactly why this happens. Staw’s work demonstrates that organisations under threat naturally restrict information, rely on familiar routines and centralise control. Meanwhile, Weick explains that, under acute stress, our collective capacity to make sense of an unfolding reality completely collapses.
When the fast answer is the expensive one
In high-stakes environments, speed is often non-negotiable. Indeed, delay is irresponsible when payroll must be funded or operations have halted. The strategic error is to confuse the speed of an action with an understanding of the problem.
To see how high-speed, centralised answers create systemic failures, look at wildland firefighting.
When a wildfire suddenly undergoes a violent “blowup” and jumps a control line, the pressure dial hits a 10. The instinctive response is aggressive: throw resources at the visible head of the flame immediately, to suppress the fire. Taking action feels like safety. But a wildfire is an interlocking system of fuel, terrain and shifting winds. If a command team orders a direct attack without analysing the broader topography, real disasters can happen.
High-Reliability Organisations survive these environments because they maintain an operational protocol known as LCES: Lookouts, Communications, Escape Routes and Safety Zones.
The critical node is the lookout. In the case of firefighting crews, a lookout is often a junior firefighter positioned on a distant ridge. They have no authority to direct heavy machinery, but they hold the one asset the commander lacks from deep inside the action: an uncompromised view of the horizon. In a disciplined system, the data provided by the lookout can instantly override the strategic plan of the command post. Speed is maintained, but it is explicitly bound to real-time, distributed data from the edges.
The Art of Asking Questions is a reader-supported publication. To support my work, please consider becoming a paid subscriber.
Four questions to open the room
To keep an organisation effective under strain, a leader must shift from a commander dictating answers to an epistemic facilitator, someone who manages the flow of collective intelligence rather than the execution of a singular will.
You need structural circuit breakers to make this happen, as good intentions are not enough. In our practice, we use four diagnostic questions to stop a room from closing too early:
🍾 1. Leveraging small wins to lower anxiety
A large-scale threat can paralyse an organisation because its sheer scale overwhelms what a human brain can hold. To lower collective anxiety and restart your team’s ability to think creatively, shrink the operational horizon by asking:
We cannot fix the entire system today. What is the most meaningful problem we can completely solve in the next 24 hours?
🪓 2. Dropping clunky tools that are slowing things down
This stems from Karl Weick’s landmark study of the 1949 Mann Gulch fire disaster, where firefighters being overtaken by the blaze refused to drop their heavy tools to run faster, perishing with their axes and shovels in hand because those objects defined their professional identity. Teams routinely cling to legacy processes and metrics out of habit, even when the environment changes. Ask your team:
What metric, workflow, or legacy habit are we carrying out of comfort that we need to publicly drop to move faster?
🫡 3. Listening to the lookout for frontline perspectives
Under stress, executives instinctively pull decision-making power to the top, isolating themselves from the frontline operators who actually hold the data. Before committing to a high-velocity path, pause the room and ask:
Who is closest to where this decision will actually land, and what do they see that contradicts the strategy we are building?
♦️ 4. Red-teaming the label to shift the macro perspective
The anxious brain craves a simple, clean label (”market failure,” “PR disaster”) just to relieve the short-term stress of ambiguity. Simple labels yield generic, blunt-force solutions. Force a cognitive pivot by asking:
Suppose our diagnosis is wrong. What structural issue might we be missing?
Check out this video discussion with Peter S. Bergeron to learn more about navigating ambiguity in your business. 👇
Turning the Dial Back
Returning to the distressed organisation from our opening, the emergency funding advanced by the board bought time, but it did not solve the structural blindness that caused the cash drain.
The turnaround began when the team understood that they could not fix a multi-million-dollar collapse in a single stroke. They used the first question to solve for immediate threats and begin restoring collective trust. They dropped legacy metrics that were hiding operational friction to begin seeing the problem differently. Simultaneously, they invited site-level directors to offer new perspectives from across the organisation. Importantly, they used the fourth question to stop treating their issues as a standard cash shortfall and begin diagnosing the deeper errors that caused the blindness in the first place.
Today, that organisation not only survived that three-week runway, but are beginning to transform how they operate. Their view is extending a bit further out toward the horizon, and they are actively working to recover their most critical asset: the capacity to learn from their own operations
The fundamental test of leadership under duress is not whether an executive can produce a confident answer. Most can. The harder, more significant question is whether they can preserve the organisation’s intelligence while doing it.
About Jason L Zimmerman: 3Fold Outcomes unpacks why some strategies quietly succeed while the vast majority (>70%) unravel. Jason writes for those leading change in the real world: executives navigating complexity, operators trying to move systems, and curious minds who know that culture eats strategy only when strategy ignores culture.
Enjoyed this piece? Become a paid member and get my Consulting with AI prompt library, the full Asking Questions Like a Pro course ($199 standalone), practical templates from a decade of fieldwork, and discounts on many other resources. 🔗 See everything included in the paid tier.
 | A guest post by
|
What you’re describing as anxiety narrowing the field is also a perception problem, because a stressed leader doesn’t just move faster, they literally take in less data while believing they’re seeing the whole board. Great article!
Perhaps it's the current time of the year, but your forrest fire analogy is appropriate. Organizations are all 'unique' in many ways and classic/standard organizational structures are not always appropriate for every business. However, the one KEY common strength is honesty. When that is misplaced or disappears entirely - especially at the CEO level the organization is doomed and dies. Sometimes the CEO is actually charged and convicted of criminal action. We learned a lot from that experience.