Product planning
Draft a factual notice for a retiring feature
State the date the feature ends, what will stop working and what users can do before then. Give the steps for keeping their data, name any approved alternatives and say where to ask questions. Use only what the approved plan confirms.
A text to start with
We are retiring [feature name]. The approved plan says: end date [date], affected function [what stops], steps to preserve data [steps], alternatives [approved options], support route [where to ask]. Write a notice for [audience] in a plain, factual tone. Use only these details. If something users will likely ask is missing from the plan, list it as a question for me instead of answering it.
Example request. Change the details to fit your situation.Retirement notice checklist
Feature being retired: [ ] End date as approved: [ ] Time zone, if relevant: [ ] Function that stops working: [ ] What remains available, if anything: [ ] Steps to preserve data: [ ] Step tested by and date: [ ] Approved alternatives: [ ] Differences from the retired feature: [ ] Support route and contact: [ ] Claim in draft: [ ] Matches plan: [yes / no] Question for the owner: [ ] Approved by and date: [ ]
Dates and migration claims
Check every date against the approved plan, including the time zone if one matters, and make sure the same date appears wherever it is repeated. Try each preservation step in the current product to confirm it works. Remove statements such as "your data will transfer automatically" unless the plan says so. Watch for alternatives described as equivalent when the plan only calls them available. Say what happens to data after the end date only if that is decided. If the plan is silent on a point, leave it out and raise it with the owner.
Ask another agent to check the result
Compare every date, deadline and migration claim in this notice with the approved plan text. List each mismatch, each claim the plan does not support and each user question the draft leaves unanswered. Do not fill gaps with assumptions.
Resolve open questions before sending
Send the list of unanswered questions to the plan's owner and wait for decisions before publishing. Try each preservation step yourself and record the date. Prepare the support route so people who reply can reach someone. Keep the final notice, the approved plan and your check results together so later questions can be traced to a source.