Retire a feature or internal tool gracefully: the usage audit, the migration path for holdouts, the comms timeline, and the actual switch-off.
Plan the sunset of: {{feature_or_tool}} (what it does, who still uses it: {{usage}}, why it's going, what replaces it). Build: the usage audit (who, how much, for what — the holdout segments and what THEY need from the replacement), the migration path per segment (self-serve for most; white-glove for the heavy/valuable few), the comms timeline (announce with the why and the replacement → reminder at T-30 → final at T-7 → off — with dates), the objection handling (the customer for whom the replacement is worse: the honest conversation, and the exception decision made once, not per-complaint), the data question (exports, retention), and the actual switch-off checklist including the redirect/tombstone. Rule: the replacement must work BEFORE the first announcement.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekTurn a feature idea into a tight one-page product spec.
Break a feature into user stories with acceptance criteria.
Generate a structured SWOT for a decision or business.
Get a tough, constructive critique of a plan or doc.
Explore three pricing models for your product — tiers, psychology, and risks — with the recommendati...
Design in-product feedback prompts that get signal, not noise: the right question at the right momen...