B0261: Portfolio Exit Sequencing Framework

Context

Context: sequencing product exits often exposes disagreements about product ROI, customer impact, and run-off cost and the reliability of contract obligations, engineering capacity, and market signals. Without a shared frame, the focus vs revenue stability remains implicit and accountability erodes across reviews. A structured record is needed to keep decisions consistent as market conditions change.

Options

• Option A: Keep the current approach to minimize disruption while accepting limited improvement.
• Option B: Pilot a phased change, validate against agreed metrics, and scale once thresholds are met.
• Option C: Redesign the approach end to end to pursue larger gains with higher execution risk.

Decision

Decision: Choose Option B. Validate product ROI, customer impact, and run-off cost early, confirm contract obligations, engineering capacity, and market signals assumptions, and pause if the focus vs revenue stability no longer holds. Document owners, constraints, and review dates.

Rationale

Rationale: Option B balances focus vs revenue stability while preserving flexibility. It tests whether product ROI, customer impact, and run-off cost respond as expected to changes in contract obligations, engineering capacity, and market signals before committing to a full rollout. This reduces the risk of locking in a costly path based on weak evidence and improves governance confidence.

Risks

• Weak data quality can hide shifts in product ROI, customer impact, and run-off cost and delay corrective action.
• Slow execution can magnify the downside of focus vs revenue stability and reduce credibility in reviews.

Next

Next: Assign owners for product ROI, customer impact, and run-off cost and contract obligations, engineering capacity, and market signals, finalize baseline values, and publish the trigger thresholds. Schedule the first review checkpoint and define stop conditions so the decision can be revised quickly.