BlogTechnical Debt
Technical Debt6 min read

Real Innovation Requires Deleting Code, Not Writing It

An expert analysis of how to audit for features you can deprecate and how to delete them. Introduces the Sunset Protocol for governing subtraction.

By Richard Ewing·

The Engineering Obsession with Addition

Engineering teams love to build. Product Managers love to launch. But very few organizations celebrate the deletion of code. The result is "Feature Gravity" — an ever-expanding codebase that demands an increasingly large share of your R&D budget just to maintain.

The Sunset Protocol

Real innovation capacity is unlocked by subtraction. The Sunset Protocol is a rigorous governance framework for deprecating code:

1. Economic Audit: Measure the usage and revenue attribution of every feature against its maintenance cost. If Cost > Value, mark it as a Zombie Feature.
2. The Kill Switch: Put the feature behind a toggle. If nobody complains for 30 days, delete the underlying infrastructure.
3. Capacity Reallocation: Measure the hours saved and immediately reallocate them to high-margin, cap-ex initiatives.

Deleting code is the highest ROI action a CTO can take to extend the team's Technical Insolvency Date.


Calculate your maintenance burden instantly at richardewing.io/tools/pdi. Original run on Built In.

Like this analysis?

Get the weekly engineering economics briefing — one email, every Monday.

Subscribe Free →

More in Technical Debt

Published Work

This article expands on ideas from my published work in CIO.com, Built In, Mind the Product, and HackerNoon. View published articles →

📊

Richard Ewing

The Product Economist — Quantifying engineering economics for technology leaders, PE firms, and boards.