<p>Published on <a href="https://blog.prototypr.io/designers-best-friend-5210bdefb1e6?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> Jason Fox </p>
<h4>The skills UX designers want their writers to have</h4>
<p>Not so very long ago, I was brand new to UX writing. I knew nothing. And I was, to put it lightly, very eager. 😬</p>
<p>In my impatience to please, I attempted to haphazardly learn every skillset the came anywhere near my role as a writer. My intentions were probably good. I didn’t want to be a burden.</p>
<p>Wouldn’t it be nice, I thought, if a designer didn’t have to burn an hour doing a copy and paste job for me.</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPzcS6-dPEu85CEddGA-Ag.png">Design boundaries are more impressive than design skills.</p>
<p>A couple YouTube tutorials later and I was directly editing design files. I widowed paragraphs, left orphan words, and meddled with buttons that shouldn’t have been meddled with. Version control went out of control. Our design process and workflow suffered. Burden not lifted!</p>
<p>I was learning in the most obnoxious ways possible that, to be a helpful writer, I needed to be an engaged communicator, an advocate for language, and sometimes, I even needed to be a pain in the ass. Sneaking around in the shadows to make copy edits without bothering anyone was an impossible game.</p>
<p>Finally I decided that instead of trying to read minds, I would ask any designer I could this one simple question: “What does your ideal writer bring to the table?”</p>
<p>So what have I learned? Well…</p>
<h3>Design skills are nice, but not necessary</h3>
<p>According to the UX designers I’ve spoken with, it’s far more important for writers to understand design fundamentals, UX principles, and communication techniques than it is to know their way around Photoshop.</p>
<p>Whenever possible, I prefer to develop copy in a rough mockup. At the very least, I like to have a visual representation of the interface I’m writing for. But the tendency to put your design 🎩 on for every writing assignment can be harmful to the collaborative process. After all, one of the most rewarding aspects of being a UX writer is having the opportunity to jam on strategy with your team.</p>
<p>Plus, there’s the chance that your good-faith design edits will suck.</p>
<blockquote><p>“If there’s a small tweak to copy and the copywriter can handle it, I’m all for that. However, having boundaries is important. The designer may have placed copy in a specific way and if the edits are larger, or alter the design of the copy (such as adding another line, or introducing a significantly longer word), that impacts design and should be handled by the designer.” — <a href="http://5ftkiersten.co/">Kiersten Clingersmith</a></p></blockquote>
<p><strong>Remember to have boundaries, folks!</strong></p>
<h3>Share your swipe files</h3>
<p>Rooted in marketing and advertising, a swipe file is a collection of proven copy elements, such as onboarding headlines, empty state body copy, transition <a href="https://uxdesign.cc/invision-a-microcopy-microstudy-cd13b8da9635">microcopy</a>, etc. It’s a reference point based on your favorite copy.</p>
<p>For writers, your swipe file is fertile ground for ideation and copy development.</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IkX04Djm7MhUWEydQZdgXA.png">“Like this? Or maybe like this…” <a href="http://uxarchive.com/">UX Archive</a> is an excellent place to start your swipe file.</p>
<p>Sharing swipes with your designer can help to align on messaging and copy parameters at very early stages of the design process.</p>
<h3>The uniter writer</h3>
<p>As a writer — and presumably someone with a background in communications — it may fall upon you to <em>communicate! </em>With colleagues, departments, customers, and yes, even investors 👻. Develop your interpersonal and cross-functional communication skill sets, because your team will invariably look to you to navigate <a href="https://medium.com/@JJFoxBox/inclusivity-in-writing-6d197a31e9ba">contentious topics</a>.</p>
<blockquote><p>“Designers can often struggle to wrangle the many teams they work with, but copywriting can help work as a bridge between those different mindsets. A skilled writer can successfully impart a message which balances the needs of business and user experience.” — <a href="http://www.gabepersons.com/">Gabe Persons</a></p></blockquote>
<h3>Understand data</h3>
<p>Here’s a fun story: An executive and a product manager get together one day and begin to commiserate on one very small piece of user feedback from usability testing. Two sprints later, morale is at an all-time low and the product is suffering.</p>
<p>Teams often stumble when it comes to understanding and applying field research. One or more stakeholders will fixate on something that one user said because it confirms their own biases.</p>
<blockquote><p>“Well, this one person didn’t like X, so I must be right about everything.”</p></blockquote>
<p>As a writer, having the ability to understand, analyze, document, and share data can help to keep a design process on track.</p>
<h3>Let me hear it</h3>
<p>What does your ideal writer bring to the table?</p>
<p><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=5210bdefb1e6" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="https://blog.prototypr.io/designers-best-friend-5210bdefb1e6">Designer’s best friend</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


Designer’s best friend

The skills UX designers want their writers to have

Top Stories