Why Most Change Initiatives Fail Before They Even Start (And What to Do About It)

Change fatigue is real. But in most organizations I work with, the problem isn't too much change — it's too much poorly explained change. Leaders invest heavily in slide decks, town halls, and communication cascades, yet employees still feel blindsided, resistant, or simply confused. Here's the uncomfortable truth: the problem rarely lies in the change itself. It lies in how — and more importantly, why — it was introduced.

The Boardroom-Floor Disconnect: Two Completely Different Realities

When leadership teams design a change initiative, they've typically spent months — sometimes years — living with the problem. They've sat through market analysis reviews, profitability discussions, competitive benchmarking sessions. By the time they announce the transformation, the why feels so obvious to them that they barely mention it.

Employees experience something entirely different.

They show up on a Tuesday morning, open their email, and learn that their operating model, team structure, or way of working is about to shift — effective Q3. The leadership team has arrived at the destination after a long journey. Employees are being asked to board a plane with no explanation of why the current city isn't good enough.

This is the boardroom-floor disconnect, and it kills more transformations than any technical failure ever could.

I saw this play out vividly with a mid-size manufacturing company I worked with last year. Leadership had done everything "right" by conventional standards: polished communication materials, a clear vision statement, scheduled town halls. What they hadn't done was answer the question their 600 employees were quietly asking in every hallway and Slack channel: "Why now? What was actually broken?"

The result? Passive resistance. Managers deflected questions. Frontline teams kept running the old processes in parallel "just in case." Three months in, adoption was stalling — not because people refused to change, but because no one had given them a compelling reason to.

Urgency Has to Be Felt, Not Just Announced

Kotter's 8-step model famously places "creating a sense of urgency" at the very top. Most leaders read this as: communicate the urgency loudly and clearly. That interpretation misses the point entirely.

Urgency isn't a message. It's an emotional state. And you can't manufacture it with a PowerPoint slide.

Real urgency comes from helping people see what you've seen. This means sharing the uncomfortable data, not just the sanitized version. It means telling employees what happens if the organization doesn't change — market share erosion, operational risk, the competitor who's already moved faster. Leaders often worry that this level of transparency will create panic. In reality, the absence of that context creates something far more dangerous: cynicism.

A concrete example: I worked with a financial services firm undergoing a significant digital transformation. Initially, leadership framed the change entirely around opportunity — "we're building for the future, this is exciting." Employee response was lukewarm at best. When we helped the leadership team reframe the narrative to include the risk side — specifically, that two direct competitors had already automated processes the firm still did manually, at a cost of 18% in operational efficiency — the tone of the conversation shifted overnight. People stopped asking "do we really need this?" and started asking "how do we move faster?"

The facts didn't change. The frame did. And that frame made urgency felt, not just heard.

The Three Questions That Rebuild the Narrative

After working with more than 50 organizations through complex transformations, I've identified three questions that — when answered honestly and specifically — fundamentally change how employees receive and engage with change. They're deceptively simple. Most leaders skip them entirely.

1. What problem are WE solving — not just the business?

This is about translating organizational pain into human pain. "We need to improve EBITDA margins" means nothing to a warehouse supervisor. "Our current process means you're spending two hours every shift on manual reconciliation that a system can do in seconds" means everything. Find the version of the problem that lives in your employees' daily experience and lead with that.

2. What happens if we DON'T change?

This question forces leadership to articulate the status quo as a risk, not a comfort zone. It also respects employees' intelligence. People can handle difficult truths. What they can't handle — and won't forgive — is being kept in the dark and then blindsided by consequences. Share the honest downside scenario. Not to create fear, but to create shared stakes.

3. What's in it for the people being asked to change?

This isn't about bribing employees with benefits. It's about genuine empathy mapping. What frustrations does this change eliminate? What capabilities does it build? What does it make possible for them — not just for the quarterly earnings call? When employees can locate themselves in the future state, resistance drops dramatically. When they can't, it doesn't matter how well-designed your change program is.

When we went back to the manufacturing company and rebuilt their communication strategy around these three questions, something shifted. Managers stopped being messengers defending a decision handed down from above. They became genuine advocates, because they now understood — and believed in — the why themselves. Adoption accelerated. The hallway conversations changed tone.

A Note on Sequencing: WHY Always Before WHAT

One of the most actionable shifts any leader can make is simple: enforce a sequencing rule in every change communication. WHY before WHAT. Always.

This sounds obvious. It almost never happens in practice. Under time pressure, leaders default to logistics — dates, org charts, new reporting lines, tool rollouts. These details feel urgent because they're concrete. But feeding people the what before they've accepted the why is like giving someone directions to a destination they haven't agreed to travel to.

In practice, this means your first town hall shouldn't have a single org chart in it. It should be entirely dedicated to the case for change — the problem, the risk of standing still, and what the future genuinely looks like for the people in the room. Give the why the airtime it deserves. The what will land far better once it does.

Conclusion: The Message Is Never Just the Message

Change management isn't fundamentally about process or methodology. It's about human beings deciding whether or not to trust a new direction. That decision gets made — consciously or not — in the first few minutes of the first communication they receive.

If you lead with logistics, you get compliance at best, resistance at worst. If you lead with a deeply honest, employee-centered case for change, you get something far more valuable: