Building a Design System from Scratch (Without Burning Out)

What I learned shipping a design system to a 12-person product team — what to build first, what to skip, and how to keep designers and engineers shipping in parallel.

Design systems are easy to start and brutally hard to sustain. After helping ship a system from zero to production this past year, here's what I wish I'd known before line one of Figma went down.

Start with tokens, not components

Color, spacing, typography, radius — once these are codified, components become trivially consistent. Skip this step and you'll re-litigate every padding decision for the next two years.

Ship the boring components first

Buttons, inputs, links, cards — the unsexy 80% of every screen.
Modals and toasts — every team builds these, badly, in isolation.
Layout primitives (Stack, Inline, Grid) — quietly the most powerful component in your library.

Documentation > Polish

A mediocre component with great docs gets adopted. A perfect component with no docs gets re-built. Always.

Let's work together

Open to UI/UX projects, collaborations, and product design support in Hong Kong and remotely.

Let's Connect