<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=749646578535459&amp;ev=PageView&amp;noscript=1">

The Certainty Trap: Why Feeling Sure Is the Warning Sign, Not the Goal

Posted by Jeff Roussel

Find me on:

Jul 20, 2026 3:30:01 AM

There's a feeling that arrives when you've finished analyzing a problem and arrived at the answer. It feels like clarity. It feels like having done the work. It feels like being right.

That feeling, according to Dr. Mark Jaben, is the warning sign.

Jaben — a board-certified emergency physician who spent years studying the neuroscience of change after watching the same Lean methodology succeed in some implementations and stall in others — calls certainty a red flag. Not metaphorically. Operationally. When you feel certain about a decision, your brain has stopped processing alternatives. The analytical functions you'd need to actually evaluate whether your answer is the best one are no longer doing analysis. They're doing defense.

This runs against most of what corporate culture rewards. Leaders are supposed to be decisive. Confidence is a virtue. The person who can walk into a meeting and state the answer cleanly is treated as credible in a way the person who says "I'm not sure yet" usually isn't. Certainty is the currency of leadership in most organizations, and the willingness to project it — even when it isn't quite justified — is rewarded explicitly and implicitly across nearly every promotion decision.

The neuroscience tells a different story about what's actually happening when that certainty appears.

The press secretary problem

Here's the mechanism Jaben walked through in his webinar. What the researcher Shankar Vedantam calls the hidden brain — processing that happens before awareness reaches consciousness — does most of the work of forming opinions and reaching conclusions. It searches stored patterns, finds one close enough to match the situation, weighs benefits and risks based on the person's worldview, and selects a story. The story arrives in consciousness as a feeling: this is the right answer, this is the wrong answer, I'm not sure about this one yet.

Only after the story has been selected do the analytical functions get involved. And they don't analyze. They construct the case for whatever the hidden brain selected. They gather supporting facts. They marshal relevant memories. They produce the rationalization that makes the conclusion feel rigorously arrived at.

Jaben calls this the press secretary problem. Your analytical functions aren't a panel of judges weighing evidence. They're a press secretary defending a decision that was already made somewhere else in the building — and the press secretary is very good at the job. By the time you walk into the meeting with your answer, your analytical functions have already gathered the supporting evidence, anticipated objections, and prepared responses. You feel certain because the press secretary has done thorough work.

The trap is that the press secretary cannot tell you whether the original decision was right. The press secretary's job is to defend it.

A Gregory Berns study using functional MRI made the underlying biology visible. Participants describing strongly-held views showed amygdala activation — the brain's threat-response center, the part that secretes adrenaline and prepares the body to fight or flee. When the same participants were offered a financial incentive to consider changing their position, those who accepted showed activity in the prefrontal cortex instead — the part of the brain responsible for analytical comparison. The same person, on the same topic, was capable of either response. But while they were defending the strongly-held view, their brain was operating in fight-or-flight mode. The neurochemistry of certainty is not the neurochemistry of analysis.

Why we default to certainty

The brain prefers certainty for a structural reason: it costs less energy than the alternative. Once a story has been selected and defended, the cognitive work is essentially done. You can act on it without continuing to deliberate. The conclusion can stay stable across conversations, meetings, and decisions, without requiring you to re-derive it from scratch each time. Energy conservation is one of the deepest patterns in how the brain operates, and certainty is one of the most reliable energy-saving moves it can make.

The opposite state — what Jaben calls ambivalence — is expensive. The brain has to actively hold multiple possibilities open, weigh competing criteria, consider information it would prefer to dismiss, and tolerate the discomfort of not knowing yet. Ambivalence is the neurochemistry of the prefrontal cortex doing genuine analytical work, and that work is energy-intensive enough that the brain will avoid it whenever possible.

Most workplace decisions also reward speed over depth. The leader who deliberates publicly is often perceived as weak, while the leader who arrives at meetings already certain is perceived as decisive. Quarterly cycles reward decisions made and announced, not decisions thoroughly examined. The result is a system that systematically pushes people toward press-secretary mode and away from genuine analysis, even when the situation calls for the latter.

This is the deeper version of what Dan Markovitz calls the conclusion trap. In his book and in his webinar, Markovitz walks through three patterns he watched leaders fall into across years inside operating companies and as a consultant: throwing money at problems, reorganizing, and buying technology. The logistics company president who wanted a smartphone app to solve what was actually a sales commission problem. The companies that reorganize from functional to matrix and back without addressing what was actually broken. The technology purchases that produce broken processes running faster.

Markovitz's framing maps directly onto Jaben's. The leaders in those stories weren't reasoning their way to bad conclusions. They were operating from certainty — the press-secretary version of decision-making — where the hidden brain had already selected an answer that pattern-matched to something familiar, and the analytical functions were busy defending it rather than examining whether it actually fit the situation.

What certainty looks like in practice

The patterns are recognizable once you start watching for them.

A leader walks into a problem-solving session having already decided what the team should do. The session is run, the team contributes ideas, the leader nods at the right moments — and the original predetermined answer is the one that gets implemented. The session wasn't analysis. It was theater performed around a conclusion that was already certain.

A CI team rolls out a methodology that worked beautifully at one facility into another facility where conditions are different. The methodology is identical. The leaders championing it are certain it will work because they watched it work somewhere else. The frontline reception is cold. The implementation stalls. The team's response is to push harder on the methodology, because the methodology is known to work — the certainty about it never gets re-examined against the actual conditions of this facility.

A senior leader requests an analysis from the team. The team produces the analysis. The conclusion doesn't match what the senior leader expected. The senior leader sends it back with questions about methodology, asks for a sensitivity analysis, requests a different framing. The questions are reasonable on their face. They're also the press secretary at work, finding reasons the inconvenient conclusion might be wrong rather than examining whether the original expectation might have been.

A continuous improvement leader presents a proposal to a plant manager who pushes back. The CI leader interprets the pushback as resistance to change and produces more data. The plant manager produces more counter-questions. Neither person is actually analyzing the other's position because both are certain — and the conversation is, as Jaben calls it, dueling solutions. Two press secretaries defending two predetermined conclusions, neither one available for genuine reconsideration.

The common thread is that certainty closes off exactly the inquiry that would produce a better answer. It's not that certain people are wrong more often than uncertain people. It's that certain people lose the ability to find out when they're wrong, because the mechanisms that would surface the disconfirming information have been switched off.

The discipline of treating certainty as a cue

The practical move Jaben proposes is small and uncomfortable: treat certainty in yourself as a signal to pause.

Not to abandon your position. Not to flip into doubt. To pause long enough to examine whether you've actually considered the alternatives, whether your framing of the problem is the only valid framing, whether the resistance you're encountering from others might be carrying information you haven't yet incorporated.

This requires noticing the feeling of certainty in real time, which most people are not in the habit of doing. The feeling tends to be invisible because it's the default state — what your brain feels like when it isn't actively working on something. Becoming able to notice it requires deliberate attention. When you find yourself thinking "but the evidence clearly shows..." or "anyone reasonable would conclude..." or "this is obviously the right answer," those are the moments to pause. The thoughts may be true. They may also be the press secretary doing its job.

Markovitz's four steps from "The Conclusion Trap" are the operational version of this discipline. Go and see. Frame the problem. Think backwards. Ask why. Each step is friction against the brain's preferred move toward fast conclusions. Going and seeing forces you to leave your desk and gather facts rather than relying on data the press secretary has already organized. Framing the problem with rigor — distinguishing symptoms from causes from actual problems, opening up vistas instead of forcing solutions disguised as problems — prevents the certainty about a particular answer from foreclosing better answers. Thinking backwards and asking why structure the analysis in ways that resist the press secretary's preferred narrative.

None of these are intellectual moves. They're disciplines. They take energy. They produce slower decisions in the short term and better decisions in the long term, but the trade-off feels uncomfortable in the moment because the discomfort of ambivalence is real.

What ambivalence makes possible

The reason to put yourself through this is that ambivalence is the only state that opens the prefrontal cortex. As long as you feel certain, your analytical functions are working as press secretary. The moment you become willing to be uncertain — genuinely uncertain, not performatively uncertain — those functions become available to actually analyze. Including analyzing information that contradicts your current position.

This is where the better answers come from. Not from working harder on the answer you already have, but from making space for an answer you don't have yet to emerge. The hidden brain, when it's allowed to consider that the current story might not be the best one, can search for a different story — one that incorporates criteria you initially missed or weighted wrong. The story it finds is often better than the one you started with, and it's usually one that was available the whole time, just drowned out by the louder voice the hidden brain originally selected.

A note here on the social dynamics. People who can hold genuine ambivalence and ask the questions that come from ambivalence are sometimes mistaken for indecisive. They aren't. They're operating with a different relationship to certainty — one where conviction is something earned through analysis rather than asserted before analysis. In change conversations specifically, this is what makes the difference between a leader whose proposals get adopted and a leader whose proposals get politely defended against. The leader who arrives uncertain, asks real questions, and incorporates what they learn produces durable change. The leader who arrives certain and pushes harder produces compliance that doesn't survive contact with reality.

The harder discipline

The trap with all of this is that the discipline is hardest to practice exactly when it matters most. On low-stakes decisions, the cost of jumping to a conclusion is low. You can be certain quickly and move on. On high-stakes decisions, the cost of being wrong is high — which is exactly when the brain is most motivated to reach for certainty, because certainty conserves the energy that genuine deliberation would consume.

The discipline isn't to be uncertain about everything. It's to recognize the situations where certainty is doing you harm — where the answer you've reached too quickly is closing off the better answer you haven't reached yet — and to deliberately pause in those moments. The pause doesn't have to be long. It has to be real. Long enough for the press secretary to step aside and the analyst to do some work.

Most of what makes continuous improvement effective is downstream of this. The methodology of going to the gemba is a structured pause against the certainty of remote analysis. The discipline of completing the left side of an A3 before debating countermeasures is a structured pause against the certainty about which solution is correct. The practice of asking why repeatedly is a structured pause against the certainty about the first answer you find. These aren't tools so much as institutional disciplines for staying with ambivalence long enough to find better answers than the press secretary's first draft.

The leaders who get this right develop a kind of working humility about their own conclusions. Not false modesty. Genuine recognition that the feeling of certainty is unreliable, that the press secretary is good at the job, and that the better answers tend to be the ones that emerge after the obvious answers have been examined and found insufficient.

The leaders who don't get this right keep being certain, keep being defended by their own analytical functions, and keep being surprised when the decisions they were sure about don't produce the results the certainty promised.

Certainty isn't the goal. It's the warning sign that the work isn't done.


This post draws on KaiNexus webinars with Dr. Mark Jaben, author of "Free the Brain: Overcoming the Struggle People and Organizations Have With Change," and Dan Markovitz, author of "The Conclusion Trap: Four Steps to Better Decisions." Both recordings are available in the KaiNexus webinar library.

Topics: Change Management, Problem Solving, Brain Science

Recent Posts