“What is it that you writers actually do?"
I get asked some variation of this question from colleagues every few months. It can make my contributions feel invisible. As UX writers, we often say that “good content should go unnoticed”, but that doesn’t mean we should.
Writing is a diligent and personal process. It takes research, deliberation, and empathy. We have to think like a spectrum of users: What does a new user need in this moment? What about an experienced one? Which words will guide them effortlessly? Which might slow them down?
We have the breadth of an entire language at our fingertips, and choosing the right phrase often means sifting through piles of clunky drafts before anything fits.
Most of the colleagues we work with don’t write that way. They’re sending Slack messages, writing Jira tickets, or updating internal docs. And while all of that requires clarity, it doesn’t demand the same level of precision.
That’s the beauty of UX writing. We’re the quiet navigators, guiding people from one moment to the next. We weigh words, challenge them, talk to them: “Are you right for this context?” “How might someone misread you?” “Can you do the job we need you to do?”
But if all that thought happens quietly, inside our own heads or in private workspaces, it’s easy to overlook. And if we don’t invite others into the trenches with us, our work can seem simple - because, well, everyone writes. So how hard can it be?
Here are three ways you can involve non-writers in your workflow so that they better understand and appreciate your craft. This includes product managers, designers, developers, your department heads, and marketing. And by bringing them in, you can create a reliable and diverse feedback group, and engage everyone in the complexity of writing for the user experience.
There’s a common misconception among non-writing teammates that those of us that have refined the practice of writing can come up with perfect words in a matter of minutes. This might be true for simple or well-documented flows, but complex flows require sensitivity, intention, and time.
When someone says, “Let’s just write something now,” don’t shy away. Use the opportunity to co-create. If you’re used to sharing polished final content, showing your messy first drafts can feel intimidating. But that’s exactly the point. Involving stakeholders in the messy part helps them understand why it takes time to craft concise content.
When I started as a UX writer, I always insisted on writing alone. When a product manager hovered nearby, I’d politely say, "I'll let you know when I have options." But it kept happening, until I decided to embrace the challenge.
What was supposed to be a 30 minute meeting turned into 2 hours. We couldn't think of appropriate content for the scenario. Turns out, the product itself was broken. This was only discovered because this seemingly small piece of content was impossible to write. The PM left the meeting with more respect for my abilities and I gained a lot of confidence. After that day, I was added to every kick off and product review meeting.
If you’re used to sharing polished final content, showing your messy first drafts can feel intimidating. But that’s exactly the point. Involving stakeholders in the messy part helps them understand why it takes time to craft concise content.
This one’s more passive, but important. You’ll inevitably get feedback on content ideas that you’ve already considered. If you keep notes about these decisions, you can quickly reference them to explain why that direction didn’t make the cut.
Write in paragraph form as comments in your design file or in a research deck. I use Figma and add sticky notes beneath designs to explain my decisions.
These notes might include:
These notes also help when advocating for more space in the UI.
In addition to inline notes, I keep a separate page with more in-depth thoughts and iterations. If I’m stuck, I type out my thought process stream-of-consciousness style. It’s a great way for product managers, and curious lurkers, to see just how much thinking goes into each word.
If public speaking isn’t your thing, this might feel intimidating, but presenting your work is one of the best ways to showcase your impact. At Wix, n flows are presented to a room full of people from across the organization. Usually, the product manager or designer leads these presentations, but you're just as familiar with the UX and KPIs as they are.
When others present, content feedback is often minimal - unless something is obviously wrong. But when I present, I take the opportunity to walk people through tough messaging decisions. I read the copy out loud, share what I tried, and explain why we landed where we did. Sometimes, you have to be your own biggest advocate.
Ask your PM or designer if you can do the presentation. They might be thrilled to hand off that task. It’s a great way to establish yourself as a subject-matter expert, and display the importance of your role, to show you’re not just the "editor of words."
These three tips only scratch the surface. There are many ways to gain visibility for your work. Good writing is thoughtful. It takes time. And while everyone you work with writes in some form, not everyone writes with intention. If you want to get your “seat at the table,” first you have to let your colleagues in. Show them the work. And help them see that behind every great experience is a writer asking hard questions and making deliberate choices.
