<?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 Scott Wilson on Medium]]></title>
        <description><![CDATA[Stories by Scott Wilson on Medium]]></description>
        <link>https://medium.com/@sjw102984?source=rss-adb840b57c24------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Wt_x1240N5Ui5psC</url>
            <title>Stories by Scott Wilson on Medium</title>
            <link>https://medium.com/@sjw102984?source=rss-adb840b57c24------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:14:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sjw102984/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[Dispatch from Pebble Beach]]></title>
            <link>https://medium.com/@sjw102984/dispatch-from-pebble-beach-c818e6fc2c8d?source=rss-adb840b57c24------2</link>
            <guid isPermaLink="false">https://medium.com/p/c818e6fc2c8d</guid>
            <category><![CDATA[golf]]></category>
            <category><![CDATA[pebble-beach]]></category>
            <category><![CDATA[journal]]></category>
            <dc:creator><![CDATA[Scott Wilson]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 15:09:13 GMT</pubDate>
            <atom:updated>2026-04-22T15:09:13.210Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LguakTS3VLnxYiSlwZ0q4g.jpeg" /><figcaption>The iconic 7th hole at Pebble Beach</figcaption></figure><p><em>Warning: This article contains specific details about one round of golf from an average golfer. If that sounds as exciting to you as watching paint dry, just skip every other word.</em></p><p>The best day I’ve ever had on the golf course started well before the sun came up. I had the third tee time of the day at Pebble Beach. Actually, it started well before that. When deciding what to do for my dad’s 75th birthday, I had the thought of trying to play Pebble Beach, but I didn’t necessarily think I could make it work. After sorting out some details, I booked the trip, and had to keep the secret for more than 6 months. A long time to wait, but at last, the day was finally here.</p><p>We left our hotel (Spanish Bay) around 5:45 am to make the quick drive to Pebble, and didn’t see another soul around the property as we dropped our bags off in the pitch dark. After a great breakfast at the empty Gallery restaurant next to the first tee, we got in a very quick warmup (the shuttle to the practice range was nowhere to be found), and then made it to the first tee.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Ftif2a1XBap2SU_UOuOpA.jpeg" /><figcaption>The first tee at Pebble Beach</figcaption></figure><p>My dad and I met our caddie, Yannick, and the other two lucky guys getting to play that morning. We got the speech on the first tee about having fun and playing ready golf. Then it was finally time to hit that first tee shot at Pebble. I can’t say that my first shot was majestic. It was short and left and almost made it to the lodges. I ended up in the left greenside bunker in 3 shots, and thought I hit a pretty good bunker shot, only to see it roll across the green and into another bunker. Triple bogey start. At this point, I was thinking that I wasn’t good enough to play a course of this caliber.</p><p><em>Just to clarify: I’m a 17 handicap. Which means that I’m a better golfer than most people you see at the neighborhood driving range, but not a great golfer by any means.</em></p><p>I was able to settle down for bogeys on 2 and 3, and at some point realized, “hey, this is just golf!” Golf with amazing views and incredible history. The fourth hole was sloppy and led to a double bogey. Then I hit my best shot of the day so far on the par 3 5th. A 7-iron that was heading right for the flag. The other members of my group thought a hole-in-one might be coming. Alas, it rolled out to 30 feet past the hole. The dream of having my first hole-in-one come at Pebble would have to remain just that: a dream. I settled for a par.</p><p>The 6th hole is a famous par 5 that has a very large hill you must hit up on your second shot. I hit a great drive, but didn’t have the 200-yard-shot-that-goes-really-high in my arsenal, so my second shot clattered into the hill, only making it about a third of the way up. I thought I hit a pretty good third shot, but had no idea where it went. When I got to the top of the hill, I still couldn’t find it. Unfortunately, it trundled into the right bunker. That led to another double bogey.</p><p>One thing that I haven’t talked about yet is the weather. When you book a bucket list round of golf months in advance, you’re really rolling the dice. If our round had been scheduled two days earlier, we would have been playing through a lot of wind and rain. On this day, the weather was perfect. Low winds and lots of sunshine (with just a brief 2-minute shower).</p><p>Back to the round. Now we’ve reached the shot I’ve been looking forward to playing the most. The tee shot on 7 — a par 3 measuring 94 yards. The execution here wasn’t great. I hit it a bit thin and out to the left, ending up in a bunker. I had to make a good putt just to make bogey. Then it was a short walk to the terrifying 8th hole. I hit a good drive and was in a great spot for the famous second shot over the water. I tried to play a safer shot out to the left with a 6 iron, but caught it thin and it didn’t quite clear the hazard. I thought for a minute that I’d still be able to play the ball from the thick rough surrounding the water, but I couldn’t find the ball. Double bogey.</p><p>This was the turning point in the round, when I started to get things in gear. I hit a nice and long (for me) drive on 9, and only had an 8 iron in for my second shot. I made an easy bogey. On 10, I got up and down from the bunker, making a long putt for bogey. On 11, I made another nice putt for another bogey. Bogeys are good for me — it’s the scores worse than bogey that I’m trying to avoid.</p><p>Then I came to the tough par 3 12th hole. I took out a 3 hybrid, trying to aim to the right, away from the bunkers guarding the green. I hit it just where I was aiming, and it took a great bounce, rolling up to about 8 feet from the hole. For the third straight hole, I made my putt. Birdie. At this point I’m thinking whatever happens from here on out is gravy. I made a birdie at Pebble Beach.</p><p>I don’t remember anything about what happened on the 13th hole, but I made another bogey. The par 5 14th is one of my favorite holes at Pebble. We were fortunate to get a more forgiving pin on the right side of the green. It took me four shots to get on the green, but I made my putt for par. Another highlight for me.</p><p>I hit my only really bad drive on 15, and almost took out a FedEx truck with my provisional (I thought my original drive was in a hazard). Thankfully, my caddy found the first ball — it had made it through a bush and into the rough. I was able to turn near-disaster into a bogey. The 16th was my only really bad hole on the back 9. I pulled my second shot into a tree, and had nothing for my third shot. I had to chip out sideways, and didn’t execute the next shot well, so I ended up with a triple bogey.</p><p>Just two holes left, and they are both quite famous. We did not get an easy pin on 17. It was the traditional Sunday pin on the far left part of the green. I did not hit a good 5 iron off the tee, and ended up in the front bunker. However, I hit my best bunker shot of the day and had a realistic putt at par. I missed it, but was happy with a bogey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KjQSSND4kp_SH-WCHJaBTQ.jpeg" /><figcaption>The intimidating 18th tee</figcaption></figure><p>Now it was time for that intimidating tee shot on the 18th hole. It didn’t help that the wind, which had been calm all day, was now picking up right into our faces. I couldn’t help but laugh as one of the guys who teed up before me hit his drive so far out into the ocean. I let out an exhale as my drive went safely down the right side of the fairway. I tried to play the hole as smartly as I could, not forcing the issue and playing away from the water as much as possible. I hit four solid shots onto the green, and had a good chance at par. Unfortunately, I did not hit a very good par putt. But I was okay with bogey. That added up to a 93 – 49 on the front, 44 on the back.</p><p>Golf can often be frustrating. You linger way more on the bad shots and missed opportunities than the good ones. There’s always a way you could have done better. But on this day, golf was fun — magical, even. The next day at Spyglass Hill didn’t go quite as well — too many bad holes (although I did have another birdie!) — but it was still an unforgettable trip. And even though this was a once-in-a-lifetime trip, I wasn’t off the golf course yet before I started trying to figure out how to come back.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c818e6fc2c8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How UX writers decide when not to write]]></title>
            <link>https://medium.com/carmax-ux/how-ux-writers-decide-when-not-to-write-001f3730f5b2?source=rss-adb840b57c24------2</link>
            <guid isPermaLink="false">https://medium.com/p/001f3730f5b2</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Scott Wilson]]></dc:creator>
            <pubDate>Thu, 29 Jan 2026 15:50:05 GMT</pubDate>
            <atom:updated>2026-01-29T15:50:05.495Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndh2LH_b_YNewFLkh-P6QA.png" /></figure><p>When’s the last time you had a really good experience buying something online? Think about what was memorable about it. Let me guess: the site had exactly what you were looking for, and you got a really good deal. Maybe your transaction was fast and easy. I make my living as a UX writer, so I would love it if you said that the wonderful microcopy on the website was the highlight of your experience. But I’ve come to grips with the fact that it’s probably a good thing if my work isn’t memorable.</p><p>Like an offensive lineman in football (or countless other jobs), most people only notice our work when something is wrong. A spelling error, unclear directions, an inappropriate tone for the action we’re taking: there are many ways microcopy can stand out in a bad way. As a UX writer, you can spend a lot of time trying to look for the perfect way to say something that everyone will understand. I’ve learned over the years that sometimes you have to recognize when saying nothing is the best approach. Here are some examples of when it’s okay to tell your product team that you recommend little or no copy:</p><p><strong>Home pages</strong></p><p>The home page is the entry point for so many people to your website, so it’s reasonable to think that you need to show something about who you are on that page. Maybe it’s explaining your mission or how your website works. But if you’re an e-commerce site focused on conversion, your primary goal is to show your product and get customers to click through to buy. Giving the customer too much information right off the bat can be overwhelming.</p><p>Do some research: take a look at some of the most popular retail sites out there and look at how much copy they have. What you’ll find is a lot of pictures of products and maybe some headers grouping types of products together. They’re able to communicate their brand in a subtle way, without overdoing it on the copy. See how Amazon weaves in “free, one-day delivery” as a benefit without the copy getting in the way of their inventory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/1*WCVKSVfzmwleTcVvwoZWCw.jpeg" /><figcaption>Amazon’s home page isn’t over-reliant on copy</figcaption></figure><p><strong>Confirmation screens</strong></p><p>Let’s go from the start of the journey on your website to what’s likely the end. Your customer has ordered your product, and they get to a confirmation screen. There is a tendency to put too much information here. All your customer is really looking for is something that tells them their payment just went through. A simple “we got your order!” should suffice. Throw in a picture of the product and a way to keep track of their order, and that’s it. Don’t overthink it.</p><p><strong>Error pages</strong></p><p>Error pages are also places where we either try to convey too much information or be too cute. Remember that the most likely emotion your customer is feeling in this moment is frustration, because they’re trying to go somewhere and hit a roadblock. The best practice here is to just tell them why they’re seeing this page and give them a clear way to proceed.</p><h3><strong>When it’s okay to have more copy</strong></h3><p>Don’t worry, UX writers. You will still have plenty of chances to flex more of your writing muscles. Here are some pages where it’s okay to be more copy-focused:</p><p><strong>Complicated instructions</strong></p><p>Maybe your product is a game-changer, but there’s a bit of a learning curve to use it. The page where you give customers specific instructions is not a place where you want to try to save space on copy. If they need to know how to use something, they’re going to read every word of your instructions. You don’t want to risk an influx of angry calls or returns to create something that might be a little more visually pleasing.</p><p><strong>Checkout pages</strong></p><p>This is the last hurdle to clear before the customer gets to the finish line. Don’t trip and fall in this moment. When they’re hovering over that button that says “Place your order”, you want to make sure there’s nothing left to the imagination. Your page doesn’t need to be the length of a CVS receipt, but it should give all the details of what the customer is paying for.</p><p><strong>Legal compliance</strong></p><p>It shouldn’t come as a surprise to UX writers that something legal-related is on this list. When it comes to legal requirements like terms and conditions or disclaimers, we often can’t skimp on the words. But that doesn’t mean that writers shouldn’t push to see where they can compromise with legal partners. Are there ways to simplify what legal requires? Once you’ve reached an agreement, find the best place to put these so that they won’t interfere with the customer’s progression, while still staying compliant.</p><h3><strong>Conclusion</strong></h3><p>One important aspect of every UX writer’s job that I haven’t talked about so far is the ability to develop relationships. And probably the most important relationship that you can develop is the one with your designer. When deciding how to prioritize copy and design, it needs to be a true collaboration between the UX writer and the designer. Using fewer words on certain pages only works if the visual elements help guide the user along. Once you’re able to find that harmony between the pictures and the words, your customer will start to remember you for the right reasons.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=001f3730f5b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/carmax-ux/how-ux-writers-decide-when-not-to-write-001f3730f5b2">How UX writers decide when not to write</a> was originally published in <a href="https://medium.com/carmax-ux">CarMax Experience Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design sprint feel overwhelming? Try this instead]]></title>
            <link>https://medium.com/carmax-ux/design-sprint-feel-overwhelming-try-this-instead-e9ff09375fcb?source=rss-adb840b57c24------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9ff09375fcb</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[content-design]]></category>
            <dc:creator><![CDATA[Scott Wilson]]></dc:creator>
            <pubDate>Tue, 24 Sep 2024 19:16:04 GMT</pubDate>
            <atom:updated>2024-09-24T19:16:04.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wFUFlOFtDQs2jqRQf9jwEw.png" /></figure><p>Does this sound like your workday? Meeting followed by meeting, with an hour fit in there somewhere to knock out as many items as you can from your to-do list. Maybe 30 minutes for lunch. You’re caught in the wheel of meeting OKRs and getting the next release out and extinguishing small fires. When do you have time to take a breath, step back, and actually try to make your product or experience better?</p><p>You may have heard of a design sprint. Product teams clear their calendars for a week and really dig into finding solutions for a problem. I’ve been part of a few of these in my time at CarMax, and they can be fun. You bring in guest speakers, take time to compile inspiration from other companies, and go through different sketching exercises. At the end of the week, you could come up with a really great solution that you want to start developing.</p><p>So, what’s the problem? When was the last time you had a whole week to focus on just one thing? While you’re spending all this time in your design sprint, you’re thinking about everything else you have to do that isn’t getting done. And if you’re one of the organizers, you’re not just dedicating time to it during that week. It takes a lot of time to create a valuable agenda.</p><p><strong>Find a happy medium</strong></p><p>How can you find a happy medium? Try this: Set aside two hours each day for a week. Have a very focused and time-boxed agenda. Call it a workshop. You’ll be surprised how much you can get done. A couple of keys here right off the bat:</p><p>1. It should be a problem space that you’re highly familiar with. You aren’t starting from scratch. You’ve built this product, and it’s been out in the wild for a couple of years. You just want to make it better.</p><p>2. Keep the guest list short. Having a lot of heads together working to come up with ideas can be great, but also takes up a lot of time. Limit the workshop to just your product team (no stakeholders).</p><p><strong>Planning your workshop</strong></p><p>Now that you know that you want to have a workshop, how should you structure it to make the best use of your time? Feel free to customize the schedule to your needs, but this is a good place to start:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*2uGCm7bPEKwwlQA-nSOcOA.png" /></figure><p><strong>Day 1: Map out the problem</strong></p><p>You probably have a good idea going into the workshop what space you want to tackle. But this is where you take the time to make sure the whole group knows what direction you want to head. Does this work tie in with an OKR? Review the exact language of the OKR with the group. Remind everyone what your current experience looks like. And lean on your analyst. Have them prepare an analytics share-out so the group can see where the opportunities lie.</p><p><strong>Day 2: Talk to your customers</strong></p><p>The team is aligned on what you’re going after, so now you can talk to your customers. Use this time to identify any pain points you might not have considered. Use a variety of methods to get customer feedback. Do a mix of moderated and unmoderated discovery. Talk to customers on the phone. Start with more general questions about their experience. You might get some valuable insights just by letting them talk instead of asking a lot of specific questions. Having trouble getting customers who are willing to talk with you? Grab a co-worker from a different part of the company and get their thoughts. Watch people use your website. Where are they rage-clicking? Where are they getting stuck? Encourage the whole team to take notes on what they see and hear as you go through discovery. The goal is to build a good list of problems and ideas.</p><p><strong>Day 3: Brainstorm solutions</strong></p><p>Now that you’ve gathered all the information you need, it’s time to start thinking of solutions. Narrow down the problems you’ve identified to one or two that you want to solution for. Have each team member work on a sketch of what that solution would look like. Say you’re an e-commerce business that’s having trouble getting customers to convert from putting an item in their cart to checking out. You’ve identified the problem as a confusing payment information screen. Give each team member 20 minutes to sketch out their idea for a better payment screen. Let them work with whatever medium they feel most comfortable with — that could be anything from Photoshop to pen and paper. Have each team member share their sketch. Take note of what you like about their ideas, because you’re going to use those best ideas to build your prototype in day 4.</p><p><strong>Day 4: Build a prototype</strong></p><p>Start the day by revisiting those best ideas from the team’s sketches. You should be able to incorporate a lot of them into your prototype. Depending on how your ideas landed, you could have the whole team work on one prototype or break the team in half to work on two prototypes. Don’t be afraid to break out of your normal product team roles, especially if you’re splitting into two groups. Your developers may end up designing and writing copy, and that’s okay. You don’t need something that’s super high fidelity. Your primary goal is to get feedback. Once your prototypes are done, plan how you’re going to do round two of discovery. You can put it before users on a site like UserTesting. Or you could just show the prototype to your friends and family and get their feedback.</p><p><strong>Day 5: Test and learn</strong></p><p>The last day is all about finding out what people think of your prototype. If you put it into UserTesting, watch the videos of the UserTesting sessions with your team. Make note of any positives or negatives you hear. If you had your team do friends and family feedback, have each person share what they learned. Understand that you aren’t going to get everything right on the first try. Use this as a starting point from which you can keep iterating until you get the solution you want. Take whatever you decide to move forward with and pull it into your regular product discovery life cycle. And keep testing and learning!</p><p><strong>Adapt to fit your team’s needs</strong></p><p>As you’re trying to decide how to tackle the next opportunity space with your team, know that this is just one possible solution. Want something that takes only three days instead of five? You can take elements of what I outlined above to create your custom schedule. Maybe you’d rather combine mapping out the problem and talking to customers in one day. Maybe you have a recent discovery session you can refer to and don’t need to do fresh calls. Hopefully you’ll find that you don’t have to take up too much time to break out of your weekly sprint rut and come up with some inspired solutions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9ff09375fcb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/carmax-ux/design-sprint-feel-overwhelming-try-this-instead-e9ff09375fcb">Design sprint feel overwhelming? Try this instead</a> was originally published in <a href="https://medium.com/carmax-ux">CarMax Experience Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why UX Writers Have to Learn to Be Less Polite]]></title>
            <link>https://medium.com/carmax-ux/why-ux-writers-have-to-learn-to-be-less-polite-de2cfb08e912?source=rss-adb840b57c24------2</link>
            <guid isPermaLink="false">https://medium.com/p/de2cfb08e912</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[carmax]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Scott Wilson]]></dc:creator>
            <pubDate>Thu, 27 Jan 2022 19:57:00 GMT</pubDate>
            <atom:updated>2022-01-27T20:20:34.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*13q5FrO2NJAlf-28E1CXRw.jpeg" /></figure><h4>Because you don’t want anything distracting from your message</h4><p>When I was very young, one of the books I can remember reading all the time was Richard Scarry’s “Please and Thank You Book.” Do you remember this one? This is the book’s description: the animal residents of Busytown learn useful lessons about manners, thoughtfulness, and caring. Since I’ve been a UX writer, I’ve had to unlearn those lessons. It’s not because I’m trying to be a bad person. It’s because a lot of that polite language can get in the way of a good user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*_ph62cu0Amln1byUJ-uONA.jpeg" /></figure><h4><strong>Stick to the principles</strong></h4><p>A UX writer looks at copy through the lens of these three core principles:</p><ul><li>It needs to be clear.</li><li>It needs to be concise.</li><li>It needs to be useful.</li></ul><p>You may think you are being friendly by saying “please” and “thank you,” but does it follow any of these principles?. Think about how many times you ask someone to perform an action on your website. If you start adding “please” and “thank you” every time you want a user to perform an action, that will get out of hand quickly. When you are dealing with people who have limited attention spans and are just scanning your website on their phones, it’s important to be concise. That’s why websites say “username” instead of “please enter your username.” Use the minimum number of words you can to get across what the user needs to do.</p><p>The same goes for “thank you.” When you order a cup of coffee on a mobile app, what information do you need to confirm that your order went through? Probably a short message that says they received your order for a latte, and it’s going to be ready at 8:30 a.m. Your users aren’t looking for a thank you for giving you their business. So why put it in your copy?</p><p>Of course, there are occasions where you do want to express gratitude to your users. Say they just made a generous donation to your business. A thank you in that scenario is welcome. If you are in the habit of over-thanking, that lessens the impact when you do show gratitude.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mtDA0OMVEDhHPgj87-fsrw.jpeg" /></figure><blockquote><strong>“Good UX writing means never having to say you’re sorry”</strong></blockquote><p>That paraphrased quote from the movie “Love Story” may be a little extreme. But let’s talk about the word “sorry.” A good place to start is sociologist Maja Jovanovic’s <a href="https://ideas.ted.com/sorry-to-bother-you-but-do-you-say-sorry-too-much-what-to-say-instead/">TED Talk</a> on the issue. She asserts that when we constantly apologize for something, it can make us appear more timid and less confident. Think about when you go out to eat. Do you want a server who’s saying “I’m sorry” all the time?</p><p>“I’m sorry to keep you waiting.”</p><p>“I’m sorry your order is taking longer than expected.”</p><p>“I’m sorry, we’re out of the tiramisu.”</p><p>An experience like this doesn’t inspire a lot of confidence in that restaurant. Similarly, a user won’t have a lot of confidence in your website if you are repeatedly apologizing.</p><p>If you’re going to use the word “sorry” in your copy, be very judicious about it. Save it for instances when you are at fault for a bad experience. Don’t apologize for something that is out of your control.. Remember that your user is probably scanning your site, and when they see the word “sorry” they’re going to assume you did something wrong that’s keeping them from where they want to go.</p><p>As UX writers, we have to focus on progressing the user and navigating around roadblocks. Instead of saying “sorry, we’re out of iPhones,” focus on moving the user forward. What’s the next step we can get them to take? Maybe it’s getting them to reserve an iPhone so they can get one as soon as it’s back in stock. If you’re able to spin what could be a negative into a positive, you’re more likely to keep that user around and improve your conversion rates.</p><h4><strong>Get right to the message</strong></h4><p>Cutting out polite language, or any unnecessary words, comes back to one thing: we need to get right to the message. One good practice as a UX writer is to look at a piece of copy and see how many words you can remove without changing the message. You’d be surprised how few words it takes for someone to understand what you are trying to get them to do. Try it yourself: go to one of your favorite websites and see how many unnecessary words you can find. It’ll make you a better writer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de2cfb08e912" width="1" height="1" alt=""><hr><p><a href="https://medium.com/carmax-ux/why-ux-writers-have-to-learn-to-be-less-polite-de2cfb08e912">Why UX Writers Have to Learn to Be Less Polite</a> was originally published in <a href="https://medium.com/carmax-ux">CarMax Experience Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>