Developer handoff is speeding up while the design-system inputs behind it remain uneven.
Design leaders need consistent system guidance, while engineering leaders need enough flexibility to ship without another review layer.
Who you’d be doing this for
“Engineering asked why three buttons with the same name behave differently, and I had to trace every variant by hand.”
Sara Ozturk · Design Systems Lead
Leads the shared component library for an enterprise product organization participating in the pilot.
What is at stake
Developers open Dev Mode but still return to designers for missing states and token names. You must weigh a repeatable programme against each customer’s different design-system maturity.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- repeatable programme vs customer-specific maturity
- developer speed vs design-system consistency
- technical depth vs scalable enablement
- near-term workshops vs renewal evidence
Why Figma
Dev Mode sits at the point where collaborative design files become inputs for enterprise developer workflows.
Written with these in mind
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.