Figma · Product sense · Mid · 45 to 60 minutes

How should Auto Layout evolve?

Figma is a browser based design and prototyping tool where teams create and collaborate on digital interfaces. Answer this product management case and get it graded line by line against a weighted rubric.

Product sense
Tradeoff judgment
User empathy
Prioritization
Written communication

The situation

Your manager, who leads Figma's editor product area, asks you to recommend what to do next with Auto Layout, a feature launched last year to help designers build interface layouts that adapt without endless manual resizing. Early adoption is encouraging, but feedback is split. Some designers still resize and rearrange elements by hand because they find the current behavior hard to predict in real files. More advanced users want Auto Layout to handle a wider range of interface patterns and feel boxed in by its current rules. Research, support, and community feedback all point to the same tension: if Figma adds more controls, the feature could become harder to learn and less approachable, but if it stays simple, many important workflows remain manual and the feature may stall. Leadership wants a product direction for the next major iteration, not just a backlog of tweaks. They need to know which user needs to prioritize, how to handle the flexibility versus usability tradeoff, and how to introduce any changes without confusing the people who adopted the first version.

What to produce

Write a one page product recommendation memo, 700 to 900 words.

Your answer must

Define the core user problem, anchored in the manual layout and resizing work designers are still doing today.
Identify at least two user groups or skill levels affected by Auto Layout, and explain how their needs differ.
Present two or three product direction options, with explicit tradeoffs between flexibility and usability for each.
Recommend one direction for the next iteration, including what you would add, what you would not add yet, and why.
Specify how you would measure success and what user feedback you would collect after launch.
Explain how you would help users understand the change so the evolution feels learnable, not abrupt.

Constraints

Your proposal must preserve compatibility with existing files and current Auto Layout usage.
Your solution must fit inside the existing Figma editor experience, not a separate product or mode.
You cannot optimize only for expert users if that would make the feature meaningfully harder for new adopters to start using.

Format

Use five sections: problem, users, options, recommendation, validation and rollout.

How Figma actually played it

An engineer on the Auto Layout team traces how the feature evolved after its 2019 launch, starting from how designers resized designs by hand and moving to more power and flexibility. The post describes the tradeoffs between flexibility and usability, and how user feedback shaped the new version. PMs can learn how to grow a feature without losing the simplicity that made people adopt it.

Launch approachable first, then add power guided by user feedback.
Name the tradeoff explicitly (flexibility versus usability) and revisit it.
Anchor the redesign in the manual task users were doing before.
Show the evolution so users understand why things changed.

Built from Behind the feature: the making of the new Auto Layout by Willy Wu, Figma.