Product Sunset & Pivot Decisions

Sunset Decision Framework Core Method

Use when: evaluating whether a product or feature should be retired.

Evaluate along five dimensions:

• Usage — how many users actively use this? Is usage growing, stable, or declining?
• Revenue impact — does this feature drive revenue directly or indirectly? Would removing it cause churn?
• Maintenance cost — how much engineering time does this consume in bug fixes, compatibility updates, and support?
• Strategic alignment — does this support the current product strategy, or was it built for a strategy the company has moved past?
• Opportunity cost — what could the team build if they weren't maintaining this?

A feature with declining usage, no revenue impact, high maintenance cost, poor strategic alignment, and high opportunity cost is a clear sunset candidate. Mixed signals require judgment — and usually a conversation with affected users before deciding.

Feature Usage Audit Technique

Use when: identifying sunset candidates across your product.

Pull usage data for every feature: MAU (monthly active users), frequency (daily, weekly, monthly), and trend (growing, stable, declining). Sort by usage. The bottom 10% are sunset candidates. For each candidate, verify: Is the low usage because the feature is bad, or because it serves a niche but critical use case? A feature used by 0.5% of users that's essential for enterprise renewal is different from one used by 0.5% who would barely notice if it disappeared. Interview 5 users of each candidate feature before deciding.

Sunk Cost Audit Tool

Use when: the team is resisting a sunset because of past investment.

In a team discussion, separate past investment from future value. List everything invested (engineering months, marketing spend, customer commitments). Then cover it up — literally, put a blank sheet over it. Now evaluate: if we were starting from zero today, with no investment in this feature, would we build it? If the answer is no, the past investment is irrelevant to the future decision. This simple exercise doesn't eliminate sunk cost bias, but it makes it visible and discussable.

Sunset Communication Plan Core Method

Use when: you've decided to sunset and need to communicate without destroying trust.

Timeline:

• 6+ months before — announce the sunset, explain why, and present the migration path.
• 3 months before — remind users, offer migration support, highlight alternatives.
• 1 month before — final warning with countdown, export tools available.
• Sunset day — feature disabled, clear messaging pointing to alternatives.
• 30 days after — data deletion (with notice that data has been deleted).

Communication principles: Be honest about why (don't say "to serve you better" when you mean "to cut costs"). Acknowledge the impact on affected users. Provide a migration path (ideally to another feature in your product, or export tools for migration elsewhere). Offer support during the transition. Never sunset without warning — surprise shutdowns destroy trust far more than the sunset itself.

Migration Planning Template Technique

Use when: users need to transition from the sunset feature to an alternative.

For each user segment affected: What they currently do with the sunset feature.

• Where they should go — the recommended alternative (in your product or elsewhere).
• How to migrate — step-by-step migration guide, data export tools, import tools on the receiving end.
• What they lose — honest acknowledgment of any functionality gaps in the alternative.
• Support available — migration office hours, dedicated support channel, concierge migration for high-value accounts.

Pivot Criteria Checklist Framework

Use when: results are disappointing and you're deciding whether to persist or change direction.

A pivot is warranted when:

• The problem is validated but the solution isn't working — customers confirm the problem exists but your approach doesn't solve it.
• A different customer segment shows unexpected traction — you built for SMBs but enterprises are the ones buying.
• A specific feature gets disproportionate engagement — your product has 10 features but users only care about one. That one feature might be a product.
• The market has shifted — competitive landscape, technology, or regulation changed the game.
• Unit economics don't work — you can acquire customers but can't serve them profitably at current margins.

Types of pivots: Customer segment pivot (same product, different audience). Problem pivot (same audience, different problem). Solution pivot (same problem, different approach). Channel pivot (same product, different distribution). Revenue model pivot (same product, different monetization). Naming the pivot type clarifies what you're changing and what you're keeping.