The Plan Was Perfect. Then People Got Involved.

I've spent more than 25 years helping organizations navigate change, and there's one thing that still makes me shake my head.

We spend months designing strategies, implementing technology, developing processes, and creating elaborate project plans. We have timelines, milestones, steering committees, and dashboards with enough green boxes to make everyone feel pretty darn good.

Green means we're on schedule. Green means we're on budget. Green means the technology works.

Apparently, green does not mean anyone has the slightest idea what they're supposed to do with it.

But hey, at least the steering committee slides look fantastic.

Then we introduce the change to the people who actually have to live with it.

And all hell breaks loose.

Suddenly, there are questions nobody anticipated. Concerns nobody thought to address. Managers who aren't quite sure what they're supposed to say. Employees who have figured out 17 creative ways to keep doing things exactly as they've always done them.

And someone inevitably asks, "Why are people so resistant to change?"

Well, there's a question.

Imagine an organization spending months developing a new process. The project team has done its homework. The technology works. Leadership has approved everything. The launch date is set.

Then someone on the front line asks a simple question.

"Okay, but how is this actually going to work when we're busy?"

Silence.

Because the people designing the process weren't necessarily the people who would be using it every day.

And that one question reveals a dozen things nobody considered.

I've seen versions of this play out throughout my career. Sometimes the biggest risks to a transformation aren't hiding in a technical specification or project schedule. They're sitting in the everyday realities of the people expected to make it work.

Here's what gets me.

We know people want to be heard. We know uncertainty creates anxiety. We know habits are hard to break. We know trust matters.

But put us in charge of a major initiative with a deadline, a budget, and an executive steering committee, and suddenly we forget everything we know about human behavior.

We start managing the project instead of leading the change.

And let's talk about leadership for a minute.

Somewhere along the way, we decided that approving a project was the same thing as sponsoring a change.

It's not.

Signing off on a budget doesn't make you a change champion. Showing up for the kickoff doesn't mean you've built trust. And forwarding an email with "Please share with your teams" isn't exactly a masterclass in leadership.

People watch what leaders do far more closely than they listen to what leaders say.

If leaders aren't visibly engaged, why should anyone else be?

When I wrote The People Stack, I wanted to challenge the way organizations define successful transformation.

Because a project can be delivered on time, within budget, and according to every technical specification, and still fail to create the value it promised.

Delivery creates potential. Adoption creates value.

Adoption doesn't happen because someone sends an email announcing that the new system is live.

It happens when people understand what's changing, why it matters, what it means for them, and how they're expected to work differently.

It happens when leaders stop assuming that announcing a decision is the same as building commitment.

And it happens when we stop labeling every question as resistance and start recognizing that sometimes people are telling us exactly what we've missed.

The irony is that none of this is particularly revolutionary.

Most of us wouldn't dream of planning a family vacation without asking the people coming along what they wanted to do. Okay, maybe some of us would, but we'd probably hear about it for the entire trip.

Yet organizations routinely make decisions affecting hundreds or thousands of people without meaningfully involving them until it's time to implement.

Then they're surprised when everyone isn't thrilled with the itinerary.

So before your next big launch, try asking three questions:

  • Have we actually talked to the people who will use this?

  • Can their managers explain what's changing without reading from a slide?

  • Do we know what people need to do differently on Monday morning?

If the answer to any of those questions is no, you might want to hold off on ordering the celebration cake.

Because the best strategy in the world doesn't mean much if nobody can make it work in the real world.

BGPD Rule: If your plan only works when people behave exactly as expected, you don't have a change strategy. You have a wish list.

A Little More on The People Stack

My book, The People Stack: Why Change Fails (and What Actually Fixes It), explores the gap between what organizations build and what people actually adopt, and what leaders can do differently to close it.

Whether you're leading a major transformation or simply trying to make a new way of working stick, the human side of change deserves more than an afterthought.

Learn more at www.juliewhittenconsulting.com.

And on a completely different note, The Panty Stack: 365 Things We Know, Forget & Learn Again is officially available! My second book takes a more personal, humorous look at the lessons life keeps teaching us about confidence, change, relationships, resilience, and reinvention. Different stack, same belief: the human side of life is always the most interesting, and usually the messiest.

Next
Next

One Year, Two Books, and a Whole Lot of Change