Most design-system advice assumes a platform team of twelve. My clients have two people and a deadline. Here's the stripped-down system I install on every project — enough structure to stay consistent, light enough to survive contact with real work.
1. Tokens before components
Colors, spacing, type scale and radii live in one tokens file. When the brand evolves, one edit propagates everywhere. I start every engagement by agreeing these four lists with the client — it takes an afternoon and prevents a hundred future arguments.
2. Ten components cover 90% of pages
Buttons, inputs, cards, modals, nav, footer, badges, tabs, tables, alerts. Build these ten well — with hover, focus, disabled and error states — and whole pages assemble themselves. Everything exotic gets designed on demand, then folded back in if it repeats.
3. Document with examples, not essays
Each component gets a one-line purpose note, a do/don't pair of screenshots, and a link to where it's used live. Nobody reads a forty-page spec; everybody copies a good example.
The payoff compounds: the second project with the same client starts at week three instead of week one. That's how small teams ship like ten — they stop redesigning buttons and start solving customer problems.