Design system release
PublicHow a component goes from request to released, documented, and adopted.
How this workflow works
Intake
Airtable — Component requests
Any team can file a request for a new or missing component here — the intake form that keeps ad-hoc Slack asks from becoming untracked one-offs.
Spec
Figma — Pattern audit
Screenshotting every existing instance of a pattern across the product to see how far it's already drifted before designing the canonical version.
Figma — Spec + tokens
The canonical component gets built with real design tokens, not one-off values — states, variants, and spacing all named and documented.
Build
Storybook — Build & QA
Engineering builds the component in isolation here, variant by variant, so it's tested against the spec before it ever ships inside a real page.
→ ship together
Release
Zeroheight — Document
Usage guidelines, do's and don'ts, and code snippets get published together so nobody has to ask in Slack how a component is supposed to be used.
Manage
Linear — System backlog
The design system's own backlog, tracked separately from feature work so system debt doesn't quietly lose every prioritization fight.
Questions
Ask about the reasoning, not just the tools. The author gets notified here.
No questions yet.