I was sitting in a project review meeting, looking at a spreadsheet that should have made me proud.

Every milestone hit, every deliverable ticked, training completed, communications sent, stakeholder workshops done.

On paper, this project was a textbook success story.

The project manager sitting across from me looked like she hadn't slept properly in three weeks.

When I asked how things were really going, she said something I haven't stopped thinking about since:

"We're doing everything we're supposed to do, but it still feels like we're pushing water uphill."

If you've said something like that recently, or heard someone on your team say it, this one's for you.

The problem isn't your framework

Change initiatives fail at approximately the same rate regardless of which methodology is running them, and that should tell us something.

It's not that the frameworks are wrong, most of them are genuinely solid.

The issue is that a framework describes what needs to happen, and what actually determines whether change works is how it feels to the people going through it.

Those are two completely different design problems, and most organisations are only solving one of them.

I've sat with local government teams drowning in consultation fatigue while implementing service models they actually believed in.

I've watched not-for-profit leaders see their people wear down during restructures that were designed with genuine care.

I've been in health organisations where the word "transformation" produced a visible flinch, because somewhere along the way it had become code for "more work, less support."

In every single one of those situations, the activity was competent and the experience was an afterthought.

People have very long memories for how things felt, and a very short tolerance for feeling like a line item on someone else's project plan.

What changes when you design the experience first

Three things show up consistently in change that actually sticks, and none of them are in any methodology I've ever read.

1. A personal why

And here's where most methods fall short.

They'll tell you to communicate the change, articulate the benefits, address concerns.

Good advice, all of it.

What they rarely do is help people build a real, personal connection to what the change actually means for them and for the people they're there to serve.

That's different from understanding the rationale.

That's the moment someone stops asking:

"Why is this happening to me?"

and starts asking:

"How do I want to show up for this?"

Until that happens, you're getting compliance.

When it does, something noticeably different happens in the room.

You'll feel it.

2. Language for the uncomfortable middle

Because most change communication is designed for the moments when leaders have answers and falls apart completely in all the moments when they don't.

Which, if we're being honest with each other, is most of the time.

Giving people language to sit inside uncertainty without it tipping into panic is underrated and almost universally underdone.

Examples like:

• "It's normal to feel unclear right now, we're still working through this together."

• "The discomfort you're feeling means you care about getting this right."

• "We don't have all the answers yet, and here's what we do know."

None of that resolves anything.

But it makes uncertainty feel like a shared experience rather than a sign that the wheels are coming off.

3. Structures people can actually rely on

Not performative town halls where questions get noted and never answered, but actual consistency in how decisions get made.

Check-ins that address what's genuinely real rather than what's comfortable to report.

Real pathways for people to influence how change unfolds rather than just receive it.

These are always the first things cut when delivery pressure spikes, and they are almost always the reason things unravel six months later, every time, without fail.

The question worth asking before anything else

Before the project plan.

Before the communication strategy.

Before the stakeholder mapping.

Ask yourself honestly:

What do we want people to actually experience as they move through this?

The dashboard question has an answer.

The delivery question has an answer.

The experience question is the one that most change leaders I've worked with have never been explicitly asked to answer, and it shows.

When it does have a clear and honest answer, the rest starts to find its place.

Communication tone, leadership expectations, timelines, support structures, all of it has something to point toward rather than just something to report against.

Your people aren’t resistant to change.

They’re tired of experiencing it in a way that makes them feel like a project risk to be managed rather than a human reality to be acknowledged.

That distinction matters more than any methodology you wrap around it, and the organisations doing this well right now know it.

If you want to get specific about where your change is actually losing traction, the Change Clarity Diagnostic is worth ten minutes of your time.

Ask it to help you identify whether your people have a genuine personal connection to the change, and whether your leaders have language for the moments when they don't have answers, and it'll tell you exactly where to focus.

It's available at nicoletewierik.com/changeclaritydiagnostic-founders, and honestly, the ten minutes you spend with it will tell you more about where your change is losing traction than most half-day workshops will.

What's been your experience of transformation that felt designed with you versus delivered at you?

I'd love to hear what made the difference.