The User Experience Was The Change Management

Every newsletter nobody reads. Every town hall nobody engages with. Every training program people sit through and immediately forget.

A wise leader once told me user experiences are like jokes — if you have to explain them they're not good ones. More communication doesn't fix a broken experience. It just compounds the debt.

A bad user experience doesn't announce itself. It quietly produces the resistance, the workarounds, and the throwaway work you've been calling a people problem.

The 52-step onboarding nobody designed. Teams just kept adding requirements until the complexity became the communication strategy. That's not onboarding. That's an obstacle course with a badge at the end. The cost isn't just a bad first day — it's a retention problem, a productivity problem, and a recruiting problem with a price tag attached.

The tech launch without user testing. The people who were supposed to use it every day couldn't navigate it. Not because the technology was wrong. Because the employee experience blocked adoption. An extra year. Millions in consulting fees. Could have been caught in a two-week usability test if anyone had looked.

If your team is bypassing the new process, they're probably responding to the terrain you built. The path of least resistance isn't the problem. It's the signal.

One of the most beautifully designed transformations I worked on had no newsletters. No separate change management workstreams. No assigned change champions. The feedback loop was embedded into the sprint itself. Every sprint — here's what's coming, here's what we heard, here's what we learned, here's what we did about it. Stakeholders aligned not because they were change managed — but because the system was designed to add value at every touchpoint. The experience was the change management.

Water doesn't decide to flow downhill. It responds to terrain. Rather than writing awareness campaigns asking people to change, redesign the conditions so the new behavior is the easier, more obvious path.

The change becomes gravity — not an uphill battle.

That's the difference between managing change and designing for it.

Are you loyal to the outcome — or loyal to the checklist?

I build the operating system between strategy and execution. If this lands — reach out. That's usually where the best conversations start.