<?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 andy healey on Medium]]></title>
        <description><![CDATA[Stories by andy healey on Medium]]></description>
        <link>https://medium.com/@andyhealey101?source=rss-315681a4091c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tNyC3V4MhEV64et0.jpg</url>
            <title>Stories by andy healey on Medium</title>
            <link>https://medium.com/@andyhealey101?source=rss-315681a4091c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:24:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andyhealey101/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[How to get a job with Shopify UX]]></title>
            <link>https://medium.com/@andyhealey101/how-to-get-a-job-with-shopify-ux-fc07161bb982?source=rss-315681a4091c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc07161bb982</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[interviewing-tips]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[andy healey]]></dc:creator>
            <pubDate>Wed, 25 Aug 2021 14:17:19 GMT</pubDate>
            <atom:updated>2021-10-27T09:44:06.523Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An illustration showing a maze in the shape of the Shopify UX logo — a winking face. A man stands at the entrance of the maze looking ahead to the end where a black woman is waving a flag. Trees flank the maze." src="https://cdn-images-1.medium.com/max/1024/1*EO-MYRZSvAa196DdvgzWCw.png" /><figcaption>Illustrations by Alisha Giroux.</figcaption></figure><h4>A four-step guide to take you from interested to interviewing</h4><p>In the summer of 2017, on the back of a tweet from <a href="https://twitter.com/amythibodeau">Amy Thibodeau</a>, I speculatively applied for a role as a Content Strategist at Shopify. I had literally no expectation of it going anywhere. Zilch. Zero. I mean this was Shopify, with its famous <a href="https://polaris.shopify.com/">Polaris design system</a> and roster of high-profile UXers.</p><p>I’d read that only 0.03% of people who applied to Shopify were hired. They’d surely want people who came from Apple or Google? Not me, from a relatively unknown tech firm based in England.</p><p>But apply I did and, as always, I tailored my application to the job. Sure, my current job title wasn’t Content Strategist, but I’d <a href="https://uxdesign.cc/how-to-make-ux-writing-a-thing-in-your-org-2b802576b702">made UX writing a thing at my company</a> over the previous two or three years. I’d been doing all the things that the job ad mentioned. So, I made sure that my resume was aligned to the job ad, and included a short covering letter saying why I’d love to work at Shopify.</p><p>A month later, I was on holiday on a small island with limited internet, and I received an email with the enigmatic subject line “<em>Shopify</em>”, proposing a first interview the following week. Less than seven days later I sat in my hotel room, batting away mosquitos in the tropical heat while speaking with Shane from the Talent Acquisition (TA) team at Shopify. And a few months later I was flying to Montreal, Canada, to start my new job.</p><figure><img alt="Email from the recruitment team at Shopify proposing an interview" src="https://cdn-images-1.medium.com/max/1024/0*sTIPel1Ae3n6DBQW" /><figcaption>The email that changed my life.</figcaption></figure><p>Fast-forward a few years and I’m now a UX Manager, hiring for folks to join my team. And it’s not just me who’s hiring: Shopify is growing at a fast clip. At any given time we have multiple positions open for a range of roles and levels of experience. Over the last 12 months I’ve been in 10s of interviews, I’ve read 100s of resumes, and looked through 1000s of LinkedIn profiles.</p><p>So why am I writing this now? Because we don’t want the interview process to be scary and unknown. I want to help you to show us why we should hire you.</p><p>This four-step process isn’t a prescriptive list, and, as you’ll see, I encourage you to make your application personal. If you’re serious about joining the Shopify UX team, there are some basics that you’ll want to do.</p><h3>1. Before you apply</h3><p>You’ve seen a job at Shopify, maybe someone you met at a conference sent you a link, and you’re buzzing to get your application in. Slow down for a moment. Before you apply, the first thing that you’ll want to do is to <strong>read the job ad again</strong>.</p><p>Do your skills match the job description? Is there a location mentioned? A level of seniority? Let’s unpack this a little.</p><h4><strong>Location</strong></h4><p>Shopify is Digital by Default. This means that unless a job is specifically marked as <em>not remote</em>, then it will be work from home (WFH). Before you apply, ask yourself if you like the freedom of WFH, or if you prefer to work in a bustling office.</p><p>While the jobs are remote, many teams are built around folks sharing the same core hours; in other words they’re located in the same or similar time zones. So if the location is marked as Americas, that <strong>doesn’t</strong> exclude Europeans, but you may be expected to work hours that line up with your North American-based colleagues. Great if you’re a night owl, not so great if you do your best work at the crack of dawn.</p><figure><img alt="Screenshot of the Shopify careers website" src="https://cdn-images-1.medium.com/max/1024/0*SH4xbzduSGXFcVS7" /><figcaption>Visit <a href="https://www.shopify.com/careers"><em>shopify.com/careers</em></a><em> for the latest open roles.</em></figcaption></figure><h4><strong>Seniority</strong></h4><p>There are a few levels that we hire at. The recruitment process at Shopify is conducted with high care, and we do our best to fit people to roles, but you’ll increase your chances by applying for the right job. Our hiring team prioritizes the most important roles to fill every three months. So if there’s not a role that you’re interested in right now, keep checking!</p><p>It helps to apply at a level that matches your experience.</p><ul><li><strong>Intern</strong> — You’ll have some relevant experience, either through your studies or work experience. The application process for interns is every quarter and you’ll be expected to demonstrate that you can bring value to your team.</li><li><strong>Content/Product Designer</strong> — You’ll need some years of direct experience and/or clear transferable skills. Even if you don’t have the same job title you might have the right experience.</li><li><strong>Senior Content/Product Designer</strong> — You’ll have multiple years’ direct experience of working in a UX role at least at a senior level.</li><li><strong>Staff Content/Product Designer</strong> — You’ll have many years’ direct experience of working in a UX role at very senior levels. You’ll be expected to lead the development of UX within your product area, and mentor other UXers.</li><li><strong>Content Manager/UX Manager</strong> — The same seniority level as a Staff Content/Product Designer, you’ll have experience leading a team of UXers.</li></ul><h4><strong>Job description</strong></h4><p>Can you do this job? Do you have the skills and experience required?</p><p>If you’re a Product Designer then you’ll likely have the most success with a Product Designer role. If there isn’t a Product Designer role advertised right now then hang on, there will be soon :-).</p><p>If you’re a realtor or an airline pilot, then the Content Designer role may not be the best fit for you. But, if you have a background in journalism or copy-writing then consider applying.</p><p>We’re 100% open to folks with transferable skills — some of the Content Design team come from backgrounds such as journalism and creating library taxonomies.</p><figure><img alt="A keyring of a set of keys in pink and blue, with a Shopify UX logo keyring, which is a pink circle with a winking face." src="https://cdn-images-1.medium.com/max/800/1*K60qhBott6CvEyVi6n6UqQ.png" /></figure><h3>2. Applying</h3><p>So, you know this is the right role for you. You’re excited. But how do you make your application stand out? Here’s a few things that you can try.</p><h4><strong>Have a well-designed resume</strong></h4><p>This is less about making it visually beautiful, but more about making the information architecture effective. In other words, putting the right content in the right order.</p><ul><li>Start with a summary to get the person reading interested (known as front-loading).</li><li>Where possible align it to the responsibilities and qualifications in the job ad — make it easy for the recruiter to see that you’re a good fit.</li><li>Show clear evidence of the impact you’ve had in previous roles.</li><li>Include relevant items from outside your day job, for example, if you do volunteer work in the design community.</li><li>Keep it to two pages maximum, and focus on your most recent roles. If you’re applying for a Content Designer role then this is a great time to show off your editorial skills.</li><li>Consider a covering letter or note, summarizing why you’d be a good fit, and what about the role excites you.</li><li>Triple check for typos — demonstrate your attention to detail and read it out loud, slowly, before you hit submit.</li></ul><h4><strong>Have a well-designed portfolio</strong></h4><p>I want to be clear here, this is 100% <strong><em>not</em></strong><em> required</em>. But if I want to learn more about a candidate, being able to easily see examples of their work online is a great place to start. If you’d like some tips for how to build a great portfolio, <a href="https://www.shopify.ca/partners/blog/113327494-how-to-build-a-great-design-portfolio-shopify-designers-weigh-in">this oldish Shopify blog</a> will help you to get started.</p><h3>3. Before you interview</h3><p>So you’ve had an email from Shopify saying they want to interview you, and WOW THAT’S EXCITING! 💥😁.</p><p>Here are three things to think about as you prepare.</p><h4><strong>Context</strong></h4><p>This is where you really want to do some groundwork. For example, you’ll probably want to read more about <a href="https://www.shopify.ca/careers/how-we-hire">interviewing at Shopify</a>.</p><p>You may want to listen to a <a href="https://anchor.fm/inside-shopify-ux/episodes/UX-hiring-at-Shopify-with-Holly-Fortier-e10esmn">podcast with Shopify’s own Holly Fortier</a>, the Recruitment Lead for UX, which is gold-dust, full of nuggets such as how to approach the famous “life story” interview.</p><p><em>“We’re really looking to get to know the person that we’re talking to, and through that interview, we’re looking for specific qualities around self-awareness, indications of impact and engagement in people’s past roles, if their skills and experience are aligned to what we’re looking for in this opportunity. And really those kinds of non-tangible skills that will kind of predict if we think someone’s going to be successful with Shopify</em>.”</p><p>You’ll likely want to read up on Shopify and your <a href="https://anchor.fm/inside-shopify-ux">potential future team</a>. You’ll learn what’s valuable to them, what they’re building, and how to frame your conversations with them.</p><p>You could even set up your own Shopify store to play with using the <a href="https://www.shopify.com/online">free trial</a>.</p><h4><strong>Storytelling</strong></h4><p>We have a lot of candidate applications at Shopify, and one thing that’s guaranteed to help you stand out is having a story to tell us about yourself.</p><ul><li>Who are you?</li><li>How did you get to where you are in your career, and how will that add value to Shopify?</li><li>What about Shopify excites you?</li><li>What makes you the right person for this role?</li><li>Do you have examples of where you’ve demonstrated an entrepreneurial spirit?</li></ul><p>We want to see you’re as enthusiastic to be here as we are. We want to work with people who’ll make us think. We want to understand how you can help our team. Plan out the story you’re going to tell us to get us excited to work alongside you.</p><h4><strong>Practice</strong></h4><p>For my interviews I was flown out to Ottawa for four days. The day before the interview I spent the entire day in my hotel room practicing. I had to present a deck and I wanted it to go smoothly.</p><p>I just dug out the deck, here’s a slide from it.</p><figure><img alt="Photo of Andy rock climbing, overlaid with career highlights" src="https://cdn-images-1.medium.com/max/1024/0*lhUxjJ6iA0QPhrQb" /><figcaption><em>Remember what I said about storytelling? (Photo credit: Dave Bond)</em></figcaption></figure><p>Of course now all our interviews are remote, and you can have notes up on your screen. You do have some notes prepared right? It’s a great way to help you clarify your story.</p><p>The interview steps generally follow this order, though we do sometimes tweak them to help them fit your calendar.</p><ol><li>Initial call with someone from our Talent team.</li><li>Life story interview then an initial work/portfolio review.</li><li>Pair working session, then a Hiring Manager interview.</li></ol><p>When you get to the work/portfolio review, you’ll be expected to walk through some relevant work examples. Sharing two specific pieces is a good approach. This isn’t just a moment to show off your visual design skills (though of course we’re interested in that too), or to go through all the things you’ve ever worked on. You have a story to tell about yourself; you need one to tell about your work as well:</p><ul><li>About the user problems it solved</li><li>The UX processes you invoked</li><li>The options you explored</li><li>The constraints you worked under</li><li>How you collaborated with colleagues</li><li>Data on the business value it’s brought</li><li>Things you might have done differently in retrospect</li></ul><p>Can you show it all in about 40 minutes, including time for questions? Only one way to find out. Well there’s two, but one of them is sub-optimal 😅</p><p>And if you’re doing a Product Designer pair working session, can you find your way around Figma? If you’re used to using other tools, then that’s fine, but ideally you don’t want to learn from scratch on the day.</p><p>Ask the recruiter what tech will be used (such as Google Hangouts), try out your setup, and go into the interviews feeling confident.</p><h3>4. Interviewing</h3><p>This is it. You’ve done your research, you have a winning story to tell, you’re excited to speak with some Shopifolk. Let’s check in with Holly Fortier again:</p><p><em>“We want people just to feel comfortable and relaxed when they’re chatting to us. And really our process is designed around setting them up for success to showcase their skills to us. And we want to give them the best possible chance to do that. And at the same time, recognizing that it’s a two-way street. So as much as we’re choosing people, people are choosing to spend most of their waking hours in a day with us.”</em></p><p>To make it to the interview stage, someone in the recruitment process thinks you might be the person we’re looking for. It’s up to you to prove them right. Whether it’s your first interview with a recruiter or your final stage interview with your potential future manager, there are a few simple things you can do.</p><ul><li><strong>Be open and honest. </strong>Shopify hires individuals: the school you went to and companies you’ve worked for aren’t the most important thing. Your experience, and even more importantly your attitude, do matter. Do you want to learn and grow? Tell us.</li><li><strong>Be inquisitive. </strong>In most interviews you’ll have the opportunity to ask questions. Have some prepared, we want to know what’s important to you and how you think.</li><li><strong>Relax. </strong>There are no trick questions or gotchas. The interview process is intended to help you show us your best side.</li></ul><figure><img alt="Screenshot from the Shopify careers website, with the slogan “We hire people, not resumes”" src="https://cdn-images-1.medium.com/max/1024/0*TutVVdRfKOWbcIDN" /></figure><h3>Summary</h3><p>Hopefully what I’ve shared here will encourage you to apply to Shopify, and to make the process a little easier and clearer. Successful applicants, while often hired by showing what they can do, also often stand out for the quality of their storytelling — about themselves, their work, and their motivations to join Shopify.</p><p>This year Shopify has hired 75 new UXers to date, and we will hire many more. There’s really no better place to grow yourself and your career, so what are you waiting for?</p><h3>Links</h3><ul><li><a href="https://podcasts.apple.com/gb/podcast/ux-hiring-at-shopify-with-holly-fortier/id1539320515?i=1000523992349">UX hiring at Shopify with Holly Fortier</a></li><li><a href="https://vanschneider.com/blog/how-to-get-a-job-at/how-to-land-a-job-at-shopify/">How to land a job at Shopify</a></li><li><a href="https://www.shopify.ca/careers/teams/ux">Shopify UX careers</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc07161bb982" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why assumptions are good for your content strategy]]></title>
            <link>https://medium.com/@andyhealey101/why-assumptions-are-good-for-your-content-strategy-7ffc6e1aa983?source=rss-315681a4091c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ffc6e1aa983</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[critical-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[andy healey]]></dc:creator>
            <pubDate>Fri, 26 Apr 2019 19:46:00 GMT</pubDate>
            <atom:updated>2019-07-19T11:44:31.117Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to recognize assumptions and decide if they’re the right ones</h4><p>Hands up if you’ve ever relocated to a new city, country, or even continent. It’s super-exciting, but at times can be overwhelming, right? There’s so much to take on board. Last year I moved from a sleepy English village to the bright lights of Montreal. And I had a lot of questions…</p><ul><li>Why do Montrealers start a sentence in English and finish it in French?</li><li>Will it ever stop snowing?</li><li>How do I pay my bills?</li><li>Why do they sell milk in a bag?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9HmfQKDognR2hI9KDMzX6g.jpeg" /><figcaption>Milk in a bag</figcaption></figure><p>These are basics of life in Canada, and they make sense to Canadians, so they assumed they’d make sense to me. But they didn’t, because I had no context.</p><p>And in content strategy and design, we make assumptions like this every day. For example, we assume that our developers know about our content guidelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xZbogpcMHPWfHFqJXo-ybQ.png" /><figcaption>True story</figcaption></figure><p>Or we make assumptions about our users’ work environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-0o4MFhUET4mdREcV423DA.png" /><figcaption>Cat and mouse (courtesy of Lucy Leicester)</figcaption></figure><p>Yes, assumptions can be dangerous, and wrong assumptions can cause projects to fail, but maybe they’re the exceptions that give the others a bad rep.</p><p>I mean, we all believe in assuming positive intent, right?</p><p>In reality, we make thousands of assumptions every day. All kinds of tiny things, like when we turn on the tap, water is going to come out. Assumptions are part of our decision-making strategy.</p><p>At a Shopify event in 2018, <a href="https://twitter.com/cynthiasavard">Cynthia Savard Saucier</a>, who co-wrote the book <a href="https://www.tragicdesign.com/">Tragic Design</a>, and <a href="https://twitter.com/biologytodesign">Alëna Iouguina</a> gave a talk on the science behind decision making. Super-interesting stuff about how the brain works to make decisions. And they concluded that “<em>A decision, even a bad one, is still way better than no decision at all</em>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RVVf-fm39fHy0bkRJRNspA.png" /><figcaption>“<em>A decision, even a bad one, is still way better than no decision at all.</em>”</figcaption></figure><p>And as content strategists we sometimes need to make fast decisions. It can be a good thing to be opinionated. And this means making a few assumptions along the way. But is there a right way and a wrong way to make assumptions?</p><p>Let’s look at how to make them the right way, so you can make the right decisions for your users. We’ll do this in three steps…</p><h4>1. It’s OK to make assumptions</h4><p>Back when I was at university, one of my majors was Philosophy. Like other things I experienced at university, philosophy was quite confusing.</p><p>I’d imagined the greatest minds in human evolution, building on each other’s work, striving to reach an ethical and social nirvana.</p><p>But I was wrong.</p><p>Take for example Descartes, and his famous “<em>Cogito ergo sum</em>” — “<em>I think therefore I am</em>”. If you google “I think therefore I am <em>is wrong</em>” there are over 200 million results.</p><p>Philosophy is basically these smart people point-scoring and trolling each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qMy-c_G1ctiYUAUIQQ44hA.png" /><figcaption>Philosopher’s tweets</figcaption></figure><p>So in the 1800s a group of American philosophers, who named themselves Pragmatists, decided to try something different. They said we can’t keep questioning everything forever. Let’s accept some basic assumptions so we can move forwards. And they gave themselves some principles to baseline their assumptions.</p><ul><li>There is no universal truth since everyone experiences their own world and environments in their own way, at their own time, in a variety of situations</li><li>If something seems to work satisfactorily, then assume that it does work satisfactorily</li><li>Always allow for the possibility that a more effective solution will be found</li></ul><p>And what’s interesting is that these principles directly align with resources that are available to content strategists.</p><ul><li>User personas, journey mapping…</li><li>Data, testing…</li><li>Design crits, UX research…</li></ul><p>The pragmatists had their principles to support their decision making. In content strategy we have all these resources to support ours.</p><p>If I just say, “I think this content will work because my opinions are great,” then that’s dangerous.</p><p>But if I say, “I think this content will work because it fits in with previous journey mapping we’ve done, we have positive data on similar content, and it aligns with our research thinking,” then that’s some strong supporting evidence, and a pretty fair assumption to make.</p><p>And this is our first step when towards making use of assumptions in our content design. Knowing that if you baseline them using these resources, then it can be ok to make assumptions.</p><h4>2. Make inclusive assumptions</h4><p>Are you ready for a context switch? You’re a content strategist, of course you are.</p><p>Back in the UK we have Mountain Rescue Teams who are groups of volunteers that help people who are lost or hurt in the mountains. Like all good project teams, they do a retro at the end of each incident and make it available online. Some are funny…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*niK8M6U-PcFwNaVIX3HBcg.png" /><figcaption>Did you try the zip?</figcaption></figure><p>Some aren’t so funny.</p><p>In 2007, Jennifer and Christopher Parratt, who described themselves as experienced hikers, drove from Oxford, up to the mountains in North Wales.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zfA_HM2DgWVGhu4FcYXTMA.png" /><figcaption>Tryfan in North Wales (courtesy of Pauline Henderson)</figcaption></figure><p>They bought themselves a map, a compass, and a guidebook, and set off to hike a mountain called Tryfan. The guidebook said it was “easy”, but there isn’t an easy way up Tryfan. In the last 30 years, 17 people have died on Tryfan.</p><p>They lost their way and Christopher Parrott slipped, and fell to his death.</p><p>The coroner’s inquest was unusual, because <a href="http://news.bbc.co.uk/2/hi/uk_news/wales/north_west/7052630.stm">the guidebook they bought was specifically criticized</a>. “<em>The title ‘Tryfan The Easy Way’ is extremely misleading”</em>. The map was virtually impossible to follow.</p><p>Having read the book, it’s clear that it contains a series of assumptions. The first one was just one word, “easy” — without that they probably wouldn’t have decided to go up Tryfan in the first place. Then the assumptions were piled one on top of the other, each one making the situation more dangerous.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZuWKHAeg-ud1DpUyls86Ig.png" /><figcaption>Stacked assumptions are dangerous</figcaption></figure><p>And what’s interesting for us in content strategy, is that all of these assumptions could be made safer by being more intentional about how content is created.</p><ul><li>User needs analysis to identify the problem we’re trying to solve</li><li>Information architecture to make sure the content is findable</li><li>Naming patterns to avoid confusion or ambiguity</li><li>User testing to see if the solution is performing as expected</li></ul><p>All of these help to make our assumptions safer.</p><p>Like a guidebook writer, our role in content strategy is to look after our users. To take them on a journey and guide them through safely.</p><p>Compare that guide with this <a href="https://www.mudandroutes.com/routes/tryfan-via-the-heather-terrace/">online one</a>, which makes safe, inclusive assumptions.</p><ul><li>The readers might be beginners, so it doesn’t say it’s easy</li><li>It says it can be dangerous</li><li>It gives it’s readers a map</li><li>And it gives detailed step-by-step instructions AND photos</li></ul><p>The writer understands that for each user it’s the same route, but a different journey. And this is very important, he keeps the content clear and simple.</p><p>At Shopify <a href="https://polaris.shopify.com/content/product-content#section-respond-to-merchant-needs">we write for the average US reading age</a>, which is 12–13 years old. And there’s a very good reason we do this.</p><p><em>“Shopify merchants are busy people who may be running their online business in addition to having a full-time job, managing their family life, and doing a million other things. They’re also located all over the world, have varying levels of literacy, and some may not speak English as their first language.”</em></p><p>By using plain language we’re making a safe assumption.</p><p>Or as <a href="https://twitter.com/ContentDesignLN">Sarah Richards</a> so beautifully puts it “<em>It’s not dumbing down, it’s opening up.</em>”</p><p>When you build a new feature, or design for a new market, be intentional about your content, and make safe, inclusive assumptions. Design for everyone. Don’t leave anyone behind.</p><h4>3. Check your assumptions</h4><p>I recently worked on a project where we made an assumption. It didn’t seem like it was a biggie.</p><p>We’d improved a feature, and intended to turn it on for all our users.</p><p>We knew that most of them wanted it, and that some wouldn’t. So we sent them all an email a week before the launch, with an opt-out option. And we assumed they’d read the email.</p><p>Problem was, 40% of the emails bounced and only 22% of the emails were opened. That set alarm bells ringing. It meant lots of people didn’t know we were turning this on for them. As one team member commented… “<em>that’s not ideal</em>”.</p><p>But it was a valuable learning moment. It’s true that in design and tech we like to have fun. In Shopify’s offices there’s a slide, and a room with a giant polar bear in it, and I have my fingers crossed that we’ll be getting a bowling alley next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oThZgBQMOuu-BTNZnLGCdg.png" /><figcaption>Polar bear roaming downtown Ottawa</figcaption></figure><p>But we’re all adults as well, and responsible for our own decisions. We as a team were responsible and we should have challenged ourselves sooner.</p><p>And I’m going to share with you a great exercise we use at Shopify for doing just that — the assumption slam! We use this to challenge our foundational beliefs about a project.</p><p>A wise person (<a href="https://en.wikipedia.org/wiki/Douglas_Adams">not me</a>) once said “<em>The hardest assumption to challenge is the one you don’t even know you are making.</em>”</p><p>An assumption slam helps you to uncover those hidden assumptions. So how this works is, you get your project team together in a room and brainstorm all the assumptions that you’ve been making in the project. As you’re doing it, write them all down on sticky notes, like how you’d do in a design sprint or a retro. So common assumptions might be things like:</p><ul><li>I believe my users have a need to ____________.</li><li>I believe these needs can be solved with ____________.</li><li>I believe the #1 value a user wants to get out of this is ____________.</li><li>I believe the user can also get these additional benefits ___________.</li><li>I believe my biggest product risk is ____________.</li></ul><p>Spend 10 to 15 minutes on this, with each person individually writing down all the assumptions they think the team is making. When you’re done, share them by putting them all up on the wall. You might find that you’re making a surprising number of assumptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*P6CgQJviYqzhRC1wAosBig.png" /><figcaption>Shenoah Plewes, with many sticky notes</figcaption></figure><p>So to make them easier to manage you can group and categorize them into themes. When you have a manageable set of assumptions you can turn to your assumption grid. Which, being the organized content strategist that you are, you prepared earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ls_do7riifWxCaiEPwFb8w.png" /><figcaption>Four quadrants, divided up by risk and knowledge</figcaption></figure><p>As a team, take each of your grouped assumptions, and place them on the grid based on how much you already know about them, and how risky they are if they go wrong.</p><ul><li>Low risk means nothing much can go wrong.</li><li>High-risk is if it could affect your relationships with your customers.</li><li>Really high risk is if it could affect their relationship with their customers.</li></ul><p>And you should end up with something similar to this. Hopefully without so many high-risk unknowns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mDpIqsYniErXTBM48y1jig.png" /><figcaption>Bright lights, big risks</figcaption></figure><p>And now you can prioritize what you do with them.</p><ul><li>Low-risk knowns you can ignore, they’re just distractions.</li><li>High-risk knowns you should include in your project planning.</li><li>Low-risk unknowns. They’re not critical, but time allowing try to understand more about them.</li><li>High-risk unknowns, these are the spicy ones. These need to be evaluated. Carry out research on them, test your thinking out on users, and so on. The more you know, the less risky they’ll become.</li></ul><p>“Does it work?” I hear you ask. Well, last year we ran an assumption slam on one of our products, <a href="https://pay.shopify.com/">Shopify Pay</a>. You can use Shopify Pay to skip through checkouts without entering your details every time. The slam raised some difficult questions including:</p><ul><li>Are we giving users a clear value prop?</li><li>Do they feel secure enough?</li><li>Will they be freaked out by the lack of friction?</li></ul><p>After the slam we went back to work and did more design and content explorations. We shared them at design crits. We did more user testing. We became more knowledgeable.</p><p>And when we were confident that no assumption was left unturned, we launched.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YS3JEAQy-zB43RqMN9xRAQ.png" /><figcaption>Shopify Pay</figcaption></figure><p>We monitored how it was performing. It worked. Our users were happy. One of those users was our COO, and he was really happy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GDgpkKjNOiXSA9T2ZC1BQw.png" /></figure><p>Now this success wasn’t entirely down to the assumption slam, but the slam was one of the tools we used in designing a successful, inclusive product.</p><h4>Summary</h4><p>OK, we’ve seen that there are right ways and wrong ways to make assumptions.</p><p>Next time you’re starting a project, remember that it is ok to use assumptions in your content strategy, as long as you take the time to check them, and to make them safe by using all the tools at your disposal.</p><p>And if you’re looking to run your own assumption slams, why not download our <a href="https://speakerdeck.com/andyhealey/running-an-assumption-slam-b84a601a-141a-4e9a-96f0-e59f6f23b6a3">template deck</a> to get you started.</p><p>Happy slamming!</p><p><em>Huge thanks to </em><a href="https://medium.com/@uxsuccess"><em>Julie Booth</em></a><em> for her wisdom and guidance. She’s also </em><a href="https://ux.shopify.com/assumption-slam-how-not-to-make-an-a-out-of-u-and-me-2d9012c105a0"><em>written more about assumption slams</em></a><em> if you want to dive into that.</em></p><p><em>Also thanks to my content critters — Caitlin Mullen, </em><a href="https://twitter.com/katiedel"><em>Katie Del Angel</em></a><em>, </em><a href="https://twitter.com/evijaaa"><em>Evi Sundman</em></a><em>, </em><a href="https://twitter.com/distilco"><em>Nic Evans</em></a><em>, </em><a href="https://ux.shopify.com/@sarah.ebbs"><em>Sarah Ebbs</em></a><em>, </em><a href="https://ux.shopify.com/@virginiastart"><em>Virginia Start</em></a><em>, and </em><a href="https://ux.shopify.com/@PaulStairmand"><em>Paul Stairmand</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ffc6e1aa983" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make UX writing a thing in your org]]></title>
            <link>https://uxdesign.cc/how-to-make-ux-writing-a-thing-in-your-org-2b802576b702?source=rss-315681a4091c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b802576b702</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[copywriting]]></category>
            <dc:creator><![CDATA[andy healey]]></dc:creator>
            <pubDate>Mon, 08 May 2017 15:51:16 GMT</pubDate>
            <atom:updated>2017-05-17T10:12:03.926Z</atom:updated>
            <content:encoded><![CDATA[<p>The role of UX Writer is trending right now, with big organizations such as Google and Dropbox actively recruiting. A few weeks ago <a href="https://medium.com/u/c586b66e24dc">Kristina Bjoran</a> wrote a great article on <a href="http://www.uxbooth.com/articles/how-to-break-into-ux-writing/">How to Break into UX Writing</a> where she identified that to land one of these roles you’re going to need to show that you’re more than just a pretty writer, and have UX design right at the top of your “Key Skills”.</p><p>UX writing is a still considered a relatively new role, a “<a href="https://www.fastcodesign.com/3068938/forget-coding-writing-is-the-new-unicorn-skill">unicorn skill</a>”, outside of California at least. I checked LinkedIn for UX Writer roles in the UK - there were exactly zero results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*tC_Ia_XaetolVbQFeFzIZQ.png" /></figure><p>So chances are that your organization (or ‘company’ if you’re in the UK) hasn’t yet thought about hiring a UX Writer. Sure, you may have a team of UX Designers or Experience Developers, but how many of them are really into honing and crafting words. <a href="https://medium.com/u/85a0d8f2e404">John Maeda</a> says in his “<a href="https://designintechreport.wordpress.com/2017/03/11/design-in-tech-report-2017/">2017 Design in Tech Report</a>” that:</p><p>“<em>A lot of times designers don’t know that words are important</em>”</p><p>Now that’s maybe a little bit harsh. Most designers are massively overstretched and have to prioritize, and words just don’t come that high up the priority list. And this is what provides you with a massive opportunity.</p><h4>The six degrees of UX writing</h4><p>Before you get started, it’s worth evaluating what degree of UX writing your organization currently has. On the scale below then chances are that it’ll be somewhere between one and three. When you get involved you should target three and four as to where you can make a short-term noticeable impact. Your longer-term goal should be to reach five, with six as the holy grail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*0kv_BAOHXoHmYTQpMcUKeA.png" /></figure><h4>1. Identify your opportunities</h4><p>When I joined Alfresco over 4 years ago, there was a small design team, working on multiple products. Their focus was on delivering great new products and features. Of course this is just the same in most other places, and changing a few words is rarely seen as a value add.</p><p>One of Alfresco’s products alone contained over <strong>40,000</strong> individual words. A lot of the copy had been written on the fly by developers and there were things that could definitely be changed to improve the user experience:</p><p>· There was no consistency</p><p>· There were typos</p><p>· Some of it didn’t really make sense</p><p>But there was no process for making changes and every day more words were being coded that didn’t have any science behind them. There was an open goal for someone to take ownership of the product copy.</p><h4>2. Start small</h4><p>The best way to show you can make a difference and grab attention is to attach yourself to a new project for a standalone feature or small product. It’s all about taking baby-steps, you can’t change everything immediately.</p><p>Chat with the Product Manager and/or UX Designer and offer to take a look at the copy in your own time. Propose to them that you can help to make a nicer product that’s more likely to be adopted. Show them a couple of examples of what you could improve. Give them some figures to show how words affect user adoption (for example, 80% of people prefer sentences written in clear English, <a href="https://gds.blog.gov.uk/2014/02/17/guest-post-clarity-is-king-the-evidence-that-reveals-the-desperate-need-to-re-think-the-way-we-write/">Clarity is King</a>). It’s all about making a better product. Plus less work for them.</p><p>No-one’s going to say no to an offer like that right?</p><h4>3. Short-cuts to validating your words</h4><p>Most of the time our gut instinct on what reads better is usually correct. If your team are happy with your gut instinct then great, but wouldn’t it be even better to back yourself up with some real data as well? Prove that the words you use are going to improve the user experience.</p><p>At this stage you don’t have writing guidelines and you probably don’t have access to a user research team. Remember that this is a stealth start-up project you’re running here. Fast and light.</p><p>Fortunately, there’s a lot of people out there who’ve already done the research for you.</p><p>Chances are that your test project has design parallels with other products. So look at those products and see what words they use. Take a look at a few writing guidelines such as <a href="https://material.io/guidelines/style/writing.html">Google’s</a> and <a href="https://developer.apple.com/library/content/documentation/UserExperience/Conceptual/OSXHIGuidelines/TerminologyWording.html">Apple’s</a> to back up your ideas. For each word choice that you make you want to justify why it’s an improvement. That can often be as simple as “this is what Google do”. Check out the <a href="https://medium.com/u/c57a1304a92b">John Saito</a> article on how data informs UX writing at Dropbox — <a href="https://medium.com/dropbox-design/design-words-with-data-fe3c525994e7">Designing words with data</a> for more on this.</p><p>Focus on <strong>consistency</strong>, <strong>clarity</strong> and <strong>simplicity</strong>. You can think about a more formalized tone and voice later.</p><h4>4. Record everything!</h4><p>A key mistake I made when I first started reviewing and writing copy was not keeping a record of what I’d done. The team I was working with knew I was involved, but you really need some metrics to show the value you’ve added.</p><p>To begin with this doesn’t need to be anything too fancy. Just keep a record of the number of lines of existing content that you’ve reviewed, the number of these that you’ve optimized, and the number of lines of new content you’ve created. And get before and after examples. Ideally for everything you change, but certainly get some of your best work for future reference. This serves two purposes:</p><ol><li><em>For your company </em>— showcase your value-add</li><li><em>For yourself</em> — you’re building a portfolio as a UX Writer</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*GgKrCdxicSoORtWdL-m-cg.png" /></figure><p>If your team is testing with users before you launch then your validation will done for you. If not, then you can run simple A/B tests yourself comparing the original to your optimized version, using online tools such as <a href="https://validately.com/">Validately</a> (which has a free month trial option). Let’s be honest though, that sounds time consuming. So why not just test out your copy with coworkers, or even your family or friends.</p><h4>5. Double down — users as advocates for change</h4><p>Having started from an ad-hoc approach, you’ll hopefully have had a visible impact on product development. The products or features you’ve worked on will have clearer, more consistent copy, with a degree of user validation and competitor analysis. Your UX team and developers can appreciate the positive impact your involvement has, and you’ve recorded evidence of the improvements your brought.</p><p>Wouldn’t it be great if you also had users on side to support your efforts?</p><p>I had some ideas about how to improve our legacy product copy, but felt that to get real support I needed to prove that users felt the same way. So I set up a survey on SurveyMonkey and asked the team at Alfresco to share it with customers, partners, and users. The result was over 200 respondents, giving us lots of insight. The most important response was to the following statement:</p><p><strong>My experience could be improved by changing the tone / terminology</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*32ifO6wHwJSez1MOTirP_Q.png" /></figure><p>There were also well over 100 specific comments such as:</p><p><em>“too technical”</em></p><p>and</p><p><em>“say it like it is, don’t assume you’re dealing with an Alfresco expert”</em></p><p>If you don’t have the means to conduct your own survey then just share these results with your Product Management team. A massive <strong>49%</strong> of our users were telling us that by focussing on UX writing we could improve their experience. That’s a pretty compelling case.</p><h4>6. Formalize processes</h4><p>You now have solid evidence behind you, and a body of work that demonstrates the impact you can have. Congratulations! You’ve made real and tangible progress towards making UX writing a thing in your org. This is where the real works starts…</p><p><strong>a) Create guidelines</strong></p><p>Before you begin to formalize processes you need to set a benchmark. The simplest way to do this is to have defined writing guidelines in place. You can either reuse existing ones such as Google’s, or create your own as we did at Alfresco — <a href="http://docs.alfresco.com/writing-for-alfresco">docs.alfresco.com/writing-for-alfresco</a>.</p><p>In defining your tone and voice there’s a huge amount of info out there, but most of the time finding a style equates to keeping things simple, clear, and non-offensive. There’s plenty of research, for example Microsoft’s presentations on “No more robot speak” (Doug Kim, 2014), showing that a clear majority of people (including developers and other “techies”) want the product voice to be clear, non-technical, and not to look like it’s trying too hard. So just focus on these three things:</p><p>1. Consistency — Create a pattern of usage to avoid ambiguity</p><p>2. Empathy — Understand your users situation and help them</p><p>3. Simplicity — “Simplicity is the ultimate sophistication”</p><p>When you’re done, share this in a public space and advertise the fact that it’s now available. If possible, get someone senior to endorse it as the new standard to work to.</p><p><strong>b) Integrate writing into the design process</strong></p><p>This is nominally straightforward, but depending on the size of your org or any internal resistance, may take some time to for a new process to become the norm.</p><p>If you have a UX team or product designers then you need to align with their workflow. My experience is based on working in an Agile environment where UX prototypes and flows are created for developers to work from. There are two key factors to instil in your team:</p><p>1. The UX team <strong>work with you</strong> to create any new copy. To begin with this will likely be that they design protocopy, then you discuss the design and user flow with them and optimize the copy. This is the 5th degree of UX writing — if you make it to here then your company is doing UX writing.</p><p>2. The developers <strong>DO NOT</strong> code anything until they know that it has your approval. This will be a gradual process and is about developing their trust. I’ve found though that most developers would always prefer to defer to the “authority” (remember those writing guidelines) rather than making up some words themselves.</p><h3>Summary</h3><p>As far back as 1985 the Apple human interface group recognized the importance of UX writing with their motto “<a href="http://www.asktog.com/columns/038MacUITrends.html">A word is worth a thousand pictures</a>”.</p><p>30+ years later we’re starting to see this being realized in the role of UX Writer.</p><p>If your org currently settles for the 1st or 2nd degree of UX writing then they’re accepting the associated costs in user unhappiness. In today’s highly competitive markets, with everyone looking to disrupt each other, you have to be better than the competition.</p><p>You have the opportunity to make a difference. Now’s the time to make UX writing a thing in your org.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b802576b702" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-make-ux-writing-a-thing-in-your-org-2b802576b702">How to make UX writing a thing in your org</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>