Product Sunset Assessment for Heads of Product: template, structure and example
For a Head of Product, the Product Sunset Assessment decides whether a product, feature, portfolio or brand should scale, reposition, transform or sunset. It weighs the reason for change, affected users, migration path, risks and closure criteria, protecting customers and the business before Portfolio Expansion Strategy.
Reviewed by Gensudo Team · Last reviewed 24 July 2026
When to use it
Create it in Scale or Sunset, when you are reducing, replacing or retiring product capability and need a defensible decision rather than one made from assumptions or loud opinions. Use it when customers depend on the capability, when contractual or reputational risk is in play, and when leadership needs to see the evidence, recommendation and ownership behind winding down, continuing or transforming.
When not to use it
If the product is healthy and the question is how to grow it, a scale or portfolio-expansion document fits better. If you are still validating a new direction rather than retiring an existing one, that is strategy or discovery work. And if there is no material customer, cost or risk impact from stopping, a lighter decision record may be all that is needed.
What you need before you start
- The strategic, commercial and operational rationale for change, with continue, pause or stop criteria
- Current usage and the customers affected, with their dependence and segment detail
- The revenue, cost and margin position, with assumptions and sensitivity
- Alternatives considered (maintain, sell, migrate) and why each was rejected
- A customer migration or retention path, and the contractual, legal, reputational and operational risks
- Security, privacy, legal, procurement and compliance input, plus named owners across the affected functions
Recommended structure, section by section
- Executive Summary — The sunset recommendation, the rationale, and the decisions required, with the confidence level, the customer and commercial impact, and the material risks made clear.
- Purpose and Scope — The product being assessed for sunset, including the audience, boundaries and exclusions, and the links to strategy or portfolio priorities.
- Rationale for Sunset — The strategic, commercial and operational reasons, including customer obligations, migration risk, capacity to execute, benefits realisation, and the criteria to continue, pause or stop.
- Current Usage and Customer Impact — The current usage, the customers affected and their dependence, broken down by segment, buyer and user, use case, willingness to pay, and retention or expansion relevance.
- Commercial and Cost Position — The revenue, cost and margin position of the product, including the assumptions and sensitivity, and the revenue, margin, ARR, churn, expansion, CAC-payback and cost-to-serve implications where relevant.
- Alternatives Considered — Alternatives to sunset (maintain, sell, migrate) and why rejected.
- Customer Migration and Retention — How affected customers are migrated or retained, including customer obligations, migration risk, capacity to execute, benefits realisation, and the criteria to continue, pause or stop.
- Risks and Obligations — The contractual, legal, reputational and operational risks, with the security, privacy, legal, procurement and compliance input, the residual risk, and any conditions to proceed.
- Wind-Down Plan — The high-level plan, timeline and dependencies, including the sequencing logic, dependencies, capacity assumptions, decision gates, cross-functional readiness, and customer-communication needs.
- Recommendation and Decisions Required — The recommendation and the approvals sought, with the recommended action and its rationale, the decision owner, the approval conditions, and the consequences of no decision.
- Evidence, Assumptions and Confidence — The usage-decline, cost, customer-impact and migration evidence behind the sunset rationale, the assumptions still unproven, the confidence level, and the validation required before committing to wind-down.
- Success Measures and Decision Thresholds — The migration, cost-saving and customer-retention targets for the wind-down, and the thresholds at which the sunset proceeds, pauses or is reversed.
- Benefits Realisation Tracking — The expected savings and risk-reduction benefits of the sunset, their owner and leading indicators, the review cadence, and the corrective actions if migration cost or customer attrition exceed plan.
- Ownership and Review — Who owns the assessment and the decision, with the accountable owners and contributors, the forums and review rhythm, the decision rights, and the escalation path.
What good looks like
A strong Product Sunset Assessment feels practical: it teaches the reader what matters, then helps them act. The reader can see the link between the evidence presented and the decision being asked for, assumptions are explained, and trade-offs are visible. A new reader can describe its purpose, understand the recommended next step, see who has approved it, and identify what would make it need updating.
Quality checklist
- Customer support, operations and communications readiness are confirmed before sign-off
- Evidence, recommendation and ownership are clear, and open questions are visible
- The migration or retention path for affected customers is set out, with obligations and migration risk addressed
- Contractual, legal, reputational and operational risks carry security, privacy, legal, procurement and compliance input and stated residual risk
- Success measures name the migration, cost-saving and retention thresholds at which the sunset proceeds, pauses or reverses
- Each recommendation states the decision required, the accountable owner, risks, dependencies and next review date
- Final sign-off sits with the Head of Product, with senior leadership endorsement where funding, risk or strategic direction is affected
Who creates it, and when
In Gensudo this document is a governed template for:
- Head of Product in the Scale or Sunset phase (as “Product Sunset Assessment”)
Where it sits in the flow
Before this document: Post-Launch Review for Product Directors · Product-Market Fit Assessment for Product Managers
This unblocks: Business Case for Heads of Product
Writing one from scratch? Read the step-by-step guide: How to Assess Whether to Sunset a Product: Steps, Examples and Checklist.
Frequently asked questions
Does a sunset assessment always mean retiring the product?
No. It weighs whether to scale, reposition, transform, migrate, decommission or retire. Alternatives such as maintain, sell or migrate are assessed on their merits, and the document records why each was accepted or rejected, so a decision to continue is as valid an outcome as winding down.
How do we protect customers through the decision?
By setting out current usage and dependence, a clear migration or retention path, and the customer obligations and migration risk involved, alongside a support and communications plan. The purpose of the document is to protect customers and the business when capability is reduced, replaced or retired.
What evidence does the recommendation rest on?
Usage-decline, cost, customer-impact and migration evidence, with unproven assumptions, confidence level and the validation still required before committing to wind-down all stated. The reader should be able to trace the recommendation back to that evidence rather than to opinion.
Can a sunset be paused or reversed once underway?
Yes. The success measures and decision thresholds define the migration, cost-saving and retention points at which the sunset proceeds, pauses or is reversed, and benefits realisation tracking flags corrective action if migration cost or customer attrition exceed plan.
Create this document in Gensudo
The governed template, role-specific guidance and AI drafting grounded in cited evidence.
Get started