Defining a Figma project structure for all product teams
How I structure Figma so exploration stays separate from production, naming reflects decisions not departments, and libraries survive real adoption.
Year 2024Read 1 min
The failure mode
Beautiful libraries that nobody adopts usually fail on information architecture — not on components.
Principles
Separate exploration from production. Name pages for decisions, not departments. Keep tokens and components in sync with a single owner and a visible changelog.
Implementation
Start with three folders: Foundations, Patterns, Product streams. Add depth only when teams prove they will maintain it.
Next field note