UX Writing and Writing for Multiple Markets
Learn practical UX writing principles for creating clear, scannable content that works across multiple languages, markets, and cultures.
TL;DR
How to write better to help people read, in multiple languages. Practical guidelines to help readers scan content faster, understand it better, and make interfaces work across different markets.
Words are everything on the web.
They tell people where to go, what to do, what went wrong, and what happens next.
And yet, when we design digital products, words are often treated as something that comes later. We design the interface, create the components, make everything look nice, and then find the words that fit inside.
Working across multiple markets taught me that it should often be the other way around.
Because writing for digital products isn't just about finding a clever CTA or making something sound "on brand." You need to understand who you're speaking to, what they need, where they might struggle, and how they actually talk about your product or service.
And once your product exists in 10, 20, or 50+ markets, there's another layer:
Will what you've written still work when it's no longer in English?
Let's break it down.
Golden Rules for UX Writing
I'm not a UX writer.
But as a UX designer, I've worked on large-scale products used across different markets, languages and cultures. And whether I liked it or not, I constantly found myself making decisions about words.
What should this button say?
How should we phrase this research question?
Does this navigation label make sense?
Will users understand this filter?
What do we call something when even the people inside the business use three different terms for it?
Over time, I've learned that good UX writing isn't really about writing.
It's about reducing the amount of work someone has to do to understand you.
There are a few principles I keep coming back to:
People rarely read websites word for word. They scan.
Put the most important information first.
Break long content into headings, paragraphs, and meaningful chunks.
Keep sentences short when you can.
Prefer familiar words over complicated ones.
Write for smaller screens, where space and attention are limited.
Make links and buttons descriptive enough to make sense on their own.
Match your tone to the situation the user is in.
Remove words that don't help someone understand or act.
And when designing for multiple markets, leave room for the language to change.
The principle behind all of these guidelines is simple: Make people work less to understand you.
People Don't Read Your Interface. They Scan It.
We like to imagine that someone opens a page and carefully reads everything we've written.
Most of the time, they don't.
People jump between headings, keywords, buttons, links, numbers, and anything else that looks relevant to what they're trying to accomplish.
They're not necessarily interested in your content. They're interested in finding an answer.
That's an important distinction.
If someone is looking for your return policy, they don't want to read the story of your company before finding out whether they have 14 or 30 days to return something.
If someone gets an error while checking out, they don't need a clever error message. They need to know what happened and what to do next.
Good UX writing respects that.
Put the answer first. Add context second.
That's the inverted pyramid approach: important information at the top, supporting details underneath.
It makes content easier to scan, but it also makes it easier to understand.
Plain Language Works in Every Language
Simple writing is sometimes mistaken for dumbing things down.
It's the opposite.
Writing something complicated is relatively easy. Making something complicated feel simple requires understanding it first.
Plain language means choosing words your audience is likely to understand, writing sentences that don't make people reread them, and removing information that doesn't help them complete their task.
This becomes even more important when your content will be translated.
A sentence that is unnecessarily complicated in English doesn't magically become clearer in German, French, Spanish, Japanese, or Polish.
In fact, you've probably just handed the translator another problem to solve.
So before thinking about localization, start with the source.
Clear English gives you a better foundation for clear translations.
Write With a Person in Mind
One technique I find particularly useful is imagining a specific person on the other side of the screen.
How would you explain this to them if they were sitting next to you?
What words would they use?
What do they already know?
What don't they know?
And, importantly, what is happening to them at this particular moment?
Your brand might usually be playful, but someone whose payment has failed for the third time probably doesn't need a joke.
Someone signing up for your service might need encouragement.
Someone about to delete their account needs clarity.
Someone reading a legal document needs precision, but that doesn't mean the language needs to be unnecessarily complicated.
Your voice can stay consistent.
Your tone should respond to the situation.
A simple test I like is to read the copy out loud.
If it doesn't sound right when you say it, there's a good chance it won't feel right when someone reads it either.
And then, give it to someone else to read.
Don't explain it. Just watch them.
See how they scan the text. Notice where they stop, where they hesitate, and whether they scroll back and forth to reread the same paragraph.
Those little moments tell you a lot.
If someone has to go back and read something twice to understand what you mean, there's a good chance you need to simplify it.
Sometimes the best way to test your writing is simply to watch someone try to understand it.
Then Comes Translation
This was one of my biggest lessons when I started working as a UX designer.
I was working for an omnichannel eCommerce company operating across 52 markets.
I was fresh in the field, so there was already a lot to grasp. Then I started designing for different markets and realized just how much room there was for error.
Like many international companies, we designed primarily in English.
And English is often wonderfully compact.
That's great, until you assume every other language will occupy the same amount of space.
I remember delivering a product page with an "Add to Bag" button.
A colleague asked me:
"What are the specifications for this button?"
I confidently gave him the dimensions in pixels.
He laughed.
Then he asked me to recreate the same interface using the German translation.
And everything broke.
We both laughed. And that was a quick lesson learned.
The German copy needed significantly more room than the English version I'd designed around.
I wasn't really designing a button. I was designing a container for information I couldn't fully predict.
Since then, I don't design text-heavy components around one perfect English string.
Because the English version isn't the product.
It's one version of the product.
Leave Room for Language to Expand
When you're designing for multiple markets, assume your text will change.
Sometimes dramatically. It can go to up to 40%. Like my example above.
A neat one-line label in English can become two lines in another language. A compact navigation item can suddenly need twice the horizontal space. A beautifully balanced set of cards can become completely unbalanced once real translations arrive.
So don't design the perfect English interface and hope localization fits inside it. Don't design in pixels.
Design a flexible system.
Buttons should accommodate longer labels.
Cards should be able to grow vertically.
Navigation needs to survive longer words.
Layouts shouldn't depend on every heading being roughly the same length.
And wherever possible, test your designs with real translations early, especially languages that tend to produce longer strings.
This isn't something to "fix later" during localization.
It's part of UX design.
Don't Translate Words. Translate Meaning.
There's another trap here.
I mentioned at the beginning that I've worked on large-scale products used across different markets, languages, and cultures.
I didn't include “cultures” just to sound fancy. Culture plays a huge role in how people understand words. And English, again, doesn't always capture those nuances.
Even when the translated words technically fit, that doesn't necessarily mean the experience works.
Literal translation isn't the same as localization.
A phrase that feels warm and natural in one language can sound strange, overly formal, or even rude in another. A clever piece of wordplay can become meaningless. A familiar metaphor might not exist at all.
Take something as simple as the word “you.”
In English, we can speak directly to someone using “you” without thinking much about it. But translate that into German without enough context, and “you” might become “Sie” - the formal, polite form and often the default when communicating with customers.
Technically, the translation is correct.
But what if your brand is casual, friendly, and speaks to customers as peers? You might have wanted “du” instead.
Suddenly, one tiny word changes the relationship between your brand and the person using your product.
The translation is correct, but the meaning is lost.
Even something as small as a button label can carry different expectations across markets.
That's why the question shouldn't only be:
“How do we translate this?”
It should also be:
“What are we trying to communicate here?”
When translators and localization teams understand the intent behind the copy — the tone, context, audience, and purpose — they can find the right expression for their market instead of being forced to reproduce individual words.
Context matters. Culture matters. Meaning matters.
UX Writing Is Also UX Design
It's easy to treat copy as the final layer of an interface.
But words affect the design itself.
Change a label and your button changes.
Change a heading and your card changes.
Change the language and potentially your entire layout changes.
Change the tone and the experience changes.
That's why writing and design shouldn't happen in isolation.
If you're designing for multiple markets, writers, designers, researchers, translators, localization specialists, and local teams should ideally be part of the same conversation.
The earlier that happens, the fewer surprises you'll have later.
A Few Things to Remember
You don't need to become a UX writer to write better product copy.
And you don't need to speak 52 languages to design something that can work across 52 markets.
You do need to remember a few things:
Write for scanning.
People are looking for information, not admiring your paragraphs.
Put the important part first.
Don't make people dig for the answer.
Use plain language.
Simple words make complicated experiences easier.
Write for a person, not "the user."
Think about who they are, what they know, and what they're trying to do.
Design for content, not around one English sentence.
Your interface needs to survive translation.
Give translators context.
Meaning matters more than matching individual words.
Test with real languages.
Don't wait until the product is finished to discover that your layout only works in English.
And perhaps most importantly:
If a word doesn't help someone understand, decide, or act. Ask yourself, whether you need it at all.
Final Thought
Good UX writing is not about sounding clever.
It's about making things easier to understand.
And when you're designing for multiple markets, that responsibility becomes even bigger.
You're no longer asking:
"Does this sentence sound good?"
You're asking:
"Will someone understand what we mean, find what they need, and know what to do next — regardless of the language they're reading it in?"
That's a much better design question.
How important do I think UX writing is?
When I became a Design Lead, one of my first missions was to bring a UX writer onto the team.
And it turned out to be one of the best decisions I made.
Having someone who thinks deeply about language, clarity, and context changed not only our copy, but the way we thought about the experience itself.
Because UX writing isn't something you add to a finished design.
It is part of the design.
And sometimes, as I learned from one very broken German button, the smallest piece of copy can teach you the biggest UX lesson.
Practical takeaway
UX writing isn’t something you add to a finished design. It is part of the design.
100% Authenticity Guarantee
Everything you read here is written by me.
I use AI daily. I won’t hype it, because plenty of people already do.
For me, it’s just a tool, something I use in my day-to-day work, and here mainly for formatting or language polish, since English isn’t my first language.
The thinking, experience, opinions, and voice are always mine.
Key takeaway
• Write for scanning, not reading. Keep it clear, simple, and put the most important information first.
• Design for translation from the start. English is only one version of your product. Leave room for other languages to expand and change.
• UX writing is UX design. Words shape how people understand, navigate, and experience your product.
