How Figma builds product

This case study examines how Figma structures its product development process, focusing on planning cycles, goal-setting frameworks, and team organization. The key challenge addressed is how to effectively scale product development processes while maintaining alignment and innovation as the company grows.

Figma employs a multi-tiered planning approach with annual company priorities set by leadership, followed by bi-annual product team roadmap reviews and quarterly adjustments. They've evolved from traditional OKRs to "headlines"—philosophical claims teams want to make about their product—and later back to OKRs rebranded as "commitments" to increase ownership. Their review process separates generative design crits (for feedback, not decisions) from product reviews (for decision-making), utilizing FigJam's collaborative features including alignment widgets to prevent the loudest voices from dominating outcomes.

The company organizes its 22 product managers around products (Figma Design and FigJam) plus horizontal platform teams for cross-product initiatives like Enterprise and Infrastructure. Both product and design report under the same organization, fostering closer collaboration.

Key takeaways for product managers include: experiment with goal-setting frameworks to find what drives real accountability rather than just tracking tasks; separate feedback sessions from decision-making meetings; use collaborative tools and voting mechanisms to democratize input during reviews; and expect to continuously evolve team structure as the organization scales, treating it as an ongoing optimization rather than a one-time decision.