B0132: Product Portfolio Sunset Framework
A decision-ready template derived from the framework.
Name variants
- English
- B0132: Product Portfolio Sunset Framework
- Katakana
- ポートフォリオ
- Kanji
- 製品 / 終了枠組
Quality / Updated / Source / COI
- Quality
- Reviewed
- Updated
- Source
- Citations & Trust
- COI
- none
Context
Context: sunsetting legacy products while protecting customers creates recurring decisions where teams interpret contribution margin, support cost per customer, churn impact and feature usage, migration effort, contract obligations differently. Without a shared frame, the simplification versus customer disruption choice becomes implicit and accountability weakens. A decision log preserves learning and improves the next cycle.
Options
- Option A: Maintain the current approach to minimize disruption, accepting slower gains and limited learning.
- Option B: Pilot changes in phases, validate results against agreed metrics, and scale after thresholds are met.
- Option C: Redesign the approach end to end for larger gains, accepting higher execution risk and effort.
Decision
Decision: Choose Option B. Run a staged rollout that validates contribution margin, support cost per customer, churn impact against thresholds and pauses if feature usage, migration effort, contract obligations change materially. Assign owners, document constraints, and set a review checkpoint to avoid drift.
Rationale
Rationale: Option B balances simplification versus customer disruption while preserving flexibility if conditions shift. It allows the team to test feature usage, migration effort, contract obligations and protect against the main risk of misjudging contribution margin, support cost per customer, churn impact. Phasing improves buy in because progress is visible and accountability is explicit.
Risks
- Weak data quality can obscure changes in contribution margin, support cost per customer, churn impact and delay corrective action.
- Execution drag may prolong exposure to the downside of simplification versus customer disruption and reduce expected benefits.
Next
Next: Confirm ownership, finalize baselines for contribution margin, support cost per customer, churn impact, and document feature usage, migration effort, contract obligations in a shared log. Schedule the first review, define stop conditions, and communicate the plan to affected teams.