Guidelines

Copy Writing

Be concise

Concise doesn’t mean limited; it means something closer to efficient. Use as few words as possible without losing the meaning. When writing concisely, we make sure every word on the screen has a job.

Log in to comment
DO
You must log in before you can write a comment
DOn't

Avoid double negatives

Double negatives increase cognitive load — they make users spend extra time decoding the message.

Keep my subscription
DO
I do not want to unsubscribe
DOn't

Begin with the objective

When a sentence describes an objective and the action needed to achieve it, start the sentence with the objective.

To see item’s properties, tap on it
DO
Tap on item to see it’s properties
DOn't

Use specific verbs whenever possible

Specific verbs (such as connect or save) are more meaningful to users than generic ones (such as configure or manage).

Edit details
Choose preferences
DO
Manage details
Configure preferences
DOn't

Make the copy consistent

Inconsistency creates confusion. One typical example of inconsistency is replacing a word with a synonym in a different part of the UI. For instance, if you decide to call the process of arranging something “Scheduling” in one part of UI do not call it a “Booking” in other parts of your UI.

Another common pitfall is combining forms of address. Don’t refer to the user in both the second person and the first person within the same phrase.

Change your preferences in Your Account
DO
Change your preferences in My Account
DOn't

Avoid jargon

One of the significant characteristics of effective UX writing is clarity and simplicity. For clarity, you need to remove the technical terms and use familiar, understandable words and phrases instead. It’s especially important to avoid jargon in error messages.

Sign-in error: You entered an incorrect password
DO
System error (code #2234): An authentication error has occurred
DOn't

Write in present tense

Avoid using the future tense to describe the action.

Video downloaded
DO
Video has been downloaded
DOn't

Write in the active voice

The passive voice makes readers yawn. Compare this sentence in both voices:

Click the Search button to search for an article.
DO
The Search button should be clicked when you are ready to search for an item.
DOn't

Use numerals

Use numerals in place of words for numbers.

You have 2 missed calls
DO
You have two missed calls
DOn't

Avoid long blocks of text

When using a product, users aren’t immersed in the user interface itself but in their work. Consequently, users don’t read UI text — they scan it. Help them scan the text by writing it in short, scannable blocks. Chunk text into shorter sentences and paragraphs. Keep the most important text up front and then ruthlessly edit what comes after it.

You can:
• Book a flight
• View pictures
• Plan trips
• Book a restaurant
• Visit tourist spots
DO
By using this app you can book flights, see pictures of your destination, plan trips around the country, book a restaurant and go visit some of the best tourist spots.
DOn't

Avoid showing all details up front

Sometimes it might be helpful to provide additional information or supplemental instruction for users. But all too often such details are presented upfront. Too much information can quickly overwhelm users. Thus, reveal detail as needed. Use a mechanism of progressive disclosure to show more details. In the most basic form, this mechanism can be implemented as ‘Read more’ link to the full content.

Progressive disclosure is especially good for mobile UI (where designers have a limited screen space to work with).

Information you need to book a flight
View all
DO
To book a flight you have to make sure you have all of your information available. Your passport, name, address, hotel address, contact information, phone number, ...
DOn't

Use language that’s consistent with the user’s platform

The terms we use when describing interaction with a desktop app do not necessarily apply to mobile platforms. For example, if you design an iPhone app, we can’t say ‘click’ when referring to the action. We need to say ‘tap’ instead.

Mobile app:
Tap

iOS:
Touch ID
DO
Mobile app:
Click

iOS:
Fingerprint
DOn't

Identify interactive elements appropriately

Users don’t like surprises. They hate situations when they’re expecting one thing, and end up with another. People should be able to tell at a glance what an element does.

When labeling buttons and other interactive elements, use action verbs, such as ‘Connect,’ ‘Send,’ ‘Subscribe’ instead of vague ‘Okay’ or ‘Submit.’

Connect
Send
Subscribe
DO
Okay
Submit
Yes
DOn't