Design System 0→1
How do you unify a 50-person design org without slowing anyone down?
- Design Systems Lead
- 2022
The Problem
Onboarding designers took 3 weeks. Teams reinvented components constantly. Handoff to engineering was messy (three design patterns for the same thing). Accessibility was inconsistent—some teams got it, others didn't.
Context
Growth-stage SaaS, 500+ employees, 15 product designers across 5 teams. Timeline: 6 months to MVP. No dedicated design systems team; I was product designer + systems lead. Success = 80% component reuse, handoff time <1 day.
Key Learning
Watched how teams actually worked. Found: they weren't reinventing because they were stubborn—they were reinventing because they couldn't *find* what already existed, or it didn't quite fit their use case. Discoverability and flexibility mattered as much as standards.
What We Did
Built a system with 3 layers: tokens (color, spacing, type—the rules), components (button, input, card—the primitives), and patterns (forms, tables, modals—how you combine primitives). Documented *why* each decision existed, not just *what* it was. Made it flexible at the component level but strict at the token level (so changes propagated globally). Held weekly office hours for questions. Made the Figma library a *joy* to use, not a chore.
Outcome
Component reuse hit 85% within 5 months. Handoff time dropped from 3+ days to hours (engineers could often just copy the spec). New designers shipped their first feature 40% faster. Bug reports from inconsistent implementations dropped 60%.
What's Next
We should have invested in a dedicated tools engineer earlier—manual syncs between Figma and code broke us. Also, we underestimated the *cultural* work—adoption was technical, but evangelism took longer. Finally, the system was brilliant for existing patterns; new patterns were painful to add. Should have built the process for that earlier.