Systems

7 min read

A design system is a list of decisions

Components are the easy part. The hard part is agreeing what 'primary' means, and writing it down where people will find it.

Every design system I’ve inherited had a beautiful component library and no rules. Three teams used the same button in three different ways.

At Tessel we started with a document instead of a Figma file: forty short decisions, each one sentence long. ‘A page has one primary action.’ ‘Status is one of five words.’

The components came later and were almost boring to build, because the arguments were already settled.

If your system is drifting, don’t add components. Find the decision nobody wrote down.

[05]

KEEP READING

More from the journal

[12]Next step

Got a messy workflow? Let's untangleText · 104 it.

Tell me what's slow, confusing or costing you support tickets. I reply within one working day with a first idea and a fixed price.

Book a 20-min intro

Local time ● online

--:--:--
Rotterdam. I reply within one working day, usually faster.

Version history v26.10

v26.10Added the Kiln Audio case studyv26.07New journal: receptionists and booking flowsv26.04Orrin pay run results are inv26.01Portfolio rebuilt as a design file
© 2026 Noor Castell. Built in Framer.Rotterdam · AmsterdamBack to top ↑

Create a free website with Framer, the website builder loved by startups, designers and agencies.