Architects, gardeners, and design systems

I compared design systems to dictionaries. My point was that design systems—like language—can be approached in a prescriptivist or descriptivist manner. And I favour descriptivism.

A prescriptive approach might give you a beautiful design system, but if it doesn’t reflect the actual product, it’s fiction. A descriptive approach might give a design system with imperfections and annoying flaws, but at least it will be accurate.

I think it’s more important for a design system to be accurate than beautiful.

Meanwhile, over on Frank’s website, he’s been documenting the process of its (re)design. He made an interesting comparison in his post Redesign: Gardening vs. Architecture. He talks about two styles of writing:

In interviews, Martin has compared himself to a gardener—forgoing detailed outlines and overly planned plot points to favor ideas and opportunities that spring up in the writing process. You see what grows as you write, then tend to it, nurture it. Each tendrilly digression may turn into the next big branch of your story. This feels right: good things grow, and an important quality of growth is that the significant moments are often unanticipated.

On the other side of writing is who I’ll call “the architect”—one who writes detailed outlines for plots and believes in the necessity of overt structure. It puts stock in planning and foresight. Architectural writing favors divisions and subdivisions, then subdivisions of the subdivisions. It depends on people’s ability to move forward by breaking big things down into smaller things with increasing detail.

It’s not just me, right? It all sounds very design systemsy, doesn’t it?

This is a false dichotomy, of course, but everyone favors one mode of working over the other. It’s a matter of personality, from what I can tell.

Replace “personality” with “company culture” and I think you’ve got an interesting analysis of the two different approaches to design systems. Descriptivist gardening and prescriptivist architecture.

Frank also says something that I think resonates with the evergreen debate about whether design systems stifle creativity:

It can be hard to stay interested if it feels like you’re painting by numbers, even if they are your own numbers.

I think Frank’s comparison—gardeners and architects—also speaks to something bigger than design systems…

I gave a talk last year called Building. You can watch it, listen to it, or read the transcript if you like. The talk is about language (sort of). There’s nothing about prescriptivism or descriptivism in there, but there’s lots about metaphors. I dive into the metaphors we use to describe our work and ourselves: builders, engineers, and architects.

It’s rare to find job titles like software gardener, or information librarian (even though they would be just as valid as other terms we’ve made up like software engineer or information architect). Outside of the context of open source projects, we don’t talk much about maintenance. We’re much more likely to talk about making.

Back in 2015, Debbie Chachra wrote a piece in the Atlantic Monthly called Why I Am Not a Maker:

When tech culture only celebrates creation, it risks ignoring those who teach, criticize, and take care of others.

Anyone who’s spent any time working on design systems can tell you there’s no shortage of enthusiasm for architecture and making—“let’s build a library of components!”

There’s less enthusiasm for gardening, care, communication and maintenance. But that’s where the really important work happens.

In her article, Debbie cites Ethan’s touchstone:

In her book The Real World of Technology, the metallurgist Ursula Franklin contrasts prescriptive technologies, where many individuals produce components of the whole (think about Adam Smith’s pin factory), with holistic technologies, where the creator controls and understands the process from start to finish.

(Emphasis mine.)

In that light, design systems take their place in a long history of dehumanising approaches to manufacturing like Taylorism. The priorities of “scientific management” are the same as those of design systems—increasing efficiency and enforcing consistency.

Humans aren’t always great at efficiency and consistency, but machines are. Automation increases efficiency and consistency, sacrificing messy humanity along the way:

Machine with the strength of a hundred men
Can’t feed and clothe my children.

Historically, we’ve seen automation in terms of physical labour—dock workers, factory workers, truck drivers. As far as I know, none of those workers participated in the creation of their mechanical successors. But when it comes to our work on the web, we’re positively eager to create the systems to make us redundant.

The usual response to this is the one given to other examples of automation: you’ll be free to spend your time in a more meaningful way. With a design system in place, you’ll be freed from the drudgery of manual labour. Instead, you can spend your time doing more important work …like maintaining the design system.

You’ve heard the joke about the factory of the future, right? The factory of the future will have just two living things in it: one worker and one dog. The worker is there to feed the dog. The dog is there to bite the worker if he touches anything.

Good joke.

Everybody laugh.

Roll on snare drum.

Curtains.

Have you published a response to this? :

Responses

Ethan Marcotte

i’d been working on this blog entry for weeks and……………you just blurted it out

Sameera

Enjoyed this so much. I’ve been thinking a lot about adoption and maintenance in a system I’m working on now, as well as I talk I’m planning. Really enjoyed reading your thoughts.

# Posted by Sameera on Wednesday, January 29th, 2020 at 5:10pm

Jordan Moore

This is great Jeremy. You’ve found words for things I’ve struggled to put into words and found new pathways of thinking that I hadn’t thought about before. The last paragraph in particular resonates with some incomplete thoughts I had scribbled down earlier this week:

Nick Dunn

So much nodding. (Random aside, this too https://t.co/U1VqkSxSNh)

# Posted by Nick Dunn on Thursday, January 30th, 2020 at 6:50am

Petch

“With a design system in place, you’ll be freed from the drudgery of manual labour. Instead, you can spend your time doing more important work …like maintaining the design system.” adactio.com/journal/16369

# Posted by Petch on Friday, January 31st, 2020 at 3:57am

ruymanfm

“The factory of the future will have just 2 living things in it: one worker and one dog. The worker is there to feed the dog. The dog is there to bite the worker if he touches anything.” Interesante post de @adactio: Architects, gardeners & Design Systems adactio.com/journal/16369

# Posted by ruymanfm on Tuesday, February 4th, 2020 at 11:39am

Mark Rickerby

“The factory of the future will have just two living things in it: one worker and one dog. The worker is there to feed the dog. The dog is there to bite the worker if he touches anything.“ adactio.com/journal/16369

10 Shares

# Shared by Shaun Rashid on Wednesday, January 29th, 2020 at 4:55pm

# Shared by Chris on Wednesday, January 29th, 2020 at 5:15pm

# Shared by Dave Rupert on Wednesday, January 29th, 2020 at 5:33pm

# Shared by James Madson on Wednesday, January 29th, 2020 at 5:58pm

# Shared by Rogier Barendregt on Wednesday, January 29th, 2020 at 6:00pm

# Shared by Javier Gala on Wednesday, January 29th, 2020 at 6:46pm

# Shared by James Nash on Wednesday, January 29th, 2020 at 6:52pm

# Shared by UX London on Wednesday, January 29th, 2020 at 7:29pm

# Shared by Harvey Ramer on Thursday, January 30th, 2020 at 3:23am

# Shared by Carlos Salgado on Thursday, January 30th, 2020 at 7:17am

50 Likes

# Liked by Kyle Halleman on Wednesday, January 29th, 2020 at 5:13pm

# Liked by Catherine Kim on Wednesday, January 29th, 2020 at 5:14pm

# Liked by Simon Collison on Wednesday, January 29th, 2020 at 5:14pm

# Liked by Jordan Moore on Wednesday, January 29th, 2020 at 5:14pm

# Liked by Damon-Elliott on Wednesday, January 29th, 2020 at 5:14pm

# Liked by Volker E. on Wednesday, January 29th, 2020 at 5:14pm

# Liked by Andy Hart on Wednesday, January 29th, 2020 at 5:15pm

# Liked by Ryan Swaney on Wednesday, January 29th, 2020 at 5:15pm

# Liked by Dave Rupert on Wednesday, January 29th, 2020 at 5:15pm

# Liked by Amber on Wednesday, January 29th, 2020 at 5:16pm

# Liked by Mat Johnson on Wednesday, January 29th, 2020 at 5:16pm

# Liked by Mark Boulton on Wednesday, January 29th, 2020 at 5:16pm

# Liked by ʀʏᴀɴ ᴡᴇᴀᴠᴇʀ on Wednesday, January 29th, 2020 at 5:43pm

# Liked by Matthias Ott on Wednesday, January 29th, 2020 at 5:43pm

# Liked by Blitter Object on Wednesday, January 29th, 2020 at 5:43pm

# Liked by Chris on Wednesday, January 29th, 2020 at 5:44pm

# Liked by rik koster on Wednesday, January 29th, 2020 at 6:13pm

# Liked by Zoran Gavric on Wednesday, January 29th, 2020 at 6:14pm

# Liked by Rogier Barendregt on Wednesday, January 29th, 2020 at 6:14pm

# Liked by New Adventures on Wednesday, January 29th, 2020 at 6:14pm

# Liked by Andrea Vaghi on Wednesday, January 29th, 2020 at 6:14pm

# Liked by Malxico on Wednesday, January 29th, 2020 at 6:15pm

# Liked by James Madson on Wednesday, January 29th, 2020 at 6:15pm

# Liked by Jonathan Dallas on Wednesday, January 29th, 2020 at 6:40pm

# Liked by Alejandro Velazquez on Wednesday, January 29th, 2020 at 6:41pm

# Liked by Adam Duncan on Wednesday, January 29th, 2020 at 6:41pm

# Liked by Clearleft on Wednesday, January 29th, 2020 at 7:13pm

# Liked by Chris Coyier on Wednesday, January 29th, 2020 at 7:14pm

# Liked by Javier Gala on Wednesday, January 29th, 2020 at 7:14pm

# Liked by paul swagerman on Wednesday, January 29th, 2020 at 7:53pm

# Liked by Rab Fyfe 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺 on Wednesday, January 29th, 2020 at 7:53pm

# Liked by Kolombiken on Wednesday, January 29th, 2020 at 7:54pm

# Liked by „Dagegen heißt immer auch Dabei“. on Wednesday, January 29th, 2020 at 8:23pm

# Liked by Dylan on Wednesday, January 29th, 2020 at 8:59pm

# Liked by Jens Tangermann on Wednesday, January 29th, 2020 at 9:00pm

# Liked by vollepeer on Wednesday, January 29th, 2020 at 11:08pm

# Liked by Antoine Renault on Wednesday, January 29th, 2020 at 11:39pm

# Liked by Philip Renich on Thursday, January 30th, 2020 at 2:09am

# Liked by Marcos Peebles on Thursday, January 30th, 2020 at 3:34am

# Liked by Harvey Ramer on Thursday, January 30th, 2020 at 3:35am

# Liked by Jason Hale on Thursday, January 30th, 2020 at 4:05am

# Liked by PKGreenHouse on Thursday, January 30th, 2020 at 6:47am

# Liked by Carlos Salgado on Thursday, January 30th, 2020 at 7:26am

# Liked by Siegfried Ehret on Thursday, January 30th, 2020 at 7:26am

# Liked by JP Santos on Thursday, January 30th, 2020 at 7:26am

# Liked by Paulo Elias on Thursday, January 30th, 2020 at 1:17pm

# Liked by Brad Frost on Friday, January 31st, 2020 at 1:01am

# Liked by mackdaknife on Friday, January 31st, 2020 at 4:50pm

# Liked by Levi McGranahan on Friday, January 31st, 2020 at 6:17pm

# Liked by Harvey Ramer on Tuesday, February 4th, 2020 at 3:00am

Previously on this day

2 years ago I wrote GDPR and Google Analytics

Do you have permission for those third-party scripts?

8 years ago I wrote Eighteen

Pausing to give thanks.

9 years ago I wrote A dark star is born

We are dark stardust, we are golden, we are puppets.

11 years ago I wrote Creative Commons Q&A

15 questions on Creative Commons.

12 years ago I wrote Outbound

I’m off to San Francisco. Again.

12 years ago I wrote Regional

You can’t play that here.

15 years ago I wrote Best. News story. Ever.

In his seminal 1946 essay, Politics and the English Language, George Orwell outlined some simple guidelines for writing. These include:

16 years ago I wrote Just plain wrong

Seeing windows apps running on OS X kind of freaks me out but not nearly as much as seeing what this guy did to a G5:

16 years ago I wrote Airport

An iChat transcript with my friend Diarmaid who I am supposed to be meeting in Dublin right about now:

18 years ago I wrote Please don't let me be misunderstood

There’s a magazine called "Cre@teOnline" which bills itself as "The Web Designer’s Bible".