Why a Stalled Initiative Is One of the Most Expensive Things in Your Business
The initiative nobody killed
Eight months ago you approved a rollout. The business case was solid, the vendor was signed, the kickoff had a slide with a go-live date on it. Training happened. The executive sponsor sent an email. For about six weeks, the dashboards moved.
Then a quarter closed. A key manager left. Two teams got an exemption "for now." The status update moved from weekly to monthly, then stopped appearing on the agenda altogether.
Nobody said the initiative was over. Nobody can say it's done, either. Ask the leadership team, and the answers don't match.
That disagreement is costing you more than anything else on the agenda, and I want to show you why.
Key takeaways
- A stalled initiative was approved, funded, and launched, but never fully adopted. Some people think it's done. Others don't. Nobody defined "done."
- The launch spend is the smallest part of the bill. The real cost is the meter that never stopped: the workaround tax, the leadership attention, and the trust it drains from your next change.
- Initiatives stall for reasons you can name. The new routine never got enough repetitions, and someone signaled that stopping was allowed.
- The recovery question is not "how do we relaunch." It is "what stopped, and what would it take to finish." Sometimes the answer is stop.
What is a stalled initiative?
A stalled initiative is one that was approved, funded, and launched, but was never fully adopted or operationalized. Ask five people on the leadership team whether it's done and you get three answers. Two say yes, it launched. Two say no; half the teams never picked it up. One asks what "done" was supposed to mean.
That last question is usually the diagnosis. Either the initiative never met the success measures, or, more often, no success measures were agreed on before launch, so there was nothing to hit. Without them, "done" is an opinion, and every opinion in the building is different.
That is why I don't use the word failed for these. Nothing was evaluated. Nothing was decided. The initiative just sits in the gap between launched and finished, and it keeps costing you the whole time.
Why is a stalled initiative so expensive?
Most leaders think of the cost as the money already spent: licenses, consultants, design time, training days, and the hours your best people put into the plan. That number is real. It is also already gone.
It is also the smallest part of the bill.
The workaround tax
When a new process stalls partway, people don't go back to the old way. They run both. The team that got the exemption uses the old system. The team that didn't uses the new one, then re-keys the output into the old one so the exempted team can read it.
Somewhere in your organization there is a person, usually a good one, who spends part of every week translating between the change you launched and the change you didn't finish. Nobody assigned that work. Nobody budgeted it. It is the workaround tax, and it is paid in the hours of the people you can least afford to lose.
You can estimate your own version of it in ten minutes. Count the people who touch both the old way and the new way. Estimate the hours per week each of them spends reconciling the two. Multiply by the weeks since the initiative stopped moving. That number is not hypothetical. It is on your payroll.
The attention it keeps absorbing
A stalled initiative still generates meetings. Someone still prepares a status slide, and someone senior still reads it and feels a small drop in their stomach. Every leadership meeting that touches the stalled item spends a few minutes on it and then moves on without a decision, which means the same few minutes get spent again next month.
Leadership attention is the scarcest resource in the building. A stall spends it on nothing.
What it charges the next change
This is the cost that compounds, and it is the one I watched do the most damage over 18 years leading learning and development inside a Fortune 500 company.
Gartner's research, published in Harvard Business Review in 2023, found that the number of planned enterprise changes an average employee experienced rose from two per year in 2016 to ten in 2022. Over the same period, the share of employees willing to support organizational change fell from 74 percent to 43 percent. You can read the HBR piece here: Employees Are Losing Patience with Change Initiatives.
Gartner put a number on the wait-and-see reflex in a second survey, released in October 2025. Of nearly 1,000 mid- to senior-level leaders surveyed in April 2025, 36 percent said their team is more likely to hesitate and delay action to see whether a change will stick before adopting it. That release is here: Gartner HR research on change goals.
Now think about what a stalled initiative teaches the people who lived through it. They learn that launches don't have to finish, that an exemption is available if you wait long enough, and that the sponsor's email means "for now." Nobody says any of that out loud, and everybody learns it anyway.
So the next change you announce arrives with people who already know it might not stick. That is the most expensive line on the bill, and it never shows up in a budget review.
one small shift: before the next launch, close the last one. Publicly finish it or publicly stop it. Either decision is cheaper than the pause.
Why do initiatives stall?
I want to be careful here, because the usual answer is "people resist change," and that answer has done more harm than good. It lets leaders off the hook, and it makes employees the problem.
The useful number comes from a July 2025 Gartner survey of mid- to senior-level business leaders, in which only 32 percent said the last change they led achieved healthy employee adoption. Gartner's release is here: Gartner HR research on healthy change adoption.
Two-thirds of leaders, by their own account, did not get the change to stick. In my experience, two things sit underneath that number, and a third usually follows.
The new routine never got enough repetitions
Habit science gives you a useful reference point. In a widely cited 2010 study on how long habits take to form, Lally and colleagues found a median of 66 days for a new behavior to feel automatic, with a range from 18 to 254 days depending on the person and the behavior. That study looked at simple daily habits rather than workplace processes, so treat the number as a floor rather than a promise.
Most rollouts protect the new behavior for two weeks. Training day, a follow-up email, maybe a floor walk. Then the quarter gets busy, and under pressure the practiced response is faster than the new one. People are not choosing the old way. The old way is simply the one that shows up first when there's no time to think.
An initiative that stalls at week six most often ran out of repetitions long before it ran out of buy-in.
Somebody signaled that stopping was allowed
Every stall I have examined has a moment in it, and it is rarely dramatic. An exemption granted to one team, a deadline that slid without comment, a leader who stopped asking. None of those moments looks like a decision. Each one is read as one.
The NeuroLeadership Institute's SCARF® model, developed by David Rock, names five social concerns that shape how people respond at work: status, certainty, autonomy, relatedness, and fairness. NLI's own 2025 assessment data, drawn from more than 15,000 responses, now shows respondents ranking fairness first and autonomy a close second. That is their data, not independent research, but it lines up with what a stall looks like from the inside.
When one team gets an exemption, every other team reads it as a fairness question. Why them and not us? When the new process removes a judgment call people used to make, that is an autonomy question. Neither gets answered in a status meeting, so people answer it themselves, and the answer is usually "this isn't real."
I saw this on a national software rollout. The MVP had been agreed, but one feature was not planned for it, and without that feature one group could not use the system at all. That group had a legitimate reason to wait. Every other group could have used the system as it was. Most didn't. Nobody talked about the one group not using the tool, and that silence did the damage. If leadership could let one group sit out without a word, then sitting out was allowed. One group's gap became everyone's permission. Nobody resisted. They read the quiet as a decision. That rollout didn't get real adoption until three iterations later, almost a year on. A year of the meter running, over a gap nobody named.
The inspiration ran out before the routine formed
Gartner's 2025 analysis also found that the inspirational approach to change only works when change trust is already high. When change trust is low, their model predicts that only one-quarter of changes led by inspirational leaders would achieve healthy adoption.
That matters for the relaunch instinct. When an initiative stalls, the first idea in the room is usually a bigger kickoff with a better speech, a new name, and always more training. But if the building has low trust in change, and after a stall it does, another round of inspiration is the intervention least likely to work. What works is routine: make the new behavior the default and protect the repetitions until it's a habit.
one small shift: stop asking "how do we re-energize this." Ask "what is the one thing that would make the new way the path of least resistance on a busy day?"
Should you restart it or stop it?
Either answer can be right. What is never right is the pause.
This is how I work through it with a leadership team, using the same five steps I use with an individual who is stuck. I call it The Shift Method, and it applies to a stalled initiative as cleanly as it applies to a stalled career.
Identify what actually stopped, and be specific about it: the behavior, the team, the week. Most leaders describe a stall in general terms because nobody has gone and looked. Go and look. Talk to the people running the workaround. They know exactly where it broke.
Question the story the organization is telling about it. "The system doesn't fit our workflow." "The team wasn't ready." "We lost the sponsor." Each of those is a belief, and you can check each one against evidence. Some will hold up. Most won't.
Reframe the situation as recovery of spend you have already made. You are deciding what to do with an investment that stopped short, and that is a business decision like any other. That framing changes the approach. It takes the blame out and puts the money back on the table.
Vision the finished state in detail. Describe what "done" looks like on a Tuesday afternoon six months from now, and who is doing what differently. Then write the success measures the launch skipped, so that next time the question has an answer. And, everybody can describe the finished state.
Act on two lists. The first is the fixes to make within the initiative's scope: the exemption to close, the repetition to protect, the default to change. The second is the other fixes needed, the ones that belong to a different owner or a different budget. Separate them, or the second list will be used as a reason to do nothing on the first.
And if the evidence says stop, you should stop. A clean stop with a decision behind it is a legitimate business outcome. It closes the meter. It tells the organization that leadership finishes what it starts, even when finishing means ending.
one small shift: put a decision date on every initiative that has gone quiet for a month. Not a relaunch date. A decision date.
Frequently asked questions
What is the difference between a stalled initiative and a stopped one?
A stopped initiative has an ending. Somebody measured it and made a decision. A stalled initiative was approved, funded, and launched, but never fully adopted. Usually no success measures were agreed, so nobody can say whether it's done. Nothing gets evaluated, so the cost keeps running: workarounds, leadership attention, and less trust in the next change.
How do I calculate what a stalled initiative is costing us?
Start with the workaround tax. Count the people who touch both the old way and the new one, estimate their weekly hours spent reconciling the two, and multiply by the weeks since progress stopped. Add the recurring meeting time spent on status updates that produce no decision. Then account for the harder number: the share of people who will support your next change, which Gartner's research shows has been falling across organizations for years.
Is it better to relaunch a stalled initiative or start over?
Neither, until you know what actually stalled it. A relaunch without a diagnosis repeats the stall with a new name. Starting over wastes spend you've already made. The first step is to identify the specific point where the behavior stopped, check the organization's story against evidence, and then decide.
Why does a bigger kickoff not fix a stalled initiative?
Because after a stall, change trust is low, and Gartner's 2025 analysis found that inspirational approaches only work when change trust is high. What restarts a stalled initiative is routine. Close the exemptions and protect the new behavior long enough for it to become the default.
Where to go from here
The money for this change is already spent, and the people who built the workarounds already know where it broke. What is missing is a clear look at the evidence, and a decision.
If you have an initiative that went quiet and you want a straight answer on whether to finish it or close it, that is exactly what the Signature 30-Day Change Engagement is built to give you. Book a discovery call and bring the one that's been sitting on the agenda.
Shift your thinking. Change everything.
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.
