Iâ€™d like to take you back in time, just over 100 years ago, at the beginning of World War One. Itâ€™s 1914. The United States would take another few years to join, but the European powers were already at war in the trenches, as you can see here.
What I want to draw your attention to is what theyâ€™re wearing, specifically what theyâ€™re wearing on their heads. This is the standard issue for soldiers at the beginning of World War One, a very fetching cloth cap. It looks great. Not very effective at stopping shrapnel from ripping through flesh and bone.
It wasnâ€™t long before these cloth caps were replaced with metal helmets; much sturdier, much more efficient at protection. This is the image we really associate with World War One; soldiers wearing metal helmets fighting in the trenches.
Now, an interesting thing happened after the introduction of these metal helmets. If you were to look at the records from the field hospitals, you would see that there was an increase in the number of patients being admitted with severe head injuries after the introduction of these metal helmets. That seems odd and the only conclusion that we could draw seems to be that cloth helmets are actually better than the metal helmets at stopping these kind of injuries. But that wouldnâ€™t be correct.
You can see the same kind of data today. Any state where they introduce motorcycle helmet laws saying itâ€™s mandatory to wear motorcycle helmets, you will see an increase in the number of emergency room admissions for severe head injuries for motorcyclists.
Now, in both cases, whatâ€™s missing is the complete data set because, yes, while in World War One there was an increase in the field hospital admissions for head injuries, there was a decrease in deaths. Just as today, if thereâ€™s an increase in emergency room admissions for severe head injuries because of motorcycle helmets, you will see a decrease in the number of people going to the morgue.
I kind of like these stories of analytics where thereâ€™s a little twist in the tale where the obvious solution turns out not to be the correct answer and our expectations are somewhat subverted. My favorite example of analytics on the web comes from a little company called YouTube. This is from a few years back.
Chris set about working on making a smaller version of a video page. He called this Project Feather. He worked and worked at it, and he managed to get a page down to just 98 kilobytes, so from 1.2 megabytes to 98 kilobytes. Thatâ€™s an order of magnitude difference.
Then he set up shipping this to different segments of the audience and watching the analytics to see what rolled in. He was hoping to see a huge increase in the number of people engaging with the content. But hereâ€™s what he blogged.
The average aggregate page latency under Feather had actually increased. I had decreased the total page weight and number of requests to a tenth of what they were previously and somehow the numbers were showing that it was taking longer for videos to load on Feather, and this could not be possible. Digging through the numbers more (and after browser testing repeatedly), nothing made sense.
I was just about to give up on the project with my world view completely shattered when my colleague discovered the answer: geography. When we plotted the data geographically and compared it to our total numbers (broken out by region), there was a disproportionate increase in traffic from places like Southeast Asia, South America, Africa, and even remote regions of Siberia.
A further investigation revealed that, in those places, the average page load time under Feather was over two minutes. That means that a regular video page (at over a megabyte) was taking over 20 minutes to load.
Again, what was happening here was that there was a whole new set of data. There were people who literally couldnâ€™t even load the page because it would take 20 minutes who couldnâ€™t access YouTube who now, because of this Project Feather, for the first time were able to access YouTube. What that looked like, according to the analytics, was that page load time had overall gone up. What was missing was the full data set.
I really like these stories that kind of play with our expectations. When the reveal comes, itâ€™s almost like hearing the punchline to a joke, right? Your expectations are set up and then subverted.
Jeff Greenspan is a comedian who talks about this. He talks about expectations in terms of music and comedy. He points out that they both deal with expectations over time.
In music, the pleasure comes from your expectations being met. A song sets up a rhythm. When that rhythm is met, thatâ€™s pleasurable. A song is using a particular scale and when those notes on that scale are hit, itâ€™s pleasurable. Music thatâ€™s not fun to listen to tends to be arhythmic and atonal where you canâ€™t really get a handle on whatâ€™s going to come next.
Comedy works the other way where it sets up expectations and then pulls the rug out from under you â€” the surprise.
Now, you can use music and you can use comedy in your designs. If you were setting up a lovely grid and a vertical rhythm, thatâ€™s like music. Itâ€™s a lovely, predictable feeling to that. But you can also introduce a bit of comedy; something that peeks out from the grid. You upset (just occasionally) something with a bit of subverted expectations.
You donâ€™t want something thatâ€™s all music. Maybe thatâ€™s a little boring. You donâ€™t want something thatâ€™s all comedy because then itâ€™s just crazy and hard to get a handle on.
You can see music and comedy in how you consume news. You notice that when you read your news sources, all it does is confirm what you already believe. You read something about someone, and you think, â€œYes, theyâ€™ve done something bad and I always thought they were bad, so that has confirmed my expectations.â€ Itâ€™s like music.
I read something that somebody has done and I always thought they were a good person. This now confirms that they are a good person. That is music to my ears. If your news feels like that, feels like music, then you may be in a bubble.
The comedy approach to music would be more like the clickbait you see at the bottom of the Internet where itâ€™s like, â€œClick here. You wonâ€™t believe what these child stars look like now.â€ The promise there is that we will subvert your expectations, and thatâ€™s where the pleasure will come.
My favorite story from history about analytics is not from World War One but from the sequel, World War Two, where again the United States were a few years late to this world war. But when they did arrive and started their bombing raids on Germany, they were coming from England. The bombers would come back all shot up, and so there was a whole thinktank dedicated to figuring out how we can reinforce these planes in certain areas.
You canâ€™t reinforce the whole plane. That would make it too heavy, but you could apply some judicious use of metal reinforcement to protect the plane.
They treated this as a data problem, as an analytics problem. They looked at the planes coming back. They plotted where the bullet holes were, and that led them to conclude where they should put the reinforcements. You can see here that the wings were getting all shot up, the middle of the fuselage, so clearly thatâ€™s where the reinforcements should go.
There was a statistician, a mathematician named Abraham Wald. He looked at the exact same data and he said, â€œNo, we need to reinforce the front of the plane where there are no bullet holes. We need to reinforce the back of the fuselage where there are no bullet holes.â€
What he realized was that all the data they were seeing was actually a subset of the complete data set. They were only seeing the planes that made it back. What was missing were all the planes that got shot down. If all the planes that made it back didnâ€™t have any bullet holes in the front of the plane, then you could probably conclude that if you get a bullet hole in the front of the plane, youâ€™re not going to make it back.
This became the canonical example of what we now call survivorship bias, which is this tendency to look at the subset of data â€” the winners.
You see survivorship bias all the time. You walk into a bookstore and you look at the business section and its books by successful business people; thatâ€™s survivorship bias. Really, the whole section should be ten times as big and feature ten times as many books written by people who had unsuccessful businesses because that would be a much more representative sample.
We see survivorship bias. You go onto Instagram and you look at peopleâ€™s Instagram photos. Generally, theyâ€™re posting their best life, right? Itâ€™s the perfect selfie. Itâ€™s the perfect shot. Itâ€™s not a representative sample of what somebodyâ€™s life looks like. Thatâ€™s survivorship bias.
We have a tendency to do it on the web, too, when people publish their design systems. Donâ€™t get me wrong. I love the fact that companies are making their design systems public. Itâ€™s something Iâ€™ve really lobbied for. Iâ€™ve encouraged people to do this. Please, if you have a design system, make it public so we can all learn from it.
I really appreciate that people do that, but they do tend to wait until itâ€™s perfect. They tend to wait until theyâ€™ve got the success.
What weâ€™re missing are all the stories of what didnâ€™t work. Weâ€™re missing the bigger picture of the things they tried that just failed completely. I feel like we could learn so much from that. I feel like we can learn as much from anti-patterns as we can from patterns, if not more so.
Robin Rendle talked about this in a blog post recently about design systems. He said:
The ugly truth is that design systems work is not easy. What works for one company does not work for another. In most cases, copying the big tech company of the week will not make a design system better at all. Instead, we have to acknowledge how difficult our work is collectively. Then we have to do something that seems impossible todayâ€”we must publicly admit to our mistakes. To learn from our community, we must be honest with one another and talk bluntly about how weâ€™ve screwed things up.
I completely agree. I think that would be wonderful if we shared more openly. I do try to encourage people to share their stories, successes, and failures.
I organized a conference a few years back all about design systems called Patterns Day and invited the best and brightest: Alla Kholmatova, Jina Anne, Paul Lloyd, Alice Bartlett â€“ all these wonderful people. It was wonderful to hear people come up and sort of reassure you, â€œHey, none of us have got this figured out. Weâ€™re all trying to figure out what weâ€™re doing here.â€ The audience really needed to hear that. They really needed to hear that reassurance that this is hard.
Gaps and overlaps
I did Patterns Day again last year. My favorite talk at Patterns Day last year, I think, was probably from Danielle Huntrods. Iâ€™m biased here because I used to work with Danielle. She used to work at Clearleft, and sheâ€™s an absolutely brilliant front-end developer.
She had this lens that she used when she was talking about design systems and other things. She talked about gaps and overlaps, which is one of those things thatâ€™s lodged in my brain. I kind of see it everywhere.
She said that when youâ€™re categorizing things, youâ€™re putting things into categories, that means some things will fall between those categories. That leaves you with the gaps, the things that arenâ€™t being covered. Itâ€™s almost like Donald Rumsfeld, the unknown unknowns and all that.
What can also happen when you put things into categories is you get these overlaps where thereâ€™s duplication; two things are responsible for the same task. This duplication of effort, of course, is what weâ€™re trying to avoid with design systems. Weâ€™re trying to be efficient. We donâ€™t want multiple versions of the same thing. We want to be able to reuse one component. Thereâ€™s a danger there.
Sheâ€™s saying what we do with the design system is we concentrate on cataloging these components. We do our interface inventory, but we miss the connective part. We miss the gaps between the components. Really, what makes something a system is not so much a collection of components but how those components fit together, those gaps between them.
Danielle went further. She didnâ€™t just talk about gaps and overlaps in terms of design systems and components. She talked about it in terms of roles and responsibilities. If you have two people who believe theyâ€™re responsible for the same thing, thatâ€™s going to lead to a clash.
Worse, youâ€™re working on a project and you find out that there was nobody responsible for doing something. Itâ€™s a gap. Everyone assumes that the other person was responsible for getting that thing done.
â€œOh, youâ€™re not doing that?â€
â€œI thought you were doing that.â€
â€œOh, I thought you were doing that.â€
This is the source of so much frustration in projects, either these gaps or these overlaps in roles and responsibilities. Whenever we start a project at Clearleft, we spend quite a bit of time getting this role mapping correct, trying to make sure there arenâ€™t any gaps and there arenâ€™t any overlaps. Really, itâ€™s about surfacing those assumptions.
â€œOh, I assumed I was responsible for that.â€
â€œNo, no. I assumed I was the one who would be doing that.â€
We clarify this stuff as early as possible in the design process. We even have a game we play called Fluffy Edges. Itâ€™s literally like a card game. Weâ€™d ask these questions, â€œWho is responsible for this? Who is going to do this?â€ Itâ€™s kind of good fun, but really it is about surfacing those assumptions and getting clarity on the roles at the beginning of the design process.
The design process
Now, the design process, Iâ€™m talking about the design process like itâ€™s this known thing and it really isnâ€™t. Itâ€™s a notoriously difficult thing to talk about the design process.
Hereâ€™s one way of thinking about the design process. This is The Design Squiggle by Damien Newman. He used to be at IDEO. I actually think this is a pretty accurate representation of what the design process feels like for an individual designer. You go into the beginning and itâ€™s chaos, itâ€™s a mess, and itâ€™s entropy. Then, over time, you begin to get a handle on things until you get to this almost inevitable result at the end.
Iâ€™m not sure itâ€™s an accurate representation of what the collaborative design process feels like. Thereâ€™s a different diagram that resonates a lot with us at Clearleft, which is the Double Diamond diagram from Chris Vanstone at the Design Council. The way of thinking about the Double Diamond is almost like itâ€™s two design squiggles back-to-back.
Itâ€™s a bit of an oversimplification, but the idea is that the design process is split into these triangles. First, itâ€™s the discovery. Then we define. So weâ€™re going out wide with discovery. Then we narrow it down with the definition. Then itâ€™s time to build a thing and we open up wide again to figure out how weâ€™re going to execute this thing. Once we got that figured out, we narrow down into the delivery phase.
The way of thinking about this is the first diamond (discovery and definition), thatâ€™s about building the right thing. Make sure youâ€™re building the right thing first. The second diamond (about execution and delivery), thatâ€™s about building the thing right. Building the right thing and building the thing right.
The important thing is they follow this pattern of going wide and going narrow. This divergent phase with discovery and then convergent for definition. Thereâ€™s a divergent phase for execution and then convergent for delivery.
If you take nothing else in the Double Diamond approach, itâ€™s this way of making explicit when youâ€™re in a divergent or convergent phase. Again, itâ€™s kind of about servicing that assumption.
â€œOh, I assumed we were converging.â€
â€œNo, no, no. We are diverging here.â€
Thatâ€™s super, super useful.
Iâ€™ll give you an example. If you are in a meeting, at the beginning of the meeting, state whether itâ€™s a divergent meeting or a convergent meeting. If you were in a meeting where the idea is to generate as many ideas as possible during a meeting, make that clear at the beginning because what you donâ€™t want is somebody in the meeting who thinks the point is to converge on a solution.
Youâ€™ve got these people generating ideas and then thereâ€™s one person going, â€œNo, that will never work. Hereâ€™s why. Oh, thatâ€™s technically impossible. Hereâ€™s why.â€ No, if you make it clear at the start, â€œThere are no bad ideas. Weâ€™re in a divergent meeting,â€ everyone is on the same page.
Conversely, if itâ€™s a convergent meeting, you need to make that clear and say, â€œThe point of this meeting is that we come to a decision, one decision,â€ and you need to make that clear because what you donâ€™t want in a convergent meeting is itâ€™s ten minutes to launch time, converging on something, and then somebody in the meeting goes, â€œHey, I just had an idea. How about if weâ€¦?â€ You donâ€™t want that. You donâ€™t want that.
If you take nothing else from this, this idea of making divergence and convergence explicit is really, really, really useful. Again, like I say, this pattern of just assumptions being surfaced is so useful.
This initial diamond of the Double Diamond phase, itâ€™s where we spend a lot of our time at Clearleft. I think, early in the years of Clearleft, we spent more time on the second diamond. We were more about execution and delivery. Now, I feel like we deliver a lot more value in the discovery and definition phase of the design process.
Thereâ€™s so much we do in this initial discovery phase. I mentioned already we have this fluffy edges game we play for role mapping to figure out the roles and responsibilities. We have things like a project canvas we use to collaborate with the clients to figure out the shape of whatâ€™s to come.
We sometimes run an exercise called a pre-mortem. I donâ€™t know if youâ€™ve ever done that. Itâ€™s like a post-mortem except you do it at the beginning of the project. Itâ€™s kind of a scenario planning.
You say, â€œOkay, itâ€™s so many months after the launch and itâ€™s been a complete disaster. What went wrong?â€ You map that out. You talk about it. Then once youâ€™ve got that mapped out, you can then take steps to avoid that disaster happening.
Of course, what we do in the discovery phase, almost more than anything else, is research. You canâ€™t go any further without doing the research.
All of these things, all of these exercises, these ways of working are about dealing with assumptions, either surfacing assumptions that we didnâ€™t know were there or turning assumptions into hypotheses that can be tested. If you think about what an assumption is, it kind of goes back to expectations that I was talking about.
Assumptions are expectations plus internal biases. That gives you an assumption. The things that you donâ€™t even realize you believe; they lead to assumptions. This can obviously be very bad. This is like youâ€™ve got blind spots in your assumptions because of your own biases that you didnâ€™t even realize you had.
Theyâ€™re not necessarily bad things. Assumptions arenâ€™t necessarily bad. If you think about your expectations plus your biases, thatâ€™s another way of thinking about your values. What do you hold to be really dear to you? The things that are self-evident to you, those are your values, your internal expectations and biases.
Now, at Clearleft, we have our company values, our core values, the things we believe. I am not going to share the Clearleft values with you. There are two reasons for that.
One is that theyâ€™re Clearleftâ€™s values. They are useful for us. Thatâ€™s for us to know internally.
Secondly, thereâ€™s nothing more boring than a company sharing their values with you. I say nothing more boring. Maybe the only thing more boring than a company sharing their values is when a so-called friend tells you about a dream they had and you have to sit there and smile and nod politely while they tell you about something that is only of interest to them.
These values are essentially what give you purpose, whether itâ€™s at an individual level, your personal moral values give you your purpose, or at a company or organization level, you get your purpose â€“ or any endeavor. You think about the founding of a nation-state like the United States of America. You got the Declaration of Independence. That encodes the values. That has the purpose. Itâ€™s literally saying, â€œWe hold these truths to be self-evident.â€ These are assumptions here. Thatâ€™s your purpose is something like the Declaration of Independence.
Then you get the principles, how youâ€™re going to act. The Constitution would be an example of a collection of principles. These principles must be influenced by the purpose. Your values must influence the principles youâ€™re going to use to act in the world.
Then those principles have an effect on the final patterns, the outputs that youâ€™ll see. In the case of a nation-state like America, I would say the patterns are the laws that you end up with. Those laws come from the principles encoded in the Constitution. The Constitution, those principles in the Constitution are influenced and encoded from the purpose in the Declaration of Independence.
The purpose influences the principles. The principles influence the pattern. This would be true in the case of software as well. You think about the patterns are the final interface elements, the user interface. Those are the patterns. Those have been influenced by the principles of that company, how they choose to act, and those principles are influenced by the purpose of that company and what they believe.
This is why I find principles, in particular, to be fascinating because they sit in the middle. They are influenced by the purpose and they, in turn, influence the patterns. Iâ€™m talking about design principles, something Iâ€™m really into. Iâ€™m so into design principles, I actually have a website dedicated to design principles at principles.adactio.com.
Now, all I do on this website is collect design principles. I donâ€™t pass judgment. I donâ€™t say whether I think theyâ€™re good design principles or bad design principles. I just document them. Thatâ€™s turned out to be a good thing to do over time because sometimes design principles disappear, go away, or get changed. Iâ€™ve got a record of design principles from the past.
For example, Google used to have a set of principles called Ten Things We Know to Be True â€” we know to be true, right? We hold these truths to be self-evident. Thatâ€™s no longer available on the Google website, those ten things, those ten principles. One of them was, â€œYou can make money without doing evil.â€ Like I said, thatâ€™s gone now. Thatâ€™s not available on the Google website.
There was another set of design principles from Google thatâ€™s also not available anymore. That was called Ten Principles That Contribute to a Googley User Experience. I think we understand why those are no longer available. The sheer embarrassment of saying the word Googley out loud, I think.
Iâ€™ll tell you something I notice when I see design principles. Like I say, I catalog them without judgment, but I do have ideas. I think about what makes for good or bad design principles or sets of design principles.
Whenever I see somebody with a list thatâ€™s exactly ten principles, Iâ€™m suspicious. Like, â€œReally? Thatâ€™s such a convenient round number. You didnâ€™t have nine principles that contribute to a Googley user experience? You didnâ€™t have 11 things that we know to be true? It happened to be exactly ten?â€ It feels almost like a bad code smell to me that itâ€™s exactly ten principles.
Even some great design principles like Dieter Rams, the brilliant designer. He has a fantastic set of design principles called Ten Principles for Good Design. But even there I have to think, â€œHmm. Thatâ€™s a bit convenient, isnâ€™t it, that itâ€™s exactly ten principles for good design? Isnâ€™t it, Dieter?â€
Now, just in case you think Iâ€™m being blasphemous by sugging that Dieter Ramsâ€™ Ten Principles for Good Design is not a good set of design principles, I am not being blasphemous. I would be blasphemous if I pointed out that in the Old Testament, God supposedly delivers 10 commandments, not 9, not 11, exactly 10 commandments. Really, Moses, ten?
Anyway, what Iâ€™m talking about here is, like I say, almost like these code smells for design principles. Can we evaluate design principles? Are there heuristics for saying whether a design principle is a good design principle or a bad design principle?
To get meta about this, what Iâ€™m talking about is, are there design principles for design principles? I kind of think there are. I think you can evaluate design principles and say thatâ€™s a good one or thatâ€™s a bad one. You can evaluate them by how useful they are.
Letâ€™s take an example. Letâ€™s say youâ€™ve got a design principle like this:
Make it usable.
Thatâ€™s a design principle. I think this is a bad design principle. Itâ€™s not because I donâ€™t agree with it. Itâ€™s actually a bad design principle because I agree with it and everyone agrees with it. Itâ€™s so agreeable that itâ€™s hard to argue with and thatâ€™s not what a design principle is for.
Design principles arenâ€™t these things to go, â€œRah-rah! Yes! I feel good about this.â€ They are there to kind of surface stuff and have discussions, have disagreements â€“ get it out in the open.
Letâ€™s say we took this design principle, â€œmake it usableâ€, and it was rephrased to something more contentious. Letâ€™s say somebody had the design principle like:
Usability is more important than profitability.
Ooh! Now weâ€™re talking.
See, I think this is a good design principle. Iâ€™m not saying I agree with it. Iâ€™m saying itâ€™s a good design principle because what it has now is priority.
Weâ€™re saying something is valued more than something else and thatâ€™s what you want from design principles is to figure out what the priorities of this organization are. What do they value? How are they going to behave?
I think this is a great phrasing for design principles. If you can phrase a design principle like this:
___, even over ___
Then thatâ€™s really going to make it clear what your values are. You can phrase a design principle as:
Usability, even over profitability.
Now you can have that discussion early on about whether everyone is on board with that. If thereâ€™s disagreement, you need to hammer that out and figure it out early on in the process.
Hereâ€™s another thing about this phrasing that I really like, â€œblank, even over blank.â€ It passes another test of a good design principle, which is reversibility. Rather than being a universal thing, a design principle should be reversible for a different organization.
One organization might have a design principle that says â€œusability, even over profitability,â€ and another organization, you can equally imagine having a design principle that says, â€œprofitability, even over usability.â€ The fact that this principle is reversible like that is a good thing. That shows that itâ€™s an effective design principle because itâ€™s about priorities.
In case of conflict, consider users over authors over implementors over theoretical purity.
Thatâ€™s so good.
First of all, it just starts with, â€œIn case of conflict.â€ Yes! That is exactly what design principles are for. Again, theyâ€™re not there to be like, â€œRah-rah! Feel-good design principles.â€ No, they are there to sort out conflict.
Then, â€œconsider users over authors.â€ Thatâ€™s like:
Users, even over authors. Authors, even over implementors. Implementors even over theoretical purity.
Really good stuff.
There are, I think, design principles for design principles, these kind of smell tests that you can run your design principles past and see if they pass or fail.
I talked about how design principles are unique to the organization. The reversibility test kind of helps with that. You can imagine a different organization that has the complete opposite design principles to you.
I do wonder: are there some design principles that are truly universal? Well, thereâ€™s kind of a whole category of principles that we treat as universal truths. Thatâ€™s kind of these laws. They tend to be the eponymous laws. Theyâ€™re usually named after a person and thereâ€™s some kind of universal truth. There are a lot of them out there.
Hofstadterâ€™s law, thatâ€™s from Douglas Hofstadter. Hofstadterâ€™s law states:
It always takes longer than you expect, even when you take into account Hofstadterâ€™s law.
That does sound like a universal truth and certainly, my experience matches that. Yeah, I would say Hofstadterâ€™s law feels like a universal design principle.
90% of everything is crap.
Theodore Sturgeon was a science fiction writer and people would poo-poo science fiction and point out that it was crap. He would say, â€œYeah, but 90% of science fiction is crap because 90% of everything is crap.â€ That became Sturgeonâ€™s law.
Yeah, you look at movies, books, and music. Itâ€™s hard to argue with Sturgeonâ€™s law. Yeah, 90% of everything is crap. That feels like a universal law.
Hereâ€™s one weâ€™ve probably all heard of. Murphyâ€™s law:
Anything that can go wrong will go wrong.
It tends to get treated as this funny thing but, actually, itâ€™s a genuinely useful design principle and one we could use on the web a lot more.
Thereâ€™s Cole and Coleâ€™s law. Youâ€™ve probably heard of that. Thatâ€™s:
Shredded raw cabbage with a vinaigrette or mayonnaise dressing.
Moving swiftly on, thereâ€™s another sort of category of these laws, these universal principles that have a different phrasing, and itâ€™s this idea of a razor. Here itâ€™s being explicit about in case of conflict. Here itâ€™s being explicit saying when you try to choose between two choices, which to choose.
Hanlonâ€™s razor is a famous example that states:
Never attribute to malice that which can be adequately explained by incompetence.
If youâ€™re trying to find a reason for something, donâ€™t go straight to assuming malice. Incompetence tends to be a greater force in the world than malice.
I think itâ€™s generally true, although, thereâ€™s also a law by Arthur C. Clarke, Clarkeâ€™s third law, which states that, â€œAny sufficiently advanced technology is indistinguishable from magic.â€ If you take Clarkeâ€™s third law and you mash it up with Hanlonâ€™s razor, then the result is that any sufficiently advanced incompetence is indistinguishable from malice.
Another razor that we hear about a lot is Occamâ€™s razor. This is very old. It goes back to William of Occam. Sometimes itâ€™s misrepresented as being the most obvious solution is the correct solution. We know that thatâ€™s not true because we saw in the stories of metal helmets in World War One and motorcycle helmets or the bombers in World War Two or the YouTube videos that itâ€™s not about the most obvious solution.
What Occamâ€™s razor actually states is:
Entities should not be multiplied without necessity.
In other words, if youâ€™re coming up with an explanation for something and your explanation requires that you now have to explain even more thingsâ€”youâ€™re multiplying the things that need to be explainedâ€”itâ€™s probably not the true thing.
If your explanation for something is â€œaliens did it,â€ well, now youâ€™ve got to explain the existence of aliens and explain how they got here and all this. Youâ€™re multiplying the entities. Most conspiracy theories fail the test of Occamâ€™s razor because they unnecessarily multiply entities.
World Wide Web
These design principles that we can borrow, weâ€™ve got these universal ones we can borrow. I also think maybe we can borrow from specific projects and see things that would apply to us. Certainly, when weâ€™re working on the World Wide Web and weâ€™re building things on the World Wide Web, we could look at the design principles that informed the World Wide Web when it was being built by Tim Berners-Lee, who created the World Wide Web, and Robert Cailliau, who worked with him.
The World Wide Web started at CERN and started life in 1989 as just a proposal. Tim Berners-Lee wrote this really quite boring memo called â€œInformation Management: A Proposalâ€ with indecipherable diagrams on it. This is March 12, 1989. His supervisor Mike Sendall, he later saw this proposal and must have seen the possibility here because he scrawled across the top:
Vague but exciting.
Tim Berners-Lee did get the go-ahead to work on this project, this World Wide Web project, and he created the first web browser. He created the first web server. He created HTML.
You can see the worldâ€™s first web server in the Science Museum in London. Itâ€™s this NeXTcube. NeXT was the company that Steve Jobs formed after leaving Apple.
I have a real soft spot for this machine because I was very lucky to be invited to CERN last year to take part in this project where we were trying to recreate the experience of using that first web browser that Tim Berners-Lee created on that NeXT machine. You can go to this website worldwideweb.cern.ch and you can see what it feels like to use this web browser. You can use a modern browser with this emulation inside of it. Itâ€™s really good fun.
My colleagues were spending their time actually doing the hard work. I spent most of my time working on the website about the project. I built this timeline because I was fascinated about what was influencing Tim Berners-Lee.
Itâ€™s kind of easy to look at the 30 years of the web, but I thought it would be more interesting to also look back at the 30 years before the web and see what influenced Tim Berners-Lee when it came to networks, hypertext, and format. Were there design principles that he adhered to?
We donâ€™t have to look far because Tim Berners-Lee himself has published design principles (that he formulated or borrowed from elsewhere) in a document called Axioms of web Architecture. I think he first published this in 1998. These are really useful things that we can take and we can apply when weâ€™re building on the web.
Particularly, now Iâ€™m talking about the second diamond of the Double Diamond. When we are choosing how weâ€™re going to execute something or how weâ€™re going to deliver it, building the thing right, thatâ€™s when these design principles come in handy.
He was borrowing; Tim Berners-Lee was borrowing from things that had come before, existing creations that the web is built on top of like the Internet and computing. He said:
Principles such as simplicity and modularity are the stuff of software engineering.
So he borrowed those principles about simplicity and modularity.
He also said:
Decentralization and tolerance are the life and breath of the Internet.
Those principles, tolerance and decentralization, theyâ€™d proven themselves to work on the Internet. The web is built on top of the Internet. So, it makes sense to carry those principles forward on the World Wide Web.
That principle of tolerance, in particular, is something I think you really see on the web. It comes from the principles underlying the Internet. In particular, this person, Jon Postel, who is responsible for maintaining the Domain Name System, DNS, he has an eponymous law named after him. Itâ€™s also called the Robustness Principle or Postelâ€™s law. This law states:
Be conservative in what you send. Be liberal in what you accept.â€
Now, he was talking about packet switching on the Internet that if youâ€™re going to send a packet over the Internet, try to make it as well-formed as possible. But on the other hand, when you receive a packet and if itâ€™s got errors or something, try and deal with it. Be liberal in what you can accept.
I see this at work all the time on the web, not just in terms of technical things but in terms of UX and usability. The example I always use is if youâ€™re going to make a form on the web, be conservative in what you send. Send as few form fields as possible down the wire to the end-user. But then when the user is filling out that form, be liberal in what you accept. Donâ€™t make them formulate their telephone number or credit card in a certain format. Be liberal in what you accept.
Be conservative in what you send when it comes from front-end development. This matters. Literally, just in terms of what weâ€™re sending down the wire to the end-user, we should be more conservative in what we send. We donâ€™t think about this enough, just the weight, the sheer weight of things weâ€™re sending.
I was doing some consulting with a client and we did a kind of top four of where the weight was coming from. I think this applies to websites in general.
4: Web fonts
Coming in at number four, we had web fonts. They can get quite weighty, but we have ways of dealing with this now. Weâ€™ve got font display in CSS. We can subset our web fonts. Variable fonts can be a way of reducing the size of fonts. So, there are solutions to this. There are ways of handling it.
At number three, images. Images do account for a lot of the sheer weight of the web. But again, we have solutions here. Weâ€™ve got responsive images with source set and picture. Using the right format, right? Not using a PNG if you should be using a JPEG, using WebP, using SVGs where possible. We can deal with this. There are solutions out there, as long as weâ€™re aware of it.
Weâ€™re seeing that now.
When it comes to choosing a language, thereâ€™s a fantastic design principle that Tim Berners-Lee used when he was designing the World Wide Web. Itâ€™s the principle of least power. The principle of least power states:
Choose the least powerful language suitable for a given purpose.
That sounds very counterintuitive. Why would you want to choose the least powerful language? Well, in a way, itâ€™s about keeping things simple. Thereâ€™s another design principle, â€œKeep it simple, stupid.â€ KISS.
Itâ€™s kind of related to Occamâ€™s razor, not multiplying entities unnecessarily. Choose the simplest language. The simplest language is likely to be more universal and, because itâ€™s simpler, it might not be as powerful but itâ€™ll generally be more robust.
Iâ€™ll give you an example. Iâ€™ll quote from Derek Featherstone. He said:
Heâ€™s absolutely right. This is about robustness here. Itâ€™s less fragile.
Thereâ€™s a set of design principles from the Government Digital Services here in the U.K. and theyâ€™re really good design principles. One of them stuck out to me. The design principle itself says:
By way of explanation, they say:
Government should only do what only government can do.
Government shouldnâ€™t try to be all things to all people. Government should do the things where private enterprise canâ€™t do these things. The government has to do these things. The government should only do what only government can do.
I thought that this could be extrapolated out and made into a more universal design principle. You could say:
Any particular technology should only do what only that particular technology can do
If thatâ€™s too abstract, letâ€™s formulate it into this design principle:
Or, alternatively, you could use a button and you style it however you want using CSS.
Okay. That seems pretty straightforward and that is a perfect example of the principle of least power. Choose the least powerful language suitable for the purpose.
But then what if youâ€™ve got a drop-down component, selecting an option from a list of options? Well, you could build this using bare minimum HTML. Again, divs, maybe. You style it however you want it to look and you give it that opening and closing functionality. You give it accessibility using ARIA. Now youâ€™ve got to think about making sure it works with a keyboard â€” all that stuff, all the edge cases.
Or you just use a select element â€” job done. You style it with CSS â€¦Ah, well, yes, you can style it to a certain degree with CSS, but if you ever try to style the open state of a select element, youâ€™re going to have a hard time.
Now, this is where it gets interesting. What do you care about more? Can you live with that open state not being styled exactly the way you might want it to be styled? If so, yes, choose the least powerful technology. Go with select. But I can kind of start to see why somebody would maybe roll their own in that case.
Do you still pick the least powerful technology here?
This would be kind of the under-engineered approach: to just use the native HTML approach: input type="date", select, button.
What you get with the native approach is you get access. You get that universality by using the least powerful language. Thereâ€™s more universal support.
What you get by rolling your own is you get much more control. Youâ€™re going from the spectrum of least power to most power and thatâ€™s also a spectrum going from most available (widest access) to least available but with more control.
You have to decide where your priorities lie. This is where I think, again, we can look at the web and we can take principles from the web.
The web does not value consistency. The web values ubiquity.
Thatâ€™s the purpose of the web. Itâ€™s the universal access. Thatâ€™s the value encoded into it.
To put this in another way, we could formulate it as:
Ubiquity, even over consistency.
Thatâ€™s the design principle of the web.
This passes the reversibility test. We can picture other projects that would say:
Consistency, even over ubiquity.
Native apps value consistency, even over ubiquity. iOS apps are very consistent on iOS devices, but just donâ€™t work at all on Android devices. Theyâ€™re consistent; theyâ€™re not ubiquitous.
We saw this in action with Flash and the web. Flash valued consistency, but you had to have the Flash plugin installed, so it was not ubiquitous. It was not universal.
The World Wide Web is about ubiquity, even over consistency. I think we should remember that.
When we look here in the worldâ€™s first-ever web browser, we are looking at the worldâ€™s first-ever webpage, which is still available at its original URL. Thatâ€™s incredibly robust.
Whatâ€™s amazing is you can not only look at the worldâ€™s first webpage in the worldâ€™s first web browser, you can look at the worldâ€™s first webpage in a modern web browser and it still works, which is kind of amazing. If you took a word processing document from 30 years ago and tried to open it in a modern word processing document, good luck. It just doesnâ€™t work that way. But the web values this ubiquity over consistency.
Letâ€™s apply those principles, apply the principle of least power, apply the robustness principle. Value ubiquity even over consistency. Value universal access over control. That way, you can make products and services that arenâ€™t just on the web, but of the web.
Many discussions influenced this document, both inside and outside of the IETF and IAB. In particular, Edward Snowden’s comments regarding the priority of end users at IETF 93 and the HTML5 Priority of Constituencies were both influential.
Since the projectâ€™s beginning in 2008, the market has evolved and Progressive Web Apps (PWAs) now bring the power of native apps to web applications.
Today, we are announcing the end of development for PhoneGap.
I think Brian was spot-on with his belief that all technology deprecates with time. I also think it was very astute of him to tie the goals of PhoneGap to that belief. Heck, itâ€™s even in the project name: PhoneGap!
jQuery is the perfect example of this. jQuery is no longer needed because cross-browser DOM Scripting is now much easier …thanks to jQuery.
Successful libraries and frameworks point the way. They show what developers are yearning for, and thatâ€™s where web standards efforts can then focus. When a library or framework is no longer needed, thatâ€™s not something to mourn; itâ€™s something to celebrate.
Thatâ€™s particularly true if the library of code needs to be run by a web browser. The user pays a tax with that extra download so that the developer gets the benefit of the library. When web browsers no longer need the library in order to provide the same functionality, itâ€™s a win for users.
In fact, if youâ€™re providing a front-end library or framework, I believe you should be actively working towards making it obselete. Think of your project as a polyfill. If itâ€™s solving a genuine need, then you should be looking forward to the day when your code is made redundant by web browsers.
I was really looking forward to speaking at An Event Apart this year. I was going to be on the line-up for Seattle, Boston, and Minneapolis; three cities I really like.
At the start of the year, I decided to get a head-start on my new talk so I wouldnâ€™t be too stressed out when the first event approached. I spent most of January and February going through the chaotic process of assembling a semi-coherent presentation out of a katamari of vague thoughts.
You should attend. Not for my talk, but for Ireâ€™s talk on Future-Proof CSS which sounds like it was made for me:
In this talk, weâ€™ll cover how to write CSS that stands the test of time. From progressive enhancement techniques to accessibility considerations, weâ€™ll learn how to write CSS for 100 years in the future (and, of course, today).
My talk will be about design principles …kinda. As usual, it will be quite a rambling affair. At this point I almost take pride in evoking a reaction of â€œwhereâ€™s he going with this?â€ during the first ten minutes of a talk.
When I do actually get around to the point of the talkâ€”design principlesâ€”I ask whether itâ€™s possible to have such a thing as universal principles. After all, the whole point of design principles is that theyâ€™re specific to an endeavour, whether thatâ€™s a company, an organisation, or a product.
Whatâ€™s interesting about both of those principles is that they are imperative. They tell you how to act:
Be conservative in what you send, be liberal in what you accept.
Choose the least powerful language suitable for a given purpose.
Other princples are imperative, but they tell you what not to do. Take the razors of Occam and Hanlon, for example:
Entities are not to be multiplied without necessity.
Never attribute to malice that which is adequately explained by stupidity.
But these imperative principles are exceptions. The vast majority of â€œuniversalâ€ principles take the form of laws that are observations. They describe the state of the world without providing any actions to take.
Any sufficiently advanced technology is indistinguishable from magic.
By themselves, these observational laws are interesting but they leave it up to you to decide on a course of action. On the other hand, imperative principles tell you what to do but donâ€™t tell you why.
It strikes me that it could be fun (and useful) to pair up observational and imperative principles:
Because anything that can go wrong will go wrong, choose the least powerful language suitable for a given purpose.
I feel like the Jevons paradox is another observational principle that should inform our work on the web:
The Jevons paradox occurs when technological progress increases the efficiency with which a resource is used, but the rate of consumption of that resource rises because of increasing demand.
This problem would be addressed if web developers were more conservative in what they sent. The robustness principle in action.
Admittedly, the expanded version of that is far too verbose:
Because technological progress increases the efficiency with which a resource is used, but the rate of consumption of that resource rises because of increasing demand, be conservative in what you send, be liberal in what you accept.
Iâ€™m sure there are more and better pairings to be made: an observational principle to tell you why you should take action, and an imperative principle to tell you what action you should take.
I think about design principles a lot. Iâ€™m such a nerd for design principles, I even have a collection. Iâ€™m not saying all of the design principles in the collection are goodâ€”far from it! I collect them without judgement.
As for what makes a good design principle, Iâ€™ve written about that before. One aspect that everyone seems to agree on is that a design principle shouldnâ€™t be an obvious truism. Take this as an example:
Make it usable.
Whoâ€™s going to disagree with that? Itâ€™s so agreeable that itâ€™s practically worthless as a design principle. But now take this statement:
Usability is more important than profitability.
Ooh, now weâ€™re talking! Thatâ€™s controversial. Thatâ€™s bound to surface some disagreement, which is a good thing. Itâ€™s now passing the reversability testâ€”itâ€™s not hard to imagine an endeavour driven by the opposite:
Profitability is more important than usability.
In either formulation, what makes these statements better than the bland toothless agreeable statementsâ€”â€œUsability is good!â€, â€œProfitability is good!â€â€”is that they introduce the element of prioritisation.
I like design principles that can be formulated as:
X, even over Y.
Itâ€™s not saying that Y is unimportant, just that X is more important:
Prioritisation isnâ€™t and shouldnâ€™t be a one-off exercise. The changing needs of your customers, the business environment and new opportunities from technology mean prioritisation is best done as a regularÂ activity.
Mind you, some technologies have no direct effect on the end user. When it comes to build tools, version control, toolchains â€¦all the stuff that sits on your computer and never directly interacts with users. In that situation, the wants and needs of developers can absolutely take priority.
But as a general principle, I think this works:
User experience, even over developer experience.
Sadly, I think the current state of â€œmodernâ€ web development reverses that principle. Developer efficiency is prized above all else. Like I said, that would be absolutely fine if weâ€™re talking about technologies that only developers are exposed to, but as soon as weâ€™re talking about shipping those technologies over the network to end users, itâ€™s negligent to continue to prioritise the developer experience.
I feel like personal websites are an exception here. What you do on your own website is completely up to you. But once youâ€™re taking a paycheck to make websites that will be used by other people, itâ€™s incumbent on you to realise that itâ€™s not about you.
Iâ€™ve been talking about developers here, but this is something that applies just as much to designers. But I feel like designers go through that priority shift fairly early in their career. At the outset, theyâ€™re eager to make their mark and prove themselves. As they grow and realise that itâ€™s not about them, they understand that the most appropriate solution for the user is what matters, even if thatâ€™s a â€œboringâ€ tried-and-tested pattern that isnâ€™t going to wow any fellow designers.
Iâ€™d like to think that developers would follow a similar progression, and Iâ€™m sure that some do. But Iâ€™ve seen many senior developers who have grown more enamoured with technologies instead of honing in on the most appropriate technology for end users. Maybe thatâ€™s because in many organisations, developers are positioned further away from the end users (whereas designers are ideally being confronted with their creations being used by actual people). If a lead developer is focused on the productivity, efficiency, and happiness of the dev team, itâ€™s no wonder that their priorities end up overtaking the user experience.
I realise Iâ€™m talking in very binary terms here: developer experience versus user experience. I know itâ€™s not always that simple. Other priorities also come into play, like business needs. Sometimes business needs are in direct conflict with user needs. If an online business makes its money through invasive tracking and surveillance, then thereâ€™s no point in having a design principle that claims to prioritise user needs above all else. That would be a hollow claim, and the design principle would become worthless.
Because thatâ€™s the point with design principles. Theyâ€™re there to be used. Theyâ€™re not a nice fluffy exercise in feeling good about your work. The priority of constituencies begins, â€œin case of conflictâ€ and thatâ€™s exactly when a design principle mattersâ€”when itâ€™s tested.
Suppose someone with a lot of clout in your organisation makes a decision, but that decision conflicts with your organisationsâ€™s design principles. Instead of having an opinion-based argument about whoâ€™s right or wrong, the previously agreed-upon design principles allow you to take ego out of the equation.
Prioritisation isnâ€™t easy, and it gets harder the more factors come into play: user needs, business needs, technical constraints. But itâ€™s worth investing the time to get agreement on the priority of your constituencies. And then formulate that agreement into design principles.
â€œServerlessâ€, is a buzzword. We canâ€™t seem to agree on what it actaully means, so it ends up meaning nothing at all. Much like â€œcloudâ€ or â€œdynamicâ€ or â€œsynergyâ€. You just wait for the right time in a meeting to drop it, walk to the board and draw a Venn Diagram, and then just sit back and wait for your well-deserved promotion.
That’s very true, and I do not like the term “serverless” for the rather obvious reason that it’s all about servers (someone else’s servers, that is). But these three principles are handy for figuring out if you’re building with in a serverlessy kind of way:
You have no knowledge of the underlying system where your code runs.
Scaling is an intrinsic attribute of the technology; so much so that it just happens automatically.
Donâ€™t build more JS than you can maintain over the long term. If youâ€™re going to be building something for a long time, make sure what you are building will grow with you. Make sure you donâ€™t depend on other peopleâ€™s work too much, lest you want to keep refactoring your code when the framework you picked goes out of style.
I like those. They’re like design principles for design principles.
One set of design principles that I’ve included in my collection is from gov.uk: government design principles . I think they’re very well thought-through (although I’m always suspicious when I see a nice even number like 10 for the amount of items in the list). There’s a great line in design principle number twoâ€”Do less:
Government should only do what only government can do.
This wasn’t a theoretical issue. The multiple departmental websites that preceded gov.uk were notorious for having too much irrelevant contentâ€”content that was readily available elsewhere. It was downright wasteful to duplicate that content on a government site. It wasn’t appropriate.
I think that the design principle from GDS could be abstracted into a general technology principle:
Any particular technology should only do what only that particular technology can do.