log 01
Design Systems Are Not a Product
There’s a trap that design teams fall into, and it usually starts with good intentions.
Someone, maybe you, maybe a well-meaning design lead, decides that the component library deserves its own roadmap. Its own backlog. Its own OKRs. A Notion page with versioning. A Slack channel. A demo day slot.
And just like that, the design system becomes a product.
This isn’t inherently wrong. At a certain scale, it’s necessary. But for most teams, treating the system as a product creates a subtle and corrosive inversion: the system starts serving itself instead of the people building with it.
I’ve seen this play out in enterprise orgs more times than I can count. A team spends a quarter perfecting a token architecture that no one asked for. A button component ships with seventeen documented variants before a single real screen uses more than three. A “contribution model” gets workshopped in Figma before a single engineer has tried to contribute.
The system becomes the work. The work becomes the system.
The better mental model, one I keep coming back to, is the design system as infrastructure. Roads don’t get feature roadmaps. A well-paved road just gets out of the way and lets you go where you’re going fast.
That reframe changes what you prioritize. Instead of asking what should we build next, you ask what’s slowing people down. Instead of shipping new components, you’re removing friction. Instead of documentation for its own sake, you’re making the right path the obvious one.
The tokens should feel invisible. The components should feel obvious. The whole thing should hum quietly in the background while actual product work happens on top of it.
This doesn’t mean design systems are unimportant, quite the opposite. Infrastructure matters enormously. But its value is measured in what it enables, not what it contains.
If your team is proud of the system and struggling to ship, the system might be working against you. If your team barely thinks about the system and ships clean, consistent work, that’s the goal.
The best design system you’ll ever use is the one you forget about.