What is Sunset Protocol?
The Sunset Protocol is a structured deprecation methodology introduced by Richard Ewing in Built In for safely removing features from a software product.
⚡ Sunset Protocol at a Glance
📊 Key Metrics & Benchmarks
The Sunset Protocol is a structured deprecation methodology introduced by Richard Ewing in Built In for safely removing features from a software product. It provides a governance framework for subtraction — the organizational discipline of removing things, which is harder politically than adding them.
The Sunset Protocol has five stages:
Stage 1: Identify — Flag features below 5% of peak usage, $0 revenue attribution, or maintenance cost exceeding 10% of value contribution.
Stage 2: Quantify — Calculate total cost of keeping the feature alive: direct maintenance hours × fully-loaded engineer cost × opportunity cost multiplier.
Stage 3: Communicate — Notify affected users and stakeholders with clear timelines. Provide migration paths where applicable.
Stage 4: Deprecate — Feature flag the feature off for new users, then gradually for existing users. Monitor for unexpected breakage.
Stage 5: Remove — Delete the code with rollback capability. Clean up dependencies, tests, and infrastructure. Monitor for 30 days post-removal.
The Sunset Protocol is the execution methodology that pairs with the Kill Switch Protocol (which identifies what to kill) and Feature Bloat Calculus (which quantifies why to kill it).
🌍 Where Is It Used?
Sunset Protocol is implemented across modern technology organizations navigating complex digital transformation.
It is particularly relevant to teams scaling beyond their initial product-market fit, where operational maturity, predictability, and economic efficiency are required by leadership and investors.
👤 Who Uses It?
**Technology Executives (CTO/CIO)** leverage Sunset Protocol to align their technical strategy with overriding business constraints and board expectations.
**Staff Engineers & Architects** rely on this framework to implement scalable, predictable patterns throughout their domains.
💡 Why It Matters
Most organizations have no process for removing features, which is why codebases grow endlessly. The Sunset Protocol provides the governance framework for safe, accountable subtraction.
🛠️ How to Apply Sunset Protocol
Step 1: Assess — Evaluate your organization's current relationship with Sunset Protocol. Where is it strong? Where are the gaps?
Step 2: Define Goals — Set specific, measurable targets for Sunset Protocol improvement aligned with business outcomes.
Step 3: Build Plan — Create a phased implementation plan with clear milestones and ownership.
Step 4: Execute — Implement changes incrementally. Start with high-impact, low-risk improvements.
Step 5: Iterate — Measure results, learn from outcomes, and continuously refine your approach to Sunset Protocol.
✅ Sunset Protocol Checklist
📈 Sunset Protocol Maturity Model
Where does your organization stand? Use this model to assess your current level and identify the next milestone.
⚔️ Comparisons
| Sunset Protocol vs. | Sunset Protocol Advantage | Other Approach |
|---|---|---|
| Ad-Hoc Approach | Sunset Protocol provides structure, repeatability, and measurement | Ad-hoc requires zero upfront investment |
| Industry Alternatives | Sunset Protocol is tailored to your specific organizational context | Alternatives may have larger community support |
| Doing Nothing | Sunset Protocol creates measurable, compounding improvement | Status quo requires zero effort or change management |
| Consultant-Led Only | Sunset Protocol builds internal capability that scales | Consultants bring external perspective and benchmarks |
| Tool-Only Solution | Sunset Protocol combines process, culture, and measurement | Tools provide immediate automation without culture change |
| One-Time Project | Sunset Protocol as ongoing practice delivers compounding returns | One-time projects have clear scope and end date |
How It Works
Visual Framework Diagram
🚫 Common Mistakes to Avoid
🏆 Best Practices
📊 Industry Benchmarks
How does your organization compare? Use these benchmarks to identify where you stand and where to invest.
| Industry | Metric | Low | Median | Elite |
|---|---|---|---|---|
| Technology | Sunset Protocol Adoption | Ad-hoc | Standardized | Optimized |
| Financial Services | Sunset Protocol Maturity | Level 1-2 | Level 3 | Level 4-5 |
| Healthcare | Sunset Protocol Compliance | Reactive | Proactive | Predictive |
| E-Commerce | Sunset Protocol ROI | <1x | 2-3x | >5x |
❓ Frequently Asked Questions
What is the Sunset Protocol?
A structured 5-stage deprecation methodology by Richard Ewing: Identify → Quantify → Communicate → Deprecate → Remove. Provides governance for safely removing features.
How does the Sunset Protocol relate to the Kill Switch Protocol?
The Kill Switch Protocol identifies what to kill and why. The Sunset Protocol provides the how — the safe, staged process for actually removing the feature.
🧠 Test Your Knowledge: Sunset Protocol
What is the first step in implementing Sunset Protocol?
🔗 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 →