Strategy
· 1 min read
What a design system is actually for

Written by
Hannah Bergström
Not consistency for its own sake. A system earns its keep by making the next decision cheaper than the last one.
Design systems are usually sold on consistency, which is the least interesting thing they do. Consistency is a side effect. What a system is actually for is making the next decision cheaper than the last one.
The test is six months later
Anyone can hand over a tidy component library. The question is whether it is still being used the way it was handed over once the people who built it have moved on, and once a requirement arrives that nobody anticipated.

Six months on, the design system is still being used as it was handed over. That is the part I did not expect.
What survives and what does not
- Tokens survive. They are small, they are named, and they are hard to misuse.
- Components survive when they do one thing and take their variations as props.
- Documentation survives only where it sits beside the thing it describes.
- Rules nobody wrote down do not survive at all.

Build the small pieces well, write the reasoning next to them, and resist the urge to systematise something that has only happened once. The third occurrence is when a pattern is real.




