UX Writing and Microcopy
Level 4 · Designing the interaction
How the words in an app guide people. UX writing, microcopy and content design, and why words carry the whole design in chat and voice.
Course contentsLesson 17 of 21
Level 1 · What UX is
Level 2 · Finding out from users
Level 3 · Making sense of research
Level 4 · Designing the interaction
After this lesson you can
- Write a clear button label
- Write an error message that helps
- Say why chat and voice depend on words
11 mincovers 5 glossary entries
Worth reading first: User Onboarding Design
How the words in an app guide people
UX writing is writing the words in an app or a site so people can use it. The tiny bits are called microcopy. Button labels, hints and error notes are all microcopy. A button that says Create account beats one that says Submit. It tells you what will happen.
Good microcopy is short, plain and specific. A hint under a password box that says at least 8 characters saves an error. An error that says something went wrong helps nobody. One that says this card has expired, try another tells people what to do next.
Content design is the wider job. It works out what facts people need, and the best way to show them. Sometimes the answer is a paragraph. Sometimes it is a table, a checklist or one number in bold. The content designer decides before anyone writes.
A conversational user interface is one you use by chatting, by text or by voice. A support bot that asks what is wrong with your card is one. In a chat, the words are the whole design. There is no layout to lean on, only the next message and the reply buttons.
A voice user interface is one you use by speaking, and it answers out loud. Voice has no screen at all. People cannot scan back up a list they heard, so options must be few, usually no more than three, and the most likely one should come first.
Write the words early, not last. A layout drawn with lorem ipsum fills in the space with fake text. Then the real label turns out to need twice the room, or the real error has no place to go. Design with real words from the first wireframe.
The common slip is to write in the company's voice instead of the user's. Your request has been processed is the system talking. Done, your table is booked for 7 pm is a person talking. Read every line aloud, and fix the ones no human would say.
Worked example
One error message, rewritten
A bank app showed Error 402 when a transfer failed. Calls to support about it ran at about 300 a week.
The new message read: your daily limit is 1,000 pounds. You can send 250 more today. Calls dropped to about 60 a week.
The words for this lesson5
Check yourself
Why should a voice interface offer only a few options at a time?
Finished this lesson?
Marking it complete also marks its 5 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.