Community continuity becomes fragile when history, identity, and consent must move at the same time.
A timely transition can conflict with the level of verification required to keep members’ trust intact.
Who you’d be doing this for
“Those old threads are where I learned half my practice—if they disappear or get disconnected, that’s not a small loss.”
Basma Yazdani · Staff Product Designer
She has contributed to years of peer discussions and uses saved threads to support current interface decisions.
What is at stake
A rehearsal found 0.11% of consent records mismatched, 73 threads missing context, and 1,406 identities flagged as duplicates. You get one cutover, so weigh a delay for review against holding the fixed date.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fixed cutover date vs. verified member records
- automation speed vs. human confirmation
- privacy integrity vs. historical continuity
- executive urgency vs. member trust
Why Figma
At Figma, durable collaboration often depends on members being able to trust both the continuity and stewardship of shared spaces.
Written with these in mind
Not your kind of problem? 11 more at Figma, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.