The setting
builds AI-powered tools for product teams. applies AI models to creative design tasks for professional creatives and designers.
A successful asset trial does not settle whether another creative tool earns a place in the budget.
Design leads want room to explore, while sponsors want comparable costs and a clear reason to keep the tool.
Who you’d be doing this for
“My director asked which subscription we'd drop, and all I had was a folder of impressive images.”
Facundo Aguilar · Design Operations Lead · a character in this brief
Coordinates the evaluation for a product design group whose sponsor is reviewing its creative software budget.
What is at stake
Six design customers need evidence that another creative tool earns its budget. You weigh a comparable evaluation service against the customer-specific work needed to make its conclusions useful.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- comparable evidence vs customer-specific goals
- measurement depth vs time to production
- creative exploration vs cost per accepted asset
- tailored guidance vs repeatable service capacity
Why Figma
Node-based asset production sits alongside Dev Mode and Code to Canvas in customer workflows, making value depend on more than generation activity.
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)
- You’ll help shape the strategy of the CEM team, coach and develop individual contributors, and contribute to the broader goals of Weave’s Customer Experience organization.
- 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)
- Deliver technical workshops and training sessions to help customers confidently use sophisticated platform features
- 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
- 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 figuring out which problem is actually worth solving.
Customers are pausing expansion when AI-related spend reaches executive review without a shared value story.
You must weigh comparable evidence against the reality that each delivery organization measures outcomes differently.
Eight of twelve API champions cannot explain their integration's contribution to sponsors despite growing use.
You must weigh a repeatable value programme against the customer-specific evidence that earns another investment.
Legal Operations Managers have usage data but no executive-ready evidence of AI efficiency.
You must weigh a credible value narrative against a programme customers can complete during activation.
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.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn ambiguous signs of buyer interest into a concrete, measurable step toward commitment.
Too few paused mid-market pros resume lead spend after reaching the budget and targeting message.
You need to weigh a sharper service-specific claim against a clean test that preserves confidence in iROAS.
Enrolled brands are stalling before their first Insider Partnership action.
You must choose which brands need tailored coaching and which need a clearer scaled path.
New users are arriving from AI-assistant questions, but their path is hidden inside generic referral traffic.
You have to weigh a focused eight-week test against a broader discovery bet with less interpretable learning.
