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
- Identify the smallest UI elements (atoms).
- Combine atoms into functional groups (molecules).
- Assemble molecules into sections (organisms).
- Arrange organisms into templates.
- 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.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
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.
