Meta
Community Chats Deprecation
Role
Content Design Lead
Platform
Messenger iOS
Timeline
8 Weeks
Skills
AI Assisted Workflows
Figma
How do you retire a product that holds years of conversations, relationships, and shared history — without confusing users, creating privacy concerns, or causing them to lose what matters?
01 — OVERVIEW
Retiring a product people actually used
When Messenger Community Chats were deprecated, users needed more than a shutdown notice. They needed to understand what was changing, when it was happening, what would happen to their messages, and what they should do before their chats were gone.
I led the end-to-end communication strategy — from content framework to legal alignment to the final deletion messaging — turning a disruptive operational change into a guided, trustworthy transition.
"Simply telling people a feature was going away wasn't enough."
Community Chats held years of conversations, relationships, and shared history. The content challenge wasn't writing an announcement — it was designing a multi-stage communication system that built trust at every step.
02 — THE CHALLENGE
A multi-stage process users had to navigate
The deprecation unfolded across four distinct stages. Each required different language, different user actions, and a different emotional register.
1
Announcement
Users learn what's coming
The first message had to be clear enough to register as significant without being alarming. Users needed to understand the timeline and know what actions were available to them.
2
Read-Only Period
Access without participation
Users could still read conversations but could no longer post. This temporary state was easily confused with deletion — requiring explicit language to distinguish "paused" from "gone."
3
Deletion
Permanent and irreversible
This was the highest-stakes moment. Users needed to understand that messages would be permanently removed and could not be recovered — without creating legal exposure or undue panic.
4
Data Preservation
A path forward
Users who wanted to keep their content could export it. The messaging needed to surface this option prominently and make the action feel accessible, not buried.
03 — CONTENT STRATEGY
Three principles for trustworthy change
1
Be explicit about consequences
Vague language leaves users guessing. Every message named the actual outcome: chats become read-only, messages are permanently deleted, content cannot be recovered.
2
Separate temporary from permanent
The difference between "paused" and "deleted" is enormous — but easy to blur. I created language that made this distinction immediate and unambiguous at every touchpoint.
3
Focus on user actions
Rather than only describing the change, messaging directed users toward what they could do: download their information, learn more, continue in Messenger. Announcements became guides.
04 — MESSAGING DECISIONS
How direct should we be?
BEFORE
Community Chats are changing
Less alarming, but understates the impact and creates ambiguity. Users may not realize action is needed.
AFTER
Community Chats are going away
Clear and immediately understood. Signals significance without over-dramatizing. Users know to pay attention.
Consistent language across the full journey
ANNOUNCEMENT
"Community Chats are going away on [date]."
READ-ONLY
"This chat is now read-only. You can still view messages, but can no longer post."
PRE-DELETION
"Messages will be permanently deleted on [date] and cannot be recovered."
DATA EXPORT
"Download your information before [date] to keep a copy of your messages."
POST-DELETION
"This Community Chat has been removed. Your Messenger conversations are unaffected."
05 — CROSS-FUNCTIONAL IMPACT
Driving alignment across every stakeholder
Product Design
Partnered on notification hierarchy and how messaging shaped modal and dialog decisions
Product Management
Translated deprecation timeline logic into language that reflected actual user experience
Engineering
Ensured messaging was technically accurate at each system state and across all surfaces
Legal
Iterated on deletion and retention language to avoid unintended commitments
Privacy
Aligned on data export framing, discoverability, and access transparency
Messenger Leadership
Kept senior stakeholders aligned on tone, directness, and the user trust framework
06 — OUTCOME
A scalable framework for product sunsets
Supported full deprecation
Successfully guided the end-to-end shutdown of Community Chats across Messenger's mobile and desktop surfaces — with a coherent narrative from first announcement to final deletion.
Reduced ambiguity at scale
Consistent, explicit messaging reduced confusion around message retention and deletion — minimizing support burden and user uncertainty during the transition.
Built a reusable system
The messaging framework established patterns for future sunset experiences at Meta — a scalable foundation for how the company communicates product endings.
Drove cross-team alignment
Content became the alignment layer across Product, Design, Legal, and Privacy — shaping decisions, not just documenting them.
Important work happens when products go away
Most content design portfolios are filled with onboarding flows and feature launches. This project was different — success wasn't measured by engagement or adoption. It was measured by how clearly and respectfully we communicated change.
It reinforced that content design at its most strategic isn't about writing. It's about systems thinking, legal partnership, and knowing that every word choice carries real consequences — especially when asking people to say goodbye to something they cared about.