Key principles
Address users clearly
You should normally address users in second person. Occasionally you might want to use first person:
- Second person (you or your): Speak directly to the user. This mimics a social interaction, with the interface and the user communicating with each other.
- First person (I or my): Occasionally you might want to use this style to emphasize the user’s consent or absolute ownership of actions and content.
Don’t mix first and second person
To avoid confusion, don’t mix first and second person in the same phrase.
Be concise
Users only read about 20% of the text on an average web page, so be concise and make every word count. If a word doesn’t serve a purpose, it shouldn’t be in the UI.
info
Ask yourself what does the user need to know right now to continue?
Write in short, scannable segments that focus only on a small number of concepts at a time. Cut any unnecessary details and words.
Introductory phrases can often be omitted.
Write in the present tense
Use the present tense to describe how the product behaves and to bring immediacy to the interaction. Avoid using the future tense to describe the way a product always acts.
Don't write in different variations of the present tense, such as the present perfect tense.
If you’re describing an action the user needs to take, or if the user needs to leave the Adjust environment for something to happen, it’s ok to use the future tense.
Use active voice
Use active voice for readability and clarity. Avoid passive voice.
In active voice, the subject of the sentence does the action. In passive voice, the subject of the sentence has the action done to it.
info
There might be some situations where passive voice is more suitable:
- When it's more important to draw the reader's attention to the person or thing being acted upon.
- When the actor is unimportant.
- When the actor is unknown.
Write for all reading levels
Use common terms that are understandable to users with only basic English. Your writing should always be at a 7th grade reading level or lower.
info
Check your reading level in Writer or using Hemingway App.
Avoid clichés, business jargon and management speak.
Use consistent words
Use the same word for the same concept throughout the UI.
To remove this permission...
To delete this permission...
Be positive
Present information in a positive way to guide the user. Tell them what they can do, rather than what they can’t do.
info
Try to present error and validation messages in the same way.
Reassure the user
When there’s uncertainty, reassure the user that everything is fine.