← Figma
Something new at Figma

Settle what evidence a concept needs before it enters shared files

You’re the design researcher. Your team is in the room. Printed Oct 15, 2026.

Polished generated concepts are reaching design review before their user rationale is visible.

Fast exploration protects momentum, while comparable user evidence protects the quality of what enters shared files.

Who you’d be doing this for

“I had three directions on the board, and everyone picked the prettiest one before we knew who it helped.”

Fumiko Sato · Senior Product Designer

Designs interfaces for a product team that now uses generated concepts during early exploration.

What is at stake

Generated concepts are entering reviews without a shared account of the user need they serve. You have to weigh rapid exploration against evidence strong enough to guide a product decision.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • rapid exploration vs. user-grounded selection
  • design freedom vs. comparable evidence
  • roadmap speed vs. research rigor
  • polished output vs. credible rationale

Why Figma

Figma files sit at the point where early interface choices become shared design and developer handoff work.

Written with these in mind

strategic UX researchermixed-methods product researcherdesign-tools researcher

Not your kind of problem? 45 more at Figma, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.