Login to course

Hey there, design reader!

Guess who’s back, back again? Me! Reminiscing on week seven of my UX Academy Journey as a student in Designlab’s UX Academy, Weingart cohort (and apologizing for the Eminem reference). This week, it’s all about the atomic mic drop.

If you’ve been following this series so far, it’s no secret that I’m exceptionally bad at making judgements about how long to spend on my homework. I’m even worse at knowing when to call time on a project—once I get moving and in a groove of sorts I zone in, unmoving, for hours on end, tinkering with minor details and finessing minutiae.

This is exactly the kind of bad habit a UX designer would be wise not to cultivate—a kind of tunnel vision that has kept me from being able to zoom out far enough to see where each lesson, project and technique in the UX Academy curriculum actually fits in with the larger whole, the puzzle of UX design in practice.

And then the curriculum dropped a very timely “aha bomb” on me.

Atomic Design Methodology, or the thing that finally blew my UX design mind

Enter Atomic Design Methodology, the simple little lesson that finally broke my brain and put it back together again (with some new and improved synapses). Suddenly, the scope of UX knowledge didn’t feel quite so infinite and instead turned into something digestible, attainable, and the beginnings of familiar.

Mind. Blown.

Mind. Blown.

Atomic design, created by Brad Frost, is a design systems methodology that breaks down those systems into five distinct parts—atoms, molecules, organisms, templates and pages. These five components double as the five phases of atomic design, working both individually and together in the service of the whole: “to create interface design systems in a more deliberate and hierarchical manner.”

Atomic Design Methodology

The atomic design methodology allows designers to visualize whole design systems at once, from the abstract to the concrete. Image credit: Brad Frost

Translation: atomic design addresses the biggest retraining hurdle many students face (myself most definitely included) when presented with a vast design landscape of seemingly infinite horizons—that the design process itself is not a linear one.

A little bit of UX chemistry

Most people, in their professional work, are used to a certain amount of process. First comes A, then B and only then, C. The creative world is known for being a little more fluid—unless of course we’re talking about Apple, which has a unique beast of a development process all its own. UX design is somewhere in the middle, the convergence of science and invention.

In my professional and educational pasts I have always tiptoed the line between right- and left-brained tendencies. It’s hard for me to see both the forest and the trees, and to use this composite perspective to strategize the best way forward. I become overwhelmed with options, with details, with small pieces, and lose sight of the whole for the sake of that one little, tiny part that’s captured my focus in that moment.

Atomic design, however, encourages designers to simultaneously think of the design system as a collection of individual parts, and as a larger, cohesive whole that those parts combine to create.

Brad Frost on atomic design at Webdagene 2014—I’m totally with it (except for his feelings about books, which I vehemently disagree with always and forever

Kaboom! Drops mic. Walks off stage.

Just like a good story, design is more than the sum of its parts. It’s also a product of their organization, tone and the way they are executed both individually and in combination. It’s why comics run the same bits over and over again, night after night; they are refining all of the story’s component parts in pursuit of the best possible whole—one perfectly executed joke.

And it takes trying that joke a bunch of different ways to get there—exercising and iterating on all of the parts at once—to create a fully polished, well written and well designed finished product.

It’s also why the best TV shows and movies today are written by not just one author, but by teams of writers and editors, constantly building upon each other’s work, iterating new drafts, making stronger choices, creating more memorable scenes with every revision.

Seven years ago, in my early twenties and filled with fanciful ideas of a writerly life in New York, I picked up and moved myself and my cat crosscountry to the beautiful sprawling midlands of Brooklyn. The next day I started classes at the Upright Citizens Brigade Theatre, the comedy school founded by Matt Walsh, Ian Roberts and Matt Besser, and one of my lady comedian loves, Amy Poehler. I see now that comedy shares a lot of the same lessons—the major tenets of storytelling are born of the same creative philosophy.

When you’re writing a script, or better yet, a comedic sketch, one of the first and most important lessons to remember is that every line must drive the scene forward. Any line that doesn’t drive the scene forward may as well not be there at all (and the fact that it is there almost certainly guarantees that you’ve already shot the whole darn thing in the foot).

Kaus wireframe sketches

My initial KAUS wireframe sketches, templates made up of a combination of preliminary particles

A story is made up of acts (organisms). These acts, in turn, are made up of a series of scenes strung together (molecules), and these scenes are made up of a bunch of lines (atoms) all in a row. Each piece must stand on its own for it to best support and inform the other elements around it—each atom is a part of greater molecule, teaming up with other molecules to make organisms greater still.

These seemingly independent design organisms are weaved together to make cohesive, elegant templates that are then further enriched by the inclusion of unique content. The result is a complete final page—a fully responsive design system.

I truly don’t know how I didn’t see it before.

A Game of UX Design Tetris

Atoms > Molecules > Organisms > Templates > Pages

In the past when approaching a new design project I have spent a fair amount of time off the top on trying to pare down my research and organize my thoughts, all before the actual design process even begins. This existing process has resulted in many labored hours in front of my computer, struggling to make sense of the smattering of design elements I’ve scattered about my artboard without any seeming rhyme or reason.

Remember the ugly, cluttered landing page I showed you in week three? Well we’ve come quite a long way since then!

Using the atomic design methodology, I was able to approach the KAUS landing page with one eye on the finessing of the elemental design patterns themselves—the navigation, the call to action button, the “Build A Quote” tool, the “How It Works” animation—and the other eye watching how the collection of these elements all fit together into a polished page, like some sort of magical design Tetris. It took zooming out far enough from the design itself to really see the big picture—the larger design principles at play, free of all the distracting details.

The truth is that UX design is made up of simultaneous micro- and macro-decisions—choices about both individual pieces and the greater whole. Sometimes it takes looking at this system from a distance to really see whether everything is working in harmony.

The result is a more flexible, more responsive, more iterable design system that lends itself to additions and evolutions still to come.

KAUS Wireframe

My first KAUS wireframe, a collection of iterated parts

Looking for some further atomic design reading? Check out these resources:

Until next time, happy atomic designing!

Looking for a change of careers? Designlab’s UX Academy program offers rigorous curriculum, personalized mentor support, and a thriving, global student community. Ready to launch your new career as a UX designer? Get all the details here.

author avatar

Thea Chard

Enjoyed this article? Try another!

More from the Designlab Blog

Go to blog homepage