<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Christopher Nosko on Medium]]></title>
        <description><![CDATA[Stories by Christopher Nosko on Medium]]></description>
        <link>https://medium.com/@chrisnosko?source=rss-1bbfedd10cdb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eO3crZFtKVm9KwQSHJZC_w.jpeg</url>
            <title>Stories by Christopher Nosko on Medium</title>
            <link>https://medium.com/@chrisnosko?source=rss-1bbfedd10cdb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:00:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrisnosko/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[6 steps to creating a UX writing style guide]]></title>
            <link>https://medium.com/wrike-design/6-steps-to-creating-a-ux-writing-style-guide-549a1eafbde5?source=rss-1bbfedd10cdb------2</link>
            <guid isPermaLink="false">https://medium.com/p/549a1eafbde5</guid>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Christopher Nosko]]></dc:creator>
            <pubDate>Fri, 14 Jan 2022 09:36:58 GMT</pubDate>
            <atom:updated>2022-01-19T08:32:33.411Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aRk6Ri8CgVNivkNZDZcFnw.png" /></figure><p>It’s Thursday. You’re sitting in your 6th meeting of the day. Your designer asks you “Hey! When you have a bulleted list, are we supposed to put a period on the end of every bullet point?”</p><p>You freeze. You wrote a list in an interface about 2 weeks ago, but you can’t remember where in the platform you did it. You <em>could</em> dig around in Figma for a while trying to find what you wrote, or you can make a list of rules (also known as a <strong>style guide</strong>).</p><h3>What’s a UX writing style guide, and why is it important?</h3><p>Similar to design systems for designers, style guides are a list of rules for writing or behaviors. Here’s are just some of the ways they help you and your team:</p><ol><li>They help UX writers maintain consistency, freeing up mental capacity for other things</li><li>They help people answer some of their own questions, taking pressure off the writers</li><li>You can point to the rules if someone on a team has a question about how things work</li></ol><p>When I first got to Wrike, we didn’t have an official UX writing style guide. There were a couple of guides that some people in marketing had started to put together in the past, but they were never finished, outdated, or the UX writing portion was only about a paragraph or two long.</p><h3>How to create (and maintain) a style guide</h3><h4>1. Try getting inspiration from other sources</h4><p>Check out some famous style guides. See what kind of rules they’re making, and think if those topics apply to you (just make sure you give them credit).</p><p>Here are some of the style guides that were influential to me:</p><ul><li><a href="https://polaris.shopify.com/content/voice-and-tone">Shopify Polaris</a></li><li><a href="https://styleguide.mailchimp.com/">Mailchimp</a></li><li><a href="https://material.io/design/communication/writing.html#principles">Material Design</a></li></ul><p>See how they’re approaching Voice and Tone, components, empty states, and things like that. If they allow you to borrow certain parts of their guide, just make sure you give them credit in your guide.</p><h4>2. When you make a decision, write it down</h4><p>This will help you set a precedent that you can point to in future situations. But keep in mind, just because you made a decision, it’s not set in stone. You can still review and change rules from time to time when faced with better methods or if new developments change things.</p><p>If you don’t have time to create the rule when you’re making the decision, I recommend keeping a list of the rules you want to create later (as a Wriker, I obviously use Wrike for my list).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItmP3V9yVHk83HuDyq-UWw.png" /></figure><h4>3. Add visual examples from the product</h4><p>Grab real examples from product designs. I like creating Do / Don’t visuals, like this one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q6P4LrK2Wh8DYzw7zGSVlg.png" /></figure><p>You may need your designers for this one, so don’t be afraid to ask them for help.</p><h4>4. Go over your rules and ideas with your designers</h4><p>It’s great to get input from people who will actually be using your guide. If you have more than one UX writer, great! Create and discuss these rules with them so you can all be on the same page.</p><p>Other than writers, the people who will probably be using this guide the most will be your designers. Guides will help take some pressure off your writing team by giving designers a place to answer some of their own questions without needing to reach out to you every time.</p><p>I recommend sitting down with a few designers that you’re comfortable with and hearing their thoughts on your rules and ideas before presenting the guide to your team. Make sure the rules are easy to understand and make sense to them.</p><p>Your designers can also give you more ideas for the guide, like frequently occurring messages that you can make templates for. For example:</p><ol><li>No internet messages</li><li>“Sorry, we’re having a tech issue on our side” messages</li><li>No search results</li><li>Empty states</li></ol><h4>5. Make it easy to find (and use)</h4><p>When I first created my guide, one mistake I made was thinking that all I needed to do was post a link in our design Slack channel, and I was done. Unfortunately, that wasn’t the case.</p><p>When I noticed some mistakes that I’d made rules for popping up pretty often, I made a survey asking my designers if they knew where to find the guide. Less than 25% of them knew where to find it, and only a couple of them actually used it. So, I made sure to add bookmarks in different places that our team worked so they could find it more easily and made some adjustments to make it easier to use.</p><p>When I sent the survey again, 80% of designers said they knew how to find it, and 60% said they used it in their work.</p><h4>6. Pick the right tool for your guide</h4><p>If you just have a simple guide, it can maybe live in Google Docs. But, if your guide has a lot of content, I usually recommend choosing a tool to help organize your style guide and make it easy to use. I decided to use <a href="https://zeroheight.com/">Zeroheight</a>, because it checked a lot of my boxes:</p><h4>Is it easily searchable?</h4><p>If a writer or designer comes to your guide with a question on how to format dates, is there a search tool in your guide that will help them find their answer?</p><h4>Does it link to Figma?</h4><p>Sure, you can just take screenshots of your mocks and paste or upload them into your guide. But, if your tool can link to your actual Figma frames, any changes made in your Figma file can immediately change your guide. Plus, if anyone looking at the guide wants to go to the actual Figma frames, all they have to do is click the image in your guide to go directly into Figma.</p><h4>Does it support text formatting (like bolding, underlining, etc.)?</h4><p>See how much of a difference a platform that offers good text formatting can make.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hBsB-ICwvhBEgHrroJNFfA.png" /></figure><h4>Can it link to specific places in the guide?</h4><p>When you’re discussing a rule with someone, you want to be able to send them a link that goes directly to the specific part or page in the guide.</p><h3>And that’s it!</h3><p>After all that, you probably have a pretty great start to a style guide. Remember, this isn’t all set in stone — this guide <em>should </em>be a living, breathing document. If you have a rule written down, and someone is able to come to you with a well-reasoned argument as to why the rule isn’t ideal, it’s absolutely fine to reconsider and change the rule.</p><p>Happy writing! ✍️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=549a1eafbde5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wrike-design/6-steps-to-creating-a-ux-writing-style-guide-549a1eafbde5">6 steps to creating a UX writing style guide</a> was originally published in <a href="https://medium.com/wrike-design">Wrike.Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>