Systems
Jul 2026
8 min
A design system that people actually use
Four rules from building one for 40 engineers.

Words by
Mara Voss

Start with what already exists
The system I built for a team of 40 engineers began as an audit, not a library. We printed every button in the product. There were 31 of them.
Four rules
Tokens before components. Colour, type and spacing first, so everything else has something to stand on.
Only what is used twice. A component joins the system when two teams need it, not before.
Names a developer can guess. If you have to look a token up, it has the wrong name.
One owner. Someone answers for the system every week, or nobody does.
A design system is a product. Its users are your own team.
What it took
Six months, one designer and one engineer part-time. The button count went from 31 to four, and new screens now take days instead of weeks.
Call sheet · Open
Need this for your product?
I design and build digital products end to end — from the first sketch to production code. Tell me what you’re making.
FRAME 10 — Contact
Have a project? Let’s shoot.
Tell me what you are making. I reply within a day with next steps and a rough plan.
Prod.
Portfolio 2026
Scene
Footer
Take
1
Roll
A-09
Director
Mara Voss
Date
27.10.26
Build
main · 9f3c1a
That’s a wrap.
Thanks for watching to the end. Say hello, I read every message and reply within a day.
Write to me
Work