Design, before Any Software · Chapter 07
A token is a decision with a name
1:50 · Narrated with a synthetic voice. Captions are available in the player.
Read the transcript
The last block is about making a decision once. A token is a design decision given a name, so that the decision lives in one place and every use points at it. The structure that matters is two layers. Primitives describe values: grey nine hundred, blue five hundred. Semantic tokens describe jobs: text, surface, action, danger, and they point at the primitives. Components refer only to that second layer. The payoff arrives the first time somebody asks for a dark theme, a rebrand, or a version for a client, because you remap a dozen lines in the middle and everything follows, instead of editing every component and missing three of them. Be careful about when. A system slows down the first three screens, because you are deciding things you cannot yet decide, and most published advice comes from organisations a hundred times larger than the project in front of you. Two triggers are worth waiting for: the same decision made three times, or a second person joining. Before either of those, the right amount of system is three things. A spacing scale, a type scale and a colour ramp. Half an hour, and they pay back immediately. And budget for the ownership, because a system is a product with users, and keeping a modest one alive costs a day or two a month for as long as it lives.