Figuring it Out: A Figma Migration Story
summary
Design org of about 60 people migrates to Figma over six to seven months with a core team of three running licensing, a temporary workspace, and a teams/projects structure; component libraries and a living design system take three to four months to rebuild; trainings include vendor demos, curated sessions, and internal workshops plus a Figma Ambassador program, twice‑monthly micro‑trainings and playdates; legal review slows rollout but migration completes in July 2021 and development teams adopt Figma using free viewer accounts.
AI-written summary · about
chapters (22)
- 0:00Introduction and speaker background
- 1:09Why this talk isn’t about Figma
- 3:18About SAS Design team
- 6:57SAS work culture and pandemic impact
- 8:25Why Figma was chosen
- 10:56Researching Figma for SAS
- 12:02Planning the Figma migration
- 14:15Setting up Figma structure
- 17:30Training preparation and sessions
- 20:28Supporting Figma long-term
- 23:18Hurdles during migration
- 25:29Wins and gains from migration
- 26:58Q&A session begins
- 30:50Training pain points and tips
- 32:36Developer integration with Figma
- 35:05Sharing designs with stakeholders
- 36:32Cloud storage and legal concerns
- 37:56Figma’s responsiveness to issues
- 40:04Canvas size and Chrome limitations
- 41:09Current Figma adoption status
- 42:38Would migration have happened without pandemic?
- 44:45Closing remarks and thanks
related talks
23mCollaborative and real-time design systems in Figma
26mA Beautiful Mess: How We Build Products at Figma
21mHow Engineers Led a Redesign of Our Design Tool
21mIt's better when we design together
18mMaking the Things That Help Others Do Their Thing
17mESPN's migration playbook: moving to Figma w/ One North
20mWhat if it all started in Figma?
25mThe story behind Figma Slides with Mihika Kapoor