Every organization has them. AI projects that aren't clearly succeeding but aren't obviously failing either. They consume resources, occupy your best talent, and create the comforting illusion of progress. In internal updates, they're always "making progress" or "on track." But dig deeper and you'll find they've been "almost ready" for months.

These are zombie projects. And they're more dangerous than outright failures.

A project that fails fast teaches you something. A zombie project teaches you nothing while draining resources that could fund initiatives that actually work.

The Zombie Identification Checklist

How do you know if you have a zombie project? Watch for these red flags:

Shifting success criteria. The project started with specific metrics, but those have been quietly adjusted—usually downward. What began as "20% cost reduction" has become "demonstrate feasibility" or "build organizational capability."

Perpetual pilot stage. The project has been running for 6+ months without a clear go/no-go decision. Every review meeting ends with "let's give it another quarter."

Champion dependency. One enthusiastic leader keeps the project alive through sheer force of will. If that person left, the project would die within weeks.

Demo-driven progress. The team produces impressive demos but can't articulate a realistic path to production deployment. The demo works with curated data in controlled conditions—a very different environment from production.

Budget creep without value creep. Costs keep increasing—more data, more compute, more specialized talent—but measurable business value remains elusive.

If two or more of these apply, you likely have a zombie on your hands.

Why Zombies Survive

Zombie projects persist because killing them is psychologically and politically harder than funding them. Several forces conspire to keep zombies alive:

Sunk cost fallacy. "We've already invested $2M—we can't walk away now." This reasoning ensures you spend $4M on something that will never deliver value rather than redirecting $2M to something that might.

Career risk. Nobody wants to be the leader who killed an AI project. Failure is personal. Continuing a struggling project feels safer than admitting it should stop.

Optimism bias. Technical teams genuinely believe the next iteration will work. "If we just get better data..." or "Once we upgrade the model..." There's always one more thing that will fix it.

Strategic ambiguity. Without clear success criteria defined upfront, it's impossible to declare failure. If you never defined what success looks like, you can't prove the project has failed.

The Discipline Framework

Killing zombie projects requires deliberate organizational discipline. Here's a framework that works:

1. Define Kill Criteria Before Launch

Every AI pilot should have explicit kill criteria—conditions under which the project stops, regardless of how much has been invested. Define these before the pilot starts, when everyone is rational and unemotional.

Examples of effective kill criteria:

Accuracy below 80% after 90 days of development
Cost per prediction above $X threshold
User adoption below 30% after 60 days of deployment
No measurable business impact after 6 months

2. Schedule Go/No-Go Reviews

Build mandatory decision points into every pilot timeline. At each review, the project must demonstrate measurable progress against predefined criteria—or face shutdown.

The key: reviews must result in actual decisions. "Continue with modifications" is valid. "Let's revisit next quarter" is not.

3. Separate the Decision-Maker from the Champion

The person who decides whether a project continues should not be the person who championed it. Champions are emotionally invested. Decision-makers need to be analytically detached.

4. Celebrate Disciplined Shutdowns

When you kill a project based on evidence and predefined criteria, celebrate it. Publicly recognize the team for learning quickly and freeing resources. Make it clear that disciplined failure is valued more than prolonged mediocrity.

The Paradox of Pilot Discipline

Here's the counterintuitive truth: organizations that are willing to kill more projects end up succeeding with more projects. Why? Because they free resources from zombies and redirect them to initiatives with genuine potential.

The 5% that succeed with AI don't have a higher success rate on individual pilots. They have faster cycle times. They launch more experiments, evaluate them rigorously, kill the failures quickly, and double down on the winners.

The discipline to kill what isn't working is the discipline that enables what could.

Your Next Step

If you suspect zombie projects in your portfolio, start with an honest assessment. The AI Leadership Assessment evaluates your Pilot Discipline alongside six other critical dimensions. Understanding where your organizational discipline gaps are is the first step toward fixing them.

The hardest part isn't identifying zombies. It's building the organizational courage to shut them down.

Pilot Discipline: The Art of Killing Zombie AI Projects