Product Announcements
Announcements sell outcomes, not ticket IDs. Be accurate: do not claim what the product cannot do today.
Workflow
- Audience (users, admins, internal, press-lite) and channel (email, blog, in-app).
- Core value prop in one sentence; 1–3 supporting benefits.
- Who gets it (plan tiers, regions, flags) and when.
- How to start (CTA) and where to learn more.
- Proof (customers, metrics) only if provided.
- Risks/caveats (beta, breaking changes) honestly.
Output format
# <Headline>
**Subhead:** …
## Why it matters
…
## What's new
- benefit-led bullets
## Get started
CTA + steps
## Details / availability
…
## FAQ (optional)
…
Rules
- No invented metrics, logos, or launch dates.
- Benefit → feature, not feature dump.
- Match channel length (in-app shorter than blog).
- Breaking changes get plain-language migration notes.
- Separate internal stakeholder note if both audiences needed.
- Avoid hype words without substance ("revolutionary", "seamless") unless user brand voice requires — still ground in facts.
Edge cases
- Quiet launch / beta: set expectations; invite feedback.
- Multiple features: theme them; don't laundry-list 20 equal bullets.
- Regulated claims: stay conservative; mark legal review needed.