Zombie Features
Zombie Features are low-usage legacy software capabilities that consume ongoing maintenance costs without generating revenue.
“Every zombie feature in your codebase is a tax on your engineers and a drag on your balance sheet.”
Zombie features are the primary contributor to Product Debt Index inflation. Every zombie feature requires regression testing on every release, slows down database queries, and introduces security vulnerabilities without generating customer value.
Multi-Hop Causal Traversal Engine
Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.
Zombie Features
Zombie Features are low-usage legacy software capabilities that consume ongoing maintenance costs without generating revenue.
Direct Relationships (4)
Transitive Neighbors (Connected via Hop 1)
Extended Causal Ripple Effects
Richard Ewing’s Research Thesis
We must identify and sunset zombie features before they trigger technical insolvency.
Why This Specification Exists
Product teams rarely delete features, leading to unsustainable complexity accumulation.
Ignoring old features and hoping they do not break.
No financial or product taxonomy defining when a feature has outlived its economic utility.
The Zombie Feature classification providing clear quantitative retirement criteria.
What Changes If You Believe This?
Frees engineers from maintaining dead code paths and slow test fixtures.
Eliminates wasted infrastructure hosting and third-party API costs.
Focuses roadmap attention on high-adoption core features.
Reduces the attack surface area of unmaintained legacy code.
Recommended Action by Role
Audit your feature portfolio against active usage to identify zombie candidates.
Product Debt Index (PDI)
Measures the carrying cost of zombie features across your software portfolio.
Frequently Asked Questions
Q:What defines a Zombie Feature?
A feature with under 5% monthly active usage that still requires bug fixes, regression testing, and compute resources.
Q:Why are Zombie Features dangerous?
They add cognitive complexity to the codebase, slow down deployments, and consume engineering salaries on dead code.
Canonical Specification Origin
Low-usage legacy features drain engineering capital.
Corpus Interconnections
Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.
External Adoption & Peer Citations
Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.
External Evidence: No independently verified references recorded yet.
This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
Recommended Citation
Ewing, R. (2026). "Zombie Features." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/zombie-features
@article{ewing_zombie_features,
author = {Ewing, Richard},
title = {Zombie Features},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/zombie-features}
}