Adoption doesn’t stall because of resistance – it stalls because we focus on the wrong things.

By Max White

Today’s systems are rolled out with big promises – AI, integration, automation, better data.

But then reality hits:

“This takes more clicks.”

“The old system did this better.”

“Why can’t it work the same way?”

This isn’t classic resistance. It’s comparison. And it’s rarely just about clicks. What’s happening is a trade-off evaluation based on incomplete information. People are comparing a familiar old system (even one they didn’t love) to a new system they haven’t mastered yet. So of course, the old one wins—at least early on. Familiarity is often mistaken for effectiveness.

But there’s another layer here. People are busy, context-switching constantly, and focused on what’s directly in front of them. So, they evaluate change at the task level: “Does this step feel faster or slower?” instead of the system level: “Does this make the overall process better?” That’s where the real value lives.

What feels harder in the moment often enables: cleaner data (critical for AI + automation), real integration across systems, fewer downstream errors and rework, and more consistent, scalable processes. That value doesn’t show up in one task. It shows up across the process. I’ve seen teams flag “extra steps” only to realize later those steps eliminated hours of reconciliation.

That’s the job of change management: not just teaching how to use the system but shaping how people interpret what they’re experiencing. One approach I’ve found useful in practice:

S.H.I.F.T.

Set the narrative: Reframe “more steps” at the task level as better outcomes and smoother system-level processes in comms and leadership messaging

Highlight what matters: Explicitly call out trade-offs (what’s different vs. what’s better) in training

Interrupt comparison loops: Redirect feedback conversations from “old vs. new” to “value vs. friction”

Fast-track early wins: Design quick-win use cases and guided walkthroughs to build confidence fast

Tie back to purpose: Consistently reinforce the why (AI, integration, scale) in every touchpoint

Because if you don’t shape the comparison, the comparison will shape your adoption.

Quick personal example—having a 1.5-year-old, nothing is efficient. Everything takes more time, more steps, more effort. It feels less efficient, but that’s not the right metric. You’re building something long-term. System transformations are no different. If you only measure the micro friction, you miss the macro value. In a world where attention is limited, helping people see the bigger picture isn’t optional; it’s the critical work.

How are you helping your teams stay focused on transformational outcomes instead of task-level changes?