UX glossary · engl. Atomic Design
Atomic Design
Atomic Design is a method for building user interfaces from small, reusable building blocks, from single elements like buttons all the way up to complete pages.
Imagine an online shop that has grown over a few years. By now it has eleven different buttons, three versions of the search field and two kinds of product cards. Nobody knows which one is the right one anymore, and every new page gets designed almost from scratch.
Atomic Design is a way out of exactly this mess.
Explained simply
Atomic Design is a method for building user interfaces from small, reusable building blocks. Think of a box of Lego bricks: you can build a house, a car or a spaceship. The bricks stay the same. Only the way you combine them changes.
The method comes from the American web designer Brad Frost. He presented the idea during a website project in 2013 and described it in detail in his 2016 book “Atomic Design”, which you can read online for free. The name is borrowed from chemistry: atoms combine into molecules, and molecules into larger organisms. Just as all matter can be traced back to a limited set of elements, an interface can be traced back to a limited set of basic building blocks.
The five stages
- Atoms: the smallest elements, such as a label, an input field or a button. Break them down further and they lose their purpose.
- Molecules: simple groups of atoms that do one job together, for example a search form made of a label, an input field and a button.
- Organisms: larger sections built from several molecules, like a website header with logo, navigation and search.
- Templates: page layouts that arrange organisms and show the structure of a page, much like a wireframe.
- Pages: templates filled with real content. This is where you see whether the system holds up with long names, missing images or lots of entries.
One important point: Frost describes Atomic Design, in essence, not as a process you work through step by step but as a mental model. You look at an interface as a whole and as a collection of parts at the same time. You can read more in What Is Atomic Design?.
An example
Back to the online shop. Before, the team designs every category page on its own. When the button color changes, someone has to go through twenty screens and still misses a few.
After, there is a single button as an atom. The product card is a molecule made of image, title, price and that button. The product grid is an organism made of many cards. A change to the button shows up everywhere, and new pages come together faster because the team combines existing blocks instead of starting over.
Common misconceptions
Atomic Design isn’t the same thing as a design system. A design system includes components but also rules, tone of voice and documentation. Atomic Design is one way to organize the components inside it. You also don’t have to adopt the chemistry terms. What matters is the idea of thinking from small to large.
In practice
- Start with an inventory. Collect screenshots of every button, form field and card. Duplicate variants jump out right away.
- Test components with real content. A card that looks great with placeholder text can fall apart with a long product name.
- Start small. A few well maintained components do more than a huge library nobody uses. Design Systems for Small Teams: When They Pay Off and How to Start Small shows how.
Related terms
Design System, Wireframe, Prototype, Gestalt Principles