Design Systems
Component libraries engineers actually reach for, because engineers wrote them.
- Build iterations
- Foundations, then components
- Deliverables
Most design systems fail the same way: they are a picture of a system, not a system. Nobody imports a swatch page.
What ships
- Tokens for colour, type, spacing, and motion, consumable by code.
- Components with states, keyboard behaviour, and ARIA already handled.
- Documentation covering when to use something, and when not to.
The test
A system is working when engineers reach for it without being asked. That is the bar — not coverage, not component count. Everything here is built to be the path of least resistance.
Design Systems: common questions
Is this Figma or code?
Both, generated from one source of truth. A token changes in one place and moves through design and production together.
What is it worth to us?
Shipping speed and consistency. A new feature starts most of the way designed, and the slow drift that makes a product feel unmaintained stops.
Can you work with our existing system?
Often the better option. Auditing and repairing what exists usually beats replacing it.