UX essay · System design

A design system is only living if it is used as code

I have built a design system at every company I have worked for since 2017. One difference decided which of them were still in use after I left: whether the library was compiled into the product, or filed as a document to consult. This page walks through the process with Findhotel as the example, then shows what the other systems shipped.

6
Companies, one method, 2017 to today
9
Rules a component had to pass before publishing
6
People on the Findhotel team, four of them developers
Clients
Role UX Designer, and the system's product owner by default
Team At Findhotel: 4 front-end developers, one from each product team, and 2 designers, on a kanban board with no product owner
Timeline Coolblue 2017, Floorplanner 2018, Maersk 2019, Findhotel 2020, and since then Zimmer Biomet 2021 and TrackBee 2025
Platform Component libraries behind web products, on desktop and mobile
Tools Sketch, Figma, Zeplin, InVision, Abstract, Storybook, Chromatic, Claude Code
A page of the style guide showing single line text fields in every state, primary and secondary buttons, sliders and an icon row
Sample of Floorplanner's design system. A text field can have multiple variants depending on its state.

Problem

Nobody decides to build four different buttons

In a company of any size, designers sit with product teams, for good reasons: each learns that team's problem and ships on its roadmap. The cost shows up later. Put two teams' screens side by side and the differences are obvious.

It happens at every scale: a font style one step off, a grey sampled from a screenshot, or a whole flow built because one team could not know another had already solved it.

This is not a quality problem. Every screen was made carefully by someone competent. The inconsistency comes from how the teams are organised, so the fix has to change the organisation too. A document asking designers to be consistent is only a request.

So I do not build a style guide. I build a place where designers and the front-end developers who care about user experience agree on a shared language, and a route that turns what they agree into part of the product.

Goals

What a system has to do to be worth the sprint

Consistency the customer feels
The customer never opens the library. They benefit because a button looks the same on every page, so there is nothing to relearn.
Open enough to be edited
Developers, copywriters and product owners all have a say in how a component behaves. If only designers can edit it, the others will work around it.
Compiled, not consulted
Change the style guide and the products change. If one person reads the guide and another types it in again, the two drift apart.
Deep dive

Who uses the library

Developers, designers, copywriters, product owners

The beneficiary is the customer. The users are four groups in a company.

Front end developers
The group that decides whether any of it is real. They need a component they can import, not a specification they have to interpret.
Designers
They need to be able to take a component off the shelf and trust it, including trusting that somebody else can edit their work without it falling apart.
Copywriters
The most consistently forgotten. Word length, tone and sentence shape are component properties, and a component made only in English at a comfortable length is a component that is likely to break.
Product owners
They need to see what already exists before they scope something that does not need building, which is the cheapest saving in the whole exercise.

Team & audience

One sprint in four, and no product owner

What has worked best for me is a borrowed team, not a standing one: a designer and a front-end developer from each product team, meeting on a fixed schedule.

For three sprints everyone works on their own product and runs into what the library is missing. The fourth sprint starts with a queue of real needs, not a wish list made up in a meeting room.

At Findhotel the team was six people: four front-end developers, one from each product team, and two designers. We ran a kanban board and had no product owner.

Scope and constraints

What did not need an experiment

Almost none of this work was tested, and that was the correct call. Two key decisions made up nearly all of it, and neither is the kind of question an experiment can answer.

The first is removing a variation nobody chose. If a product has three greys where two teams each invented one and nobody can say what the third is for, collapsing them is not a hypothesis. There is no version of the result that argues for keeping an accident.

The second is applying guidance that already exists and is better evidenced than anything we could run ourselves. Contrast ratios are the clearest case: W3C has done the work, at a sample size no single company reaches, and rerunning it locally to see whether our users also prefer being able to read things would be theatre.

When a change genuinely was a question, it left this team. It went down to the product team that owned that flow, where there was a product owner to prioritise it and a data scientist to design the test.

Process

Six steps, and the first three are politics

The order matters. Three of these six happen before a single component is made, and skipping them is how a design system becomes a folder somebody made once.

01

Mapping what is already there

An inventory before a proposal. Colours, text fields, font families, toggles, sliders, popups, buttons, split buttons, galleries, and every variation of each that the product turned out to contain.

The deliverable is the list, drawn out. Someone can dispute a count of thirteen button styles. Nobody disputes thirteen buttons laid out across three slides.

At Findhotel the primary button appears three times, in three different blues: #3979F5 on the buttons slide, #0074F8 in the header, #4476FB in the dialogues. Nobody picked three on purpose.

Buttons

13
Search
Primary button
Filter by
Secondary button
Reset
Quiet button
Go back to search
Link button
Unlock Deal
Private deal button
Field icon button
Show details
Accordion button
EN€
Button row
English
List icon text button
Delft
Anchor button
Icon button
9+
Toggle button
Best match
Radio button
  • #3979F5Buttons slide, Search
  • #0074F8Header section, Search
  • #4476FBDialog, Back to form

One primary button, three blues.

Deep dive

The rest of the catalogue

43 components

Form

13
First name *
Empty input with placeholder
Taipei City
Text input completed with clear option
Empty text input with button
e.g. city, region or hotel
Taipei CityTaiwanDec 15 - Dec 16, 2 GuestsCity
Taipei CityTaiwanNov 24 - Nov 25, 2 GuestsCity
Autocomplete text input
Taipei City
Taipei CityTaiwanDec 15 - Dec 16, 2 GuestsCity
Taipei CityTaiwanNov 24 - Nov 25, 4 GuestsCity
Autocomplete filled input
Choose a bed type1 double bed2 single beds1 double bed and 1 sofa bed2 double beds1 king bed1 twin bed
Select field
Tue, Jan 21January 2020 ›MoTuWeThFrSaSu1314151617181920212223242526
Date field
Telephone number *This does not look like a valid phone number
Error message on an empty input
Requests (optional)
Textarea
Hotel
Checkbox
Expiration MM/YY *12/19
Input with mask
Telephone country code *Netherlands +31
Complete input with validation
Telephone number *0654331553You may be reached at: +31 654331553
Empty input with info

Display

9
The price for this hotel has dropped today
Tooltip
Private deal unlocked8.3Efficient check-in/check-out
Chips
Stars
Couples50%
Progress bar
Spinner
Searching all the best travel sites
Toaster
We use cookies. Continue browsing if you are okay with that.
Overlay banner
Unfortunately the price has changed.The price raised from €181.72 to €182.00Secure bookingIt takes only 2 minutesThe deal you chose is no longer availableWe found you these other great deals
Inline banner
Property TypeHotel854Apartment212Guest house63Hostel29Bed and breakfast11Inn4Show more
Filter options

Containers

8
Movenpick Hotel AmsterdamOostelijk Havengebied8.8FabulousBooking.com€111View DealACCOR€111€105View Deal
Card
Check in/Check outCheck in from 15:00Check out prior to 12:00GeneralPaymentHouse rules
Expansion panel
Booking.com€141View Deal
Clickable row with hover
Option 1Free cancellation↑ Before Mon, Jan 20€123Reserve
Row
Booking.com€92View DealExpedia€94View DealHotels.com€94View Deal
Row list
Divider
FINDHOTELEN€
Header section
Footer section

Images

Avatar
Image thumbnail
Image, one round corner
Image with round corners
1/49
Image

Menus

FINDHOTELEN€EnglishEspañolFrançaisPortuguêsItalianoDeutschNederlandsPolskiTürkçeSvenskaDanskNorskSuomiČeštinaMagyarRomânăHrvatskiSlovenščinaEestiLatviešuLietuviųFilipinoMelayuSlovak
Dropdown menu
PreferencesEnglish (en)Euro (€)About UsPrivacy PolicyHotels FAQContact
Burger menu
AmsterdamCheck InTue, Jan 212 Guests, 1 RoomCloseSearch
Expansion menu

Navigation

View on Google Maps
Link
Link list
PhotosDetailsLocationReviewsDeals
Tabs

Overlays

FINDHOTELEN€Sold out on your datesLooks like there are no longer any rooms available for the dates you selected.Back to previous page
Page overlay
Payment failedSorry, we could not process your payment. Please try again.Back to formCustomer Support
Dialog
02

Buying the time

With the inventory in hand, a lead developer and I presented to the people who decide where sprints go. We invited the people who had been complaining that the product did not look like itself. They had already seen the problem; they just had no name for it.

Nobody funds a design system as an idea. They fund it once they have seen the thirteen buttons.

03

Composing the team from every team

A designer and a front-end developer from each product team.

With someone from every team, the library has a voice in every room where it will be used. By launch day, adoption has already happened. That is the difference between a library the company uses and a library only its authors use.

Four product teams, and the six people who put their strengths together: four front-end developers and two UX designers.

04

Choosing tools

On the design side this came down to two decisions: what to draw in, and where to publish. At Maersk in 2019, InVision was already licensed and widely used. At Findhotel it was Zeplin. Both companies used Sketch. In each case the answer was the tool already in use.

On the development side there was a new requirement rather than an inherited one: the main consideration was to make the process of publishing and debugging a component as automatic as possible.

05

Making components, and agreeing what one is

Divided among the designers, one component at a time, and the unit of work is the component in all of its states.

Two designers splitting the work will make two halves that do not fit, unless someone writes down what "finished" means. So I wrote nine acceptance criteria every component had to pass.

  1. Flexible to resizing with autolayout
  2. Using the official list of named font styles
  3. Using the official list of named colours
  4. Fitting exactly within the grid: one unit is 8px, and it can be halved to 4px when needed
  5. Carrying a mobile and a desktop version, where that applies
  6. Exposing the fewest editing permissions that still make it useful
  7. Properly named, including every sublayer
  8. Tested on a canvas for resizing and for permissions
  9. Published to the official platform

Three of them are worth seeing rather than reading, because each is a rule about a shape.

Shape rules

PlaceholderPlaceholder1u = 8px
Placeholder
2u
2u
Placeholder3u
2u
Placeholder
Placeholder
1.5u1u1u
One unit is 8px, and every edge of the component lands on a whole number of them.
PlaceholderUser inputUser inputUser inputUser input
Six states, not one: normal, focused, filled, disabled, error, and resolved. All states of one component.
Placeholder
Placeholder
Placeholder
Which parts stretch and which parts hold, decided once rather than per artboard.
06

Publishing, which is where the argument is settled

My earlier attempts got this step wrong, and at the time it did not look like failure. I published the library to designers. Designers used it, and the products drifted anyway: developers who rebuild a design from a picture produce the same drift, one handover later.

Design only ships once it is code. So this time I published for the developers. I mapped each component between design and code, each with its own URL in an index file the front end could read.

Below is one component, the star rating, in all the three places it exists. It is the same object with variations.

What shipped

Pages that came out of the design system

These pages are assembled entirely out of parts made in their corresponding design systems.

Findhotel, 2020

The whole funnel, on desktop and mobile. The mobile captures are full page exports.

Deep dive

Floorplanner, 2018

Floorplanner, 2018

A drawing tool rather than a funnel. The two marketing pages at the end are the interesting ones, because a marketing page assembled from the product's own components is an example case where the guide reached beyond the core product.

Deep dive

Maersk, 2019

Maersk, 2019

Twill, Maersk's platform for the small and medium exporters and importers who book LCL (less than container load) cargo: shipments too small to fill a container, sharing the space and the cost with other people's freight. The screens below follow one booking from the destination search to the confirmation screen.

Deep dive

Zimmer Biomet, 2021

Zimmer Biomet, 2021

A surgical planner, built over eighteen months. Most of the dialogues in this product are one component with different content inside it. Change the component once and every dialogue changes with it.

Deep dive

TrackBee, 2025

Five flows shown at three widths each: signing in, creating an account, connecting ad platforms, choosing a plan, and coming back after a lapsed subscription.

Conclusion

A living design system is a system that is coded

Used in every product

By the time I left it was a live library, imported by every product in the portfolio rather than referred to by them.

Every component becoming accessible

Bringing every component up to W3C accessibility guidance improved every product at once.

Lessons

A silo on either side does the same damage
Even if the designers agree perfectly, developers who build the system from a picture or a guide produce the same drift, one step later.
One source of truth, no more drift
The principle that has done the most for me, and the easiest to break by accident. Every other place a component is described is a place it will drift.
Make improving cheaper than starting over
Designers and developers never stop producing. Make improving an existing component the easiest path, so the system gets better instead of being started again.

What changed since

Since then Figma has become the default design tool, and Storybook has kept its place. The bigger change is underneath the tools: a designer working with agentic AI like Claude Code can write and commit a component directly, instead of waiting for a developer to build it.

2019 2020
Figma The online alternative, and still very much the challenger, not yet the default.
Storybook The other end of the same shelf. A component that exists here exists in the product.
Zeplin The source of truth both sides looked at. Fallen out of use
Sketch Where the components were drawn, and the seat both companies had already paid for. Fallen out of use
Chromatic What made a pull request something a designer could review, by turning a diff into a picture. Fallen out of use
2026
Figma Stayed exactly where it was, except it is no longer the challenger. It is simply the platform people design in.
Storybook Still the other end of the same shelf, for the same reason it always was.
Claude Code The actual change. A designer can write and commit a component here directly, so the handoff above is sometimes just one person, one file.