You walk into the meeting prepared. The data is clean. The metrics are clear. The cost of doing nothing is documented. The proposed change has a strong return, a reasonable timeline, and a defensible plan.

And then it goes sideways.

Someone pushes back on the assumptions. Someone goes quiet and stays quiet. Someone says yes in the meeting and does nothing for the next three weeks. The data didn't land. The proposal that should have been obvious to anyone reading the numbers honestly is now stuck somewhere between the meeting and the actual work.

If you've led continuous improvement work for any length of time, you've lived this often enough to develop a private theory about it. The theory is usually some version of "people resist change." It's a comforting theory because it locates the problem in the other person. It's also wrong — or at least wrong enough to be operationally useless.

The more accurate theory, drawn from a recent webinar with Dr. Mark Jaben and his book "Free the Brain," implicates the way our brains actually work.

Opinions form before analysis, not after

Think about a workplace decision you formed a strong opinion about recently. A vendor selection. A reorganization. A new metric leadership wanted to track. Did you study the evidence and then arrive at the opinion? Or did you arrive at the opinion fairly quickly and then notice yourself gathering evidence that supported it?

If you're honest, it was almost certainly the second one. And it works that way on essentially every issue you've ever had a view on.

What the researcher Shankar Vedantam calls the hidden brain — processing that happens before awareness reaches consciousness — does most of the work of forming opinions. 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 a good idea, this is a bad idea, I'm not sure about this one.

Only after the story has been selected do the analytical functions get involved. And here's the part that matters for change work: they don't analyze. They construct the case for whatever the hidden brain selected. Jaben, an emergency physician who spent years studying the neuroscience of change after watching the same Lean methodology succeed in some places and stall in others, 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.

Why your data is hitting a wall

When you walk into a meeting with your proposal and your supporting data, you're addressing the other person's press secretary. Their press secretary is already employed full-time defending the position their hidden brain selected before the meeting started.

Picture an operations director proposing a new standard work protocol for medication reconciliation. The spreadsheets show the current error rate. The benchmark data from comparable hospitals is solid. The case is, on its face, overwhelming.

Across the table is the nurse manager who runs the unit where this would go in first. Her hidden brain has already selected a story. The story is something like: "Another initiative from above, another six weeks of training disruption, another conversation with the night shift about why we're doing this differently than we did last month." She hasn't said any of that. She doesn't even know she's thinking it. What she's saying is, "I'm not sure the data captures what's actually happening on the unit."

The operations director produces more data. The nurse manager produces more counter-questions. Were the comparison hospitals running the same EMR? Was the baseline period representative? Every question is reasonable. Every question is also her press secretary doing exactly what press secretaries do — defending the position her hidden brain selected before the conversation began.

He leaves frustrated. She leaves feeling she successfully protected her unit. Nothing changes.

The data didn't fail because the data was wrong. The data failed because it was being aimed at the wrong target.

Resistance is rational, not emotional

Here's the reframe that changes the operational shape of all of this.

People aren't wired to resist. They're wired to succeed. When someone pushes back on a proposed change, they're responding to a perceived threat to their ability to be successful in their responsibilities. The perception might be accurate or inaccurate, but the response to it is rational. From inside their head, defending against your proposal is the obviously correct move.

The problem in most change conversations is that two people have arrived at different conclusions about whether a proposal helps or threatens their respective definitions of success — and each person's notion of success was constructed by their hidden brain from criteria the other person has never seen. Jaben calls the result "dueling solutions." Each person is defending a position their hidden brain selected. Neither person is actually examining the other's logic.

A CI leader rolling out a new daily huddle structure sees it through one lens: huddles happening on schedule, the right metrics being reviewed, problems surfacing earlier. The plant manager he's proposing it to sees it through another. He just spent twelve months stabilizing operations after a brutal year of supply disruptions, and his definition of a good month is one where his team isn't being pulled in fourteen directions by corporate initiatives. He doesn't analyze the proposal that way. He feels it that way. His press secretary is now producing reasonable-sounding objections about pilot scope and timing.

Neither person is wrong, exactly. They're operating from different stories, each defending a notion of success the other hasn't engaged with.

What actually moves a position

If the analytical functions can't change the underlying story, what can?

You can't, strictly speaking, change someone else's mind. Only their hidden brain can revise its own story. What you can do is create the conditions in which their brain might be willing to reconsider — to shift from press-secretary mode into analyst mode.

Several things have to be true. The other person has to perceive you as trustworthy, which the British philosopher Onora O'Neill defines as a track record of demonstrated reliability across time. Trust isn't claimed; it's accumulated. If your track record is thin or mixed, your data is being filtered through that history before it reaches their analytical functions.

They have to perceive you as credible on this specific issue — operating without deception or coercion, not just in intent but in perception. Data that appears cherry-picked, metrics that seem strategically framed, presentations that omit inconvenient information all undermine credibility regardless of how honestly they were assembled.

They have to feel their notion of success is part of the conversation. If your proposal addresses your understanding of success but never engages theirs, their hidden brain has no basis for considering it worth investing energy in. The stories have to overlap enough for the change to serve their definition of success as well as yours.

And you have to treat their resistance as information rather than obstruction. "Why are you against this?" activates defense. "What about this doesn't work for your situation?" activates curiosity. The questions invite the other person's brain into the prefrontal cortex, where the story itself becomes available for revision.

The CI leader who walks into the plant manager's office with one more piece of evidence about why the huddle structure will work is going to lose that conversation again. The CI leader who asks, "When you imagine this rolling out across your facility, what's the part that worries you most about your team's ability to sustain it?" is having a different conversation. Not because the question is a tactic. Because the question genuinely invites the plant manager to surface his real concerns — and the answers are the information the CI leader actually needs to build a shared outcome instead of a dueling solution.

Certainty is the trap

The hardest part of this in practice is that the strongest sign you're operating in press-secretary mode is the feeling that your proposal is obviously correct.

Certainty feels like clarity. It feels like having done the work. What it actually is, neurochemically, is the absence of the energy expenditure that genuine reconsideration would require. Your brain has selected a story and stopped processing alternatives.

The discipline is to treat certainty in yourself as a signal to pause. Not to abandon your position. To examine whether you've actually considered the other person's notion of success, whether your framing is the only valid framing, whether the resistance you're encountering might be carrying information you haven't yet incorporated.

This is uncomfortable. The brain doesn't enjoy ambivalence. But ambivalence is what opens the prefrontal cortex, and the prefrontal cortex is where genuine analysis happens. As long as you feel certain, your analytical functions are working as press secretary.

The harder, slower, better path

The harder, slower path is to assume your great idea is an opinion. To assume the other person's pushback is information about a gap between your notion of success and theirs. To ask questions that surface their criteria rather than presenting evidence that defends yours. To build a shared outcome before debating countermeasures.

This path is slower in the short term and faster in the long term. Pushing harder on the data produces a particular kind of speed — the speed of decisions made and announced — that often becomes meaningless when those decisions don't translate into the daily behaviors they were supposed to produce. Engaging with the other person's notion of success takes longer up front and produces durable adoption rather than reluctant compliance.

The hidden brain on the other side of the conversation is going to decide whether the change is workable for them. Your data isn't reaching that brain directly. Your trustworthiness, your credibility, and your willingness to engage their notion of success are.

Get those right, and the data eventually gets its hearing. Skip them, and the data never reaches the room where the decision is actually being made.

This post draws on a KaiNexus webinar with Dr. Mark Jaben, board-certified emergency physician and author of "Free the Brain: Overcoming the Struggle People and Organizations Have With Change." Watch the full recording in the KaiNexus webinar library.