Enterprise expansion depends on proving that shared design systems matter after prototyping gets faster.
Design leaders need consistent collaboration across the canvas, while procurement leaders need a credible reason for broader plan spend.
Who you’d be doing this for
“Engineering keeps asking why the generated code drifted, and I’m still chasing five teams for the same component rules.”
Leandro Vargas · Design Systems Director
Leads the shared component library across a large product organization evaluating whether to expand its Enterprise Plan.
What is at stake
Strategic accounts are questioning broader Dev Mode spend while inconsistent components still create engineering rework. You must weigh a repeatable enterprise motion against the pressure for account-specific commercial concessions.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- repeatable package vs account-specific urgency
- design-system consistency vs procurement scrutiny
- enterprise expansion vs bespoke commitments
- quarter-end momentum vs durable value proof
Why Figma
Organization and Enterprise plans sit at the point where large product organizations standardize collaboration across design and engineering.
Written with these in mind
Not your kind of problem? 51 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.