Plan a feature sunset and customer migration
A deprecation plan with usage analysis, timeline, migration path, and communications for every affected group.
The prompt
Help me plan the retirement of a product feature.
Feature to sunset: [NAME AND WHAT IT DOES]
Why we are removing it: [COST, LOW USAGE, REPLACED, SECURITY, STRATEGY]
Usage data: [ACTIVE USERS OR ACCOUNTS, SEGMENTS, REVENUE TIED TO THEM]
Replacement or alternative: [NEW FEATURE, WORKAROUND, PARTNER, OR NONE]
Contract or API commitments: [SLAS, PUBLIC API, ENTERPRISE CONTRACTS - or "unknown"]
Target end date: [DATE]
Build a plan with:
1. Impact analysis: who is affected, heavy versus light users, accounts at risk, revenue exposure.
2. Timeline with stages: announce, stop new adoption, read-only or limited mode, shutdown, data deletion. Recommend notice periods that fit the user type (longer for API and enterprise users).
3. Migration path: steps for users, data export, tools or help we provide.
4. Communications: message for each audience (heavy users, all users, internal teams, API developers), channel, and timing. Draft the first announcement.
5. Internal readiness: support macros, sales talking points, documentation updates, removal of in-product entry points.
6. Risks and rollback triggers, e.g. a key account escalation.
Ask legal to check contracts and data-retention obligations before announcing. Mark unknowns [CONFIRM].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- NAME AND WHAT IT DOES
- COST, LOW USAGE, REPLACED, SECURITY, STRATEGY
- ACTIVE USERS OR ACCOUNTS, SEGMENTS, REVENUE TIED TO THEM
- NEW FEATURE, WORKAROUND, PARTNER, OR NONE
- SLAS, PUBLIC API, ENTERPRISE CONTRACTS - or "unknown"
- DATE
- CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Check my iOS app for App Store rejection risksPre-submission compliance check against Apple's App Store Review Guidelines.
- Audit a website or app for accessibility (WCAG)Checks against WCAG and gives prioritized, specific fixes.
- Find the edge cases and failure states in my feature specA structured list of edge cases, empty and error states, and open questions to settle before engineering starts.
- Audit a codebase for bugs, risks, and tech debtA systematic review of a repository with prioritized findings and a remediation plan.