The setting
builds AI-powered tools for product teams. applies AI models to creative design tasks for professional creatives and designers.
Active accounts and completed onboarding tell different stories.
Early intervention protects the first value review, while customer-specific milestones protect legitimate pauses from unnecessary outreach.
Who you’d be doing this for
“We finished the workshop, but my developers are still waiting on approval. Yesterday someone asked us to book the same training again.”
Haslina Wibowo · Design Operations Lead · a character in this brief
Coordinates a new enterprise design team's onboarding and reports progress to its sponsor.
What is at stake
New enterprise customers remain active while their onboarding steps stall. You decide whether AI can assign a stalled milestone from conflicting notes and activity, or must ask the CSM to establish the step first.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- shared milestones vs customer-specific plans
- early warnings vs unnecessary workshops
- product activity vs demonstrated capability
- broad coverage vs explicit completion signals
Why Figma
Enterprise adoption spans creative asset production, Dev Mode handoffs, and Code to Canvas exploration, so activity on one surface does not establish progress across the customer's agreed workflow.
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)
- In this role, you’ll partner with various internal teams to deliver a seamless, impactful, and engaging customer experience.
- 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)
- As the Manager, Customer Enablement, you will lead a team of CEMs who partner deeply with Weave’s customers.
- Our team of Customer Experience Managers (CEMs) work closely with some of Figma Weave’s largest customers to drive engagement, adoption, and value realization.
- 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)
- Delivered technical workshops, enablement sessions, or advisory services in past roles
- 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
- As one of our founding Technical Quality Specialists on the Product Support team for Figma Weave, you’ll have the exciting opportunity to help define, build, and elevate this new support function.
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.
Strategic developers reach weekly calls with onboarding work still stalled after cases close.
You must decide whether the AI only flags missing evidence or also names the stalled milestone for CSM review.
CSMs discover missed UAT steps at account reviews despite scientists using the application.
You decide whether the watcher can classify a missed step as a stall or must ask the CSM to interpret conflicting notes first.
Six of 18 new business accounts passed an onboarding milestone without a recorded explanation.
You decide when an inferred missed step warrants a flag in HubSpot rather than a request for the CSM to clarify the account first.
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.
