How to Lead Change Effectively: A Brain-Based Strategy for Real Results

You announce the change on Monday. The questions asked are polite. A few people say it makes sense. Three weeks later, the old process is still running, and nobody has said a word against the new one.

That is the version of resistance most leaders get. Nobody argues with you, and people keep doing what they did last month.

In October 2024, Gartner published a survey of 473 HR leaders fielded that July. 73% reported that their employees were fatigued from change, and 74% said their managers were not equipped to lead change. Most advice on how to lead change effectively speaks to the first number. This article is about the second one.

Key Takeaways

• Change fatigue is your starting condition. Plan as though your team has already spent most of what it had.

• Inspiration is the fix most leaders reach for. Gartner's research found it only works where trust in change is already high.

• Routine beats persuasion. Gartner's model points to making change ordinary and predictable.

• Certainty is not the lever most change advice assumes. In NLI's 2025 SCARF® data, respondents rank fairness first and certainty last.

• A change people can follow has visible steps, a named owner for each one, and a standing time on the calendar.

Why leading change effectively gets harder every time

Change fatigue is cumulative. Each initiative spends some of what your team has, and the next one starts from a lower place. By the time you launch, the people on the receiving end rarely have fresh attention to give. They have been through this several times already.

Gartner's 2022 research shows how that lines up with whether people plan to stay. Among employees reporting above-average change fatigue, 43% said they intended to stay with their organization. Among employees with low fatigue, 74% said the same. Gartner reports that as a correlation rather than a demonstrated cause, and intent to stay is what people said, not who actually left. It is still a 31-point gap between the tired group and the rested one.

What fatigue looks like on an ordinary Tuesday

It almost never looks like refusal. It looks like this:

• People attend the training, then ask a colleague how to do it the old way.

• Questions get asked once, and then they stop.

• The new process runs for anything that gets audited. The old one runs for everything else.

• Nobody escalates, because the last few escalations went nowhere.

You are not being defied. You are watching people protect a working day that already has too much in it. A tired team needs a smaller ask, not a better argument.

Your one small shift this week: Take the change your team is living with right now and ask three people what they are still doing the old way. Don't fix anything yet. You need the real starting point before you can plan the next step.

The usual fix is to inspire harder, and it stops working first

When adoption stalls, the standard move is to make a bigger case. A better deck, a clearer why, a leader who sounds more convinced.

Gartner looked at how well that holds up. In research published in July 2025, Gartner found that "the inspirational approach only works when there is high change trust. When change trust is low, Gartner's model predicts that only one-quarter of changes led by inspirational leaders would achieve healthy change adoption."

That finding rests on trust, and trust is the part most teams are short on. In the same research, a survey of more than 2,850 employees in April 2025 found that 79% had low trust in change. Only 32% of mid-to-senior leaders said the last change they led achieved healthy adoption.

So the first thing most leaders reach for needs trust that most teams don't have yet. Say why the change matters. Just don't let the why be the plan.

I've seen this happen over and over: a leader gives a wonderful, inspiring talk about the change; everyone leaves fired up, they've got the vision, and they know the why, then the reality of the change hits and crickets. When that happened, I started watching, and it wasn't anyone trying to destroy an initiative, but people just trying to get the work done. What I found consistently was we left too much up for interpretation with the "how" for the overwhelmed state people find themselves in

The brain-based case for routine

Gartner's own conclusion from that research is to make change ordinary rather than exciting. In their words: "When leaders routinize change, our model predicts that employees are three times more likely to adopt changes on time and in a healthy way even though they have low change trust." That is a model prediction rather than an observed result, and Gartner says so.

The reason routine helps is not complicated. Under pressure, people do the response they have practiced most. A new way of working is competing with an old one that has months of repetition behind it, and in a genuinely busy week the practiced one wins. You don't beat that with conviction. You beat it by making the new way the thing people repeat, and by keeping it the same each time so there is something to repeat. Steadiness is cheap to give. It mostly means not changing your own approach halfway through.

This is also where the standard advice misses. Leaders are usually told to give people certainty. But the SCARF® model, David Rock's work at the NeuroLeadership Institute, was updated in 2025. Across more than 15,000 assessment responses from 2024 and 2025, respondents ranked fairness first and certainty last. Autonomy, in NLI's words, jumped "from the bottom of the list in 2012 to a close second in 2025." That is NLI's own assessment data, and it is what respondents say matters to them.

Read plainly, it says the two things people rank highest are whether the change is being handled fairly and whether they have any say in it. Both are things you can do something about this week.

A template for leading change with The Shift Method

The Shift Method is the five step process I use for change, whether it is one person's habit or a rollout across a business: Identify, Question, Reframe, Vision, Act. Here is how it runs when the thing changing is how a team works. Copy the five prompts and answer them in writing before your next update.

Identify. Name what is happening and look past the presenting problem. "Low adoption" is the presenting problem, not the obstacle. Write down the behavior you can see, like "seven of nine people still start the request in the old form, then re-key it," and then ask what a person would have to assume for that to be the sensible choice. The assumption underneath is the thing you are actually working on.

Question. Surface the belief and test it. It is usually something specific: this will be reversed in six months, nobody checks the new field, the person who reviews my work still wants the old format. Ask the people doing the work and write down the answer you get rather than the answer you expected. Some of what you hear will turn out to be accurate, and that is useful too. A real constraint is something you can design around once you know it is there.

Reframe. Give people a more accurate way to see the change. If the answer to step two is that the new way costs someone twenty extra minutes, then the change you are asking for is twenty minutes, not a mindset. Fix the twenty minutes, or say plainly who is absorbing it and why. That is the fairness point the SCARF® data raises, and it is the one most rollouts leave unaddressed.

Vision. Paint the picture concretely, at the level of a working week. Describe the review meeting three months from now: who is in it, which report opens it, what gets decided there, and what a good one feels like to sit in. People can move toward a week they can picture.

Act. Turn it into do-it-Monday actions. Name one owner per step and a standing time when the change gets looked at. Fifteen minutes inside a meeting that already happens will beat a new monthly forum that nobody protects when the quarter gets tight. The change needs a routine slot so it gets repeated in a bad week instead of dropped.

That last step is where most initiatives quietly end. The leader still believes in it. It just never had a place in the calendar that survived a bad month.

Where to start

I spent 18 years running learning and development inside a Fortune 500 company, leading national rollouts that reached thousands of employees and customers, and the ones that stuck were rarely the ones with the best launch. They were the ones where somebody owned a short slot in week seven, when the excitement was gone and the work was still there.

If your team is tired, you have less attention to spend than the plan assumes. Spend it on fairness, on giving people a say, and on repetition. That is a less satisfying answer than a better speech, and it is the one Gartner's research points to.

If you want help designing that into a live initiative, Feed Your Brain | Consulting works with leaders on exactly this.

Frequently Asked Questions

Why do employees agree with a change in the meeting and then not do it?

Agreement and action are different asks. Agreeing costs nothing in the meeting. Doing it costs time on a day that is already full, and the old way is faster because it has been practiced more. When adoption stalls after a good meeting, the useful question is not whether people were convinced. It is what the new way costs them on a normal Tuesday, and whether anyone has removed that cost.

How long does it take for a new way of working to stick?

There is no reliable number of days, and any source that gives you one is selling certainty it doesn't have. Gartner's research points to repetition and predictability mattering more than intensity. A change that gets a little attention every week usually outlasts one that gets a three-day offsite and then nothing.

Is change fatigue the same as resistance?

No, and treating them the same is why plans misfire. Resistance is targeted. Someone has a reason, and it is worth asking them what it is rather than guessing. Fatigue is general. People are not arguing with this change; they have simply run out of room for another one. Resistance needs a conversation. Fatigue needs fewer, steadier initiatives.

What should I do first when a change has already stalled?

Find out what people are doing instead, in specifics, from the people doing it. Most stalled initiatives have a practical blocker nobody mentioned, usually because the last person who mentioned one got nowhere. Start there, not with a relaunch. A relaunch spends attention you have already established you don't have.

Does explaining the why still matter?

Yes, once, clearly. It stops being useful when it becomes the whole plan. Gartner's 2025 research is direct about this: the inspirational approach only works where trust in change is already high, and most teams are not starting there. Say why, then spend the rest of your effort on how the work actually changes and who decides what.

How do I lead a change I don't feel confident about myself, like an AI rollout?

You are not being asked to be the expert on the technology. You are being asked to run the change well, which is a different skill and the one this article is about. Name what you know, name what you don't, and give people a date when you will know more. For leaders who want to build their own fluency alongside the rollout, there is FYB | AI Confidence.

What is the single most common mistake leaders make when leading change?

Stopping too soon. The initiative keeps running, but the leader's attention moves on. The launch gets their full presence, and week seven gets nothing, which is exactly when people decide whether the new way is real.

About this article. Tiffany Whitney is a NeuroLeadership-trained brain-based coach with 18 years of Fortune 500 Learning & Development leadership, and Amazon bestselling co-author of Strength with Kathy Ireland. Statistics are cited to primary sources; where a figure comes from an organization's internal data rather than independent research, that is noted in the text. This article is for educational purposes and is not medical, psychological, or clinical advice. SCARF® is a registered trademark of NeuroLeadership Institute, Inc. or its affiliates. Feed Your Brain is not affiliated with or endorsed by the NeuroLeadership Institute.