Writing
Draft a launch announcement from approved notes
A launch post needs an accurate availability statement as much as a strong opening.
OfficeCubs · · 2 min read
A launch post needs an accurate availability statement as much as a strong opening. Separate released features from planned work before drafting.
Set the editorial constraints
Give the writing teammate a clear audience, purpose and approved facts. Include a short voice sample when tone matters, and state what the draft must not promise. Save a draft file for review rather than treating a generated message as published copy. A final human edit should verify names, dates, claims and links against the source material.
Inputs for this workflow: Approved release notes, audience and availability details.
Work through the task
- Choose the main user benefit.
- Map each supporting claim to a released feature.
A brief you can adapt
Draft a 300-word announcement with a clear availability paragraph and three headline options. Keep planned features in a labeled future section or omit them.
The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.
Review the deliverable
Check the release status, download link and every capability claim against the approved notes.
Where this approach can fail
Do not imply a feature is available just because it appears on a roadmap.
For the related desktop setup, see company playbook.