The Complexity Tax
The economic phenomenon where the quadratic formula for connections (n * (n-1)/2) is applied directly to feature bloat within software products. The Complexity Tax dictates that each new feature does not add a linear, isolated cost; rather, it creates combinatorial integration surface area with every existing feature in the system. This tax manifests as exponentially slower release cycles, massive QA burdens, and degraded user experiences as the system grows.
“Every feature you add is a tax on everything you build tomorrow.”
Product teams continually justify new features by looking only at the isolated cost to build them. They ignore the Complexity Tax - the permanent, compounding cost of maintaining that feature and ensuring it does not break the rest of the system. This ignorance leads to feature bloat, where the organization eventually spends 80% of its engineering capacity just maintaining the connections between features rather than creating new value. Understanding this tax is essential for knowing when to sunset legacy features.
Richard Ewing’s Research Thesis
A healthy product roadmap must prioritize feature deletion as highly as feature creation.
Why This Specification Exists
Organizations constantly add features but never remove them, choking their own velocity.
Treating legacy features as free once they are shipped.
No mathematical model explaining why velocity grinds to a halt as feature counts grow.
Applying quadratic network effects directly to software feature portfolios.
What Changes If You Believe This?
Adopts strict "one in, one out" policies for system architecture.
Accounts for compounding maintenance overhead in long-term R&D budgets.
Actively hunts for features to sunset.
Surface area reduction becomes a primary defense strategy.
Recommended Action by Role
Audit product analytics and delete the bottom 10% of features by usage to immediately lower the Complexity Tax.
Latest Publications & Research Activity
When the Cost of Writing Software Approaches Zero, Traditional Product Management Frameworks Break Down
Why Your CFO Hates Your Agile Transformation
The Innovation Tax Audit: Is Your R&D Actually Just OpEx?
Frequently Asked Questions
Q:Why does a new feature slow down the whole team?
Because the new feature must be tested against, integrated with, and designed around all the existing features, increasing the cognitive load for every developer.
Q:How do you lower the Complexity Tax?
By aggressively deprecating and deleting old, unused features. Subtraction is the only way to pay down the tax.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
| Evidence Item | Publisher | Evidence Type | Strength | Role | Action |
|---|---|---|---|---|---|
| Quadratic Burden | Internal | Observation | ★★★★★ | Origin | Inspect ↗ |
Recommended Citation
Ewing, R. (2026). "The Complexity Tax." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/complexity-tax
@article{ewing_complexity_tax,
author = {Ewing, Richard},
title = {The Complexity Tax},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/complexity-tax}
}