Principle 02: People don't resist change. They resist extra work.

"People hate change" is one of the most repeated lines in business. It is also wrong. Confidently, repeatedly wrong. Like a horoscope with a corner office.

People change constantly. They switch phones, apps, routes to work, and coffee orders. Some people change their coffee order weekly, with great enthusiasm and zero training. Nobody needed a training deck to start using a map app instead of a paper map. It was easier, so they switched.

People do not resist change. They resist change that costs them more than it saves.

People do not resist change. They resist change that costs them more than it saves.

Every new tool comes with a tax

When leadership announces a new tool, they see the upside. The people doing the work see the invoice.

• One more login. Password must include a capital letter, a symbol, and a hieroglyph.
• One more tab.
• One more place to check.
• A new way of doing the task, while the old deadline stays exactly where it was.

That last one is the killer. You are asking someone to learn a new system and hit the same targets in the same week. For them, the change is not a promise. It is homework. Homework with no grade and no summer break.

Then we act surprised when they quietly go back to the old way.

Memos do not remove friction

A memo announces a change. It does not make the change easier. It usually adds one more thing to read, right between the benefits reminder and the email about whose lunch is growing fur in the fridge.

A memo announces a change. It does not make the change easier.

I have written those memos. They produce a brief spike of enthusiasm, followed by a long, polite silence. The kind of silence that sounds a lot like "I'm too busy for this."

My personal best was a three-page memo announcing a tool that would "save everyone time." It took most people longer to read the memo than the tool saved them in its first month. One colleague hit reply-all with a thumbs up. That was the entire adoption campaign. I framed the thumbs up. Metaphorically. Mostly.

So I stopped writing memos and started removing steps.

Subtract before you add

Before I ask anyone to adopt anything, I ask one question. What can I take off their plate first?

Here is what that looks like with AI.

1. Count the clicks. Literally. If the new workflow takes more steps than the old one, it is not ready. Fix the workflow, not the people. The people were never the problem. The seventeen steps were.
2. Bring the AI to the work. Do not make people visit a new tool. Put the output where they already live: the doc, the spreadsheet, the chat channel.
3. Build the prompt for them. Asking a busy person to become a prompt engineer is extra work. Hand them a tested prompt that already knows the brand voice and the format.
4. Pay the learning cost up front. Give people time to learn. Move a deadline. Take a task away. Show that the investment is shared.
5. Retire the old way. If both paths stay open forever, the familiar one wins. Every time. Comfort food beats salad. Ask anyone at 9 p.m.

The real signal

When a team "resists" a change, treat it as data, not defiance. They are telling you the cost is too high.

They are usually right.

Lower the cost and the resistance disappears. Not because you persuaded anyone. Because you finally made the new way worth it.

Lower the cost and the resistance disappears.