write-a-product-announcement

name	write-a-product-announcement
category	write
description	Write an accurate announcement for a verified product change. Use when customers, users, partners, or internal teams need to understand what changed, why it matters, what they should do, and what remains limited.

write-a-product-announcement

Announce what is actually available to the audience receiving the message.

Procedure

1. Confirm release status, audience availability, rollout scope, dependencies, limitations, pricing, support, and rollback state.
2. Identify the audience and the useful change in their workflow.
3. Lead with the outcome and eligibility, not internal project history.
4. Explain how it works using concrete examples and the smallest necessary feature detail.
5. State required action, migration, permissions, deadlines, or no-action status.
6. Include limitations, unavailable regions or plans, compatibility, and known issues that affect adoption.
7. Link to authoritative instructions, support, release notes, security details, or policy changes.
8. Remove unsupported superlatives, implied guarantees, and roadmap language presented as shipped.
9. Obtain product, support, legal, accessibility, and communications approval as applicable.
10. Test links and eligibility, publish, and monitor questions or correction needs.

Guardrails

• Distinguish implemented, released, generally available, and fully rolled out.
• Do not expose security-sensitive details or customer data.
• Never imply automatic benefit when users must configure, migrate, or qualify.
• Correct material errors through the authoritative announcement record.

Done

• Release evidence verifies availability for the stated audience
• The announcement states outcome, action, limits, support, and status accurately
• Links, rendering, accessibility, and eligibility checks pass
• Approval and any correction history are recorded