<?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 Brett Barnes on Medium]]></title>
        <description><![CDATA[Stories by Brett Barnes on Medium]]></description>
        <link>https://medium.com/@brett_23686?source=rss-aa47249deebd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*P9OQhzxwl1GqiGPlTr0qsg.gif</url>
            <title>Stories by Brett Barnes on Medium</title>
            <link>https://medium.com/@brett_23686?source=rss-aa47249deebd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:52:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brett_23686/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[Writing for Readability]]></title>
            <link>https://medium.com/@brett_23686/writing-for-readability-d01494ba4b84?source=rss-aa47249deebd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d01494ba4b84</guid>
            <category><![CDATA[content-creation]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Brett Barnes]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 14:48:04 GMT</pubDate>
            <atom:updated>2019-03-04T14:48:04.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5wTVu2yEmrU5OcwvoWPKVw.jpeg" /></figure><p>Reading is hard. We spend our entire time in school, from kindergarten to graduation, learning how to do it, and we still kind of suck at it.</p><p>As a UX writer, I always have to write for accessibility. It’s a requirement of the Americans with Disabilities Act (ADA). This means I have to write for an eighth-grade reading level — give or take a grade. If I’m doing my best, I want to land on a fifth-grade reading level. That’s the sweet spot.</p><p>But isn’t that insulting to adult readers? Nope. In a totally non-scientific poll, I asked people if they would rather cut an acre of grass with a pair of rusty scissors or a riding mower — 100% of respondents favored the mower. It doesn’t matter how educated and well-read a person might be; making things hard is just making things hard. Though I’m writing for accessibility, making the reading easy for everybody makes the experience better for everybody.</p><p>There are two things to consider when writing for readability: high-syllable density and compound sentences. You want to avoid both.</p><p>Don’t write a sentence with two independent clauses. Write two sentences instead. (See what I did there? I could have written, “Don’t write a sentence with two independent clauses, write two sentences instead.” But that would have given me a reading-grade level of 8.4. By breaking it into two sentences, it gave me a reading-grade level of 5.4.)</p><p>A high syllable count in a short sentence will kill readability.</p><p>Bad:</p><p><em>Avoid sesquipedalian words.</em>(Flesch-Kincaid Reading Level: 20.9)</p><p>Better:</p><p><em>Avoid long words.</em>(Flesch-Kincaid Reading Level: 1.3)</p><p>Two sentences, three words each, but one of them takes a Ph.D.to comprehend. (Again, it’s the syllable density, not the fact that no one knows what sesquipedalian means. Honest.)</p><p>You can test for readability in Microsoft Word, but you will need to turn it on. Go to <em>Preferences, Spelling, and Grammar </em>and check <em>Show readability statistics</em>. Hit the spelling and grammar button in the <em>Review ribbon</em>. Once the check is done, you will get a window with the reading statistics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*TsvB0pikOZU3MBhW0sF05A.gif" /></figure><p>One last note, if you highlight a single sentence, like a headline, to check readability, make sure it has closing punctuation like a period, or you’ll get a reading grade level of 0.0, and that would be false.</p><p>If you still think readability doesn’t matter, read Hemingway. He started as a newspaperman. He wrote for an audience of diverse reading levels. He wrote simple, declarative sentences. When he moved to novels, he kept that same style. Read a Hemingway novel, and you’ll have a hard time finding a comma, semicolon, or four-syllable word. Most of his work is written on about a sixth-grade reading level. It worked out well for him. It can work for you too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d01494ba4b84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Write Error Messages Customers Love]]></title>
            <link>https://medium.com/@brett_23686/write-error-messages-customers-love-df98a5b04e77?source=rss-aa47249deebd------2</link>
            <guid isPermaLink="false">https://medium.com/p/df98a5b04e77</guid>
            <category><![CDATA[error-handling]]></category>
            <category><![CDATA[error-message]]></category>
            <category><![CDATA[content-writing]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Brett Barnes]]></dc:creator>
            <pubDate>Tue, 19 Feb 2019 18:01:36 GMT</pubDate>
            <atom:updated>2019-02-19T19:12:12.835Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Z0jbFJtLLBSOg7zTFupyA.jpeg" /></figure><p>Error messages are the most difficult pieces of content to write. They tend to sound cold, or cutesy and schlocky. But finding that happy medium shows customers that you care about them, their time and that you pay attention to every detail of the experience. They can be an easy boost to your reputation.</p><blockquote><em>“Easy reading is damn hard writing.” — Nathaniel Hawthorne</em></blockquote><p>Before we dive in, here are some things to consider when tackling your error messages:</p><p>· Avoid error traps</p><p>· Don’t let your developers write your error messages</p><p>· Use velvet ropes instead of long messages</p><p>· You’ll only need one message for system errors</p><p>· Don’t help hackers</p><p>· Be delightful, but don’t get cute</p><h3>It’s a Trap</h3><p>Don’t let your design trap for your users. Too many times users will miss a tiny little checkbox in a sea of text and form fields. It’s a trap. They click the continue button and instead of continuing they have to read an error message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C0osfJ6wXfjegKmnr0ZL7g.jpeg" /></figure><p>Make that checkbox as big as the other input fields on the page. Then consider making it stand out enough to give users a chance to see it especially if the checkbox is near a button. We humans are like Pavlov’s dog when we see a button on our screens. Our conditioned response kicks in, and we want to hit it. A few users will still miss the checkbox, but at least you’ve done what you can to avoid dinging them with an error.</p><p>You’ll find lots of little traps like this, unnecessary buttons, and hidden checkboxes. Get rid of the buttons and fix those checkboxes. You don’t want to spend time writing unnecessary error messages, and your users certainly don’t want to read them.</p><h3>Don’t Let Your Developers Write Your Error Messages.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*4mwTyvvH7Y6d8V_skZ9Xyw.jpeg" /></figure><p>Oof. That’s bad. I can always tell when a developer has written an error message to help them diagnose code, and too often these messages get deployed to the production site. They usually contain words like “operation” or “invalid” and have a weird error code, “CDNToken.TokenError error 0.” The developers know what that means, but your users are left befuddled.</p><p>Talk to your programmers; they will usually have a spreadsheet with these error codes and the cryptic message they wrote for themselves. You will need to rewrite those messages. Developers are very talented, but they speak in machine language all day, don’t put them in the position of writing in human terms. It’s not their forte, and that’s okay. Keep in mind that you don’t want to write an error message for each code. It’s way too much maintenance. You will most likely find a spreadsheet with over one hundred error codes that can be combined into 5 or 6 messages that will be relevant for your users.</p><blockquote><em>“There are two types of errors: The ones the user can fix, and the ones they can’t.”</em></blockquote><h3>System errors — things the customer can’t fix</h3><p>Customers don’t need specifics when your system has a hiccup. You only need one message to let your users know that it’s you, not them. Again, you’ll need to talk to your developers and get a list of all the system errors they are capturing and the messages they have written for themselves for debugging. You don’t want these messages making it in front of your users, and one error message is much easier to maintain than dozens.</p><p>Amazon does it right, same message, different dog. Amazon knows that the first thing we humans do when we hit a snag is try again. We’ll get the same message, but a different dog. Amazon still needs to keep a database of pooch pics, but the payoff in delighting users makes it worthwhile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*yDEb3xpc3NZLPmUZ0Oc9oQ.jpeg" /></figure><h3>Validation errors — things the customer can fix.</h3><p>A validation error is usually for a field or checkbox that is missing expected information. A blank field that is required, an email field missing an “@,” an unchecked box, that sort of thing.</p><p>For validation errors, don’t tell your users what the problem is, show them. Give them a velvet rope that shows them what’s needed instead of giving them a message at the top of the screen that they have to read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*-BEMrmOngx-AM17Lopfcyw.jpeg" /></figure><p>Websites have gotten a lot better about this. Instead of an error message that sends a user on a hunting expedition; site pages will jump (focus) to the field that needs attention.</p><p>The great thing about this type of error, reading isn’t even necessary, it’s optional.</p><p>This velvet-rope methodology is becoming more standard across the web. Getting on board now will keep your user experience from looking as old fashioned as a home page that says, “Welcome to our home page.”</p><h3>Never Help The Hackers</h3><p>At my company, The Telecommunications Giant That Shall Not Be Named, security is a big deal.</p><p>When writing error messages, particularly around usernames and passwords, never tell hackers specifically what is missing. For example, when writing an error message for a username and password never say, “We don’t recognize that password. Please, try again.” If you do, you’ve just told a potential hacker she got the username right, and she doesn’t have to worry about it. You’ve just done half the hackers work for her.</p><p>As you experience the web yourself, and you encounter a username or password error message, read it. If it says something like, “We’re having trouble finding this <em>username or password</em>…” Your security is in good hands.</p><h3>Don’t get cute</h3><p>Error messages are bad news; humans are terrible at delivering bad news. As a result, we tend to be terrible at writing error messages.</p><p>At the very least, you can get by following this one piece of advice: Use plain, non-accusatory language, that isn’t cute or clinical. I’ve made a healthy career for myself turning corporate-speak, lawyer-language, and professional-prose into plain language that human beings readily understand. Don’t be afraid to say what you mean.</p><p>Also, never accuse a user of being incompetent. “You have entered an invalid email address.” This is a hallmark of lazy writing. Never use a personal pronoun unless it’s referring to yourself like Amazon does in their system error. It’s better to say something like, “We don’t recognize the email you entered. Please, try again.” It seems like a little thing, but we humans are automatically put in a defensive posture when the word “you” is used in connection to an error.</p><p>Finally, don’t get cute. “Oopsy woopsy we saw-wee!” This kind of thing usually comes with an image of a kitten hanging from a branch. Maybe the spread of messages like this was perpetrated by Big Monitor. I imagine lots of monitors get punched after seeing the hang-in-there kitten when all you want to do is pay your water bill. Clever writing should be left to the professionals, and professional writers rarely show how clever they are in error messages. It’s not the venue. Customers just want the facts.</p><p>Talk to your designers before they start designing. Content strategy comes first and catching the error traps is a big part of that. Work with your programmers and rewrite and reduce the error messages they wrote for debugging. Finally, hire a professional UX writer. Sure, you’ve got a keyboard, but it doesn’t mean you can wield it like a surgeon’s scalpel. Leave error messaging to the professionals. It will give your reputation an easy coat of polish and give you a leg up on the competition.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df98a5b04e77" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>