What is Zombie Feature?
A zombie feature is a product feature that is technically alive (deployed, receiving maintenance, consuming resources) but effectively dead (few or no users, minimal revenue impact, no strategic value).
A zombie feature is a product feature that is technically alive (deployed, receiving maintenance, consuming resources) but effectively dead (few or no users, minimal revenue impact, no strategic value). Zombie features persist because organizations lack the data or courage to kill them.
Zombie features are uniquely destructive because they compound:
- Maintenance cost — every sprint, engineers spend time keeping zombie features compatible with platform changes - Cognitive overhead — new engineers must understand code paths that serve no users - Testing burden — QA must verify zombie features don't break during releases - Security surface — unmaintained code paths become vulnerability vectors
Why It Matters
Richard Ewing's Feature Bloat Calculus quantifies how zombie features destroy engineering economics. In a typical SaaS product, 20-40% of features are zombie features, consuming 15-30% of total maintenance burden.
The Kill Switch Protocol provides a systematic framework for identifying and deprecating zombie features. Companies that execute the Kill Switch Protocol typically recover 20-40% of engineering capacity.
How to Measure
Feature usage analytics: MAU per feature, revenue attribution per feature, maintenance hours per feature. Features below a threshold on all three metrics are zombie candidates.
Frequently Asked Questions
Why don't companies just remove zombie features?
Fear of breaking things, fear of upsetting the one customer who uses it, sunk cost fallacy, and lack of usage data. The Kill Switch Protocol addresses all four blockers.
How many zombie features does a typical SaaS product have?
Products with 3+ years of development history typically have 20-40% zombie features by feature count, representing 15-30% of maintenance burden.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →