What If Nobody Wants to Move the Needle?

Every company has this meeting. Someone says, "We need to move the needle." Everyone nods. There's a slide with the word transformation on it, and someone promises this quarter will be different.

Three months later: same room, same people, same slide with a new date on it. Nothing broke. Nothing moved either.

If you're a founder, a product lead or an operator, you know this meeting. You might be the one running it. And you've probably started to suspect that good ideas were never what you were short on.

The short answer

People love change as an idea, because ideas are free. Change in practice costs something: status, certainty, a skill you're known for, a routine that feels safe. Until a team says out loud what the change will cost each person, "moving the needle" stays something people say in meetings.

"Move the needle" has no names in it

Take a typical line: "We need to move the needle on retention." Who's "we"? What does anyone do differently on Monday? What do they stop doing?

Nobody knows. That's exactly why the phrase is so popular. A sentence with no names in it is easy to agree with, because it doesn't ask anything of anyone. "Meaningful change," "transformation" and "alignment" work the same way. Everyone in the room nods, and each person quietly pictures a version where someone else does the changing.

So the agreement is real. Everyone just agreed to a different change.

Talking about change feels like doing it

A strategy offsite feels productive. So does a new roadmap, a fresh set of OKRs, a beautifully formatted deck. You walk out with something to show.

Stanford professors Jeffrey Pfeffer and Robert Sutton called this the "smart talk trap": using plans, meetings and presentations as a substitute for action. It sticks because talk is safe. A deck can't fail in front of a customer. A pilot can.

So the person who writes the best document about the new process gets praised at the all-hands, and the person who actually tries it, and gets it wrong twice, gets the awkward questions. Run a team like that for a year and you've built people who are great at describing change and careful never to attempt it. Individuals do the same thing to themselves. I've written about the illusion of doing: staying busy so you never have to touch the scary work.

The people who want the change are often the ones blocking it

The person slowing a change down usually wants it. Sincerely.

Picture a team lead who pitched a new planning process at the kickoff, got everyone excited, and then approved every request to do it the old way. They weren't lying at the kickoff. Under the old process, they were the go-to person, the one who knew where every dependency lived. The new process made that knowledge less special, and part of them quietly protected it.

Harvard researchers Robert Kegan and Lisa Lahey call this a competing commitment. You're sincerely committed to the change, and at the same time, without noticing, you're putting real energy into protecting something the change threatens. For most experts, that something is simple: not becoming a beginner in front of their own team.

Add basic human wiring on top. People stick with whatever is already in place more often than it deserves, a pattern economists call status quo bias. Change asks you to give something up today for a maybe-better tomorrow, and most of us feel the giving up a lot more.

A team that talks change and never does it has a health problem

When a team keeps talking about change and never does it, look at how the team works before you look at the people. McKinsey describes a healthy organization as one that aligns on a direction, adapts, executes and renews itself, and says healthy companies are three times more likely to outperform unhealthy ones. Change theater nails the first step and skips the rest.

The usual root cause is fear. Amy Edmondson at Harvard studied 51 work teams and found that teams where people felt safe taking interpersonal risks did more learning, and that learning went hand in hand with better performance. She calls it psychological safety. Now flip it. If saying "I can't do this" or "this costs me something" feels dangerous, nobody says it. People nod in the meeting and stall on the calendar. When the project finally dies, nobody can find the moment it happened, because nobody ever objected out loud.

If you want a way to see what your organization is actually missing, the five elements framework is one lens for that.

Even "70 percent of change fails" is just more talk

You've heard it in a deck somewhere: 70 percent of change initiatives fail. Mark Hughes at the University of Brighton went looking for the evidence behind that number and concluded that "there is no valid and reliable empirical evidence to support such a narrative."

It keeps getting repeated because it's comforting. If most change fails, your failure is normal, and nobody has to ask what they personally skipped. Stop quoting it.

How to tell whether your team actually wants the needle to move

Skip the next offsite. Watch what people do between meetings instead. Five checks, in the order I'd run them:

  1. Ask each person what this change costs them. Do it one on one, away from the group meeting. A sales lead might tell you, "I lose the clients I've handled personally for years." That's a real answer you can work with. If someone says "nothing," either the change is still too fuzzy for them to picture, or they don't feel safe telling you yet. Do this before you launch anything else.
  2. Ask what people stopped doing. A week after the kickoff, ask each person what they dropped because of it. If the team now has a new weekly sync, a new dashboard and a new Slack channel, but everyone still does the actual work the old way, nothing has changed. Real change almost always means letting go of something.
  3. Make it small enough to start this week. "Improve customer onboarding" is too big for anyone to begin on Monday. "Our account manager calls every new customer within 48 hours of signup, starting this week" is something one person can actually do, and by Friday you'll know whether it happened. Pick one action, give it to one named person, and check back in a week.
  4. Watch for "just this once." The old way usually survives as a series of exceptions: a manager still signs the old approval form "just for this client," or a report still gets built the old way "because the deadline is tight." Each exception sounds reasonable on its own. Count them. If they keep piling up, sit down with the person approving them and ask what the new way would cost them personally. That's usually where the real resistance lives.
  5. Make it safe to say "I'm not ready for this." Say it yourself first, about something you're struggling to let go of. When people can say it out loud, you hear about the problem early and can do something about it. When they can't, you find out three months later, when the deadline slips and nobody can explain why.

The resistance nobody looks at: yours

Often the person who least wants the needle to move is the one asking for it.

If you're a founder, a lot of who you are at work is built on how things run right now: the way you sell, the calls only you make, the problems you're known for fixing. Real change threatens some of that. The resistance usually shows up in your body before it shows up in words. It's the small relief when a decision slips to next quarter. The tight chest when someone offers to take a process off your plate. The sudden urge for "one more round of analysis."

Pay attention to it. In the three brains framework, the gut is the part of you that flags a problem before you can explain it, and that's exactly what this feels like. In my Emotional Wisdom work, this is where we start: stay with the feeling long enough to ask what it's protecting, before your mind relabels it as "bad timing."

When a leader says out loud, "I think I might be the one holding this up," everyone else gets permission to say it too. After that, the five checks above start getting honest answers.

Key takeaways

  • Treat "move the needle" as a placeholder until someone can say who changes what, by when.
  • Praise the person who tried the new way and stumbled at least as loudly as the person who wrote the best deck.
  • Before you launch a change, ask each person privately what it will cost them.
  • Drop the 70 percent statistic from your decks.
  • Each week, ask what people stopped doing and count the "just this once" exceptions.
  • Notice your own relief when a decision gets postponed. It's often the first sign you're the one holding things back.

Definitions

Psychological safety: A shared belief among team members that the team is safe for interpersonal risk-taking, a concept developed in Amy Edmondson's research on work teams.

Change theater: Activity that signals an organization is changing, such as offsites, roadmaps and announcements, without a matching change in how people work day to day.

Knowing-doing gap: Pfeffer and Sutton's term for the distance between what an organization knows it should do and what it actually does.

Change fatigue: Exhaustion from a steady stream of overlapping change initiatives, which leads people to disengage from new ones regardless of their merit.

Frequently asked questions

What does "move the needle" mean in business?

"Move the needle" means making a noticeable, measurable difference to an outcome, borrowed from the image of a needle on a gauge or dial. In practice it's often used without saying which outcome, by how much, or who is responsible, which is why it's easy to agree with and hard to act on. Replace it with the metric, the target and the owner, and the phrase either becomes a real plan or quietly disappears.

Why do people agree to a change in the meeting and then not follow through?

Agreeing costs nothing in the room, while the cost of the change arrives later, on the calendar, as a habit someone has to drop. If disagreeing openly doesn't feel safe, silent delay becomes the only available form of objection. Ending every change meeting with one named behavior, one owner and a date makes that gap visible within a week.

Is resistance to change always a bad sign?

No. Sometimes the person resisting has spotted a real flaw the change's sponsors missed, and treating every objection as a mindset problem throws that judgment away. The useful move is to ask what the resistance is protecting. If the answer is a genuine risk to customers or quality, adjust the change. If it's personal status or comfort, name it kindly and keep going.

What is the difference between change fatigue and resistance to change?

Change fatigue comes from volume: too many initiatives, overlapping, none finished, so people stop investing in any of them. Resistance comes from a specific loss one particular change would cause. Fatigue is fixed by launching less and finishing more. Resistance is fixed by naming the loss and deciding together what to do about it. Plenty of fatigued teams get misdiagnosed as resistant.

How do you restart a change initiative that has stalled?

Shrink it. Pick the single behavior that would prove the change is real, give it to one person, and set a date within a week or two. Before restarting, ask the people involved what the first attempt cost them, since a stalled initiative usually has an unspoken loss behind it. Relaunching the full original plan with fresh energy tends to repeat the same stall.

Does this apply to small businesses or only large corporations?

The pattern applies to both, and in a small business it gets more personal. A ten-person company has less room for change theater, but the founder's own competing commitments carry more weight, because nearly every process runs through them. When the founder quietly prefers the old way, the whole company does too, whatever the plan says.

Sources