How to get started with UX writing when your project really needs it
What you should do if no one knows how to write good copy
My writing habit and UX work crossed paths when I did UX writing for a re-designed website.
When working with Subject Matter Experts (SMEs), you'll encounter that they often spend a ton of time working in specific environments and using certain terminology. As a result, they’re often biased about what they think the average person can understand.
So when I had to re-design a web application created by technical experts, I knew that I needed to start with the writing right away. Even though I had specialized knowledge in the field, I couldn’t understand some of the terminology and phrases on the landing page.
Some team members might have been second nature, but it was a surefire way for new users to get lost.
To fix this, I had to get a crash course in UX writing, and that started by understanding what this field was.
Copywriting, UX writing, and Content design
First of all, many terms get thrown around when it comes to the idea of writing and design.
The ‘big 4’ are often called UX writing, Copywriting, Content Strategy, and Content Design. They all have slightly different definitions, but what I’ll be focusing on is UX writing.
UX writing is focused on writing the UI elements for digital product use. In essence, they’re the ones that take what may be lorem ipsum (or sketch copy) and turn it into something our users can understand. These may include:
Buttons
Error messages
Controls
Instructions
Notifications
Onboarding sequences
etc.
They’re the ones that have to think about what the reader can understand when they read labels and text, and they have to think about anything unclear to your target audience.
This means that you have to start at the very beginning when you’re wearing the UX writer hat. Here are some of the lessons that I learned from UX writing.
Tips for getting started as an (unofficial) UX writer
Check your style guide (and see if it works)
One of the first things you should do when starting is to check the style guide. For example, your style guide might have three font categories: “Header,” “Subheader,” and “Body.”
The fonts listed here are your UX writing canvas: these are the fonts that you’ll use to create text elements throughout your website. Even if these fonts aren’t listed, at least one font is likely because someone probably played around with fonts to establish a company logo and tagline.
You could go in-depth into typography here, thinking about letter spacing, line height, contrast, focus points, etc. But what we’re concerned about isn’t beautiful web typography: it’s consistency.
The main thing is to establish consistency across your entire website with your fonts. For example, the title text for the entire page and the header for a particular section might look different, but you want to make sure that it’s the same font.
Figma makes this incredibly easy by establishing text styles to serve this purpose.
Align UX writing and copywriting with a copy language spreadsheet
If people confuse copywriting with UX writing, you might as well use that to your advantage.
While we may use certain words to explain what we’re doing to users, they might be landmines from a marketing perspective. Or, the elements of the product we find most useful might help other members of the team understand how we should talk about it.
This is where keeping a spreadsheet of the current copy can be helpful for your team to weigh in.
For example, one back and forth discussion came from the phrase “Discover and purchase x content.” Team members objected to the word “purchase” since it not only raised a whole lot of questions (i.e., What sort of format would the purchase come in (.pdf, .docx, etc.), Is this a subscription, etc.), it missed the point of what we were trying to convey.
Have a ‘brain dump’ section about what you’re trying to convey
Anyone who’s dabbled in writing will tell you that sometimes, the hardest thing to do is cut down the number of words you use. People aren’t going to read 12 paragraphs of text to understand what you offer, but getting from 12 paragraphs to 1 sentence requires a ton of work.
That’s why one of the most valuable things (on your spreadsheet) is to have a ‘brain dump’ section, where you can explain what you’re trying to convey in a lot of words.
This really helped me with a “How it Works” page. The typical “How it works” page has one word (or a short sentence) as a header for a step and maybe a few sentences to explain in greater detail.
Figuring out the right word or phrase requires a lot of careful consideration, and one thing that can help is to summarize what you’re trying to tell your user in this section. Writing it down makes it so that the team can see what you’re thinking, and they can tweak it as necessary.
The correct word can often mean the difference in your user's understanding of what you’re trying to convey and them missing the point. But that’s not all.
Understand the reading level
Plain and simple language works best for everyone, even experts. As a result, one thing you need to check constantly is your website's reading level.
Fortunately, there are many free tools to easily check this in the digital content age. Anything from Hemingwayapp to Prowritingaid, Grammarly, and even Microsoft Word provides you with a ‘reading level’ of your text just by copy-pasting it into their application.
The Nielsen Norman Group recommends your text be at an 8th-grade reading level if you’re writing for a general audience and a 12th-grade reading level for specialized or B2B audiences.
If you’re running into issues with the reading level, here are some things you can look for:
Can you simplify jargon or terminology into something more generic (i.e., “from planning to point-of-care” → “from beginning to end.”)?
Are you using words that have simpler alternatives? Hemingway app is great for this (it highlights it in magenta).
Are your sentences/paragraphs too long? Prowritingaid/Grammarly is great for this since it shows you lengthy sentences.
You don’t have to be perfect at UX writing because you have one built-in process to help you: user testing.
Do your best, then user test.
You don’t have to spend hours laboring over a few words: do the best you can and seek user feedback. You’re trying to convey things as best you can and then check to see if your users are on the same page.
This is an advantage that UX has over other teams, like Marketing. We can see feedback on things that are not finalized, like prototypes and text. A simple user testing question can give you insight as to whether your words make sense:
“There are some labels on the sidebar navigation. Could you tell me what you think they mean?”
Remember, you’re not the ultimate judge of whether something’s easy to read: your users are.
While the world of UX writing may be very deep, it doesn’t take much investment to get it to the point where you can user test it. So if you spot words that seem like they might be hard for your user to understand, don’t be afraid to jump in and spend some time working on the UX writing.
The words you use, just like the way you design things, can impact how your users use your product.
Kai Wong is a Senior UX Designer, Design Writer, and author of the Data and Design newsletter. His new book, Data-informed UX Design, explains small changes you can make regarding data to improve your UX Design process.