Code, craft, and the making of nested folders

Figma has recently unveiled nested folders, a feature that has been highly anticipated by users seeking better organization as their teams grow and tackle increasingly complex projects. While the concept of nested folders may seem like a simple enhancement, the implementation required a comprehensive overhaul of Figma’s content and permissions model. This involved rethinking various aspects of the platform, including the file browser, admin controls, sharing capabilities, and the core infrastructure that supports these functions.

The development of nested folders began a year ago, following a conventional product development methodology. Initially, the product team defined requirements, the design team created user experiences, and engineering commenced building once the foundational ideas were solidified. However, midway through the project, the context shifted significantly. The team was also pursuing new AI-native capabilities that began to stretch resources thin. Simultaneously, tools like Figma Make, which includes a properties panel and annotations, began to bridge the gap between design and code, enabling users to adjust elements directly and use in-context prompts.

As the project progressed, the Figma MCP server expanded its reach across the platform, facilitating updates and design shipments in a more integrated manner. This evolution in functionality underscored the need for a new approach to product development, particularly in how teams collaborated and communicated.

A New Approach to Development

Recognizing that the traditional product development process was too slow, the team adopted a more agile methodology. Instead of engaging in lengthy discussions about product requirements in Slack threads or meetings, they led with code as a proposal. This shift was particularly beneficial in an era dominated by agents, where the cost of writing code had decreased significantly. By spinning up pull requests (PRs) to validate ideas, the team could quickly demonstrate concepts in a live testing environment. This approach allowed for rapid iterations, where imperfections in copy or functionality could be addressed later, ultimately enhancing the team's velocity and confidence in the proposals that were selected.

The collaboration dynamic also evolved. Previously, the product manager would dictate requirements, and the engineer would execute them. In this new model, the engineer proposed ideas, merged prototypes into staging, solicited feedback, and refined the product collaboratively. This verification loop fostered a sense of shared ownership and responsibility.

Interestingly, the engineer’s PR count remained low, indicating that team members began to step into roles traditionally held by others. Engineers contributed to design work, while designers engaged with code, fostering a more integrated approach to product development. This cross-functional collaboration was particularly evident in the design of folder sharing flows, where engineers and designers worked together to create intuitive user experiences.

The Importance of Customer Feedback

As the project unfolded, the focus shifted towards understanding customer needs and behaviors. Running an early-access program allowed the team to gather valuable insights into how nested folders functioned within real-world organizations. This direct interaction with users helped identify bugs, refine the user experience, and mitigate risks associated with migrating customers to a new content model.

Customer feedback provided clarity that traditional specifications could not offer. Engaging with users allowed the team to prioritize their efforts effectively, ensuring that the final product aligned with customer expectations. This emphasis on user experience was crucial in navigating the complexities of implementing nested folders.

The collaborative culture fostered throughout the project was vital for its success. Trust among team members facilitated the blurring of roles, allowing individuals to experiment and step outside their traditional boundaries. Although this shift sometimes led to awkward moments, the investment in relationships enabled the team to navigate discomfort and find a new normal. Shared rituals, such as weekly bug bashes and cross-functional syncs, helped maintain focus on their collective goal of delivering a high-quality product that met customer needs.

Why it matters

The introduction of nested folders represents more than just a new feature; it signifies a shift in how product development can be approached in the tech industry. By embracing a more collaborative and agile methodology, Figma has demonstrated the potential for faster iterations and more effective communication among cross-functional teams. This approach not only enhances productivity but also fosters a culture of shared ownership and accountability.

For creators and technologists, the implications are significant. As tools like Figma continue to evolve, the ability to adapt quickly to user needs and incorporate feedback will be crucial in maintaining relevance in a rapidly changing landscape. The success of nested folders could serve as a model for other teams looking to innovate and improve their workflows, emphasizing the importance of collaboration and user-centric design in the development process.

In conclusion, Figma's nested folders are set to roll out to all users in the coming weeks. This long-requested feature not only enhances file organization but also reflects a deeper understanding of the complexities involved in modern design and product development. As teams continue to navigate the challenges of scaling their work, the lessons learned from this project could provide valuable insights into fostering collaboration and innovation in the tech space.