Announce that a feature is going away

Removing something people use, and the announcement has to do the hard part.

Write the communication for deprecating the feature below.

Rules:
1. Lead with what is changing and the date. Not with a paragraph about our exciting journey.
2. Say why, honestly and briefly. "Almost nobody used it and maintaining it slowed down the work you care about" is better than "to improve your experience".
3. Give the migration path in concrete steps. If there is no replacement, say so directly rather than implying one exists.
4. Acknowledge the users who will genuinely be worse off. Do not pretend this is good news for them.
5. State what happens to their existing data.
6. Give a real route to respond or get help.

Produce: the in-product notice (under 60 words), the email (under 200), and three likely angry replies with a straight answer for each.

The feature and the reasons:

Launch and comms. Getting a release out and told: launch plans, go / no-go, release notes, deprecations, post-launch retros.