The Zombie
Detector.

Is your project alive or just twitching?

A Zombie Project consumes resources but creates no value. It looks alive on dashboards but is dead in the marketplace. These walking dead are draining your organization's capacity to innovate.

Select all symptoms that apply to your project.

The Autopsy Checklist

The "Me-Too" Syndrome

Started because a competitor announced something similar—not because you identified a real problem to solve.

The Executive Pet Project

Exists because a senior leader championed it—and nobody wants to tell them it's failing.

The Metrics Ghost

Success is measured by activity (meetings held, code committed) rather than business outcomes. Nobody can define what "done" looks like.

The Moving Goalposts

The definition of success has changed three or more times. Each time it gets vaguer.

The Silo Seclusion

IT is building it alone. The people who will actually use this haven't been consulted in months.

The Orphan Syndrome

The original sponsor has left, retired, or moved on. Nobody claims ownership anymore.

The Endless Runway

"We just need 6 more months" has been said more than twice. The deadline has been pushed back repeatedly.

The Talent Drain

Good people have quietly transferred off the project. The team is now staffed with whoever was available.

The Customer Void

No actual customer or end-user is asking for this. It solves a theoretical problem that nobody experiences.

The "If We Build It" Fallacy

The business case depends on adoption that has no evidence. "Users will love it once they see it."

The Integration Nightmare

It requires integrating with systems that don't want to be integrated. Data architecture is an afterthought.

The Technology Tourism

The tech stack was chosen because it's "cutting edge" rather than because it fits the problem.

Diagnosis

0/12
The Cure.

Kill It. Learn. Move On.

Stopping a bad project is as important as starting a good one. A killed zombie releases resources for experiments that might actually work.

Reallocate the Budget

Move funds to safe-to-fail experiments with clear hypotheses.

Document the Learning

A killed project with documented lessons is an asset, not a failure.

Ask the Hard Question

"If we deleted this today, who would complain?" If the answer is "nobody," you have your answer.

Celebrate the Kill

Publicly recognize the courage to stop. This builds psychological safety for future experiments.

← Back to The Trenches Scale the Future →