The concepts behind atomic design have revolutionized how we think about design systems. 8 years after Brad Frost discovered atomic design, we at R/GA still leverage it on countless projects. But how did it all start? Where did atomic design come from? How did it find Brad Frost?
As part of his work at Zeroheight, contributing UX Booth writer Luke Murphy has been talking to teams across the world about what makes good documentation sites, from small 2-3 designer companies through to large enterprises corporations. The common thread across the successful design systems is that the team managing the design system are treating their system as if it’s a product, complete with KPIs and ways to measure, a full product design process and enough resource to achieve their goals. Unfortunately, this doesn’t mean that anyone can provide a standard template for how to build an effective Design System, as the problems, needs and measures of success for any single design system will be different. However, there are some standard processes and common wins that can help.
If you’re on the job market in the UX design field, chances are you will be asked about design systems in your next interview. Don’t make the mistake of thinking a design system is just a UI kit and forgo preparing for this popular interview topic. The next time a hiring manager asks you about design systems, you will be able to intelligently respond. If you follow these steps, you will no longer lack hands-on design system experience. You can be the rare bird that goes above and beyond and land your dream job.
The Zendesk design team had a growing library of patterns and as I started to wonder about canonizing those as working bits of code, I knew we could be on to something: a system that could be used by developers to achieve intended designs with pixel perfection. We didn’t arrive here in one go. Growing Garden happened as a series of fits and starts, and I learned a thing or two along the way.
The Zendesk design team had a growing library of patterns and as I started to wonder about canonizing those as working bits of code, I knew we could be on to something: a system that could be used by developers to achieve intended designs with pixel perfection. We didn’t arrive here in one go. Growing Garden happened as a series of fits and starts, and I learned a thing or two along the way.
Design systems are all the rage (and also really useful). But are they useful for all organizations and teams? This week, UX Booth Senior Editor Kristina Bjoran invites readers to chime in.