B0132: Product Portfolio Sunset Framework

Quality / Updated / COI

Quality

Reviewed

Updated

02/14/2026

Source

Citations & Trust

COI

none

TL;DR

Product Portfolio Sunset Framework is used for sunsetting legacy products while protecting customers. It organizes contribution margin, support cost per customer, churn impact and feature usage, migration effort, contract obligations, clarifies the trade off between simplification versus customer disruption, and preserves assumptions for future cycles.

Applicability

Use it in situations where sunsetting legacy products while protecting customers depends on consistent contribution margin, support cost per customer, churn impact definitions and transparent feature usage, migration effort, contract obligations. It is strongest when multiple options compete for scarce resources.

Steps

1. Define scope and horizon, then lock success metrics (contribution margin, support cost per customer, churn impact) and data definitions so teams compare the same baseline.
2. Gather inputs (feature usage, migration effort, contract obligations) and normalize timing, units, and ownership to remove inconsistencies before analysis.
3. Model scenarios to test how the balance of simplification versus customer disruption shifts; record thresholds that would change the recommendation.
4. Select a preferred option, document decision criteria, and list approvals or constraints before execution.
5. Set monitoring cadence, owners, and revisit triggers so the decision log stays current as evidence changes.

Template

Template: Background and objective; Scope and time horizon; Success metrics (contribution margin, support cost per customer, churn impact); Key assumptions (feature usage, migration effort, contract obligations); Options A/B/C; Scenario ranges; Trade off summary (simplification versus customer disruption); Risks and mitigations; Decision criteria; Recommendation; Owner and timeline; Review triggers. Add data sources, confidence notes, and variables that would change the conclusion.

Pitfalls

• Using inconsistent definitions for contribution margin, support cost per customer, churn impact makes comparisons misleading and erodes trust.
• Ignoring how simplification versus customer disruption priorities shift over time leads to reversals later.
• Leaving feature usage, migration effort, contract obligations unverified creates audit challenges and weakens accountability.

Case

Case: A platform retired an old edition and needed a structured migration plan. The team mapped contribution margin, support cost per customer, churn impact and aligned feature usage, migration effort, contract obligations before ranking options. They documented how simplification versus customer disruption affected the final call and set review checkpoints to prevent drift.

Citations & Trust

• Principles of Management (OpenStax)