Free playbook
How to build UI infrastructure your team actually uses: readiness gates, build order, adoption, governance, and measurement. Worksheets included.
Contents
Not a component catalog. A practitioner's playbook for the messy middle: getting from UI chaos to something squads trust.
01 · Start here
You don't need another Pinterest board of component screenshots. You need a path that survives contact with engineering, product pressure, and the next reorg.
This playbook is for product teams (roughly 20, 200 people) who:
I've led design systems at enterprise scale (Aurora used by dozens of teams and millions of users) and spent 16+ years in the seam between Figma and the repo. This guide is what I wish every team had before they spent six months on a library nobody adopted.
40-Point Audit = score where you are today. 100-Day Playbook = day-by-day execution timeline. This guide = the decisions, worksheets, and failure modes that determine whether your system survives handoff.
Read straight through once. Then use the worksheets with your design, engineering, and product leads.
02 · The inconsistency tax
Every squad that reinvents buttons, form layouts, and spacing is paying a tax. It shows up as hours, not line items.
The tax compounds in four places:
Fixing problems gets exponentially more expensive the later you catch them. A spacing mistake caught in design costs an hour. In code, a day. After release, a sprint (or a rollback).
A design system isn't decoration. It's infrastructure that turns one good decision into a hundred correct implementations. Without it, you're paying the tax every sprint.
Most teams don't need permission to feel the pain. They need a shared picture of what it's costing and a sequence that doesn't require stopping the roadmap for a year.
03 · Three things teams confuse
Teams argue for months about "building a design system" when they mean three different things. Name it clearly.
A library without governance becomes shelfware: impressive in a demo, bypassed in production. A system without code connection becomes a PDF engineers ignore.
Practical test: Can a new engineer build a compliant screen on day one without Slack archaeology? If not, you have pieces of a system, not a system.
Public systems use different words (patterns, regions, modules). Pick names that fit your team and stick to them. Alignment beats perfection.
04 · The readiness gate
Starting too early creates process drag. Starting too late cements debt. Five green lights, three red flags.
Green lights (consider formalizing):
Red flags (stay lightweight for now):
If you're in the red zone: organize tokens and top 10 components informally. Document decisions in comments. Revisit the gate in one quarter.
05 · The six-layer stack
Think stack, not shopping list. Upper layers depend on lower ones. Skip a layer and the stack wobbles.
Squads usually ask for Layer 3. The expensive bugs live in Layers 4, 6. Patterns (configuration flows, data tables, settings wizards) are where teams bleed time, not another button variant.
06 · Pain map worksheet
Interview design, engineering, and product. Rate each area 1 (fine) to 5 (major pain). Highest totals = your starting point.
| Area | What to ask | 1, 5 |
|---|---|---|
| Workflow | Where does design → dev handoff stall? How often do engineers re-ask for assets? | |
| Assets | Can people find and trust reusable components? How many button variants exist in production? | |
| Communication | Do PM, design, and eng share the same words for UI decisions? | |
| Product / user | Do inconsistencies drive support tickets or user confusion? | |
| Culture | Does leadership fund consistency? Is the system seen as "design only"? |
Do 3, 5 short interviews, then a team pulse. Qualitative stories + numeric scores convince leadership faster than either alone.
07 · Dual inventory method
Screenshots show what users see. The repo shows what ships. You need both.
Visual pass (half a day):
Technical pass (with an eng partner, half a day):
#hex, arbitrary px) bypassing tokens| Item | Locations | Visual match? | Code match? | Priority |
|---|---|---|---|---|
| Primary button | ||||
| Text field | ||||
| Page heading | ||||
| Nav pattern |
Prioritize by: frequency in product × fix effort × user impact. Not everything gets fixed in sprint one.
08 · 30-day starter sprint
Pair system work with active product delivery. Visible wins beat big-bang launches.
Pain map + dual inventory. Name one eng champion and one product ally. Pick one live feature to improve (checkout, settings, onboarding).
Spacing (5, 7 steps), color (base → semantic aliases), typography (UI vs long-form). Export to JSON. One source both design and code can reference.
Button, text field, form label, card. All states (hover, focus, disabled, error). Wire to tokens. Ship in the chosen feature.
Before/after on the feature. Rough hours saved. Demo in eng standup. Document do's/don'ts for what you shipped.
Don't pause the roadmap. Replace UI in a live flow while you build the library. Leadership funds what ships, not what sits in Figma.
09 · Build order that sticks
Teams that jump to 40 components before tokens almost always drift within two quarters. This order holds.
space-section, space-inline), not isolated pixel picks per component.surface-raised). Never attach hex directly to components.For EU products: plan logical CSS (margin-inline), RTL tokens, and typography that tolerates German copy expansion (~30%) from day one.
10 · Winning the room
"Consistency" doesn't open wallets. Hours saved, tickets avoided, and faster shipping do.
15-minute ROI exercise:
Direction beats precision. You're proving the shape of the benefit, not winning a finance audit.
| Stakeholder | Lead with | Avoid |
|---|---|---|
| Engineering | Less rework, copy-paste components, fewer review loops | Pixel-polish arguments |
| Product | Guardrails for safe exploration, faster discovery | "Everything through design" |
| Executive | ROI, risk reduction (a11y, brand), onboarding speed | Component counts |
| Sales / marketing | Demo matches shipped product | Abstract design theory |
Pair system work with an active OKR when possible: "We improved checkout and shipped a reusable form pattern."
11 · Adoption beats assets
I've seen teams spend a year on components only to hear "the design system failed" because only designers knew it existed.
Adoption playbook:
Consumption and contribution are different strategies. Design for the 95% who consume. Make using the system faster than bypassing it.
Figma is the map. Users touch production. Live examples in Storybook beat static spec PDFs. When designers join PRs for component edge cases, handoff stops being a cliff.
12 · Governance without police
When governance is unclear, squads duplicate components and use one-off hex values. That's not rebellion. It's rational.
Hybrid model (works for most scale-ups):
Publish a one-page ownership map: who to ask, how to contribute, expected review time. Transparency beats more process.
Deprecation done right: announce → provide migration path → maintain for 1, 2 release cycles → remove. Old patterns clutter libraries and confuse AI tools.
13 · Measure outcomes
"We have 400 components" is not a win. Tie the system to product outcomes leadership already cares about.
Metrics that survive budget reviews:
Align system goals to active product OKRs each quarter. Example: "Standardize billing forms → 25% fewer billing support tickets → WCAG 2.2 AA on all form components."
Establish baselines before you claim impact. A one-question pulse in Slack after each release beats an annual survey nobody fills out.
14 · Five ways systems die
Most failures are predictable. Spot your team in this list early.
Start small. Iterate in public. Pair with product work. Celebrate one squad adoption win per month.
15 · AI guardrails
One prompt can generate a dozen plausible screens that all disagree with each other. Without guardrails, AI adds entropy.
Make your system machine-readable:
color.action.primary, not blue-500)AI accelerates production. It doesn't replace intent. Designers who strengthen systems thinking, ethical constraints, and cross-functional collaboration become more valuable, not less.
I placed 1st at the Into Design Systems AI Hackathon 2026 with a Figma plugin that smart-swaps mismatched components. The system was the constraint that made AI reliable.
16 · 90-day roadmap worksheet
Fill this in with your leads after the pain map and dual inventory. One theme per month.
| Month | Theme | Ship in product | System output | Owner |
|---|---|---|---|---|
| Month 1 | Foundations | One high-traffic flow updated | Tokens + button + input | |
| Month 2 | Expand | Second flow or dark mode | +6 components, Storybook live | |
| Month 3 | Patterns | Settings or table pattern | Governance doc + champions |
Need a day-by-day version? See my 100-Day Playbook. Need a health score? See the 40-Point Audit.
17 · What to do next
I help DACH and EU product teams turn UI chaos into systems that scale, govern, and ship.
Fixed-scope diagnostic across design, code, and process. Prioritized roadmap + readout call. Fee credited toward a build.
Tokens, core components, docs starter, and the Figma↔code connection. Built for adoption, not shelfware.
Ongoing governance and design engineering so the system stays healthy as you grow.
16+ years · Nord/NordVPN design systems (dozens of teams, millions of users on Aurora) · React/TypeScript · 1st place, Into Design Systems AI Hackathon 2026
I'll give you two or three concrete observations on your situation. No pitch deck.
Get a free consultation · christophhellmuth.com · post@christophhellmuth.com
© Christoph Hellmuth · Free to share with attribution · Not for resale
Full compendium → · 40-Point Audit → · Pilot-First Playbook → · 100-Day Playbook → · Collaboration ebook →