X — before and after
Shipped: [Feature name]. Before: [how the task worked, with the annoying part]. Now: [how it works today, in one line]. Available to [all users / plan name] from today. Find it under [menu path]. [link to docs or changelog]
LinkedIn — customer request angle
You asked for it [number] times, so here it is: [Feature name]. The problem: [describe what users had to do before, and what it cost them]. What changed: [Feature] lets you [action] directly from [place in the product]. No [workaround], no [second tool]. A few details worth knowing: - [Detail 1, e.g. works with existing data] - [Detail 2, e.g. available on which plans] - [Detail 3, e.g. how to turn it off] Thanks to [customer or community member] for the first request and the patient testing. How to try it: [link]
Mastodon — plain changelog voice
[Product] update: [Feature name] is out. What it does: [one sentence]. Why we built it: [one sentence about the user problem]. Where to find it: [menu path or command]. Full notes: [link] #[ProductTag] #[TopicTag]
Bluesky — one-screen demo
New in [Product]: [Feature name]. [Action] now takes [new time] instead of [old time]. Short demo attached. Docs: [link]
Tips
- Name the feature the same way the interface names it, so readers can find it without guessing.
- Show the old workflow in one line before the new one. The contrast carries the value better than adjectives do.
- Say who gets the feature: every user, a specific plan, or a staged rollout. Unclear availability produces a wave of support replies.
- If a user requested the feature publicly, credit them by handle with their permission. It rewards feedback and invites more of it.
Frequently asked questions
What is the difference between a feature announcement and a launch post?
A launch post introduces a new product to people who may not know you. A feature announcement assumes the reader already uses the product and focuses on one change, where to find it, and who has access.
Should I post every feature I ship?
Post features that change how someone does a task they care about. Batch smaller fixes into a weekly or monthly changelog post instead of posting each one.