Every company has them. An initiative that has been running for so long that asking why it exists feels almost rude. It has a team, a budget line, a slide in the quarterly review, and a status that is reliably some shade of green. What it does not have, if you push on it, is a living reason. The objective it was created to serve has moved on. It was hit two quarters ago, or it was quietly deprioritized, or the strategy pivoted and left this one piece of work behind like a tide going out and leaving a boat in a field.

The initiative did not notice. Initiatives never notice. They keep running on the momentum of their own existence, because in most companies the act of starting work is wired to a decision and the act of stopping it is wired to nothing.

Why dead initiatives keep breathing

Starting an initiative is a moment. Someone decides, allocates budget, names an owner, and the thing begins. Stopping one is not a moment, because nothing forces the question. There is no recurring prompt that asks, for each piece of work in flight, whether the reason it was started still holds. So the default for any initiative is to continue, and continuation requires no decision at all, which means it requires no one to be accountable for it.

This is the structural asymmetry behind most wasted effort. The work was connected to a reason at birth and then the connection was never maintained. When the objective changes, nothing propagates that change down to the work that was serving it, because the link between the objective and the work lives in someone's memory of the kickoff rather than in the structure. This is the silent pivot seen from the work's perspective: the strategy moved and the work did not get the message.

Green is exactly the wrong signal

The cruelest part is that a zombie initiative usually reports healthy. Its team is competent and busy, its milestones are being hit, its dashboard is green. That green measures whether the work is progressing against its own plan. It says nothing about whether the plan still matters. This is the green dashboard problem in its purest form: an initiative can be flawlessly executing toward an outcome that no longer has any value, and every status indicator will applaud it the whole way.

A status system that only tracks progress-to-plan cannot catch this, because progress-to-plan is the wrong question for an initiative whose plan has been orphaned. The right question is progress-to-reason, and almost no tool asks it, because almost no tool holds the link between the work and the reason in a form that can go stale visibly.

The cost is not just the wasted work

The obvious cost is the budget and the people tied up in something pointless. That is real, but it is the smaller cost. The larger one is opportunity. Every zombie initiative is holding capacity that a live priority needs. The engineers maintaining the orphaned work are engineers not available for the bets that actually matter now, which is why capacity is a strategic question and not an HR one. A company full of initiatives that outlived their reasons is a company that feels fully utilized and is somehow never able to staff the thing it most needs to do, because its capacity is pre-committed to the ghosts of old decisions.

There is a cultural cost too. People know. The team running the zombie initiative usually senses that the energy has gone out of it, and working on something everyone quietly suspects is pointless is corrosive in a way that shows up later as disengagement. This is one of the quieter mechanisms behind the quiet quitting of strategy.

How to make initiatives die on schedule

The fix is to wire stopping to the same structure as starting. Every initiative should be linked to the objective it serves, and that link should be live, so that when the objective is hit, changed, or dropped, the initiatives hanging off it are immediately flagged as having lost their reason. The question "does this still serve a live objective" should be answered by the structure continuously, not by a brave person remembering to ask it in a review.

When work is traceable to the goal it serves, an orphaned initiative cannot hide, because the moment its objective goes away, its trace points at nothing, and a piece of work pointing at nothing is a visible anomaly rather than an invisible default. The review stops being a place where everything reports green and becomes a place where the few initiatives that have lost their reason light up on their own. You do not need the courage to ask whether everything still matters. You need a structure where the things that stopped mattering announce themselves.

What to do this quarter

Run a reason audit. List every initiative currently consuming meaningful capacity and, for each one, name the specific objective it serves and check whether that objective is still live and still a priority. Do not accept "it supports the strategy" as an answer. Demand the specific objective. The initiatives that cannot name a live one are your zombies, and the capacity they hold is the capacity your real priorities are missing.

Then kill at least one. Not pause, not deprioritize, kill. The hardest part is not identifying the zombie. It is the social cost of ending something with a competent team and a green dashboard, which is exactly why these things survive. If your operating rhythm cannot routinely end work that has outlived its reason, you do not have a prioritization problem. You have a stopping problem, and it is quietly eating the capacity you need for everything else.

FAQ

What is a zombie initiative? A piece of work that keeps running after the objective it was created to serve has been hit, changed, or abandoned. It still has a team, a budget, and a green status, but no living reason. It survives because starting work requires a decision while continuing it requires none, so continuation is the default.

Why don't dashboards catch initiatives that outlived their reason? Because dashboards measure progress-to-plan, not progress-to-reason. A zombie initiative executes its plan flawlessly and reports green the whole way, while the plan itself has been orphaned. Catching it requires a live link between the work and the objective it serves, which most tools do not hold in a form that can visibly go stale.

What does a zombie initiative actually cost? More than its budget. It holds capacity that live priorities need, which is why capacity is strategic. A company full of them feels fully utilized yet can never staff its most important new bet. There is also a morale cost: people sense the energy has gone and disengage.

How do we stop initiatives on time? Wire stopping to the same structure as starting. Link every initiative to its objective so that when the objective is hit or dropped, the work hanging off it is flagged as reasonless automatically. When work is traceable to its goal, orphaned initiatives announce themselves instead of hiding behind green.