UX Writing: How to do it like Google with this powerful checklist Notes from Google I/O 2017 on choo…
UX Designer. Writer. Ex-Entrepreneur. Dad to Inty & Luna. Husband to Sandrita. Scotsman with an English accent. Living in Australia 😜
Writing is easy. All you have to do is cross out the wrong words. (Mark Twain)
These are my notes from a Google I/O 2017 talk by three UX Writer’s. It’s a great resource to start creating a UX Writing process within your organisation. Useful for anyone involved in putting words on interfaces.
1. Introduction to Content Strategy
Maggie Stanphill, UX Director, Content Strategy, Google
2. Three UX Writing Best Practices
Alison Rung, UX Writer, Google
3. Building Brand voice for your new Product
Julian Appenrodt, UX Write, Google
4. Your UX Writing Checklist
Maggie Stanphill, UX Director, Content Strategy, Google
1. Introduction to Content Strategy
Google follow the principle, focus on the user and all else will follow. Focusing on the user starts with the content.
Content strategy is the crafting and development of all product messaging. UX writing is a speciality within this discipline. It focuses on helping users achieve their goals with language.
Language helps the user get where they want to go. By focusing on what the user wants to achieve content strategy builds loyalty and trust.
How Google incorporates UX Writing within UX
Writers work with Designers to think about information hierarchy on the page. This then guide user actions. Writers work with researchers to test hypothesis about language and inform our insights.
When you have the foundation of UX writing and you add brand voice, something amazing can happen. UX writing can survive with the fundamentals but it can thrive with brand voice.
Oh don’t use big words. they mean so little.
2. Three UX Writing Best Practices
Often words used are software problems and not people problems. Pay attention to verbs. A verb is an action word. It tends to be the most powerful part of your sentence. In a perfect world it will relate some action to the user.
For clarity we remove technical terms and we put the action in the context of the user.
This is especially important when you’re writing a product announcement or an app update. Currently focus is on the technical specs of the new feature you’re releasing. Instead focus on the new action that people can perform. Jargon free offers context.
Concise doesn’t only mean short, it means something closer to efficient. When we are writing with concision we look at our message and we make sure every word on the screen has a distinct job.
The above is a common problem in product writing. Here we don’t need the header. This is typical in interfaces. Because the design field shows some pre-existing text field, we feel we need to fill it in. You should avoid this. When you can instead practice content first design.
Content first design makes sure your visuals are inline with what you’re trying to say. Not the other way around. So try not jam your message in boxes that weren’t meant for them.
Try to have designers work in parallel with writers.
Here we’ve removed the header. As you know we don’t read every word on screens, we scan.
We know that peoples eyes follow an F shaped pattern as they read over the screen. They read the first line. Then the second line. Then they start skipping down the page, catching only the first or second word of each sentence. For this reason we keep our text not only concise but also frontloaded.
Frontloading means to put your important concepts first. This is so people’s eyes catch those important words as they skip down.
Above most of the words are at the end of the sentence. We can fix this by flipping it around with the below
You won’t always be able to do the above. The principle will always hold true and you can use it anywhere you are writing for screens. Keep the most important text up front and then ruthlessly edit what comes after it.
The call to action (CTA) guides people to there next step. You want your text to help people get where they want to go. For that reason the call to action needs to resonate with what they want to do. Here OK is not a good call to action.
Try again is a good option instead, but this isn’t all we need. We need to give them an option if they’ve forgotten their password. If you forget your password and your only option is to ‘try again’ then you’ll be frustrated.
Paying attention to writing and the people you’re writing for is so important. It can uncover some of the basic functions that your app or website needs to offer. So if you don’t think of those edges cases and write for them you might see some drop off in the usage.
If you pay attention to these three principles you’ll connect better with your users.
Good UX writing is not a science.
These three principles are not always in harmony. There is a kind of tension between them. They are competing with each other.
When we made the text clear it is still pretty long, and not so scannable. When it made the text concise it made it shorter but at the expense of some clarity. Finally when we made the text useful it became longer again and became less scannable.
Consider your user context and you’ll find the right balance between these principles. Think about what they want to do in the moment.
You can also look towards your products brand voice. Your brand voice should create the right balance of clear, concise and useful. This should be true to your products character.
Think about your products core function. Then you’ll begin to find the elements of that character. Then think about what makes it special, how it’s differentiated.
Below is what Google would do inline with their own positive brand voice. We don’t like to lead with a negative words like wrong. We are also ok to have a the text a little longer, a little less concise, to be friendly and chatty. Now this sounds like Google. It doesn’t mean it’s right for your brand. It’s up to you to build your own brand voice for you own product.
Make the most of your words.
3. Building Brand voice for your new Product
Start with a set of brand principles. These can be 3 or 4 adjectives that embody your brand, and how you want people to perceive it. To come up with these adjectives you can do a brainstorming exercise.
Imagine you are signing up your product to a dating site.
What words or info would you put in your products profile. What is about your product that you think would make it stand out or seem most interesting to people.
What would make them want to swipe right and want to learn more?
You can then distil these qualities into descriptive words. These will then will become your brand principles.
With Google Pay the principles were: fresh, empathetic and approachable.
Now you have your brand principles. The next step is what these principles will sound like when you apply them to you writing. These will then become your writing guidelines.
You can then take it one step further and think about what your voice will sound like in different contexts. This is tone.
An easy way to remember the difference between voice and tone, is to think about like a person. A persons voice stays the same. The tone they talk to you in may change, depending on the situation or what they’re saying.
In an app this might be like talking to users in a different way for different circumstances.
For Android Pay we mapped these different moments on a user journey. We did it in a tone spectrum ranging from serious to whimsical. This makes sure that we are using our voice in a consistent way across the entire user experience.
For your product the two ends of the spectrum might called something different. Your tone might range from informative to inspiring or direct to humorous. Once you have created your two ends you then need to determine what moments in the user journey you’re going to map.
A good way to do this is to think about the distinct milestones or interactions in your user experience. These can be thing like on-boarding, education or troubleshooting.
To help you decide were these will fall on the spectrum you can then think about:
What they might be feeling in that moment
What you’d like them to feel
So you established your voice and you have mapped your tune. Now it’s time to apply both of these and do some UX Writing.
It’s time to decide what words will go in your user interface. That ends up being a combination of everything we’ve talked about today.
To be successful your interface text needs to be:
As well as reflect your brands natural voice
To show you how we get there we can walk through how the UX writing process looks like.
As an example lets try to see what we say to the user, the first time that they use Android Pay. We can guess that they’re curious. So we want to tell them what we can do with the app, as well as give them reason to move beyond this screen and set it up.
At the beginning of the process we start with something descriptive like the below.
We then think about the three principles of good UX Writing. This text is clear and useful but it’s not concise. We look at what pieces of information are essential. What parts could use visuals instead. We edit it to something like.
For this we’ve ticked off clear, concise and useful and need to think about one more part. Tone. We’d ask ourselves, does this text convey our brand? Not too much, it fells pretty generic.
So going back to our brand principles we think about how we can make it fresher and more exciting. Even whimsical as this might be our first impression on the user.
In our final iteration we end up with something like this.
It’s a little longer than before, but adding a little personality can do this. It’s up to you whether infusing this personality is worth the words. This is not always a clear decision. If you’re not sure whether some words will be more effective than others then A/B test it.
When trying to find the right words for your product never underestimate the power of A/B testing.
We ran an A/B test on the start screen on Android Pay. We changed the button from ‘add card’ to ‘get started and it resulted in a 12% increase in click throughs.
testing is a great way to confirm a hypothesis you might have. Or to decide between two different version of text, you’re not sure which will connect more with you users.
Bad writing slows things down. Good writing speed them up.
4. Your UX Writing Checklist
With this checklist, you’re on your way to make your product stand out with language.
Standout UX Writing Checklist
User First: Focus on your users
Clear: Write in a language free of jargon, and with context
Concise: Write in a style that’s efficient and scannable
Useful: Write in a way that directs the next action
On Brand: Define your brand voice and apply an appropriate tone
User First: Choose language that performs, proven by research and A/B testing
Bringing writers in at the end of the creative process, is like trying to put toothpaste in to a tube.
If you enjoyed this, have a read of my other UX articles:
24 Ways to Look Like an Awesome UX Designer
51 Research Terms You Need to Know as a UX Designer
53 Tech Terms You Need to Know as a UX Designer
How to become a UX Designer at 40 with no digital or design experience
Please click the 💚️ below to help others find it, and leave a comment. Thanks for reading.
