Change doesn’t fail because the idea was bad. It fails because the people being asked to make the change never understood why it was happening.

I’ve seen this play out more times than I can count. A leader or team identifies something that needs to change, puts together a plan, and announces it. Adoption is slow and resistance quietly shows up in the form of workarounds, lip service, and people reverting to old habits the moment no one’s watching.

The most common thing missing is the why. Not the organizational why, the personal why. Why is this better than what we’re doing now? Why does this make things better for me personally, or my team?

“Why?” is an important tool in my toolkit. I’ve used it to build things up, and I’ve used it to tear things down that had outlived their purpose. It works in both directions. When people understand the reason behind a change, they stop being passengers and start taking ownership.

If you can’t explain the why, you’re not leading change, you’re just mandating it. And mandated change without understanding produces resistance or compliance, not ownership.

There’s one more thing that gets overlooked: all changes should be treated as experiments.

That means going in with a hypothesis, an agreed-upon way to measure success or failure, and a stated willingness to revert if it isn’t working. “We’re trying this. Here’s how we’ll know if it’s working. If it isn’t, we’ll adjust or undo.” That framing does something important. It reduces the stakes. People are more willing to participate in an experiment than to commit to a permanent shift in how they work. And if it works, no one will want to go back.

Change needs a reason. Make sure everyone in the room knows what it is.