Design systems that survive a small team
Most design systems collapse under their own governance. For teams under twenty people, fewer rules and stricter tokens work better.
Priya Gurung
CT Tech Nepal
Design systems fail in two directions. They either become so minimal that every new screen reinvents a button, or so elaborate that maintaining the system becomes a full-time job nobody was hired for. Small teams need the narrow path between those.
What has worked for us is a token-first system with a deliberately small component set. Colours, spacing, typography, radii, and motion durations are defined once and consumed everywhere. Components cover the fifteen patterns that appear in almost every product: button, input, select, checkbox, radio, card, modal, drawer, table, tabs, badge, tooltip, toast, avatar, and empty state. Anything beyond that gets built in the product, not the system.
The governance rule matters more than the component count. We use a simple test: if a component is used in fewer than three places, it does not belong in the system yet. That keeps the surface small and forces the system to prove itself through usage rather than speculation.
Accessibility belongs in the tokens, not in a checklist at the end. Contrast-safe text colours, a minimum touch target size, and a visible focus ring should be impossible to get wrong because the defaults are correct.
Key takeaways
- Tokens before components
- Fifteen components covers most product surfaces
- Only promote a pattern to the system after three real uses
- Bake accessibility into defaults rather than auditing later