You need three things to design content

You need three things to design content. Those three things are people, standards, and patterns. Maybe you’re not convinced.

People Standards Patterns
For content design to make sense, you need to know who the user is and what they’re thinking. For content design to be consistent, you needs guiding principles and conventions. For design to happen quickly, you need to identify repeated problems and solve them.

Do I really need people?

Yeah. They use and pay for your software. And they generally have a choice about the matter so you need to design with them in mind. People are a critical part of the design process.

Do I really need standards?

Double yeah. Without standards you’ll taste two flavors of confusion:

Internal confusion

No company ever sets out to work in silos”. It’s a communication problem. It’s solved when everyone agrees on how to communicate. When folks talk about the same thing in different ways, it makes effective knowledge transfer impossible.

Here’s a question: What does your product do? Can you describe it in a sentence using plain language? Here’s a less simple question: Would everyone on your team give the same answer? What about everyone in the company?

In music, a harmony is achieved when notes of the same wavelength are played together; the resulting chord is louder than the sum of its parts. The opposite of harmony is dissonance. Standards are like sheet music: they keep everyone in sync.

External confusion

Users feel the pain too. Inconsistency in terminology makes a system challenging to learn and frustrating to use. Ever try to find your way in a neighborhood with multiple streets with the same name?

Consistent voice and tone is important too. It might seem like a nice to have,” but remember, some folks use your software all day, every day. A disjointed semantic model and clumsy product narrative can slowly wear a groove in your users’ brains.

These are real humans with lives outside our software. Build a product that treats them with respect.

Do I really need patterns?

Go ahead and build things from scratch every single time. You might be good at it. But it’s a pain in the neck. And every time you approach a design problem without considering what’s happened before, you risk introducing inconsistencies and making mistakes. I suggest you always look for patterns.

For users, repetition is a part of learning; conventions make a product easier to learn. Patterns are how you do this. So while, you theoretically could design without patterns, it’s not recommended.

Up next Permanently fixed Never, ever use the term microcopy When you focus too much on words you belittle the craft of writing. You do this when you call yourself a “wordsmith” or describe your output as
Latest posts The three sees of content design The definitive post on whether chatGPT will take your job The new clothes fallacy A Smallish Book about content design How to make Confluence less horrible I am a writer designer 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