<?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 Andrea Azcurra on Medium]]></title>
        <description><![CDATA[Stories by Andrea Azcurra on Medium]]></description>
        <link>https://medium.com/@andyazcu?source=rss-81913a8cf8e7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*EW_uV4A1q92Nl2SGpq3UBw.jpeg</url>
            <title>Stories by Andrea Azcurra on Medium</title>
            <link>https://medium.com/@andyazcu?source=rss-81913a8cf8e7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:27:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andyazcu/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: Create Product Content Guidelines]]></title>
            <link>https://medium.com/compass-true-north/how-to-create-product-content-guidelines-ac7ba1f01be5?source=rss-81913a8cf8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac7ba1f01be5</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Andrea Azcurra]]></dc:creator>
            <pubDate>Tue, 10 Dec 2019 17:01:01 GMT</pubDate>
            <atom:updated>2019-12-10T17:01:01.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p0jpbYznC9GsLzH6V9Mvpw.png" /></figure><p>For the last year, I’ve been developing, implementing, and maintaining a set of content guidelines that help make language, style, vocabulary, and voice more consistent throughout our product.</p><p>Along the way, I’ve partnered with product designers, user researchers, product managers, and marketers and it’s been an unprecedented learning experience for everyone involved.</p><p>Below I’ll share my process, findings, and plans thus far for anyone interested in creating something similar.</p><h3>What are content guidelines?</h3><p>Even though it sounds formal and boring, content guidelines can breathe life into your UX and are an important tool for any product org.</p><ul><li>A <strong>source of truth </strong>for UI copy standards</li><li>A <strong>shared resource</strong> for anyone writing, editing, or thinking about the content in our product</li><li>An <strong>integral part of your design system </strong>and brand</li><li>A <strong>tool to streamline production</strong> and promote consistency</li></ul><h3>But first, research</h3><p>Before you can sit down and actually <em>write</em> a set of guidelines, you need to do some research.</p><h3>Competitive analysis</h3><p>Every smart design project starts with competitive analysis. See what’s out there, compare it to what you’re thinking, ingest the good and bad, and come out with an informed opinion about the direction you should take.</p><p><a href="https://styleguide.mailchimp.com/">Mailchimp</a> and <a href="https://polaris.shopify.com/content/product-content#navigation">Shopify</a> are great examples of established content guidelines and served as inspiration for layout, sections, and how best to integrate the final product into a larger design system.</p><h3>User interviews</h3><p>Another important part of the process is conducting user interviews. Sit down with the people who interact with your content most — designers, PMs, customer support, and actual end users — to hear their thoughts on the current state of product copy, frustrations and pain points, and ideas on how content could improve user experience.</p><p>Hearing all of this firsthand really put our content problems into perspective and helped distill high-level themes — both of which would influence what areas needed more content rules than others.</p><h3>Voice and tone workshops</h3><p>In order to further engage people in your process (and drive awareness of the importance of having content guidelines in place), consider hosting some interactive workshops around voice and tone.</p><p>I created 3–4 light activities focused on uncovering our ideal attributes — who we are, how we sound, and what personality we wanted to portray in our product. Using whiteboarding, worksheets, and sticky notes, it was easy to visualize trends and use them to create a voice and tone everyone identified with.</p><h3>Content audits</h3><p>Ah, the famous content audit. Tedious but brimming with insight, take inventory of all the content elements of your website, app, and user journeys in order to better understand what’s working and what’s not. Typo? Screenshot it. Dead end? Screenshot it. Onboarding that needs more explanation? Screenshot it.</p><p>Doing this validated previous research and helped stakeholders (literally) see gaps in user flows and specific problems by feature area.</p><p>At the end of the research phase, you should have a solid opinion on voice and tone as well as general themes that will guide you as you begin writing. You should know what your UX lacks (consistency, personality), what your content needs to do more of (educate, guide), and quick win focus areas (empty states, CTAs).</p><h3>Just write it</h3><p>After analyzing and circulating your initial findings, you can now begin writing your content guidelines! For me, it was easiest to start by outlining each section and fleshing them out one at a time:</p><ul><li><strong>Goals and Principles</strong></li><li><strong>Audiences</strong></li><li><strong>Voice and Tone</strong></li><li><strong>Grammar and Punctuation</strong></li><li><strong>Naming</strong></li><li><strong>Terminology</strong></li><li><strong>Word List</strong></li><li><strong>Components</strong></li></ul><p>Your sections may differ and that’s okay. Adapt them based on what makes sense for your company.</p><p>Throughout the writing process, I gathered stakeholder feedback and revised accordingly until we all felt good about what the guidelines represented. Once we got to that “final” draft, we used Contentful to host the content and built an internal wiki page similar to the other style guides mentioned above.</p><h3>Educating the masses</h3><p>So your content guidelines are coded — we’re done, right? Not quite. Now’s the time to start shipping your finished product internally. Get people familiar with the wiki, walk them through it, give them access and encourage questions and feedback. What made sense to a UX writer and Design Director might not to an engineer or PM.</p><p>For maximum visibility, I presented ours at a monthly all hands. In true TLDR; format I highlighted best practices, processes, and next steps. Anything you can do to showcase the value of what you’ve created will help with org-wide adoption.</p><p>For added measure, I’ve also started putting together a curriculum for bi-weekly content workshops to immerse people in UX writing best practices as they relate to our product. It’s a great hands-on way to get teams actively using and understanding how to apply the guidelines in their day-to-day.</p><h3>Update, implement, test, repeat</h3><p>In tandem with education comes execution (or, putting your money where your mouth is).</p><p>Make an implementation plan. Based on your research, what areas are a top priority? What content needs the most updating? Seek out quick wins (a login experience, a settings page) and work strategically to align with company OKRs to make the most impact.</p><p>Once you decide on a focus area, partner with a PM to sprint plan copy revisions alongside design and engineering. Content QA everything before it’s pushed to production. Test, revise, and repeat. Then give yourself a huge pat on the back because there’s nothing like seeing your writing out in the wild (and hearing what users think)!</p><p>I started small to test my implementation process and eventually adapted it to larger, more content-heavy features, working collaboratively across most of the product org.</p><h3>Next Steps</h3><p>It’s been a long 12 months (and counting) but creating our product’s content guidelines has taught me so much.</p><p>The most important lesson here is that this sort of initiative will always be a WIP. View your guidelines as a strong foundation for product copy but always allow room to adapt and change as your product (and users) do.</p><p>And remember, your job as a content designer is never finished. You’ll need to be a constant advocate for great UI copy but eventually, all the hard work pays off in the form of a better, more consistent user experience.</p><p><em>This article was originally published in </em><a href="https://uxdesign.cc/how-to-create-product-content-guidelines-ae8c1b6521ea"><em>UX Collective</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac7ba1f01be5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/compass-true-north/how-to-create-product-content-guidelines-ac7ba1f01be5">How To: Create Product Content Guidelines</a> was originally published in <a href="https://medium.com/compass-true-north">Compass True North</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Writing: expectations vs. reality]]></title>
            <link>https://uxdesign.cc/ux-writing-expectations-vs-reality-d6b3a2ea2862?source=rss-81913a8cf8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6b3a2ea2862</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[copywriting]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Andrea Azcurra]]></dc:creator>
            <pubDate>Fri, 26 Jul 2019 16:37:39 GMT</pubDate>
            <atom:updated>2019-07-29T23:28:23.537Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Ko0KXk4ObM3b_WqXW60sg.png" /></figure><p>I’m often asked what it is I do. And like any good writer, the answer I give depends on my audience.</p><p><strong>To a designer:</strong> “I’m also a designer. But for content.”</p><p><strong>To a product manager:</strong> “I help tell the product’s story and create a seamless user experience.”</p><p><strong>To mom and dad: </strong>“You know the words you read in apps? I write those.”</p><p><strong>To grandma:</strong> “Yes, I’m still working on my first novel.”</p><p>The point is, most people have very different ideas of what a UX writer’s day-to-day looks like. And to be honest, the industry is still trying to figure out <a href="https://medium.com/@andreadudla/the-product-design-ratio-b4926f3034b6">how to use us to our fullest potential.</a> It’s a classic case of expectation vs. reality.</p><p>So I’ve put together a list of some of the most common UX writing expectations I’ve personally encountered—and my own reality behind them.</p><h3>We’re human thesauruses.</h3><p>“What’s another word for _______?”</p><p>Believe me, I wish I could close the Power Thesaurus tab for good, but contrary to popular belief, most UX writers are not living, breathing word repositories. Knowing when to use the right words is critical, but sometimes I still have to Google them first.</p><h3>We have an English degree.</h3><p>“Didn’t you study language in school?”</p><p>Short answer: Sort of. Long answer: I studied photography. Then advertising. And my first job out of college was a web producer. While it helps to have <em>some</em> knowledge of communication, it isn’t everything. Drawing from other experiences outside of writing has made me more empathetic and poised to understand a broader audience.</p><h3>We can write on the spot.</h3><p>“Hey, what can we say instead of this?”</p><p>Rome wasn’t built in a day. And your new modal certainly can’t be written in 2 seconds while a room of people is watching. There’s a lot that goes into writing that sentence and getting it right takes time. What I can do is give you ideas of how to message XYZ and why, but give me a day or two to create my version of pixel perfect.</p><h3>We’re grammar nazis.</h3><p>“What’s an Oxford comma?”</p><p>This is probably the #1 assumption I get—that UX writers are hired to police your product’s content. Yes and no. I care about commas, capitalization, et al because it affects readability and trust across the entire experience (kinda like designers care about the grid). Without guidelines, it feels messy and inconsistent—imagine what it’s like for your user.</p><h3>We write in a vacuum.</h3><p>“Can you share the copy deck?”</p><p>Not every writer is the recluse in the woods. I thrive on collaboration and rely heavily on other teams to do my job. I want to be in usability testing to hear firsthand what our users think. I want to be in whiteboarding sessions to help solve content problems before they create larger ones. I want to QA before launch to make sure we’re putting our best face forward. Most of all, I want to hear other people’s thoughts on copy.</p><h3>We only care about the words.</h3><p>“Okay, but what does the designer/developer/PM/researcher think?”</p><p>Words. I love ’em. But I also love strategy, design, QA, marketing, and research. You know why? Because I love user experience and user experience is all of the above. Creating relationships and actively learning about the stages of product development helps me have a more holistic approach to UX writing. It’s like having x-ray vision, but for storytelling.</p><p>—</p><p>As mysterious as the UX writing role may seem right now, the industry needs more word unicorns. We’re the people who craft the narrative, bring a product’s voice to life, and insist on sentence case for a more human-centric approach to content design.</p><p>There’s a lot that goes into a successful user experience. And like many unicorns before us, we’re here to (help) do it all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6b3a2ea2862" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-writing-expectations-vs-reality-d6b3a2ea2862">UX Writing: expectations vs. reality</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>
        <item>
            <title><![CDATA[The Product Design Ratio]]></title>
            <link>https://medium.com/@andyazcu/the-product-design-ratio-b4926f3034b6?source=rss-81913a8cf8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4926f3034b6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Andrea Azcurra]]></dc:creator>
            <pubDate>Tue, 07 May 2019 21:08:58 GMT</pubDate>
            <atom:updated>2019-05-07T21:12:47.477Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UA0B_RCHQkZsHXZicWUMpw.png" /></figure><p>The other day I was scrolling through Twitter and saw this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6cClwjgSnfH0ZGSF1aPXYA.png" /><figcaption>Thank you, <a href="https://uxdesign.cc/@rachel.mcconnell">Rachel</a>, for tweeting everything the UX writing community wants to scream.</figcaption></figure><p>To say it hit home would be an understatement. I paused, tapped retweet, and haven’t stopped thinking about it since.</p><p>I’ve written a lot about <a href="https://medium.com/@andreadudla/flying-solo-da0fbdee840d">being the only UX writer</a> at my company. It’s pretty typical not to have a robust content team with solid processes and rituals. And it’s rare to have dedicated feature team writers — even rarer to have them involved in the right ways. So, this got me thinking:</p><p><strong>Why is the product design ratio so skewed?</strong></p><h3>Doing It All</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QCDxTbwJaPGIyIjhmL4_bw.png" /><figcaption>Typical product team structure: 1 writer catering to all feature teams</figcaption></figure><p>Ask any UX writer what they write and you’ll probably hear “well, everything…”. Their day-to-day involves all kinds of content creation, from in-app microcopy, multi-screen onboarding, UX strategy, taxonomy, and occasionally product marketing. Some of us even own tone and voice guidelines, design systems, usability testing, and content QA. I’ve even been tapped to proofread all-company meeting presentations and job postings. Basically, <strong>you’ll be hard-pressed to find a writer in tech who isn’t tasked with anything remotely involving words.</strong></p><p>But why?</p><p>I look at product designers who are content to focus on their feature area and not much else. If there’s not a dedicated designer, it’s a huge red flag. The same for PMs and engineers. Even UX researchers are becoming embedded and influencing product decisions without a second thought.</p><p>Why is it different for writers? Why are we expected to know about, fix, and maintain <em>everything</em> content-related? Why is it for every 5 designers, there’s 1 writer trying to self-manage across an entire user experience? Why are we given that level of autonomy and responsibility but still have to advocate for the value we bring?</p><p>Yes, I know, “everyone can write”. But not everyone is a writer. So perhaps instead of focusing on the “why”, we should start asking “how”.</p><h3>The Ideal State</h3><p>As a team of one for almost a year now, I’ve had to wear a lot of hats. I welcomed the challenge and have done a lot of great things to steer content in the right direction. But I realized pretty early on that my job would have a lot more impact if I had a clone (or 3). Not only would having multiple writers build trust and confidence in our craft (power in numbers), it would also streamline the workload and help in creating higher quality content, faster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3GQVmLfByS5RICvCOazMQ.png" /><figcaption>Better product team structure: A team of writers that become SMEs for their feature</figcaption></figure><p>When each feature team has a dedicated writer, they gain a writer who can focus on becoming a subject matter expert. It’s UX writing 101. <strong>We need context in order to create an experience that resonates with our users</strong>. And fully understanding that context demands our time and attention in ways that only being a dedicated member of a feature team can offer.</p><p>To put it in perspective, think about a person in your life who you know everything about — all their quirks and worries, all their nuances. You probably spend most of your time with them and are very familiar with their day-to-day activities, relationships, and problems.</p><p>Then think about 5 more people and all their individual, unique attributes. In order to keep up with everyone, you have to divide your time. You end up missing key moments and opportunities because you can’t be everywhere at once. That’s what writing for multiple feature areas is like. You play the game of sacrificing quality for quantity when, really, it should be the other way around.</p><h3>More Writers, Please</h3><p>As I’ve watched my own product team grow, I’ve always wondered how a new hire is justified. A lot of it is skill-based (mobile, animation, visual design) but it seems it’s mostly about filling niches for specific business needs.</p><p>A good place to start, then, is figuring out what content skills are most in-demand in your product org. It’s extremely tempting to say “all of them!!!!” but try to be as specific as possible. Ask yourself:</p><p><em>Where are you spending too much time?</em></p><p><em>Where are you spending too little time?</em></p><p><em>Which teams need you most? Not at all?</em></p><p><em>What content skills is your team lacking or not that confident in?</em></p><p><em>What are your blockers and why?</em></p><p><em>If you had a clone of yourself, what would you give them to work on?</em></p><p>Once I had answers to these questions, I felt more confident approaching the powers that be about hiring more writers. In a way, it helped me realize what I enjoyed about my job and what I didn’t. What things I was great at and not so much. Eventually, all the gaps and opportunities I was looking for came into focus.</p><h3>Conclusion</h3><p>As Rachel mentions in her tweet, there’s no such thing as a catch-all subject matter expert. It’s unrealistic for 1 writer to do the job of 5 and we need to change that.</p><p>If we want companies to use us to our fullest potential (and their greatest advantage), they need to better understand our strengths and expertise. But we need to know how to apply them to company goals. Only then will we be able to build the content teams we deserve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4926f3034b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To: create product content guidelines]]></title>
            <link>https://uxdesign.cc/how-to-create-product-content-guidelines-ae8c1b6521ea?source=rss-81913a8cf8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae8c1b6521ea</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Andrea Azcurra]]></dc:creator>
            <pubDate>Mon, 22 Apr 2019 19:50:28 GMT</pubDate>
            <atom:updated>2019-04-25T14:40:14.941Z</atom:updated>
            <content:encoded><![CDATA[<h3>How To: Create Product Content Guidelines</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3g7LhiGv_J3fmNofbCB4wg.png" /></figure><p>As the one, single UX writer at my company, I wear a lot of hats. A little microcopy here, I little content strategy there. But by far, my biggest responsibility is shaping the user experience through words—a.k.a. content design.</p><p>For the last 10 months, I’ve been developing and implementing a set of content guidelines to help make language, style, vocabulary, and voice more consistent throughout our product.</p><p>Along the way, I’ve partnered with product designers, user researchers, product managers, and marketers and it’s been an unprecedented learning experience for everyone involved.</p><p>Below I’ll share my process, findings, and plans thus far for anyone interested in creating something similar.</p><h3>What are content guidelines?</h3><p>Even though it sounds formal and boring, content guidelines can breathe life into your UX and are an important tool for any product org.</p><ul><li>A <strong>source of truth </strong>for UI copy standards</li><li>A <strong>shared resource</strong> for anyone writing, editing, or thinking about the content in our product</li><li>An <strong>integral part of your design system </strong>and brand</li><li>A <strong>tool to streamline production</strong> and promote consistency</li></ul><h3>But first, research</h3><p>Before you can sit down and actually <em>write</em> a set of guidelines, you need to do some research.</p><h4>Competitive analysis</h4><p>Every smart design project starts with competitive analysis. See what’s out there, compare it to what you’re thinking, ingest the good and bad, and come out with an informed opinion about the direction you should take.</p><p><a href="https://styleguide.mailchimp.com/">Mailchimp</a> and <a href="https://polaris.shopify.com/content/product-content#navigation">Shopify</a> are great examples of established content guidelines and served as inspiration for layout, sections, and how best to integrate the final product into a larger design system.</p><h4>User interviews</h4><p>Another important part of the process is conducting user interviews. Sit down with the people who interact with your content most—designers, PMs, customer support, and actual end users—to hear their thoughts on the current state of product copy, frustrations and pain points, and ideas on how content could improve user experience.</p><p>Hearing all of this firsthand really put our content problems into perspective and helped distill high-level themes—both of which would influence what areas needed more content rules than others.</p><h4>Voice and tone workshops</h4><p>In order to further engage people in your process (and drive awareness of the importance of having content guidelines in place), consider hosting some interactive workshops around voice and tone.</p><p>I created 3–4 light activities focused on uncovering our ideal attributes — who we are, how we sound, and what personality we wanted to portray in our product. Using whiteboarding, worksheets, and sticky notes, it was easy to visualize trends and use them to create a voice and tone everyone identified with.</p><h4>Content audits</h4><p>Ah, the famous content audit. Tedious but brimming with insight, take inventory of all the content elements of your website, app, and user journeys in order to better understand what’s working and what’s not. Typo? Screenshot it. Dead end? Screenshot it. Onboarding that needs more explanation? Screenshot it.</p><p>Doing this validated previous research and helped stakeholders (literally) see gaps in user flows and specific problems by feature area.</p><p>At the end of the research phase, you should have a solid opinion on voice and tone as well as general themes that will guide you as you begin writing. You should know what your UX lacks (consistency, personality), what your content needs to do more of (educate, guide), and quick win focus areas (empty states, CTAs).</p><h3>Just write it</h3><p>After analyzing and circulating your initial findings, you can now begin writing your content guidelines! For me, it was easiest to start by outlining each section and fleshing them out one at a time:</p><ul><li><strong>Goals and Principles</strong></li><li><strong>Audiences</strong></li><li><strong>Voice and Tone</strong></li><li><strong>Grammar and Punctuation</strong></li><li><strong>Naming</strong></li><li><strong>Terminology</strong></li><li><strong>Word List</strong></li><li><strong>Components</strong></li></ul><p>Your sections may differ and that’s okay. Adapt them based on what makes sense for your company.</p><p>Throughout the writing process, I gathered stakeholder feedback and revised accordingly until we all felt good about what the guidelines represented. Once we got to that “final” draft, we used Contentful to host the content and built an internal wiki page similar to the other style guides mentioned above.</p><h3>Educating the masses</h3><p>So your content guidelines are coded—we’re done, right? Not quite. Now’s the time to start shipping your finished product internally. Get people familiar with the wiki, walk them through it, give them access and encourage questions and feedback. What made sense to a UX writer and Design Director might not to an engineer or PM.</p><p>For maximum visibility, I presented ours at a monthly all hands. In true TLDR; format I highlighted best practices, process, and next steps. Anything you can do to showcase the value of what you’ve created will help with org-wide adoption.</p><p>For added measure, I’ve also started putting together a curriculum for bi-weekly content workshops to immerse people in UX writing best practices as they relate to our product. It’s a great hands-on way to get teams actively using and understanding how to apply the guidelines in their day-to-day.</p><h3>Update, implement, test, repeat</h3><p>In tandem with education comes execution (or, putting your money where your mouth is).</p><p>Make an implementation plan. Based on your research, what areas are a top priority? What content needs the most updating? Seek out quick wins (a login experience, a settings page) and work strategically to align with company OKRs to make the most impact.</p><p>Once you decide on a focus area, partner with a PM to sprint plan copy revisions alongside design and engineering. Content QA everything before it’s pushed to production. Test, revise, and repeat. Then give yourself a huge pat on the back because there’s nothing like seeing your writing out in the wild (and hearing what users think)!</p><p>I started small to test my implementation process and eventually adapted it to larger, more content-heavy features, working collaboratively across most of the product org.</p><h3>Next Steps</h3><p>It’s been a long 10 months (and counting) but creating our product’s content guidelines has taught me so much.</p><p>The most important lesson here is that this sort of initiative will always be a WIP. View your guidelines as a strong foundation for product copy but always allow room to adapt and change as your product (and users) do.</p><p>And remember, your job as a content designer is never finished. You’ll need to be a constant advocate for great UI copy but eventually, all the hard work pays off in the form of a better, more consistent user experience.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%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/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae8c1b6521ea" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-create-product-content-guidelines-ae8c1b6521ea">How To: create product content guidelines</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>
        <item>
            <title><![CDATA[Writing For Every Generation]]></title>
            <link>https://blog.prototypr.io/writing-for-every-generation-beae02609173?source=rss-81913a8cf8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/beae02609173</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Andrea Azcurra]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 20:58:27 GMT</pubDate>
            <atom:updated>2019-04-13T14:12:35.385Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pZbijHMLOo8qnq3v7hPK0A.png" /></figure><h3>The Power of Personas</h3><p>The goal of any product is to get people to use it and, ideally, never stop. But before we can convince them to stick around, we first need to find (and understand) our ideal customers. A quick, lightweight way to do this is through personas.</p><p>In UX, user personas answer the question, <strong>“Who are we making this for?”</strong> They’re a pretty useful tool when crafting messaging and aligning strategy to different audiences. Usually, they represent a subset of a population and work to provide general insight into how best to cater your product to their needs.</p><p>But I thought it’d be interesting to think about it more broadly.</p><h3>Generational Thinking</h3><p>Let’s explore the four human generations alive today and how certain tendencies might influence how (and why) they use technology at large.</p><p>For the purpose of this article, we’ll treat each generation as an audience. <em>Of course, every person is unique and there’s no way to account for absolutely every use case. That’s where more in-depth user research comes in.</em> <strong>Personas are meant to help form a high-level understanding of your users. </strong>A big piece of that is how you communicate with them—the way we speak to different audiences is extremely relevant and vital to making a connection. Have you ever tried to explain Facebook to your grandma? What about asking a 10-year-old to use a VCR?</p><p>In order to communicate effectively, you need to speak your user’s language, which means knowing who they are, what they want, and how to approach designing a solution that fits their needs. Otherwise, a lot gets lost in translation and your user experience fails to resonate.</p><p>All right, humankind. Let’s do this.</p><h3><strong>Baby Boomers</strong></h3><p>Born: 1946–1964 | Age: 54–72 | Current population: ~73.5 million</p><p>Born in a time of sluggish tech advancement, Baby Boomers aren’t as proficient as other generations. They see technology as innovative and life-changing and like to learn everything about it before adopting. Those from this generation have increasingly <strong>high expectations when it comes to quality and usability</strong> and value function over form.</p><p>How to resonate: Purposeful messaging that explains the who, what, why, and how.</p><h3><strong>Gen X</strong></h3><p>Born: 1965–1980 | Age: 38–53 | Current population: ~66 million</p><p>Gen X-ers make up the smallest generation but are largely independent and resourceful by nature. Their self-sufficient attitude stems from growing up in the midst of turbulent times, both economic and political. Gen X-ers <strong>bridge the gap between analog and digital</strong>. They’re tech savvy but are more traditional users—more so for critical thinking than self-promotion.</p><p>How to resonate: Integrated communication that’s straightforward and speaks to value and quality.</p><h3><strong>Millennials</strong></h3><p>Born: 1981–1996 | Age: 22–37 | Current population: ~72 million</p><p>Growing up in a time when the internet was still in its infancy, Millennials have a sense of nostalgia for simpler times. But convenience is their vice, so they’re eager and willing to adopt new technology if it makes their lives easier (and more mobile). This generation wants their opinions heard, so they’re naturally collaborative and <strong>seek opportunities to make an impact.</strong></p><p>How to resonate: Mobile first with a focus on ease of use and proactive involvement.</p><h3><strong>Gen Z</strong></h3><p>Born: 1997+ | Age: 0–21 | Current population:~86 million (<em>and counting!</em>)</p><p>Those in Gen Z are the newest generation, growing up with the internet and an inherent craving for all things instant. They’re multi-tasking masters when it comes to emerging technology and first to engage with the latest trends. They’re highly visual go-getters and <strong>view technology as an extension of self</strong>.</p><p>How to resonate: Short videos or other easily digestible media that tell the story visually.</p><h3>Compelling At Any Age</h3><p>Regardless of age or demographic, <strong>messaging should always strive to be relevant, personalized, and contextual</strong>. Being well-versed in your user’s wants, needs, and expectations is an important (if not the MOST important) piece of creating an experience that resonates.</p><p>So remember: people read what matters to them. If your user experience hits home, they’ll be more apt to keep the conversation going and stick around for the long haul.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=beae02609173" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/writing-for-every-generation-beae02609173">Writing For Every Generation</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[People Don’t Read]]></title>
            <link>https://medium.com/@andyazcu/people-dont-read-f4361114a01?source=rss-81913a8cf8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4361114a01</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Andrea Azcurra]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 19:34:50 GMT</pubDate>
            <atom:updated>2019-04-04T18:32:45.539Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zkpHKObi-YQNgEK_jpTADA.png" /></figure><blockquote><strong>“People don’t read.”</strong></blockquote><p>Ah, the phrase heard round and round the product development world. If you’re a writer, you’ve probably heard this roughly 1.5 billion times. It’s a common defense for cutting copy and relying on design to do the heavy lifting. But, as someone who makes a living off of people reading, I’m here to champion the contrary.</p><p>First, let’s dive a little deeper into the sentiment itself. How did it originate? Is there proof of concept? And why has it been so largely accepted as a UX principle?</p><h3>Back To The Future</h3><p>The earliest known acts of reading date back to the invention of writing in the 4th millennium BC. For a while, the norm was reading everything aloud, often in a communal setting. <em>Imagine reading every word in an app out loud as you use it…</em>During the Age of Enlightenment, reading was encouraged as a means of education and philosophical interpretation. The invention of the printing press made content accessible to the masses, and up until the late 1990s, books, magazines, and newspapers were still the most common way of digesting information.</p><p>At the dawn of the internet, reading experienced a revolution. Words became pixels, messages were instant, and the whole process of communication became faster, easier, and more passive than ever before. Screens have become a way of life, but it didn’t happen overnight. Every year for the past decade there’s been some sort of advance in technology that makes the mere idea of words seem obsolete. <em>Just think about the last time you liked an Instagram post for the caption or wrote out your true feelings instead of replying with an emoji.</em></p><p>It seems we’ve gone from treasuring reading as a means of leisure and escape to damning it as an unbearable task that’s time-consuming and just plain unnecessary. Slowly but surely, we’ve been trained to use and understand things visually, sans sentences.</p><h3>To Read Or Not To Read</h3><p>It’s true, our habits have changed. And people want experiences that match their habits, that’s UX 101. But do people really want those experiences to be as quick and painless as possible? As a UX writer and fellow human, I beg to differ.</p><p>I work in real estate tech, helping to create an all-in-one platform for agents to communicate with clients, promote listings, and close deals. And a huge part of my process is understanding our users — digging deep into their intentions, expectations, and ultimately, surfacing problems and solutions.</p><p>It’s no surprise the bulk of a real estate agent’s job is done outside the office, which means they’re extremely mobile users. With any on-the-go user flow, it’s common to assume it’s all about speed and automation and the product strategy follows suit. But in speaking with agents directly and working with our research team to test copy in design, we’ve discovered that less is actually <em>not</em> more.</p><p>Our agents do care about speed. They do want to be able to create a social post or email campaign relatively quickly. For them, time is of the absolute essence when it comes to selling homes. But their usability problems aren’t manifesting because of how many words are on the screen. It’s about what they say. It’s a classic tale of quality vs. quantity. And research doesn’t lie. Our agents didn’t need less information. What they really needed was more context.</p><h3>Conclusion</h3><p>As much as we’d like it to be, UX is not black and white. There’s a whoooooole lot of grey. Brevity is not always the answer and reading is not extinct. It’s just become more selective. So when it comes to “People don’t read”, I’ll agree to disagree.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4361114a01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flying Solo]]></title>
            <link>https://medium.com/@andyazcu/flying-solo-da0fbdee840d?source=rss-81913a8cf8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/da0fbdee840d</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Andrea Azcurra]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 15:52:10 GMT</pubDate>
            <atom:updated>2019-03-22T19:07:03.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PgIHsXgCXo_cyGsT-OU_rA.png" /></figure><h3><strong>Me, Myself, and UX</strong></h3><p>9 months ago I embarked on a journey I didn’t know would transform my career. It’s been the ultimate test of my patience, confidence, and resilience. No, it wasn’t finally publishing my first novel (I wish) or going Twitter viral (no thanks). It was a job at a tech company as the only UX writer.</p><p>Yes, you read that right. <em>Only UX writer.</em> As in: <strong>I’m the only content expert in my 100+ person product org.</strong> But that’s not the weird part. The weird part is this is the norm in the industry right now and we need to change that.</p><p>Browse any product design thought leadership piece and you’ll see that UX is becoming integral to business success. Ask any great CTO and they’ll tell you your user experience should drive your go-to-market strategy. Companies like Google, Spotify, and Dropbox have invested a lot of time and money into building out UX teams and have become tech giants because of it.</p><p>But “UX”, for most of its youthful existence, has referred primarily to designers and engineers. I don’t believe people intentionally forgot about writers. Someone has to hashtag the company Instagram! But the hard truth is our legacy is that of Mad Men-esque storytellers, not product developers. And teams learned to do their jobs without us.</p><p>…..but <em>why</em>?</p><h3>Miss Interpretation</h3><p>I blame this sentiment: <strong>“People don’t read”</strong>. Nowadays it’s easy to believe that. The average human attention span is 8 seconds. <em>Insert zombie-like scrolling tendencies in an increasingly hyper-visual, on-demand society.</em> But it’s also easy to forget that some of the most basic everyday activities couldn’t happen without language.</p><p>Imagine texting someone “Good morning!” but you had to do it without using words. It’s not impossible — everyone with a phone would instinctively choose a gif or emoji. But what if the other person interprets it wrong? That “😑☕️”, to them, means “I’m so unbelievably tired” and now the narrative and its expectations have changed.</p><p>Without the right words, misinterpretation is inevitable. And it’s a product’s worst enemy. It’s also exactly why it’s <strong>so important to think strategically about how we communicate in design</strong>. Yes, visual cues can tell a story (or in the product sense, guide a user to complete a task). But language has the power to make things personal, to resonate on levels that a beautiful interface alone cannot. In the end, great user experiences are more than their code and pixels. They need context and relevance, too. And that’s the part of UX where writers thrive.</p><h3>Fueled By Uncertainty</h3><p>So, 9 months ago I starting thriving. I dove headfirst into creating content standards, rewriting most of our app, and owning my expertise. My role isn’t clearly defined. Every day is an exercise in education, advocacy, and assertiveness. UX writing is a whirlwind profession and most of us, like me, are flying solo. But part of gaining trust and honing our unique craft is making sure we have a seat at the table. Only then will people realize writing isn’t the frosting. It’s actually the cake.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da0fbdee840d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveling Up: How Playing Video Games Can Make You a Better Writer]]></title>
            <link>https://medium.com/@andyazcu/leveling-up-how-playing-video-games-can-make-you-a-better-writer-b13fe9ac3182?source=rss-81913a8cf8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b13fe9ac3182</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[writing-tips]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Andrea Azcurra]]></dc:creator>
            <pubDate>Thu, 13 Dec 2018 16:50:47 GMT</pubDate>
            <atom:updated>2018-12-13T18:22:11.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*613SL8exAjUqz9V9zAUOsw.jpeg" /><figcaption>Ah, the good ol’ days.</figcaption></figure><p>Most UXers I know share the desire to make things that matter—by definition, a product or experience that impact people’s lives in a positive way. But in order to keep up the motivation to create said things, we need a constant stream of inspiration.</p><p>For writers, it’s crucial to always have a sense of what’s relevant to our audiences. That’s the challenge we face on a day-to-day basis. What’s the magic formula to get people to sign up? Even more daunting: what will make them stay?</p><p>Learning more and more about what makes people tick is one of my favorite things about being a writer. More often than not, you can find me in between the pages of a new book, at a local coffee shop people watching or neck-deep in documentaries on Netflix. These might seem like eccentric study materials, but understanding what’s important to people and why they do the things they do requires some rather unconventional research.</p><p>When I was little, I spent hours watching my dad play RPGs on PlayStation. I was enamored with the storylines, characters, and interactions and got completely swept up in those intricate virtual worlds. Many times I’d go so far as to re-enact scenes with my brothers. “I’m Solid Snake and you guys be the guards,” I’d yell as we built a makeshift war zone in our living room, complete with blanket fort tunnels and a cardboard-box Metal Gear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*j_Emc4QdA6otbk9SNHRt4g.jpeg" /><figcaption>Sassy banter, anyone?</figcaption></figure><p>Something about all those Saturday afternoons helped me understand the way people work in the purest way possible: seeing the world through the eyes of someone else. After a lifetime of investigating, I’ve eventually found a common theme. Most people want to succeed. We have an inherent desire, whether real or fictional, to be the hero. After all, even villains strive for the coveted “most evildoer in the universe”.</p><p>Like the main character in a video game, most people are on a path to personal victory. That’s what UX writing is all about — tapping into what makes people feel like a champion, giving them a realistic goal to reach, and a piece of the map to find a way to get there.</p><p>Sometimes it’s obvious. Sometimes we have to do a little digging. So whether it’s getting nostalgic with old levels of Mario or figuring out which spell to cast next in Final Fantasy, it’s all useful in becoming a better writer. There’s a power-up in there somewhere, it’s just up to us to use it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b13fe9ac3182" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>