Engineering manager Michael Lopp is the author one of my favorite articles: “Stables and Volatiles.” I’ve referenced this article constantly over the last 10 years since he wrote it.
In the article, Michael talks about what happens shortly after teams get to a v1 of a piece of software. (His writing references engineers specifically, but I find that this applies equally well to designers.) He describes two groups that emerge strongly after the birth of an official 1.0: one called “Stables” and the other called “Volatiles.” Here’s the full set of characteristics for both each:
Admittedly an overgeneralization, but, looking at the characteristics, which one of these groups seems to fit better the needs of a design system team? At first glance: Stables. The simplest value proposition of a design system is to create efficiency and consistency in user interface design and establish shared process and vocabulary… all words that make a Stable smile.
So, here’s a basic guideline for starters: if you’re a Stable, you’ll probably enjoy and thrive in design system work. If you’re a Volatile, design system work might be a little boring for you.
But wait: there’s more!
If Volatiles should steer clear of design system teams, where should they be working on instead? On product design teams! That’s where they’re free to innovate and invent new things. The virtuous cycle of digital organizations is where design systems and the product design process have a symbiotic relationship. Ideally, Volatiles invent new things in the product, and, as those things become more common, Stables can systematize them and make them more “boring.”
Somewhere along the way, though, the idea that, once you have a design system, everything you make will both come from it and be contributed to it became popularized (probably evangelized by well-intentioned Stables). This is an overreach of a Stable’s mentality. Setting a goal that, one day, every interface will be made wholly from the design system is a death sentence for Volatiles. It leaves no place for them and their skills of invention and innovation at all, certainly not on design system teams but also not even on product teams. It’s not inclusive, and it’s a terrible business strategy. This kind of mentality leads to a very efficient product design process that has no innovation included whatsoever. The trajectory goes from efficiency to stagnation to atrophy to decline.
How do you stop this? Figure out how to establish an equilibrium in your product design ecosystem between the diametrically opposed Stables and Volatiles. This won’t be an easy feat. From Michael’s article:
Lastly and most importantly, these groups hate — hate — each other. Volatiles believe Stables are fat, lazy, and bureaucratic. They believe Stables have become “The Man.” Meanwhile, Stables believe Volatiles hold nothing sacred and do whatever they please, company or product be damned. The bad news is that everyone is right.
But it’s a worthwhile effort. If you’re a Stable, decide what your design system won’t try to wrangle, and encourage your Volatile counterparts to go wild in these areas. If you’re a Volatile, decide the small number of areas where you want to spend time, and accept help from your Stable counterparts in doing the rest as quickly as possible.
The closing thought from Michael’s article:
I believe a healthy company that wants to continue to grow and invent needs to equally invest in both their Stables and their Volatiles.
In any thriving virtuous cycle of product design, some people can work on the settled solutions while others can venture out, seeking the new. Make sure you’re investing in both.
In the next article, I’ll share some specific targets on how to do just that.
Join 57,400+ subscribers to the weekly Dan Mall Teaches newsletter. I promise to keep my communication light and valuable!