Skip to main content
Question

​​​​​​​How do you organize Figma files to fit real life company's workflow

  • January 29, 2025
  • 0 replies
  • 38 views

Amit Kadosh

 

Hey everyone,

I've read a lot about best practices for organizing Figma files, but most advice feels generic and doesn’t fully address real-world challenges at scale. I’d love to hear how your team structures Figma to support your workflow in practical scenarios.

Here’s just one specific example we can use for a baseline for the discussion.

We designed a new feature that involved changes across multiple components and screens. The designs were finalized, handed off to developers, and ready for implementation. However, after all that work, the feature’s priority dropped, and it got postponed indefinitely. Now, as I start working on new feature designs, I have these "not-yet-developed" changes mixed into my files, making it difficult to keep things organized and preventing a clean handoff for new work.

How do you handle cases like this in your Figma workflow?

  • Do you move postponed features to a separate file?
  • Keep a branch or versioned copy?
  • Use a structured system to separate ongoing vs. pending work?

I’d be happy to get full description of how you organize figma to fit your company’s workflow (and then how is the above use case resolved as well as part of it)

 

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings