Feature Deprecation Strategy
Create a comprehensive strategy for deprecating [legacy feature] from your product. Include: 1) Usage analysis to understand impact scope, 2) User segmentation based on feature dependency, 3) Communication timeline and messaging by segment, 4) Alternative solution or migration path, 5) Technical implementation plan with phases, 6) Internal training for customer-facing teams, 7) Success metrics for a smooth transition, 8) Feedback collection mechanism during the process, 9) Contingency plan for users with critical dependencies, and 10) Post-deprecation support strategy.
How to Use This Prompt
- Copy the prompt using the button above
- Replace placeholders in [brackets] with your specific details
- Paste into your AI assistant (ChatGPT, Claude, Gemini, etc.)
- Iterate as needed - ask follow-up questions to refine the output
Why This Prompt Works
This prompt produces thorough deprecation plans by requiring user impact analysis before any action steps, ensuring you understand who is affected and how. By demanding both migration paths and contingency plans for users with critical dependencies, the AI generates strategies that minimize churn risk. The inclusion of internal team training and feedback collection creates a plan that addresses both external and internal stakeholders throughout the deprecation lifecycle.
When to Use This Prompt
- When removing a legacy feature that overlaps with a newer solution and you need to migrate users without friction
- When technical debt from an old feature is slowing development velocity and you need a structured retirement plan
- When sunsetting a feature due to low usage but want to ensure the small group of power users is properly supported
Tips for Better Results
- Include actual usage data such as DAU/MAU counts and the percentage of users relying on the feature for accurate impact scoping
- Describe the replacement feature or alternative workflow so the AI can build a specific migration guide
- Mention any contractual obligations or enterprise customer commitments tied to the feature for risk-appropriate planning