"We should build a design system" is one of the most expensive sentences a small team can say out loud.
It sounds responsible. Big companies have them. Every conference talk about consistency ends with one. But a design system as usually pictured β a documented component library with tokens, variants, a Storybook, a versioning policy and a team to maintain it β is infrastructure. Infrastructure has a cost, and for a three-person startup shipping its first product, that cost often arrives long before the benefit.
What the team actually wants is smaller: screens that look like they belong together, and fewer arguments about padding. You can get most of that with ten decisions written down on one page.
What a design system is really for
Strip the ceremony away and a design system does three things:
It removes repeated decisions. Nobody re-picks the button radius every time they build a form.
It makes inconsistency visible.β¦