A Space Shuttle cockpit with glowing green displays, overlaid with a grid of white design-tool icons
Product

From NASA to Design Tokens: A Short History of Design Systems

The design system is usually described as a product of the 2010s. Its real ancestors are a subway manual from 1970 and a ring binder NASA issued in 1976.

Read Article
CategoryProduct
Reading Time5 min
DateAug 2, 2026

TL;DR

Design systems did not start with Figma libraries or React components. They started as printed manuals that told thousands of people how to apply one identity without asking the designer. Each generation since has kept the same idea and changed what the “manual” is made of: paper, then code, then components, and now design tokens, which received their first stable shared specification in October 2025.

1970: a manual for a subway

In the late 1960s the New York City subway was a tangle of signs inherited from three separate rail companies. The Transit Authority hired Unimark International, and in 1970 Massimo Vignelli and Bob Noorda delivered the New York City Transit Authority Graphics Standards Manual.

It reads like a modern component library. It defines a small set of parts (a typeface, arrows, coloured discs for lines) and precise rules for combining them: what information appears at which point in a journey, how big, in what order. The designers knew they would never hang a single sign themselves. The manual was the product.

1976: the NASA binder

A few years later, Richard Danne and Bruce Blackburn redesigned NASA’s identity and replaced the agency’s busy “meatball” insignia with the red logotype now known as the worm. The NASA Graphics Standards Manual, issued in 1976, specified how that identity applied to everything from letterheads to vehicles, aircraft and spacecraft.

Two things about it are worth remembering. First, it was a system for people who were not designers: engineers, printers and contractors spread across the United States. Second, a system is only as strong as its support inside the organisation. NASA retired the worm in 1992 and went back to the meatball. It was brought back for the SpaceX crew launch in 2020, by which time the manual had become a design classic. Jesse Reed and Hamish Smyth reissued both the subway and NASA manuals as books through Kickstarter campaigns in 2014 and 2015, and what was, in effect, old corporate documentation found a new audience among designers.

1977 to 2011: patterns, then code

In 1977 the architect Christopher Alexander published A Pattern Language, a catalogue of 253 reusable solutions to recurring problems in buildings and towns. Software engineers adopted the idea of patterns first, and interface designers followed.

The web made the manual executable. In August 2011, Mark Otto and Jacob Thornton released Bootstrap, built at Twitter to stop internal tools from each inventing their own buttons and grids. For the first time the rules and the thing that enforced them were the same file: you didn’t read how a button should look, you used the button.

2013 and 2014: the vocabulary arrives

In 2013 Brad Frost proposed Atomic Design, which describes interfaces as atoms, molecules, organisms, templates and pages. It gave teams a way to talk about building from small parts upwards instead of page by page.

In June 2014 Google announced Material Design, a single visual language intended to work across phones, tablets, watches and the web. It showed that a system could carry a point of view about light, depth and motion, and it made “design system” a job title.

Design tokens: the smallest decision

Around the same time, the team building Salesforce’s Lightning Design System had a practical problem: the same brand had to appear on the web, iOS and Android, in several codebases. Designer Jina Anne and engineer Jon Levine started storing each visual decision (a colour, a spacing value, a font size) once, under a name, in a format every platform could read. They called these values design tokens.

A token is a decision with a name. Instead of the hex value #0e1011 copied into forty files, there is one entry called something like color.background, and everything else refers to it. Change it once and every product follows. Most systems now layer them: raw values at the bottom, purpose in the middle (“background”, “danger”), specific components on top.

For a decade every tool had its own token format. On 28 October 2025 the Design Tokens Community Group, which works under the W3C, published the first stable version of a shared specification, so that design tools and code can exchange tokens without translation.

What stayed the same

The medium changed four times in fifty years. The ideas did not.

  • Few parts, clear rules. Vignelli’s subway system used a handful of elements. Systems fail when they try to cover every case with a new component.
  • Written for someone else. The NASA manual was for contractors, and a token file is for a developer who has never met the designer. The test of a system is whether a stranger can use it correctly.
  • Explain why. The old manuals are full of reasoning as well as measurements. People follow rules they understand and work around the ones they don’t.
  • It needs a champion. The worm had a manual and still lost for twenty-eight years. A system survives when the organisation decides to keep it.

The next time someone presents a design system as a new idea, it is worth remembering that two of the most admired examples of the genre are books of rules written in the 1970s.

Sources

Related Articles

View All