Product planning
Draft a feature announcement from confirmed changes
Begin with the changes that are confirmed and live, then state who can use them and how to start. Add the known limits in the same message. Leave out plans, hopes and anything that depends on unfinished work.
A text to start with
We are announcing [feature name] to [audience]. Confirmed behavior: [what users can do now]. Access: [who has it and how it is granted]. To start: [first step]. Known limits: [list]. Draft an announcement of about [length]. Use only the facts above. Do not mention upcoming work, and do not describe benefits I have not listed. Mark any sentence that needs a fact I have not provided.
Example request. Change the details to fit your situation.Announcement facts sheet
Feature name: [ ] Live since: [ ] Behavior users can use now: [ ] Who has access: [ ] How access is granted: [ ] First step to start: [ ] Starting step checked by and date: [ ] Known limits: [ ] Where each limit appears in the draft: [ ] Support route: [ ] Sentence from draft: [ ] Source of confirmation: [ ] Status: [confirmed / unconfirmed / removed] Approved by and date: [ ]
Roadmap leaks and implied access
Announcements drift toward the future. Look for phrases like "soon," "coming" or "first step toward," and remove them unless the date and scope are approved. "Available to everyone" is a claim about every plan, region and role, so confirm it or cut it. Outcome claims such as saving time or reducing errors need evidence you can point to. Compare the starting step in the draft with an attempt in the live product, since menu names change between builds. Place each limit next to the behavior it affects, not in a footnote.
Ask another agent to check the result
Scan this announcement for roadmap items, implied eligibility and outcome claims without evidence. Quote each sentence that depends on something missing from the facts sheet and suggest a supported replacement or deletion.
Confirm with the owner before sending
Send the draft to the feature owner and ask them to mark each sentence confirmed or unconfirmed. Replace unconfirmed lines with a supported fact or delete them. Try the starting step yourself in the live product and note the date. Decide where support questions should go and add that route to the text before publishing.