What is Zombie Features?

Zombie Features is a term coined by Richard Ewing to describe product features that are technically alive (still running in production) but functionally dead (no meaningful usage, no revenue contribution, no strategic value). Like zombies, they consume resources while producing nothing of value.

Zombie features come in four varieties:

Ghost Features: Built, launched, and never adopted. They sit in the codebase consuming maintenance hours but have near-zero usage metrics.

Legacy Bridges: Compatibility layers, deprecated API versions, and backward-compatible code paths that serve a tiny percentage of users but add complexity to every future change.

Vanity Features: Built because a senior stakeholder wanted them, not because users needed them. Protected by organizational politics rather than business merit.

Abandoned Experiments: A/B test variants never cleaned up, prototypes that became permanent, and "temporary" solutions that became load-bearing infrastructure.

Richard Ewing's audits find that 40-60% of a typical codebase consists of zombie features, consuming 30-50% of the total maintenance burden.