The setting
builds AI-powered tools for product teams. applies AI models to creative design tasks for professional creatives and designers.
A year of support commitments rests on disputed evidence of production use.
Design leadership wants eight teams protected, while finance wants funding restricted to the three with visible shipped work.
Who you’d be doing this for
“Finance asked me to name what shipped, and I spent last night chasing eight leads instead of preparing our launch.”
Thierry Wolf · Design Operations Lead · a character in this brief
Coordinates the eight customer teams whose shared asset workflows will remain funded or enter retirement after signature.
What is at stake
Eight design teams face a funding decision tomorrow, but only three have shown where generated assets shipped. You must weigh broader continuity against a year of support promises that the available evidence may not justify.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- adoption breadth vs demonstrable value
- shared workflow continuity vs funding discipline
- annual commitments vs incomplete evidence
- specialist depth vs number of supported teams
Why Figma
Figma Dev Mode and Figma Code to Canvas activity must translate into customer outcomes rather than stand in for evidence that generated assets reached shipped interfaces.
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)
- Guide customers through enterprise API usage and system integrations, helping them extend Figma’s capabilities within their broader technology ecosystems
- Technical Quality Specialist - Figma Weave (Singapore) (opens in a new tab)
- Work with the Product Support Learning and Performance team as a subject matter expert to develop documentation and training materials for future Technical Quality Specialists
- Develop expertise in Figma Weave’s products and the journey of our customers—from Product Designers to Developers—to accurately diagnose sophisticated bugs
Reporting read before this brief was written
The pieces closest to the situation in this brief.
According to an August 2026 account of Figma's token pricing change, some organizations found their annual Figma bill had quadrupled within two months once Dev Mode access for designers and PMs began to be charged.
Rapid-Fire Shipping is not the same as Delivering Good Products (opens in a new tab) · strategiccreations.beehiiv.com · Aug 26, 2026
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 figuring out which problem is actually worth solving.
A 10,000-seat renewal is at risk because faster planning is not yet tied to reviewed AI Workflow outcomes.
You must weigh product momentum against controls that IT and the Center of Excellence can defend.
A Premium account with 180 active builders may restrict access nine days before renewal because credit charges are not predictable.
You have to weigh builder adoption against a commitment procurement can trust.
The customer has six weeks to decide whether automated plays stay in its forecast workflow.
You have to weigh measurable adoption gains against evidence that leaders can defend to privacy and finance.
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.