From Pixels to Pull Requests: Inside Figma's New Way of Working
Figma recently introduced nested folders, a long-awaited feature for organizing files. But behind this seemingly simple update lies a story of a team that completely reinvented its workflow to make it happen. Facing shifting priorities and new AI capabilities, the team adopted a radical approach: leading with code, blurring roles, and turning handoffs into conversations.
Leading with Code: Proposals Over PRDs
Software Engineer Ethan Adams realized early on that the traditional product development process would be too slow. Instead of debating requirements in long Slack threads, the team started spinning up pull requests (PRs) to test ideas. As Ethan puts it, "A working demo in your actual codebase beats a PRD every time." This approach allowed them to quickly sketch ideas and get feedback in a live testing ground, accelerating their velocity and building confidence in their choices.
Blurring Roles: Designers in Code, Engineers in Design
Product Designer Cai Charniga admits their PR count was low, but the team's dynamic shifted dramatically. Engineers like Jenny Yu brought strong design instincts, mocking up flows and tweaking UI. Cai, in turn, pushed code and gained a deeper empathy for engineering. This cross-pollination meant work never stalled waiting for the "right" person. As Cai notes, "When you have a strong design system and trust, an engineer can go deep on a design feature."
Trading Control for Conviction: The PM's New Role
Product Manager Sachi Shah had to let go of the idea that all product thinking came from the PM. Instead, she focused on matching people to problems and letting them run. This freed her to tackle strategic questions, like whether folders still mattered in an AI-first world. She also dove into customer discovery, running an early-access program and cold-pitching at Config. "Trading control for conviction," she says, allowed her to focus on the work she was best positioned to do.
Building Trust Through Shared Rituals
This new way of working only succeeded because of deep trust and shared rituals. The team held weekly bug bashes, cross-functional syncs, and celebrated milestones together. They became teachers and learners, sharing the parts of their craft they once guarded. The result? A successful launch of nested folders, delivered without compromising quality.
Key Takeaways for Your Team
- Lead with code: Use PRs as proposals to test ideas quickly.
- Blur roles: Encourage engineers to design and designers to code.
- Turn handoffs into conversations: Foster continuous collaboration.
- Trade control for conviction: Let PMs focus on strategy and trust the team.
- Invest in relationships: Shared rituals build the trust needed for flexibility.
Nested folders are rolling out to all users over the next few weeks. For more details, check Figma's help center.
Hero illustration by Sebastian Cestaro




Comments
Join Our Community
Sign up to share your thoughts, engage with others, and become part of our growing community.
No comments yet
Be the first to share your thoughts and start the conversation!