The One Question That Unlocks Every Resistant Team

I want to be upfront about this question. There is no silver bullet that works every time, for every situation, for every team. Anyone who tells you otherwise is selling something. Resistance is complicated, people are complicated, and organizations are complex.

But there is one question that consistently opens doors that nothing else does. In my experience, it's the one question most consultants or practitioners don't think to ask.

The question

"What would have to be true for this to actually work for you and your team?" That's it.

Not questions like "what are your concerns?" Not "how can we get you and the team on board?" or "what do you need from us to support this initiative?" Those questions — however well-intentioned — still put the practitioner in the driver's seat. They're still asking the other person to fit into a framework you've already built. This question does something different. It hands the wheel over completely. It says — I don't know what this needs to look like for you. Tell me.

Why it works

Most resistance isn't about the methodology. It's about something underneath the methodology — a fear, a history, an unmet need, a concern that nobody has taken seriously enough to ask about. It took me a while to get my head around those questions. I defended the methodology, I knew the value in Lean.

When you ask what would have to be true, you're not defending the initiative. You're not trying to overcome the resistance. You're getting genuinely curious about the world the other person is operating in, understanding and appreciating their perspective. People respond to that. Not always immediately, not always completely. But they respond to it in a way they don't respond to persuasion, data, or a better presentation.

Because what most resistant people actually want — before they'll engage with anything else — is to feel like someone is actually listening. Not listening to find the right counter-argument. Actually listening and taking in the very real challenges that is on the operational floor.

What I've heard when I've asked it

I've asked the question before. I've heard about previous consultants and practitioners that made promises and didn't follow through. I've heard of people that made fairly ambitious statements of project results without really understanding the work. There have been public supporters of continuous improvement yet privately undermine the work.

None of that was in the project brief. None of it showed up in the data. And none of it would have surfaced if I had kept persuading instead of asking. Every one of those answers changes the work approach.

The hard part

Asking the question is easy. The hard part is what comes after. You have to actually listen to the answer. Not in the way you listen when you're waiting for your turn to speak — really listen. Let it land. Sit with it, even when it's uncomfortable. You may even have to give it some time to percolate with you — and that's hard when results are driven by the timeline.

And then you have to be willing to act on what you hear. Because if you ask this question, gather the answers, and then proceed exactly as planned — you've done something worse than not asking. You've confirmed what the leader or team already suspected. That this is just another initiative where the people at the front say the right things and nothing actually changes. The question only works if you mean it.

One more thing

I said at the start there's no magic question that works every time. That's still true. There will be teams where the resistance runs so deep, the trust is so damaged, that no question opens the door quickly. There will be situations where the history is too heavy, the culture too entrenched, for one conversation to shift.

But even in those situations, asking the question does something useful. It tells you what you're actually working with. It gives you honest information about the gap between where things are and where they need to be. And in this work, honest information — however difficult — is always more useful than comfortable assumptions.