Gumshoe · Method reference

Atomic design

Build interfaces from small, composable parts that combine into larger structures.

Conceptual illustration of atomic design.
Effort
High
Participants
Not required
Remote friendly
Yes
Evidence / output
Expert review

What it is

A methodology, coined by Brad Frost, that organizes interface components into a hierarchy of atoms, molecules, organisms, templates, and pages, so UIs are built from reusable, composable parts.

When to use it

During Prototype and Implement, when structuring a design system or component architecture.

Why (value)

Gives a shared mental model and vocabulary for composing interfaces from small, reusable pieces, improving consistency and reuse.

How to run it

  1. Identify the smallest UI elements (atoms).
  2. Combine atoms into functional groups (molecules).
  3. Assemble molecules into sections (organisms).
  4. Arrange organisms into templates.
  5. Fill templates with real content as pages.

Inputs and outputs

  • Inputs: UI requirements and existing component patterns.
  • Outputs: A hierarchical component system and shared vocabulary.

Time and effort

High. A substantial structural investment.

Evidence and limitations

Atomic design is an expert-review organizing framework for construction, not evidence of usability; a well-structured system can still be hard to use. See Evidence and limitations.

Tips and pitfalls

  • Do not over-engineer the taxonomy.
  • Keep naming pragmatic for the team.
  • Pair structure with usability validation.

Variations

Strict atomic hierarchy and pragmatic adaptations by team.

Need help choosing and applying a method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Explore related methods

  • Design system work — Build and maintain the shared components, tokens, and guidelines a product is made from.
  • Design pattern library — Document reusable solutions to recurring design problems so teams solve them once.
  • UI inventory — Collect every variant of each interface component to see the real scope of your UI.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.