Organize content with sections to help teammates navigate through busy Figma files. A section is a default top-level element on the canvas and its own layer type is used primarily for organizing files and grouping designs. Additionally, sections allow you to organize prototypes and preserve their state, as Miggi shows in one video and Anthony in another. See also Sho Kuwamoto’s notes on the controversy surrounding launching this feature.

The step-by-step guide on cleaning up a Figma file that was inherited from another designer. I like Edward’s focus on communicating with the team and automating repetitive work in the process.

Clara Ujiie shows how to archive your work using pages and version history.

The design team at Spotify discusses balancing conflicting goals of creating a playful space for experimentation and fostering interdisciplinary team collaboration in the Figma files. The key to achieving both is balancing the exploratory nature of design with a logical organization in your shared work. ​“A chaotic mess of brilliant designs is incomprehensible without a helpful file structure but too much structure early on might stifle your team’s inspiration.”

Post-it notes are great for gathering and organizing feedback. (I often use comments as to-do’s, but also copy a post-it note from FigJam to my Figma files for higher visibility and questions.)

Patrick Morgan created a useful library of Figma helpers and wrote about designing systems and tools for yourself to facilitate your own unique design workflow.

Matthew Jedraszczyk shares a few solid recommendations on organizing your files and projects in Figma.

Interesting way to organize a large Figma workspace using a department store floor map as a mental model.

Joey Banks talks about his approach to organizing and naming in Figma.

Luis explores a few approaches to layer naming based on a level of fidelity, team conventions, and who is responsible for this work.

“Organizing your Figma files can be a daunting task, especially as your design system team and wider org grows. We’ve gathered some of the tips that we’ve picked up along the way, including ways you can make Figma work better with zeroheight.”

“One significant aspect that design systems solve is serving as a single source of truth across products so that we can save ourselves from this mess at handoff. But what is this single source of truth and how do the teams working on it build and manage it?”

Joey Banks with a tip on indicating component or layer status through naming.

Josh Cusick shares how the Design Systems team at Microsoft built, maintained, and set up for people to contribute the Figma UI kit for Teams Component Libraries (TCL). He covers structuring pages, naming things, aligning with code, design tokens, and version control.

Ridd shares his approach to organizing files in Figma.

“Learn how to use branching for exploring and testing alternate designs, and for sharing work with development partners.”

Luis Camino, a UI/UX designer at BMW and MINI, shares a few best practices for Library editors.

The team at Onfido Tech moved to Figma from Sketch and Abstract, and they organized projects and files to work around the lack of branches back then. Their structure may be a good fit for a larger organization.

Anton Lovchikov shares his approach to structuring pages in the Figma file.

Luis talks to Santosh Komaragiri from Dataguard, who showed how they manage their Figma workspace. Their team has built some incredibly detailed product, marketing, and brand design systems which shows how you can take Figma to new levels of usage.