CONTENT STRATEGY / UX
Style guides / brand voice
User education / onboarding
Information architecture
Notifications / errors / ads
Product strategy
Chatbots
Personalized content
Product-generated emails
MARKETING
Blogs
Success stories / case studies
In-product marketing
Emails
Reports / white papers
EDITING
SQUIRRELS
About us
Contact us
Product style guide
The problem
My experience creating and owning the style guide and brand voice for Ancestry’s health product was one of the main reasons Google wanted me to lead UX writing for their TV platform. As at Ancestry, this young product lacked a consistent voice and vocabulary. This would complicate and slow things as engineers and PMs tried to track down existing language for new screens and features — and would confuse users when, inevitably, different terms were used to describe the same functions.
The solution: bring someone (me) on board to oversee all the language in the product. This would mean creating and owning the product style guide and communicating those language and messaging decisions to the team and company as a whole
The process
In my first couple weeks, I audited as much of the product as I could, scanning for inconsistencies in language that might be problematic for users or the team. I found, for instance, that TV shows were sometimes referred to as “shows,” sometimes “TV shows,” sometimes “TV” and sometimes “series.”
With this done, I had a list of the first decisions that needed to be made.
I then audited competitors’ products, reviewed our existing user research and looked around for any insights around how the ways we talk about TV today are changing, and how that language varies by place. For instance, I found that TV dramas are usually called “series” in Europe, while “shows” typically refers only to reality TV or sitcoms. And I found discussions on how many shows today, particularly those made by streaming networks, blur the definitional lines between what we’d once call a movie, a TV show or a miniseries.
Perhaps most importantly, I reviewed any relevant existing Google style guides I could find, such as those for YouTube, YouTube TV, the Android Play store and Google’s overall UX and style guidance documentation. Google TV is a unique product with specific types of users and functionality, but it’s voice and terminology still has to feel “Google-y” and to mesh with, for instance, the other pre-installed Google apps on an Android device.
Based on all this, I drafted recommendations for a product vocabulary, as well as guidance on our brand voice and tone.
I shared out these initial recommendations with the product owners, tweaked a couple recommendations based on their feedback, and then concretized these recommendations as final decisions in our new product style guide.
Sample excerpts
from the word list section of the Google TV style guide
The result
Now, whenever there is confusion on what to say or how to say it — or even whether to capitalize a term — we consult the style guide. If the answer isn’t there, I discuss the issue with the most relevant PMs or designers, reach a decision and record it in the guide.
It’s a living document. If new features are added or deprecated and a previous style decision no longer makes sense, I revise it and notify the relevant members of the team.
And the guide serves as a useful resource for all of Google/Alphabet as a whole, ensuring that marketing materials or new features or products that tie in to Google TV all share the same language.