Atomic design: structuring interface components as a product evolves

Perforated concrete blocks forming a grid of squares.

Atomic design helps an interface evolve without redesigning everything for every new page. It organises reusable elements: buttons, fields, cards, content blocks and templates. When a page changes, the team knows what to reuse, what to adapt and what to maintain.

Think of the interface as something that can change

An interface rarely stays still. An offering becomes clearer, a journey gets shorter, a feature appears, a team shifts its priorities. Without a structure, adjustments pile up: a slightly different button, a card tailored to one page, a typography rule forgotten in a file, mobile behaviour addressed too late.

Atomic design offers a practical response. It breaks the interface into components that are simple enough to understand, complete enough to reuse and documented enough to change without surprises. A form field, for example, is not just a border and text. It includes its states, label, helper text, error message, keyboard behaviour and mobile version.

The vocabulary popularised by Brad Frost, atoms, molecules, organisms, templates and pages, can act as a guide. It should not become doctrine. Some teams will be more comfortable with “foundations”, “components”, “sections” and “pages”. The goal is not to classify every element perfectly. It is to make dependencies visible and to reuse the same decisions.

Atomic design, design system and brand system: three distinct roles

These ideas complement each other, but they do not mean the same thing.

  • Atomic design structures the way an interface is composed. It helps decide what becomes a component, what belongs in a variant and what remains specific to a context.
  • The design system brings together components, rules, documentation, accessibility principles, usage guidelines and governance. It can draw on atomic design, but does not have to.
  • The brand system frames how the brand is expressed: tone of voice, visual identity, hierarchy, motion, iconography, editorial rules and adaptation across channels. It guides the interface, but goes beyond it.

In practice, the brand system answers: “How is the brand recognised and how does it adapt?” The design system answers: “How does the team design and deliver consistently?” Atomic design answers: “How do interface building blocks fit together without multiplying unnecessarily?” To explore the relationship between the first two levels, read our article on the brand system and the design system.

Put the method to work for the product

Do not start with an empty component library. First, look at the screens and journeys that matter. Where do the same patterns recur? Which elements actually change with context? Which decisions are creating inconsistencies or slowing development today?

Step Decision to make Useful deliverable
1. Audit Identify recurring patterns and duplicates. Screen audit and component list.
2. Define foundations Set rules for colour, typography, spacing, grid and states. Documented tokens or baseline rules.
3. Compose Group elements that serve a clear use case. Components with limited variants.
4. Test in journeys Check that components support real cases, including on mobile. Reference screens and usage feedback.
5. Evolve Clarify who decides, documents and deprecates. Simple contribution rules.

This progression avoids two pitfalls: creating an abstract catalogue that answers no need, or allowing every page to become an exception. A card does not necessarily deserve to become a standalone component when it first appears. But when the same need returns across several journeys, it is better to formalise it than to improvise each time.

Decisions and risks to own

A set of components does not remove choices. It makes them explicit. Before creating a variant, ask whether it answers a lasting need or a one-off circumstance. Before adding a colour or spacing value, check whether the existing rule is truly insufficient. This discipline keeps the system readable.

  • Risk of over-componentisation: breaking things down too far creates assemblies that are hard to understand. Keep components focused on an identifiable use case.
  • Risk of infinite variants: every added option increases the cost of testing, documentation and maintenance. Prefer intentional choices to universal properties.
  • Risk of a design-development gap: a component designed without behavioural rules is not enough. Define its states and constraints with the people who will build it.
  • Risk of late accessibility work: contrast, focus, error messages and keyboard navigation must be part of the component from the outset. Find the essential guidance in our article on accessibility and the design system.

SourceHub: a structure built to move

At SourceHub, the product evolved every week. Fauves developed the identity and interface with the project and development teams, rather than treating the brand as a layer added afterwards. The mock-ups, wording and micro-interactions were aligned with the product’s mission and technical constraints.

This way of working called for a modular, adaptable brand. The components did not only save production time: they provided a shared framework for change while giving the product the flexibility it needed. Discover the SourceHub project.

Resources

Evolve without losing the thread

A good set of rules does not prevent change. It helps teams make changes without losing consistency, speed or the purpose behind decisions. If your interface is growing faster than its rules, let’s talk about the structure to build.