Figma · Strategy · Mid · 45 to 60 minutes

How should Figma serve developers?

Figma is a browser based product design and collaboration platform used by teams to create and review digital interfaces. Answer this product management case and get it graded line by line against a weighted rubric.

product strategy
user insight
prioritization
tradeoff analysis
metrics thinking

The situation

The VP of Product asks you to propose Figma's strategy for developers. Figma is already central to design teams, and developers often arrive at the end of the process to inspect mocks, pull details, and ship the product. But their experience is inconsistent. Some teams stay in Figma, some move information elsewhere, and some rely on separate handoff tools or ad hoc messages. Leadership believes there may be a bigger opportunity to make Figma useful to developers, which could deepen collaboration across product teams and fit the company's broader ambition to serve more roles, not just designers. The hard part is deciding where to play. Should Figma focus on turning designs into code, create a stronger developer workflow inside the product, or keep investment light and stay primarily designer centered? A bigger move could unlock a new persona, but it could also bloat the product, distract from designers, or chase a use case Figma cannot uniquely win. You need to recommend a strategy and how Figma should test it. You may consider build, partner, or buy if speed materially changes the recommendation.

What to produce

Write a 1 to 2 page strategy memo.

Your answer must

State the product goal and explain why serving developers matters to Figma now.
Define the target developer segment you would prioritize and the main jobs they are trying to complete around designs.
Compare at least 3 strategic paths for Figma, with the main benefit, risk, and company fit of each.
Make a clear recommendation, including what Figma should build or enable first, and what it should explicitly not do yet.
Propose success metrics and a validation plan for the first 6 months, including the biggest risks or assumptions to test.

Constraints

The core value for designers and cross functional collaboration cannot be materially weakened.
Developers should get value without needing deep design expertise or a major change to their existing engineering workflow.
The plan should produce a clear learning signal within one planning cycle.
If you recommend build, partner, or buy, keep it at strategy level and do not assume named targets or signed deals.

Format

Use sections for goal, target user, options, recommendation, risks, and metrics.

How Figma actually played it

The Dev Mode team describes how Figma set out to give developers a home inside a design tool, including an early pivot away from a code-generation-first approach and an acquisition that sped up the work. It ties the move to Figma's goal of making design accessible to product managers, developers and others. A good case on expanding a product to a second persona.

Expanding to a new persona means building their workflow, not only inviting them in.
A pivot away from the first idea (codegen) can be the right call once users show what they need.
Acquisitions can accelerate a bet when speed matters.
Tie the new surface to the company's longer-term vision to keep scope honest.

Built from Dev Mode: building a design tool that works harder for developers by Alia Fite, Figma.