Build a design
system in ninety days.
Eight chapters mapped to a 90-day path. Days 1–7 to orient. 8–30 to build the spine. 31–60 to ship to other teams. 61–90 to operate. Practitioner-voiced, opinionated, links to canonical examples instead of abstract theory.
The arc
Ninety days at a glance.
Four phases, eight chapters, sized by their share of the ninety days. Each band is proportional to its day count — Orient is the narrowest, Operate the widest. Click any chapter to open it.
Orient
Build the spine
Compose and ship
Operate
Orient
Build the spine
Compose and ship
Operate
90 days · 8 chapters · 4 phases
If you only have
Pick the budget you actually have.
Most people read "90 days" and bounce. Don't. Each entry point ends with a concrete artifact you can show your team — even if all you have is an hour between meetings.
A defensible answer to “should we build one?”
Chapter 01 plus the ROI calculator. Forty-five minutes of reading, fifteen minutes of inputs. You leave with a number you can defend to your director and a written threshold for “not yet.”
A written foundations brief.
The Day 1–7 phase: chapters 01–02 and the foundations index. By end of day you have a one-page foundations document — color decision, type scale, spacing baseline — that the rest of the system reasons against.
A token catalog and a component list.
Days 1–30: chapters 01–04 plus the token generator. Outputs: a portable token catalog (W3C-format export), a draft list of the ten components you'll build first, and a deprecation policy for anything you replace.
The path
Four phases. Eight chapters. One ninety-day arc.
Each phase ends with an artifact you can ship to other people. If a phase passes without producing one, you're behind — pause and recover before moving on. The path is opinionated; the order matters.
Orient.
Week 1
Decide whether to build the system at all. Run the math. Get the funding conversation right before any artifact ships.
Build the spine.
Weeks 2–4
Foundations first (color, type, spacing), then tokens (not raw values), then the right ten components. Three weeks, three artifacts.
Compose and ship.
Weeks 5–8
Stop building primitives. Document the ten patterns specific to your product, get a distribution mechanism (npm or registry) wired up, and start the adoption funnel.
Operate.
Weeks 9–13
Governance: who decides, who deprecates, who reviews. Measurement: what proves the investment was worth it. The work that turns a launched system into a sustained one.
Other track
Already have a product? Migrate instead of build.
The 90-day build path assumes you're starting near-zero. If you have an existing product that's already grown its own quasi-system, the migrate track is a different sequence — same opinions, different starting point.
Track · 5 chapters
Migrate to a design system
Getting an existing product onto a design system without burning out the team or stalling product work. The audit, the wedge component, the strangler-fig pattern, the deprecation playbook, the post-migration cleanup.
Start
Day 1. Chapter 01. Forty-five minutes.
The question isn't which framework. It's should you build at all. The first chapter answers that, defensibly.