Writing product announcements
Quick start
Collect or infer:
- •What changed (feature, release, fix, deprecation)
- •Announcement type (launch, update, deprecation, incident resolution)
- •Target channels (email, blog, in-app, social, changelog)
- •Target audience (all users, segment, developers, admins)
- •Timeline (available now, rolling out, scheduled)
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- •Classify announcement type and urgency level.
- •Identify primary channel and adapt format.
- •Write headline emphasizing user benefit or impact.
- •Structure body: what changed → why it matters → what to do.
- •Add timeline, availability, and any required actions.
- •Include CTA appropriate to channel.
- •Run the rubric check. Revise until it passes.
Degrees of freedom
- •Low: Deprecation and breaking change announcements must follow exact structure.
- •Medium: Launch and update announcements can vary tone and structure for channel.
- •Allowed variation: headline style, CTA phrasing, detail depth per channel—as long as rubric passes.
References
- •Templates: TEMPLATES.md
- •Rubric: RUBRIC.md
- •Examples: EXAMPLES.md
- •Announcement types: reference/announcement-types.md
- •Channel formats: reference/channel-formats.md