Here's a leadership lesson to ponder from a phone system nobody wanted to use: change nobody asked for doesn't get adopted because you explain how it will help the bottom line. It gets adopted because you explain how it will help the individual person.

Before we built out a dedicated team of Inside Sales Agents (ISAs, the folks whose whole job is working the phones), we needed our existing sales team to do that work themselves. Problem was, that team had built their whole career on outside sales … showing houses, meeting clients face to face, writing up deals in person. Nobody on that team signed up to make 25 cold calls a day off their own cell phone.

The Change Landed Like an Insult, Not an Upgrade

We rolled out a system called the Mojo dialer (a tool that calls multiple numbers at once, connects you to whoever actually picks up, and drops a voicemail automatically on everyone who doesn't). On paper, it was a productivity win. To the team, it looked like we'd just handed them a job they never wanted.

They didn't ask for this. They didn't want it. And announcing a new system, even a good one, to a team that feels like the change is being done to them instead of for them is the fastest way to get quiet resistance instead of real adoption — the same quiet resistance I've written about when feedback lands as a threat instead of information.

We Almost Made the Mistake Every Leader Makes

The easy pitch would have been the business case. More calls, more leads, more closings, better numbers for the company. All true. All completely beside the point to a team that had never wanted to be on the phone in the first place.

Nobody changes their behavior because the P&L needs them to. They change because something in it actually helps them, and if you can't name that part, you don't have a pitch. You have an announcement. It's the same mistake I made chasing growth for its own sake at a business I helped run — leading with what the company needed instead of what the people carrying it out actually needed to hear.

What We Actually Told Them

So we didn't lead with the company's upside. We led with theirs. "Instead of it taking you two hours to make these calls, you'll be able to do them in thirty minutes." That was the whole pitch, distilled to one sentence: this is what's in it for YOU, not just what's in it for the P&L.

That reframe changed everything, because it was true and it was theirs. A task they hated doing for two hours a day suddenly cost them thirty minutes instead, freeing up an hour and a half to do the part of the job they actually loved: showing houses, meeting clients, writing up deals.

Why This Worked When the Business Case Wouldn't Have

The system didn't change. The dialer did exactly what it was always going to do. What changed was whose problem we solved with it first. We solved the team's time problem before we ever mentioned the company's lead problem, and the lead problem got solved anyway, as a byproduct of them actually using the tool.

That's the whole trick to leading unasked-for change. The company's reason for the change and the team's reason to accept it are almost never the same sentence. Find the team's sentence first.

The Difference Between Selling a Change and Announcing One

An announcement tells people what's happening. A sale tells people why it's good for them specifically. Most leaders default to the announcement, because it's faster and it feels more honest. It usually backfires, because "here's what we're doing" invites exactly one response: why.

If you don't answer that why in terms the team actually cares about, they'll answer it themselves, usually with a worse story than the true one. Somebody decides the new tool is about surveillance. Somebody else decides it's about squeezing more out of them for the same pay. Neither is true, but silence on the real why hands them the microphone to invent their own — the same discipline it takes to pause before reacting under pressure applies here too, just aimed at your own instinct to skip the explanation and just push the change through.

This Isn't Manipulation. It's Translation.

I want to be clear about something here, because "sell the change" can sound like spin. It's not spin if the benefit is real. Thirty minutes instead of two hours was real. We didn't invent an upside that wasn't there. We just led with the true upside that actually mattered to the people living the change, instead of the true upside that only mattered to us.

That's not manipulation. That's just translating the same fact into the language the audience actually speaks.

Marching Orders

Think about the last change you rolled out to your team that they didn't ask for. Did you lead with what it does for the company, or what it does for them? If it was the company's case, go back and find their sentence, not just yours. If you want to get sharper on how you actually lead through change, take the free 3-minute leadership assessment. Your mission starts here.