
Content design: the process behind a product's words
Content design starts from the user's need, researches, writes, tests, and maintains content. Learn its stages and how to review microcopy well.
What is content design?
It is the discipline that treats a product’s text as part of the design, not something added at the end. It covers the microcopy of buttons and errors, headings, navigation, instructions, and status messages.
The difference from traditional writing is the starting point. A writer starts from the message they want to convey; a content designer starts from what the user needs to know and do, and only then decides how to write it.
This matters because almost every screen contains words that decide whether the user moves forward. An error that says “Operation failed” does not help; one that explains what is missing and what to do does. A designer who works on content alongside structure avoids screens that look right but confuse.
It also reduces rework. Agreeing on what each screen should say before polishing every sentence saves editing cycles.
What are the stages?
Public guidance does not use a single format. The Canadian Digital Service (CDS) has eight steps, from investigating to implementing and evaluating; GOV.UK talks about starting from a user need and deciding what to do with the content. This table condenses them into one sequence, with what each one says:
| Stage | What happens | What the guidance says |
|---|---|---|
| 1. Need | Define what the user needs to know or do | GOV.UK: content design starts by taking a user need |
| 2. Research | Understand vocabulary, mental models, and existing content | The CDS recommends researching vocabulary and mental models, and auditing what exists |
| 3. Reduction | Decide how much content, what format, and which channel are needed | GOV.UK suggests reducing content, splitting large pieces, and removing duplicates |
| 4. Writing | Write in plain language, including microcopy | GOV.UK: good content is written in plain English and optimised for the web |
| 5. Testing | Test with real users and iterate | The CDS has a ’test and iterate’ step with real users |
| 6. Review | Verify facts and follow the style guide | The CDS asks for a fact check by a subject-matter expert and an inclusive design review |
| 7. Maintenance | Keep content current or withdraw it | GOV.UK: content is current and kept up to date, or no longer current but kept as a record; the CDS closes with ‘implement and evaluate’ |
How do you review microcopy?
The CDS publishes a peer review checklist with concrete points. It is written for English and French, but most of it carries over to other languages. Some of its points:
- Address the user in second person. The CDS gives the example “you must answer this” versus “this must be answered”.
- Avoid jargon, technical language, and acronyms. If you use an acronym, spell it out the first time, unless data shows everyone knows it.
- Check links out of context. They should make sense on their own, with no “click here”, and say when they open in a new tab.
- Do not use “above” or “below” to locate things on the page: it does not work well for people using assistive technology, and responsive layouts change the order.
- Avoid metaphors and phrasal verbs such as “check out” or “go ahead”.
- Keep sentences that begin with a conditional “if” to the exception. The CDS prefers “Do Y if you are X” to “If you are X, do Y”, with one condition per sentence.
The checklist has one advantage: it turns a subjective review into questions anyone can answer. Adapt it to your product and your language.
How do you test content?
A content test is a usability test focused on the text. Ask the participant to complete a task and observe where they stop, what they misread, and what is missing. The CDS includes this step, with real users, before moving to the final review.
A practical trick: ask the person what they think a button will do before they click it. If the answer does not match the action, the text needs revision, even if it is grammatically correct.
What happens after publishing?
Many teams treat content as a deliverable that closes at launch. GOV.UK proposes a different view: content must stay current or be kept as a historical record. A text that describes a feature that no longer exists confuses people as much as a badly written one.
The CDS’s last step is to implement and evaluate. It is worth planning the evaluation: which metrics to review, how often, and who is responsible for retiring what no longer helps.
When is a formal process unnecessary?
For a small screen with simple text, a full process is excessive. Reviewing the user’s need, reading the text aloud, and testing it with one person is enough. A formal process is justified when content is extensive, when several teams write it, or when the text must be maintained in several languages.
Example
Illustrative example: a medical appointment app receives complaints because the message “The booking could not be completed” does not say what to do. The content design team starts from the need: knowing whether the slot is still available and what options exist. It audits the existing messages and finds four different ones for the same error. It writes one with the cause and two clear actions: “That time slot is no longer available. Choose another, or tell us if you prefer this one.” They test the text with five people, and two say they would have understood without asking. The text goes into the product’s message library, with its review date.
Common mistakes
- Writing before knowing the user’s need.
- Leaving microcopy to the end, when the structure is already locked.
- Having several versions of the same message across screens.
- Testing only in your head and not with real people.
- Using words that change meaning from screen to screen.
- Not planning how long content stays valid after publishing.
To bring content into several languages, internationalization explains how to prepare the text. For plain language for people with reading or memory difficulties, cognitive accessibility offers complementary criteria. And to place content within the overall flow, the UX design process shows at what point each stage fits.