Your Change Stopped in April. Nobody Told You.

By Heather Haygood, founder and Chief Leadership Strategist of HMH Solutions.

It is the third week of October, and a director is walking her leadership team through the year. Slide nine is the new intake process her team launched in January. Every box on it is green.

After the meeting, she stops by a coordinator's desk to ask about something else. On his second monitor is a spreadsheet she recognizes. It is the tracker the new system was supposed to replace.

"Oh, that," he says. "We all still use it. The new one takes forever when we're slammed."

She asks how long. He thinks about it. "Since spring, maybe?"

The slide has been green since January.

A change can stop without anyone deciding to stop it

A stalled change is one people have stopped using in practice while it still counts as done on paper. Nobody announced it. Nobody pushed back in a meeting. The team went back to what worked under pressure, and the report kept saying what it said in February.

Why do change initiatives stall after launch?

Change initiatives usually stall when the new way costs people more than the old way on their worst days, and nobody feels safe saying so. In my work, I almost never see a team decide to abandon a change. They drift back to the old way one bad week at a time.

Every new process is slower while people learn it. On a normal week, they push through. On a short-staffed week with a deadline, they reach for whatever they can do without thinking, and that is the old way.

The workaround makes sense to the person using it. It also helps the people around them, so it spreads. And nobody escalates, because raising it feels like admitting you are not complying, or like criticizing something leadership is proud of.

Here's the shape I see this take most often:

1. January. The change launches. Training happens, people attend, and the go-live date holds.
2. February. The new way is slower while people learn it. Leaders expect that.
3. March. A deadline lands on a short-staffed week. Someone finishes the work the old way, just this once.
4. April. A colleague sees it working and asks how. Now two people are doing it.
5. Summer. The old tool is back in daily use. New hires learn the workaround from their peers.
6. October. The status report still says complete, because everything it measures was completed.

Look at what is missing from that sequence. Between January and October, nobody went looking. The report tracked what was finished, so it stayed green, and the leader found out by accident.

How do you know if a change is actually sticking?

You know a change is sticking when you check for it on a schedule, using evidence, before anyone has a reason to tell you it slipped. That means deciding before launch when you will look and what you will look for.

For a small project, five checkpoints are enough: before launch, at launch, at the midpoint, at wrap-up, and a few months later, when the change should be how the work gets done. The bigger and longer the change, the more checkpoints you add in between. Put them all on the calendar the week you announce the change. Checkpoints that are not scheduled before go-live get pushed aside by whatever comes next.

At each checkpoint, look at five signals:

Rate each signal with one of four words. On track means you are seeing what you hoped to see by now. Watch means it is moving, but unevenly, or only because a few people are carrying it. Gap means it has not moved. Too early means it is not time to expect it yet.

That last rating matters more than it looks. At launch, Apply, Sustain and Integrate should mostly read Too early. Marking them as gaps makes a healthy change look like it is failing, and leaders start fixing things that are not broken.

Every rating needs evidence. Before you mark anything On track, ask yourself how you know.

Gathering that evidence takes emotional intelligence. Resistance during a change is rarely loud. It shows up as quiet workarounds from people who do not feel safe telling you the new way is not working for them, and silence in a rollout meeting does not mean people agree. The status report will never show you that. The people doing the work will, if you ask in a way that makes it safe to answer.

Ask what people actually do, and make it safe to answer

At any checkpoint, your best evidence comes from the people doing the work. Be upfront that you are checking how the process is working, and make it clear you want the real answer. If it sounds like a compliance check, you will hear the process recited back to you.

"I'm looking at how the new process is really working, and you'd know better than anyone. Walk me through how the work gets done now, especially on a busy week. Where has it slowed you down? Have you found a better way? I'd rather hear it now, while we can still fix it."

When a signal reads Gap, tell the team what you found before you fix anything:

"I talked with a few of you about the intake process, and it's clear the new way isn't working on busy weeks. That's on how we rolled it out. Nobody's in trouble for finding a workaround. Here's what we're changing, and I'd like your help getting it right this time."

Many companies stop leading the change at launch

Adoption is the point where people use the new way on a bad week without being reminded. It happens long after go-live, when many companies have moved on to the next priority. Teams notice when that happens, because your team takes its cues from what you pay attention to. This is the part leading change training should prepare leaders for.

I built the ALIGN Change Leadership System© for leaders who carry change on top of their day job. It is the framework behind my change management training, and its last two phases, Guide Adoption and Nurture Integration, exist for this stretch. In ALIGN, the checkpoints and signals above make up the Adoption Check inside the Change Alignment Index.

You do not need ALIGN to start. A calendar invite and the five questions in that table will catch most drift months before a status report would.

Start with your next change, and catch up on the last one

For the next change you lead, put your checkpoints on the calendar before you announce it. Paste the five questions from the table into each invite.

If a change from earlier this year is already drifting, do not wait for a checkpoint you never scheduled. Pick that change and ask three people who do the work every day what they actually do now, on a week when they are behind. Talk to them separately, so nobody is answering for the group.

In my experience, you will get three different answers, and none of them will match the process. The distance between those answers and the process is where your change really stands.

Then say out loud what you found. Fix whatever made the new way slower than the old one. Relaunch smaller, with the people who found the workaround helping shape it, because they already know where the new way cost too much. And this time, put the checkpoints on the calendar before you go live.

If you want the full system, the ALIGN Change Leadership System© gives busy leaders a clear way to lead change and the emotional intelligence to bring people along. The ALIGN Journey Planner keeps every checkpoint, rating and action in one place, including the Change Alignment Index. See how ALIGN works.

Heather Haygood is the founder and Chief Leadership Strategist of HMH Solutions in the Treasure Valley, Idaho. She is a Prosci-certified change practitioner, a Genos Certified EI Practitioner, and a Boise State University instructor. She created the ALIGN Change Leadership System© for busy leaders who lead change on top of their day job, with a heavy focus on emotional intelligence and leadership presence. She also created the EQ Mastery Cycle©.

Frequently asked questions

What skills do leaders need to lead change?

In my work, leadership presence comes first: people watch how you show up during a change and decide from that whether to commit to it. Close behind are checking for adoption on a schedule, listening for what people are not saying, and adjusting a change without abandoning it. Emotional intelligence sits under all of them, because most resistance to change shows up in behavior long before anyone says it out loud.

How is change leadership different from change management?

Change management is the structured process an organization uses to plan, communicate and track a change, and change leadership is how the leaders closest to the work carry that plan day to day. The two depend on each other: the plan tells leaders what is changing and when, and leaders are the ones who get people to use it on a busy week. In my experience, the leadership side is the one most often left to chance, which is why so many well-planned changes stall after launch.

How do you know if a change has stalled?

Check at set points after launch instead of waiting for the status report. Ask whether people use the new way on a busy week, whether it continues without reminders, and whether new hires learn it from their peers. If the old tool is back on people's screens, the change has stalled.

Should you relaunch a change that stalled?

Usually, yes, but smaller, with the people who found the workaround helping shape it and with checkpoints scheduled before go-live. Their workaround shows you where the new way cost too much. A relaunch that ignores it tends to stall in the same place.