This thing called UX writing... *sigh

I can’t tell you the name of the website anymore.

It’s been years.

But I remember the moment vividly. The developer was working on a project, building something pretty cool, in my opinion. It was a VTU platform where people could buy airtime, data bundles, and pay their bills. The website looked clean, sharp, and professional.

But there was a problem.

The words.

I wasn’t a UX writer back then. Heck, I didn’t even know what that meant. But I wasn’t a stranger to bad copy, and something about the hero section immediately felt off.

The headline said something like, “Welcome to (let’s call it RechargeHub), the one-stop solution for all your VTU needs.”

It sounded clunky and stiff, and for the life of me, I didn’t know what VTU meant.

So, I asked him, "What's this product about?”

He explained, and I said, “Okay, but that’s not what this is saying. It sounds way too formal for a product that’s supposed to make life easier.”

“How about, ‘Instantly recharge MTN, DSTV, PHCN, and more’ as a header, then a body sentence that talks more about the services?”

He agreed.

I didn’t stop there. I offered suggestions. Simpler ways to say things, words that matched the flow of the product itself. It was a small thing, really. But when the developer made those changes, the whole experience just…clicked. It was easier to read, and easier to understand.

Looking back, that was my first real UX writing project. I didn’t know it then, but I was already stepping into this world, where words take on the very important responsibility of guiding, clarifying, and creating trust in the products that make up our everyday existence.

Why UX Writing?

The first time I taught a class on UX writing, this was the topic.

So, why UX writing?

UX writing isn’t loud. You don’t always see it, but you feel it.

It’s the words that make you feel confident when you click “Submit.”

The text that reassures you when something goes wrong.

And when it’s missing? You know.

If a health app forgets to explain why it needs some of your more sensitive data, most users would never sign up. Or if a payment button left people wondering, “Wait, am I being charged now or later?” most people would drop off from purchasing. These aren’t just small missteps; they’re big problems that could’ve been avoided with a UX writer in the room.

2025 with Content & Context 🤝 

This year, I want to take you on a journey.

Not just through my takes on what content founded on better context looks like (it looks pretty good actually), but through the world of UX writing itself. What it is, what it isn’t, and why it matters in product UX in general.

And because you’ve been with me through this journey so far, I’ve put together something special: a free resource, UX Writing for Small Teams. It’s my way of saying thank you and making sure that even if you don’t have a UX writer on your team yet, you can start creating better experiences right now.

You can grab it here.

Now I know this resource may not be beneficial for everyone, so if you have a special resource request, please reach out by replying to this email with what would be beneficial to you. That’s what UX is about, really.

Happy New Year, and welcome to 2025. Let’s make this a year where our words do more than just fill space because, honestly, ‘lorem ipsum’ can do that too.

New Here? Catch Up on These Reads

Here are a few past articles you might enjoy:

• A tale of two strategies⚔ 

• 👋 First impressions only happen once 

We are on LinkedIn!

Join the Content and Context community on LinkedIn! We share updates, insights, and continue conversations there. It’s a space to learn and grow together. Follow us here.

P.P.S. Your feedback makes us better!❤️ Reply to this email to share your thoughts, or reach us on LinkedIn to keep the conversation going.