Figma · Strategy · Senior · 45 to 60 minutes
How should Figma grow beyond designers?
Figma is a browser based collaborative product design platform used to create, discuss, and ship digital products. Answer this product management case and get it graded line by line against a weighted rubric.
- Strategic prioritization
- Platform thinking
- Customer insight
- Sequencing
- Metric design
The situation
You are a senior PM advising Figma leadership shortly after the company has proven strong demand for its core multiplayer design tool among designers. The original browser bet is starting to look right as web technology improves, but the company still has to keep performance high, fend off strong design incumbents, and respond to skeptics who think serious design work should stay on desktop tools. Kris Rasmussen asks for a strategy recommendation on the next company level product bet. Leadership sees an opening: design work is larger than drawing screens, it also includes brainstorming, feedback, prototyping, and handoff to engineering. If Figma can serve more of that workflow, it may become central to how product teams work, not just where designers make files. But moving beyond the core too early could dilute focus, hurt the product quality that won designers, and create weak offerings against specialist tools. Assume the company can fully back only one major adjacent bet over the next year. What should Figma prioritize, for whom, and in what sequence?
What to produce
Write a 2 to 3 page strategy memo for the CTO and product leadership team.
Your answer must
- State the decision you are making, the primary goal, and the customer problem behind it.
- Compare at least three strategic paths, including doubling down on the core design tool and at least two adjacent expansion options aimed at non designer collaborators.
- Recommend one path and a sequencing plan for the next 18 to 24 months, with explicit tradeoffs and why now logic.
- Explain how the recommendation uses Figma's existing strengths, including browser based collaboration, multiplayer workflows, and customer proximity.
- Define success metrics, leading indicators, and key risks, including second order effects on core designer adoption, collaboration, and product quality.
- Describe a validation plan that uses direct customer learning, dogfooding, and lightweight experiments before full commitment.
Constraints
- Do not assume a desktop pivot or a full rewrite of the core product architecture.
- Your plan must protect the core design experience for existing designers, especially performance and quality.
- Do not rely on acquiring another company to execute the strategy.
- You can fund only one major adjacent product bet in the near term, so choices and sequencing matter.
Format
Use five sections: decision and objective, options, recommendation, sequencing, metrics and risks.
How Figma actually played it
Describes Figma breaking into a crowded market, leveraging inflection points, staying close to customers and extending beyond designers.
- Break away in crowded markets with a different base technology
- Stay close to customers
- Expand users beyond the core persona
Built from How Figma Grows: Design Beyond Designers by Jaryd Hermann (How They Grow).
Related case studies
- Figma's AI boundary: make, monetize, or own the recordFigma · Strategy · Senior
- Should Figma bet on prompt to app creation?Figma · AI product · Senior
- How should Figma rally support for a new bet?Figma · Execution · Mid
- How should Figma sequence growth motions?Figma · Go-to-market · Senior
- Plan Figma's upcoming price increaseFigma · Go-to-market · Mid
- How should Figma improve comments?Figma · Metrics · Mid