The setting
builds AI-powered tools for product teams. applies AI models to creative design tasks for professional creatives and designers.
Tomorrow's workshop must choose between a broader workflow and a simpler handoff.
Keeping Code to Canvas in scope protects the customer's intended workflow, while narrowing to Dev Mode protects time for independent practice.
Who you’d be doing this for
“My developer opened the file and asked which version to use. We waited fifteen minutes for our champion.”
Katharina Dubois · Product Designer · a character in this brief
Participates in the customer's adoption cohort and prepares generated assets for a developer partner.
What is at stake
Only six of eighteen designer-developer pairs finished an asset handoff independently. You must weigh keeping the intended workflow against giving everyone enough time to practice a narrower one.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- workflow breadth vs time for practice
- independent completion vs champion assistance
- simple exercises vs representative customer work
Why Figma
Generated visual assets earn a place in the customer's production workflow only when developer partners can use what designers produce.
Written with these in mind
Not your kind of problem? 55 more at Figma, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Figma. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Customer Enablement Manager - Figma Weave (London, United Kingdom) (opens in a new tab)
- Customer Enablement Manager - Figma Weave (New York, United States) (opens in a new tab)
- Manager, Customer Enablement - Figma Weave (New York, United States) (opens in a new tab)
- Technical Account Manager (opens in a new tab)
- Partner with developer teams to improve design-to-code workflows, including Dev Mode adoption, extensibility initiatives and other emerging platform capabilities (Code to Canvas)
- A background in frontend development or familiarity with design-to-code workflows
- Technical Quality Specialist - Figma Weave (Singapore) (opens in a new tab)
- Keep the broader Product Support team up to date on current high-priority bugs and fixes that have been implemented in Figma Weave
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about people starting something and never quite finishing it.
Four of six researchers still need a developer to finish their first task.
You must weigh tailored guidance for Friday against a reusable walkthrough that reaches future users.
Three finance departments still run reports manually after completing dbt training.
You weigh customer ownership through a workshop against specialist configuration in the only available session.
Eight of twelve consulting analysts rebuild their generated briefings despite acceptable content.
You must weigh a tailored skill against teaching flexible inputs in the only working session available.
The same setting, from another role
Each is set around Figma’s Figma Weave, written for a different role. They’re separate briefs, not the same scenario.
Repeated sandbox failures leave designers retrying asset workflows while engineers reconstruct causes across layers.
You must decide what AI assembles, what engineers verify, and how the team runs it after handover.
Designers are leaving custom Weave tool runs when they cannot tell what file context a tool will access.
You must weigh workflow speed against explicit control over shared design assets.
Published previews are showing earlier asset versions after a newer workflow state was approved.
You must weigh uninterrupted design-to-code work against a publish path that cannot prove what it rendered.