A design system does not need to be large to be useful. For a small organisation, it can start with a type scale, a few colours and a small set of reusable components.
Start with what repeats
If every new landing page gets a slightly different button, every form uses different spacing, and the same details are discussed again, a system already exists. It is simply undocumented.
The GOV.UK Design System is built around reusing existing components and patterns. One of its community principles is to start with what already exists rather than solve the same problem again without a reason.
Shared values remove repeated micro-decisions
Colour, font size, spacing and line height can technically take almost unlimited values. A product rarely needs that much choice.
The U.S. Web Design System describes design tokens as a limited palette of values for things such as colour, spacing and typography. One purpose is to improve design efficiency and make communication between design and development less granular.
For a small team, that can mean one type scale, a small spacing scale, defined colours and clear hover, focus and disabled states.
Components should solve real needs
A component earns its place when it appears in more than one context and has a clear job. That might include buttons, input fields, cards, navigation, tables or product cards.
GOV.UK describes components as reusable parts of an interface and pairs them with guidance on when and how to use them. That guidance matters: a design system is not just a Figma file full of components.
Consistency is not the same as sameness
USWDS uses the phrase be consistent, not static. A design system should provide a stable starting point, not make every page identical.
A small system can grow step by step
A realistic start is to review the most-used screens, collect the core typography, colour and spacing values, standardise the components used most often, and add short guidance on when to use them. New variants should be reviewed before they become permanent.
Design and code should use the same language
Shared names for components, sizes and states make collaboration easier. Design tokens can also act as a bridge because both design and code can refer to the same limited set of values.
When do you not need a design system?
Not every project needs a full system. A short campaign page may be fine with a tidy style guide, while a small website may need only clear rules and a limited component set.
A design system becomes more valuable when something repeats over time: many pages, multiple products, several designers or developers, or continuous updates.
The goal is not more rules
A good design system should make work lighter and more predictable. For a small team, the best system is rarely the biggest one. It is the one people actually use.