Design tokens in plain English

Ask three people at a growing company for the brand’s blue and you’ll get three blues. Not because anyone is careless — because the brand lives in scattered files, and humans copy approximately. Design tokens are the fix, and understanding them takes about four minutes.

The plain-English definition

A design token is a named decision: instead of “our blue is #1A4FD8” living in someone’s memory and forty documents, there’s a single named value — color-action — that everything else refers to. Buttons don’t have a color; buttons have the token. Change the token once, and every button, header, and PDF template that uses it updates together.

That’s the whole idea. Names for decisions, stored once, referenced everywhere. It applies to colors, fonts, spacing, corner radii — every repeatable visual choice your brand makes.

Why owners should care (it’s not aesthetics)

Tokens are what make brand automation possible. Every generated artifact — the proposals from Automating proposals, reports, and PDFs, the decks from Slide decks on autopilot: when it works, your website, your email templates — needs to know your colors and fonts. Without tokens, each system has its own hardcoded copy, and they drift apart the way all copies drift. With tokens, they share one source of truth, and “refresh the brand” becomes an update instead of an archaeology project.

There’s a second, quieter payoff: decisions with names get respected. When the rule is “use color-action for buttons,” people follow it. When the rule is “use the blue from that one PDF,” people improvise.

What a useful token set looks like

You don’t need hundreds. A working small-business set is roughly: three to six colors with roles (not “navy” but “ink — for text,” “action — for buttons and links”), two font choices (headings, body), a small spacing scale, and any rules that protect you — like “never put orange text on cream, it fails accessibility contrast.” The roles and rules are the value; the hex codes are just the payload.

What to ask your designer for

Next brand project, add one sentence to the brief: “Deliver the system as named tokens — roles, values, and usage rules — not just logo files and a PDF.” Any designer working systematically can produce this, and it converts your brand from a look into an asset your software can enforce. What that enforcement buys you day-to-day is the subject of Why brand consistency is an automation problem.