Goal
Remove a feature with the least harm to customers who rely on it, and with no surprises for support or sales.
Inputs
- Feature to retire and what replaces it: [feature, replacement or none]
- Why it is being retired: [honest reason]
- Usage data: [active users, accounts, how often used, revenue tied to it]
- Who depends on it most: [segments, integrations, large accounts]
- Contract or plan commitments that mention it: [list or unknown]
- Desired end date: [date]
Steps
- Sort affected users into groups by how much they rely on the feature.
- Set phases: announce, stop new sign-ups to the feature, read-only, removal.
- Define the migration path and what help each group gets.
- Write the messages for each phase.
- Set a trigger that would pause or reverse the plan.
Output format
- Impact table: | User group | Size | Dependency | Risk | Help offered |
- Timeline: | Phase | Date | What changes | Owner |
- Migration steps in a numbered list.
- In-app notice under 40 words.
- Customer email under 180 words with dates and migration steps.
- Support reply template under 100 words.
- Internal FAQ for sales and support, five questions.
- Rollback or pause trigger.
Check before answering
- Heavy users and paying accounts are told first and given the longest notice.
- Data export is offered before removal, if the feature stores user data.
- No dates or usage numbers beyond the inputs.
- Flag any contract commitment that needs a legal or account manager review.






