When a Well Designed Process Fails in the Real World: What I Learned

“Without credible communication, and a lot of it, the hearts and minds of people are never captured.”   — John P. Kotter

After months in the “laboratory”, debating every detail, every edge case, every theoretical outcome, our leadership team emerged proud and seemingly victorious. We had built a process we believed would dramatically improve the experience for our frontline teams, elevate customer outcomes, and help us hit the KPIs we’d been chasing.

We were behind schedule though, eager to launch, and excited to finally get the new process into the hands of the people who would use it. Implementation began with curiosity and early enthusiasm.

And then… reality hit.

The Moment Everything Shifted

Once we moved past the surface and into the actual mechanics of the new process, the tone changed fast. Excitement gave way to hesitation. Hesitation turned into anxiety. Anxiety turned into resistance.

The most common reaction became: “What the hell are we doing?”

Just like that, support evaporated.

Everyone agreed with the theory. But theory wasn’t enough. The big lesson I learned was quite humbling: We built a strong vision, but we didn’t build enough understanding.

We hadn’t clearly explained the how or the why in a way that helped people execute. We had spent months perfecting the strategy, but not enough time validating it with the people who would actually live it. It’s a tough feeling to realize you invested deeply in the right problem, but not with the right people in the room. This article is my reflection on that experience, and how I plan to avoid repeating it.

The Core Lesson: Top‑Down Alone Doesn’t Work

Leadership can (and should) set the vision. But building a process in a vacuum creates a hollow outcome. Without the right voices involved early, even the best ideas collapse under real‑world pressure.

If I could do it again, I would change three things.

1. Build a Clear, Shareable Vision

Before anything else, I would create a simple, visual representation of the vision, something every future stakeholder could see, understand, and react to. Something everyone could print and put on their desks.

Not a dense deck. Not a long narrative. A single visual that answers:

• What are we trying to accomplish?

• Why does it matter?

• What will be different when this works?

Having that clarity would create an initial alignment momentum we were sorely needing.

2. Map the Process End‑to‑End Before Building Anything

Next, I would outline the entire process at a high level — start to finish — assuming a straightforward, happy‑path flow.

This could be tedious but it’s about giving people a shared mental model:

• What happens first?

• What happens next?

• Where do handoffs occur?

• What does success look like at each stage?

When people can see the flow, they can spot gaps, risks, and opportunities long before rollout.

This though, I would build with a small group first to get it down, get it ready, and get to a tighter alignment, then start to burst it outwards to others for review, feedback, discussion.

3. Bring Champions Into the Build — Early and Often

Once the vision and high‑level flow are clear, that’s when the real work begins.

I would bring in champions from across the business to:

• pressure‑test the process

• poke holes in assumptions

• identify operational realities

• translate theory into execution

  
  

Then I’d break those champions and accountable leaders into committees, each focused on a bite‑sized portion of the process. After working independently, we’d bring everyone together to stitch the full process back into a cohesive whole.

This approach does two things at once:

1. Builds a stronger, more realistic process

2. Builds advocates who help champion the rollout

That’s a far cry from the legacy approach: build in isolation, create training, launch broadly, and hope for adoption.

Yes, this method takes more time. More meetings. More voices. But it saves far more time, and trust, on the back end.

Final Reflection

I’m sure there are still things I’m missing. Transformation is messy, unpredictable, and deeply human. We were not just building a transformed process, but building momentum, trust, buy-in. There are so many factors to it that focusing so narrowly on the what limits success, and holds you and others back. I am happy we learned this lesson and have already started down the path towards building larger momentum and understanding. They key takeaway:

Momentum comes from shared understanding, building alongside one another, with a healthy amount of real and honest communication.

I’d love to hear your experiences, the wins, the misses, and the lessons you’ve learned while leading transformation.