|||

Look for patterns

If you are writing an error message from scratch every single time, you’re doing it wrong. Write less and design more. Be on the hunt for patterns.

I’m say pattern instead of principles to emphasize that you are looking for repeated moments in a user experience to codify into standards. A pattern says, Here’s the way we do tooltips at Shark Lasers Incorporated.” Principles are loftier versions of patterns: We never repeat ourselves at Shark Lasers Incorporated.”

Patterns come from the ground up. Principles come from top down. They are different flavors of the same thing. Both help prevent unnecessary thinking” in the design process because thinking takes time and uses up precious calories.

Create standards around patterns

Remember to create standards around patterns. Creating standards around patterns is design. Creating standards around language is called writing a dictionary” and you have better things to do.

For example, from the user’s point of view, an error message is your system’s annotation on some behavior they do.

Standard around pattern Standard around language
Errors explain what happened. Use Try again” as a CTA unless there is a specific action the user can take to resolve the error. Start error messages with Oops” and make them fewer than 12 words. Never use the world Error” in an error.

Standards around patterns allow writers to choose their own solution. They are like principles. Standards around language are just rules. Rules lead to tiring conversations about minutia:

Is it OK if this error message is 13 words?

What if I have to use the word error?”

Patterns are easier to follow and allow designers leeway in choosing the right solution.

Patterns are an artform

That said, patterns also provide defaults for those moments when you don’t have time (or resources, freedom, energy, wherewithal) to design a bespoke solution. It’s not a bad thing to have boilerplate error messages that apply to 80% of situations. In this sense, patterns are like cookie cutters. How well your cookie cutters work is a matter of trial and error and experimentation.

If cookie cutter sounds pejorative, then I implore you to go eat some cookies. There’s nothing wrong with cookies that all look the same, they’re just as delicious. Cookie cutters enable uniformity at scale.

If you want to ship quality design, quickly, over and over again, then you need to abstract away some thinking. Learn to look for patterns. The hard part of content design isn’t the words. It’s learning how to write patterns that give rise to flawless experiences.


Other principles of content design

Up next Start with the story Respect the user Every alert in software might as well be saying ‘Hey, idiot.’ John Hull Treat humans with dignity and respect. Behind the abstract label of “user”
Latest posts Work is like a hill Badge of dishonor Ceci n'est pas un poubelle This sign is a crime Beware the lure of consistency Do not water Never, ever use the term microcopy You need three things to design content Permanently fixed Assembly instructions for a side table Extraneous labels, ignored conventions The double diamond model Don't have an emergency here Product tours that don't suck Quickly edit text on the web How content designers can get the most out user interviews Let's be reasonable How to derisk trial experiences Turn around, bright eyes We could be zeroes Content design vs visual design The recipe approach to writing labels Sorry no pizza 6 truths for first-time public speakers Do not enter, exit only What the %&@! is content design Content design has a nomenclature problem Solve the real problem Respect the user Look for patterns Start with the story