Design systems: why small teams need one too

When people hear "design system", many picture hundred-page documentation from large companies and conclude it isn't for them. But the core of a design system is simple: a set of repeated decisions made once and then reused everywhere.

Why it matters even for two people

Without a system, every new page means deciding again about color, spacing, button size and font. Those decisions take time and drift out of sync over time. With a lightweight system:

• Pages get built faster because the pieces are ready.
• The product looks consistent, even with several people working on it.
• Changing one decision (say, the primary color) applies across the whole product at once.

The minimum you need

To start, stick to these:

• Color tokens: a few meaningful colors (primary, text, background, border, error), not a 40-value palette.
• Spacing scale: one base number (4 or 8 pixels, say) and its multiples.
• Type scale: three to five text sizes with defined line heights.
• A few base components: button, form field, card.

That's enough for most small products.

Keep it in code, not just in the design file

If the tokens live only in Figma, they fall behind the code quickly. The best move is to define the same tokens as variables in code, so design and implementation feed from one source.

Let it grow with the product

A design system isn't a separate project that "finishes". Every time a new pattern repeats two or three times, add it to the system right then. Not sooner, not later.

In short: start small, keep it in code, and only add something once it has repeated.