Why does Chasing Buy-In Stall a Rollout?
"We need to get buy-in before we move forward."
It sounds reasonable, collaborative, and like great leadership.
It's also sabotaging your ability to implement change.
Buy-in is a category error
When you say you need buy-in, you're implying that people have the option to not buy in.
But most organizational changes aren't optional. The new system is getting implemented. The policy is changing. The restructure is happening.
Framing it as something that requires buy-in creates false expectations. You're asking people to agree to something that will occur regardless of their agreement.
That's not collaboration. That's theater.
It delays clarity
When you're focused on getting buy-in, you spend time trying to make people like the change before you've even established what the change actually is.
You soften the message to make it more palatable. You emphasize benefits and downplay disruption. You invite feedback on elements that aren't negotiable.
All of that delays the moment when people understand what's actually changing. And you can't adapt to something you don't clearly understand.
Clarity has to come before acceptance. Not the other way around.
It creates false negotiations
"Getting buy-in" often involves asking for input on decisions that have already been made.
You announce a restructure and ask for feedback on the org chart. But the decision to restructure isn't open. So what exactly are people supposed to do with that invitation?
If you incorporate their feedback, you're reopening a finalized decision. If you don't incorporate it, they feel like you wasted their time and never intended to listen.
Both outcomes damage trust. The first creates confusion about what's decided. The second creates cynicism about participation.
It conflates agreement with compliance
You don't actually need people to agree with your decision. You need them to understand it and execute on it.
Buy-in focuses on changing minds. But behavioral change doesn't require agreement. It requires clarity about expectations, support to navigate the transition, and accountability for execution.
People can disagree with a decision and still implement it professionally. In fact, many of your best performers already do this routinely.
Confusing agreement with execution wastes energy on the wrong problem.
It misdiagnoses resistance
When people push back on a change, leadership often interprets it as lack of buy-in: "They just haven't understood the benefits yet."
But most resistance isn't about disagreement with the strategic rationale. It's about operational confusion, perceived unfairness in process, or lack of clarity about personal impact.
Trying to get buy-in when the real issue is ambiguity or missing support just means you're solving the wrong problem. You'll keep hitting resistance no matter how compelling your case for the change is.
It puts the burden in the wrong place
"Getting buy-in" frames change as something people have to be convinced to accept.
But in most cases, the burden shouldn't be on your team to agree with your decision. The burden should be on you to communicate it clearly enough that people can act on it.
That's a different standard. It doesn't require enthusiasm. It requires precision.
What actually works
Instead of buy-in, focus on clarity and support.
Make the decision final before you announce it. Don't invite negotiation on non-negotiable elements. State what's changing, why it's changing, and who it affects without softening the reality.
Then provide what people actually need: clear information about impact, support to navigate the transition, and answers to questions that matter for execution.
That doesn't guarantee agreement. But it creates the conditions for effective implementation. Which is what you actually need.
Buy-in is a distraction
It's appealing because it sounds collaborative. But it introduces ambiguity at the exact moment you need clarity.
If the change is happening regardless, stop pretending it's optional. If input matters on certain elements, be explicit about what's decided versus what's flexible.
Your team doesn't need to love the decision. They need to know what it is, what it means for them, and what to do next.
References & Related Reading:
1) Fogg Behavior Model (B=MAP), BJ Fogg, Stanford: https://www.thebehavioralscientist.com/articles/fogg-behavior-model
2) Morrison and Milliken, "Organizational Silence" (Academy of Management Review, 2000): https://journals.aom.org/doi/abs/10.5465/amr.2000.3707697
Related Blog Posts:
When should I ask for feedback on a change?
Why do change emails get ignored?
