Change Management

Start by discarding the most-cited number in this field. You have probably heard that around 70% of change initiatives fail. Mark Hughes went looking for the evidence behind it in the Journal of Change Management in 2011 and found none: each of the five most prominent published sources for the claim either asserted it without evidence or cited someone else who had. The trail ends at Hammer and Champy's 1993 Reengineering the Corporation, where it appears as an explicitly "unscientific estimate" that Hammer himself walked back two years later.

That matters beyond pedantry. A number that high implies change usually fails, which quietly excuses failure and points blame at dysfunction. The more honest position is that we don't have a reliable industry-wide failure rate, and the outcome in your organization depends on mechanics you control. Netflix is the case worth studying: DVD-by-mail to streaming to original content, driven by data and a genuine willingness to cannibalize its own working business model before something else did it for them. Most organizations don't fail at change because the destination was wrong. They fail at the mechanics of getting there.

A model for the mechanics

Kurt Lewin's foundational framing is simple. Change happens in three phases: unfreeze the current state, change it, then refreeze into the new normal. Skip unfreezing and people experience change as an ambush. Skip refreezing and the organization drifts back to the old pattern the moment attention moves elsewhere.

Kotter's eight-step model fills in the middle with specifics:

1. Establish real urgency, so people understand why comfort isn't an option.
2. Build a coalition with enough credibility to lead the change, rather than trying to carry it alone.
3. Craft a clear vision for where this is headed.
4. Communicate that vision constantly, well past the point where you're sick of repeating it.
5. Empower action by removing the obstacles in people's way.
6. Generate quick wins early to build momentum and credibility.
7. Leverage those wins into the next, harder phase of change rather than declaring victory too soon.
8. Embed it in the culture, so the new way of working survives after the initiative officially ends.

Most failed change efforts don't fail because the plan was bad. They fail because a step got skipped, usually urgency, quick wins, or embedding, all of which feel skippable and aren't.

Why your best team might be your most resistant one

It's counterintuitive, but highly cohesive teams, the ones that work brilliantly together day to day, are often more resistant to change, not less. Strong norms and comfortable routines create real inertia. Groupthink can suppress dissent precisely because everyone wants to preserve the harmony they've built. Insularity can close a tight team off from outside perspective. And a team that's used to reaching internal consensus can spend too long seeking full agreement when the moment actually calls for a fast, directive response.

None of this means cohesion is a liability. It means cohesion needs to be paired deliberately with openness. Actively invite dissenting opinions rather than assuming silence means agreement. Bring in outside perspective on a regular cadence, not just when something's already gone wrong. And watch for the specific signs of groupthink and internal-consensus-seeking so you can interrupt them before they slow down something urgent.

Planned change vs. emergent change

Not all change follows a tidy top-down plan, and treating all change as if it should is its own mistake. Planned change is deliberate: assessed, designed, rolled out top-down, aiming for predictable outcomes. Think implementing a new company-wide system or reorganizing a department. Emergent change is unplanned. It arises from inside or outside the organization, spreads laterally or bottom-up, and adapts as it goes. Think a team's organic response to a competitor's move or a sudden market shift.

Planned change offers control at the cost of flexibility. Emergent change offers speed and adaptability at the cost of predictability. In practice, the organizations that handle change well use both, starting with enough structure to give people direction, while staying genuinely open to adjusting the plan as new information arrives rather than defending the original plan for its own sake.

Choosing your leadership stance

McGregor's Theory X and Theory Y describe two very different assumptions about people, and each implies a different way of leading through change. Theory X assumes people are resistant to change and need control and enforcement to get there: change imposed top-down by a small group of experts, resistance met with force rather than dialogue. Theory Y assumes people are adaptable and capable of self-direction: change built through collaboration, a diverse group of voices, and treating resistance as something to understand rather than something to suppress.

Neither is universally correct. The right stance depends on context. Theory X tends to fit crisis response, compliance-driven change, or workforces doing routine, low-autonomy work, where speed matters more than buy-in. Theory Y tends to fit cultural transformation, strategic shifts, or knowledge-based teams where long-term commitment and creative problem-solving matter more than fast compliance. The mistake isn't picking either approach. It's applying the wrong one to the situation in front of you: forcing consensus-building onto a genuine crisis, or forcing top-down compliance onto a team of senior professionals who need buy-in, not orders, to actually change how they work.