Figma · Execution · Mid · 45 to 60 minutes

How should FigJam move from beta to GA?

Figma is a browser based collaborative design platform used by teams to create and work together in real time. Answer this product management case and get it graded line by line against a weighted rubric.

beta strategy
execution planning
cross functional leadership
prioritization
product judgment

The situation

You are the PM for FigJam, Figma's collaborative online whiteboard, and your manager asks for a recommendation on how to run the product from public beta toward general availability. The beta has created useful early interest and feedback, but the team is hearing many competing requests about templates, collaboration workflows, onboarding, and polish. Design and engineering both have strong views on what must be done before GA, and leadership also wants to understand whether launch should include plan and pricing decisions rather than only product changes. Internally, many Figma employees already use FigJam for their own work, which gives the team fast feedback, but you need to decide how much weight to give that signal versus external beta users. The hard part is that a beta can be a learning period or a soft launch, and those paths lead to different scope, timelines, and communication choices. Assume no final launch date or numerical success targets have been locked yet. Your job is to propose an execution plan that helps the team learn quickly without drifting or launching GA unprepared.

What to produce

Write a 2 to 3 page product brief for the VP of Product.

Your answer must

State the primary goal of the beta period and how that goal should shape scope decisions before GA.
Define 3 to 5 questions the team must answer before committing to GA, including at least one about user behavior and one about business readiness.
Recommend a process for using both internal dogfooding and external beta feedback, including how to resolve conflicts between them.
Propose clear GA readiness criteria across product quality, cross functional alignment, and launch readiness.
Outline the PM's operating plan with design and engineering for the next phase, including decision cadence and how trade offs will be made.

Constraints

Do not assume major new product lines, partnerships, or acquisitions.
You cannot rely on large scale quantitative history or locked success metrics, because the product is still in beta.
Any recommendation must preserve flexibility to change direction based on what the beta reveals.
GA planning must consider plan and pricing readiness, not only feature completion.

Format

Use five sections with short headings: objective, key unknowns, learning plan, GA readiness, and team operating model.

How Figma actually played it

Figma's product manager for FigJam describes how the whiteboard went from an internal idea to a public beta and then general availability. The conversation covers how the beta was used to learn quickly, how the PM role works across design and engineering, and what changed on the way to GA. It is a good look at running a beta as a learning tool rather than a soft launch.

Use a beta to stay flexible and respond to users before locking scope.
A PM's job is often to keep a cross-functional group listening to each other.
Dogfooding inside the company is a cheap source of early signal.
Pair the GA moment with plan and pricing decisions, not only features.

Built from Jamming on FigJam: a journey from beta to GA by Alia Fite (interview with PM Emily Lin), Figma.