Studio of Stories

Most people think UX writing is about choosing the right words.

After sitting in a UX Writing workshop, I realized that’s not quite true. UX writing is about choosing which decisions users shouldn’t have to make.

Words are just the surface.

The real work happens earlier, when you decide what to explain, what to remove, what to repeat, and what to never say at all.

In theory, UX writing sounds simple. Be clear. Be concise. Be conversational. In practice however, it’s one long negotiation between users, systems, and constraints you don’t control.

You’re constantly asking questions like:

• Where will this text appear?
• How much attention does the user have right now?
• What happens if this sentence is misunderstood?
• What does the system need to say and what can it stop saying?

None of those questions are about creativity. They’re about responsibility.

One thing that stood out in the workshop was how different product content is from marketing content. Marketing can persuade. UX writing doesn’t get that luxury.

Once someone is using a product, they didn’t come to be convinced. They came to do something. The job of UX writing is to help them do it and get out of the way before they notice the text at all.

That reframes everything.

Cleverness becomes a liability. Personality takes a back seat. Consistency starts to matter more than style.

The workshop also made something uncomfortable very clear: UX writing rarely happens in ideal conditions.

In large organizations, there are teams, guidelines, reviews.

In reality, often maybe it’s only you.

You’re the one deciding terminology.

You’re the one spotting inconsistencies.

You’re the one explaining, again, why three different labels for the same action is a problem.

That’s why UX writing sits somewhere between content strategy, information architecture, and design. It’s not just about writing, it’s about shaping systems that can survive scale.

Voice and tone were another turning point for me.

I’d heard the theory before: one voice, many tones. But seeing it applied across onboarding, UI copy, and error messages made it click.

A product shouldn’t sound cheerful when something breaks.

It shouldn’t sound technical when someone is new.

And it shouldn’t sound like marketing when someone just wants to finish a task.

Tone isn’t branding. It’s situational awareness.

What I appreciated most about the workshop was its realism. There was no illusion that UX writing is about polishing text at the end of a process. It’s about making trade-offs early, often with incomplete information.

You choose clarity over completeness.

You choose consistency over cleverness.

You choose fewer words, even when more words would feel safer.

Those choices are invisible when they work.

But when they don’t, users feel it immediately.

The biggest takeaway I walked away with wasn’t a checklist or a framework.

UX writing isn’t about making interfaces sound nice.

It’s about reducing uncertainty.

Every sentence either helps a user move forward or makes them pause.

And in products, pauses are expensive.