Six Months In and Nobody Uses It: Why Change Initiatives Stall After the Announcement

You announced it in March. A new system, a new process, an executive sponsor, and a launch deck that got a real round of applause. It is now September. Roughly a third of the team is using it the way it was designed. The rest have quietly rebuilt the old workflow in a spreadsheet nobody mentions in status meetings.

Nobody refused. That is what makes this so hard to address. There was no confrontation, no petition, and no one stood up and said, "This will not work." There was agreement in the room and drift outside of it. And now you are stuck deciding whether to push harder, start over, or quietly let it fade and call the rollout a success.

Resistance to change almost never looks like resistance. It looks like capable people who mean well and never quite get to it. Which is why the standard responses - more training, more communication, more executive visibility - so often make things worse. They treat a diagnosis problem as a volume problem.

Start by Naming What the Change Actually Costs Them

The Rawe Adaptive Leadership Framework begins with diagnosis rather than persuasion, and the first diagnostic question is not "why won't they adopt it?" It is "what does adopting it take away?"

Every change carries a price tag, and that price tag lands on someone else's desk. A new process retires a workaround a senior analyst spent two years perfecting. A new tool makes a manager's informal influence less valuable, because now the information is visible to everyone. A new reporting cadence forces a team that has been quietly protecting its own capacity to explain where the time goes.

None of those are bad people. They are people accurately assessing that the change is a downgrade for them personally, even when it is an upgrade for the organization. Until you can name that trade in specific, individual terms - not in change-management abstractions - you are negotiating with a problem you have not defined.

I usually do this in short one-on-ones, and the question is blunt: what does this make harder for you? The first answer is polite. The third one is useful.

Change the Habit That Keeps the Real Objection Off the Table

Here is the part most leaders would rather skip: the reason the honest objection never reached you is usually something you did, repeatedly, without noticing.

It is the sigh when someone raises a concern late in a meeting. It is the phrase "we've already decided this" used to close a conversation rather than open the next one. It is the pattern where the people who ask hard questions get a little less airtime the following week. None of it is malicious. All of it teaches a team that the fastest route to a peaceful Thursday is agreement in the room and a workaround afterward.

So the framework's second move is behavioral, and it applies to the leader before it applies to anyone else. Pick one habit and change it visibly. For the next month, when someone raises an objection to the rollout, write it down in front of them and repeat it back before you respond. That is the whole assignment. Not "be more open" - an actual, observable behavior your team can watch you perform.

What that buys you is not warm feelings. It is data. You cannot adapt a change you are not receiving accurate information about.

Put the Change Where the Work Already Lives

Most initiatives die in the gap between launch and routine. The announcement gets a meeting. The follow-through gets a reminder email.

The third step is to build the change into the operating rhythm your team already runs on instead of stacking a new ceremony on top of it. Adoption becomes a standing five-minute item in the meeting that already happens every week - not a separate check-in that competes with real work. Blockers get a named owner and a date in the same tracker everything else uses. And critically, you commit in advance to changing the rollout based on what you hear, then do it publicly at least once.

One visible adjustment, credited out loud to the team member whose objection prompted it, does more for adoption than a full quarter of reinforcement messaging. Adaptive is the operative word. A change that cannot absorb feedback is not a change initiative. It is an announcement with a deadline attached.

If the Rollout Has Stalled, You Have Better Options Than Pushing Harder

A stalled change is not evidence that your team is difficult or that the original decision was wrong. It is usually evidence that the change was designed for the organization and not for the twelve people who have to live inside it every day. That distinction is where the work is.

It is also fixable, and usually faster than starting over. If you are six months into something that has not taken hold - or you are about to launch something and would rather not end up here - I would be glad to talk it through with you. Reach out through williamcrawe.com and let's take an honest look at what your team is already trying to tell you.