<?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 Julia Goncalves on Medium]]></title>
        <description><![CDATA[Stories by Julia Goncalves on Medium]]></description>
        <link>https://medium.com/@julia-goncalves?source=rss-5dd0ee7972a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7umbU3xnwJKujzkrKuaFcg.png</url>
            <title>Stories by Julia Goncalves on Medium</title>
            <link>https://medium.com/@julia-goncalves?source=rss-5dd0ee7972a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:10:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@julia-goncalves/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[Escrevendo para um produto global]]></title>
            <link>https://julia-goncalves.medium.com/escrevendo-para-um-produto-global-e4bf52176ccc?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4bf52176ccc</guid>
            <category><![CDATA[localização]]></category>
            <category><![CDATA[tradução]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Wed, 23 Nov 2022 17:26:43 GMT</pubDate>
            <atom:updated>2022-11-23T17:26:43.452Z</atom:updated>
            <content:encoded><![CDATA[<h4>A jornada de uma UX writer não nativa de Inglês escrevendo para um produto global.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*zSBGjb3X-s40NTjWbdAHdA.png" /><figcaption>Charco by <a href="https://blush.design/artists/2R6I2GWLU5B6Czx7Jma4/karthik-srinivas">Karthik Srinivas</a></figcaption></figure><p>Um ano se passou desde que comecei a trabalhar na <a href="https://www.pipefy.com/pt-br/">Pipefy</a>, e que experiência tem sido!</p><p>Desde o processo de seleção, um aspecto que me fez brilhar os olhos, foi o desafio de escrever para um produto global. E o que isso significa?</p><p>Significa que tudo o que escrevemos para a interface do nosso produto, é pensado primeiramente em Inglês, e mais: consideramos aspectos não apenas gramaticais, mas também aspectos culturais e tendências linguísticas para entender a nossa pessoa usuária e endereçar os problemas ou oportunidades no produto.</p><p>Dando alguns passos para trás, essa não é a primeira vez que eu trabalho em um produto com versões para diferentes idomas, mas é a primeira vez que o Inglês se tornou o meu idioma de trabalho principal.</p><p>Antes da Pipefy, eu escrevia exclusivamente em Português, e tudo que eu criava passava pelo time de tradução <em>(Oi, </em><a href="https://www.linkedin.com/in/jacoboleen/"><em>Jacobo</em></a><em> e </em><a href="https://www.linkedin.com/in/peterstanley1/"><em>Peter</em></a><em>!).</em> Esse time garantia a qualidade do conteúdo traduzido e localizado para o Inglês e Espanhol. Embora tivéssemos uma plataforma de localização chamada <a href="https://crowdin.com/">Crowdin</a>, eram eles que verificavam se todos os títulos, instruções e CTAs estavam adequados nos outros idiomas.</p><p>Depois de um tempo, esses profissionais foram alocados na equipe de Design de Produto para que nosso trabalho ficasse ainda mais conectado, já que eles também precisavam entender o contexto das nossas soluções de design e as nossas pessoas usuárias. Um exemplo de como esse processo se tornou intrínseco ao nosso dia a dia, é termos adicionado um guia de localização ao nosso <a href="https://tangram.rdstation.com.br/docs/guidelines/localization/">Design System</a>.</p><p><strong>Com essa experiência anterior ao Pipefy, pude entender como a </strong><a href="https://rockcontent.com/br/blog/localizacao-de-produtos/"><strong>tradução e a localização</strong></a><strong> são vitais para qualquer negócio que deseja garantir a melhor experiência para qualquer público. Aprendi como os tradutores podem ser um bem precioso e como eles complementam muito bem o meu papel de UX writer.</strong></p><p>Na Pipefy eu sabia que não teríamos pessoas especializadas cuidando da qualidade da tradução e localização do produto. Uma justificativa para isso era a de que no time de conteúdo tínhamos pessoas americanas, e elas revisavam os textos. Esse processo, por mais que não fosse o ideal, resolvia.</p><p><em>Mas o que isso impactava na minha atuação? </em>Muito<em>.</em></p><p>Cada linha de texto deveria ser entregue em Inglês e Português, o que significava o dobro da carga de trabalho para mim como UX writer solo. Além disso, não ter uma cultura ou processo de localização dentro da empresa fez com que algumas partes do produto não estivessem traduzidas corretamente ou estavam traduzidas de maneira inconsistente. Só isso já levou um tempo para consertar.</p><p>Após os primeiros meses, eu sabia que tinha muito o que estudar e investigar para entender os aspectos linguísticos e culturais das nossas pessoas usuárias, e ainda reforçar a necessidade de uma equipe especializada em localização na Pipefy.</p><p>Para poder escrever em Inglês levando em consideração os aspectos de localização, e sem uma equipe me apoiando, contei com a minha parceria com a equipe de pesquisa. Isso me deu a energia para iniciar o processo de entender e validar nossas decisões de conteúdo.</p><p>Uma das primeiras estratégias foi sempre trazer pessoas nativas do Inglês para todo e qualquer estudo de pesquisa. Gerávamos um roteiro em Inglês e Português para entrevistas, por exemplo, e versões nos dois idiomas também para os testes não moderados.</p><p>Nunca deixa de me surpreender como os resultados dessas pesquisas são consistentemente diferentes entre pessoas falantes de Português e Inglês. Se simplesmente traduzíssemos o conteúdo, estaríamos usando palavras e expressões que estariam longe do que ressoa com as pessoas usuárias.</p><p>É importante pontuar um desafio para o nosso time: a nossa base de clientes fora do Brasil é menor do que a base de clientes no Brasil, o que torna o recrutamento de pessoas falantes de Inglês mais demorado. Para contornar esse obstáculo, contávamos com plataformas como <a href="https://www.usertesting.com/">User Testing</a> e <a href="https://www.userinterviews.com/">User Interviews</a> para recrutar e testar rapidamente.</p><p>Um aspecto curioso que aprendemos ao longo do caminho é o quão objetivas as pessoas falantes da língua inglesa geralmente são. Para se ter uma ideia, um roteiro de entrevista que com brasileiros dura em média 50 minutos, com pessoas não brasileiras cai para quase a metade.</p><p>Diferenças entre número de caracteres dos textos é algo que constantemente estamos nos preocupando também, pois em Português os textos tendem a ficar bem maiores do que quando comparado ao Inglês.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*BAyrKythn8r-_B_MiP9SgA.jpeg" /><figcaption>A dor de escrever para produto em Inglês e depois localizar para Português</figcaption></figure><p>Participar das pesquisas em Inglês e Português, me fez aprender muito sobre como a cultura reflete na maneira como as pessoas se expressam e compreendem os conteúdos. Essa imersão é o que me permitiu escrever para um produto global, mesmo não sendo uma pessoa nativa do Inglês.</p><p>Ainda estamos trabalhando para um processo de tradução e localização maduro no Pipefy, mesmo sem um time especializado dando suporte.</p><p>Nessa jornada de aprendizado, reforço mais uma vez a necessidade desse perfil de profissional trabalhando em parceria com Designers de Produto, Gerentes de Produto e Pessoas Desenvolvedoras.</p><p>Espero que esse artigo tenha lhe ajudado a encontrar caminhos para atuar ou mesmo a reconfortar de que você não está sozinha. Boa localização para você!</p><p><a href="https://julia-goncalves.medium.com/writing-for-a-global-product-e75bd01a2b18"><em>This post is also available in English.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4bf52176ccc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing for a global product]]></title>
            <link>https://julia-goncalves.medium.com/writing-for-a-global-product-e75bd01a2b18?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e75bd01a2b18</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[translation]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Wed, 23 Nov 2022 16:17:04 GMT</pubDate>
            <atom:updated>2022-11-23T17:19:30.224Z</atom:updated>
            <content:encoded><![CDATA[<h4>The journey of a non-native English speaker working as a UX writer for a global product.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*zSBGjb3X-s40NTjWbdAHdA.png" /><figcaption>Charco by <a href="https://blush.design/artists/2R6I2GWLU5B6Czx7Jma4/karthik-srinivas">Karthik Srinivas</a></figcaption></figure><p>A year has passed since I began working at <a href="https://www.pipefy.com/">Pipefy</a>, and what an experience it has been!</p><p>An aspect that caught my attention since the first interview with the Pipefy team was the challenge of writing for a global product. What does that mean, one might ask?</p><p>It means that everything we write for the product’s interface is written primarily in English. We consider more than just grammar but also cultural aspects and language trends when understanding our users and addressing the product’s problems or opportunities.</p><p>Taking a step back, this is not my first time working on a product with different language versions. However, it is the first time that English has become my primary working language.</p><p>Before Pipefy, I used to write exclusively in Portuguese, and the translation team localized everything I created. (Hi, <a href="https://www.linkedin.com/in/jacoboleen/">Jacobo</a> and <a href="https://www.linkedin.com/in/peterstanley1/">Peter</a>!) This team was responsible for quality assurance of the translated and localized content. Even though we used a localization platform called Crowdin, they checked that all titles, instructions, and CTAs were accurate in English and Spanish.</p><p>After a while, these professionals were assigned to the Product Design team so our work would be even more connected. After all, they needed to understand the context of our design solutions and our users. An example of how this process has become essential to our daily lives is that we added a localization guide to our Design System.</p><p><strong>Through this experience, I understood how vital </strong><a href="https://www.mindtheproduct.com/implement-product-localization-strategy/"><strong>translation and localization</strong></a><strong> are for any business that wishes to reach a broader audience. I learned how translators can be valuable assets and how they complement my role as a UX writer very well.</strong></p><p>When I joined Pipefy, I knew there wouldn’t be a specialized team that handled translation and localization quality. Before my arrival, American colleagues from the Marketing Content team used to review some of the content created for the product. Despite its shortcomings, this process was effective.</p><p>And in what ways did that affect my work? Quite a bit.</p><p>Every line of text should be delivered in English and Portuguese, which meant double the workload for me as a solo UX writer. Also, not having a localization culture or process within the company meant that some parts of the product were not translated correctly or were inconsistent. This took a while to fix.</p><p>After the first few months, I knew I had a lot to study and investigate to understand our users&#39; linguistic and cultural aspects while highlighting the need for a team specialized in localization at Pipefy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7GjRg4Pib35QMn3pu-SeBA.jpeg" /><figcaption>In my case, change Spanish to Portuguese.</figcaption></figure><p>To be able to write in English, considering the localization aspects, and without a team supporting me, I relied on my partnership with our UX research team. That gave me the motivation to understand and validate our content decisions.</p><p>It was crucial to bring native English speakers to the moderated research stages. Likewise, we always generated versions in English and Portuguese for unmoderated tests. Additionally, we could rely on platforms like <a href="https://www.usertesting.com/">User Testing</a> and <a href="https://www.userinterviews.com/">User Interviews</a> to recruit and test quickly.</p><p>It never ceases to amaze me how consistently different the research results are between Portuguese and English speakers. By simply translating the content, we would rely on words and expressions that would not resonate with users.</p><p>It is important to point out a challenge for our team: it takes longer to find English-speaking testers outside Brazil due to a smaller client base.</p><p>We learned another curious fact along the way: native English speakers are generally more objective. To give you an idea, interviews that last an average of 50 minutes with Brazilians drop to almost half with non-Brazilians.</p><p>Also, we are constantly concerned about differences in the number of characters between Portuguese and English because Portuguese texts tend to be much longer.</p><p><strong>Happy place</strong></p><p>Having participated in the research process, I have learned a lot about these cultural factors that affect how people express themselves and understand the content. That kind of immersion allowed me to write for a global product, despite not being a native English speaker.</p><p>We are still working towards a mature translation and localization process at Pipefy, even without a specialized team supporting us.</p><p>Through this learning journey, I again emphasize the importance of these professionals working closely with Writers, Product Designers, Product Managers, and Developers.</p><p>I hope this article has helped you find ways to act or even reassured you that you are not alone. Happy localization to you!</p><p><em>Você pode ler este conteúdo também em Português.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e75bd01a2b18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to evaluate the content of your UI?]]></title>
            <link>https://uxdesign.cc/how-to-evaluate-the-content-of-your-ui-b3201fc2935b?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3201fc2935b</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[content-writing]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 18:56:09 GMT</pubDate>
            <atom:updated>2021-09-09T22:10:47.042Z</atom:updated>
            <content:encoded><![CDATA[<h4>Conducting content testing and investigations.</h4><figure><img alt="illustration of a woman holding a flashlight that emits a purple light with a question mark in the middle." src="https://cdn-images-1.medium.com/max/1024/1*kJgvXpZnuro1zcqyYEC6RA.png" /><figcaption>Illustration by <a href="https://twitter.com/ninaLimpi"><strong>Katerina Limpitsouni</strong></a></figcaption></figure><h3>Why evaluate content</h3><p>Think of this step as prototyping the conversation we should have with people using the product. So, test for:</p><ul><li>Establish a structure for our conversations with people, create patterns.</li><li>Understand the words we need to use so that people understand us.</li><li>Understand the information and emotions that interfaces need to convey.</li><li>Understand if what we present in the interfaces is the information that needs to be shown (if there is too much or is missing) and how it makes people feel. Are they low on trust, for example? From this, we have a better vision of what and how to communicate.</li></ul><h3>What to test first?</h3><p>Testing and measuring the effectiveness of content always happens from the macro to the micro.</p><p>In the macro stage, we will be thinking about questions like:</p><ul><li>Are our general keyword choices attacking the pain points?</li><li>How does the product relate to the language people use? Is there anything else that Marketing emphasizes?</li><li>Does the user have enough context to go through our main task streams</li><li>Do people understand what we are communicating on each screen and what its purpose is?</li></ul><p>In the micro stage, we will try to respond to:</p><ul><li>Are our CTAs clear, effective, and motivating?</li><li>Do our commands provide enough information for people to pass through points of friction or trust in our task flows?</li><li>Do users understand our labels, titles, instructions, and functionality?</li></ul><h3>Readability x Reading x Comprehension</h3><p>We can investigate the effectiveness of a text in terms of its readability, readability, and comprehension.</p><h4>Readability</h4><p>The readability of a text tells us about a person’s ability to see your text.<br>The faster the decoding of characters into concepts, the better their readability.<br>Some factors will influence this ability, such as font, body, width, angle, style (bold, uppercase), color, the contrast of the letter’s shape with its background, the length of the lines, the leading, the measurement of spacing, and margins. All of this has enormous weight in the readability of a text.</p><h4>Reading</h4><p>Ease of reading will measure the complexity of words and sentence structure in a piece of content.<br>The assumption behind this metric is that complex sentences are more complicated to read than more straightforward sentences.</p><h4>Comprehension</h4><p>Finally, the densest level is that of textual comprehension, which will depend on much more than just literacy skills but also the level of education and prior knowledge. The ability to understand the text measures the assimilation of words and ideas present in the text objectively.</p><p>That is if a person understands the intended meaning of a text and draws the correct conclusions about it.</p><p>We also want them to perform the intended actions after reading the text in instructional or action-oriented content.</p><ul><li>All of these aspects must be considered when testing for content. What are you looking to investigate with your test? Ease of reading only, or understanding as well?</li><li>It is essential to define the target audience for the test clearly, and that it represents the actual user. Avoid testing internally, as the load of prior knowledge can be too great and compromise the results, except for cases where doubt may prevent the finalization of the product taken for testing.</li><li>Clearly outline the content to be tested. The smaller the scope, the better. You can even test just phrases. And always remember to contextualize the person who will respond and explain what is expected of them.</li><li>Reinforce that answering “I don’t know” is possible. A guessed answer is not interesting for investigation. If the person doesn’t know how to answer or complete the task, ask about what they wanted to find on that screen, for example. Explore the moment.</li></ul><h3>Methods</h3><p>Once you have defined what you intend to test, define the best method. There are several out there. I’ll leave some examples below of good articles about various testing methods:</p><p><strong>Discovery</strong></p><ul><li><a href="https://xd.adobe.com/ideas/process/information-architecture/card-sorting-best-practices/">Card Sorting</a></li></ul><p><strong>Explorations</strong></p><ul><li><a href="https://userresearch.blog.gov.uk/2014/09/02/a-simple-technique-for-evaluating-content/">Highlighted test</a></li><li><a href="https://uxpamagazine.org/writing-usable-survey-questions/">Surveys</a></li></ul><p><strong>Validation and Iteration:</strong></p><ul><li><a href="https://www.nngroup.com/articles/usability-testing-101/">Usability</a></li><li><a href="https://neilpatel.com/blog/ab-testing-introduction/">A/B testing</a></li></ul><h3>Tools</h3><p>I have used the following tools to apply content evaluation. Here are my highlights on each of them.</p><h4>Qualtrics</h4><p>This is the motherload of all surveys software. With <a href="https://www.qualtrics.com/">Qualtrics</a>, you will find a huge variety of question types, which will help you a lot in the evaluations. Its interface is not the friendliest, but it’s worth it. Especially when we talk about the Reports, it is unnecessary to open any excel file to compile the data and cross-reference answers.<br>It’s expensive, but it’s awesome for surveys.</p><h4>Alchemer</h4><p>Use <a href="https://www.alchemer.com/">Alchemer</a> if you are on a budget and still need good survey software. You will find a good amount of question types specific for content evaluation. Their report is also robust. It gets the job done.</p><h4>User Testing</h4><p>I love working with <a href="https://www.usertesting.com/">User Testing</a>. Despite their usability issues, it’s remarkable how quickly you can recruit and test prototypes. The video analysis is also excellent. You can make notes and clips of users testing your product. 10/10</p><h4>Full Story</h4><p><a href="https://www.fullstory.com/">Fullstory</a> is a platform that allows you to understand better the behavior of users and how their experience is going. It’s like Hotjar, but with steroids. You can filter sessions to get a more accurate perspective of how users interact with your pages or content.</p><h3>Highlights</h3><ul><li>UX Writing and UX Research MUST walk hand in hand. Research is an essential part of creating quality UX writing. So work closely with the UX Researcher of your team, if you have one.</li><li>Remember: If you have data to back your UX Writing decisions, everything flows better. Evaluating your decisions is one of the best ways to prove the UX Writing ROI.</li><li>Don’t rely on just one method of research. We have a lot of tools to help us experiment and bring results fast.</li><li>Research allows us to create copy with the end-user in mind. Don’t write copy for yourself!</li><li>Engage with your target audience. Build a list of users enthusiastic to test your prototypes and participate in early surveys. Trust me, recruiting is a crucial part of your research and a very exhausting one.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3201fc2935b" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-evaluate-the-content-of-your-ui-b3201fc2935b">How to evaluate the content of your UI?</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[5 coisas que aprendi com Compliance]]></title>
            <link>https://medium.com/design-rd/5-coisas-que-aprendi-com-compliance-53b3bca0d9d5?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/53b3bca0d9d5</guid>
            <category><![CDATA[ux-writer]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[lgpd]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Thu, 12 Nov 2020 20:29:55 GMT</pubDate>
            <atom:updated>2021-09-08T13:33:37.078Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 things I learned from Compliance</h3><h4>Here are my lessons on creating texts with the new data protection laws in mind.</h4><p>Since 2019, when the <a href="http://lawsofbrazil.com/2020/09/18/brazils-data-protection-law/">General Data Protection Law</a> (GDPL) had not yet been enacted, we at RD Station have been developing tools that allow our customers to <strong>build a more transparent relationship with their consumers</strong>.</p><p>These efforts allowed me to work closely with the Compliance tribe, supporting the creation of texts that had the function of engaging the adoption of our tools and providing <strong>guidance</strong> on their use, and <strong>educating</strong> about the GDPL itself.</p><p>As this is still a very nebulous topic for most small and medium-sized companies in Brazil, which are our main customers, explaining what the law says and its implications for the use of our product was essential.</p><p>The team did and still does super lean work. We do experiments all the time to improve the experience and adoption of the Compliance tools within the product. <em>Sometimes I felt like I was changing the tire of the car while it was moving. And that was really good!</em></p><p>“But what do you mean by that, Julia?”</p><p>I mean that we couldn’t feel comfortable. All the time, new data was making us rethink and propose improvements. And that forced us to test a lot and bet on several different approaches for the Compliance tools.</p><p>Out of this entire process, I’ve picked out 5 main points that can light the way for others involved in product suitability for GDPL.</p><h4>#1. Ask the right questions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*BIzDW0XBVFMo9BoD0Bd_-g.gif" /></figure><p>After a round of in-product Compliance tool releases, followed by usability testing, I suggested a break. I prompted questions about why people were struggling to engage and start using the tools.</p><p>Until then, we had no data on our customers’ level of knowledge about the GDPL and its impacts on their business or how they were preparing for the new legislation.</p><p>Some of the questions we asked ourselves were:<br>- What is the level of familiarity with the subject?<br>- How long did our customers think they would be able to comply with the law?<br>- What were their main difficulties in this imminent adjustment?<br>- General knowledge about some terms intrinsic to the GDPL, such as privacy, legal bases, and consent.</p><p>Starting to understand this scenery was very important for us to evolve the tools assertively.</p><h4>#2. Test and test again</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*6MjHyfIgOTakkSUhgyAwqQ.gif" /></figure><p>From point #1 came a very extensive survey that we carried out with our customers. We had some hypotheses that needed to be corroborated or overturned by evidence. So, in addition to usability testing, we surveyed our entire customer base, from which we took much input to attack the Compliance education part.</p><p>Plus, I had the chance to run questions about the general content and terms regarding GDPL, leaving aside the visuals or interactions. My intention was solely to test people’s understanding of what I had been writing. For this, I used the <a href="https://www.qualtrics.com/">Qualtrics</a> research platform with highlighter questions.</p><p>In other words, this research step helped us better address customers’ pain points of understanding the new law and using our tools within the product, and also brought me actionable ideas for content changes.</p><h4>#3. Know what the law says, and translate it</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*x6rpjb1x2BgKJtBjFfitCg.gif" /></figure><p>With the survey results, it was evident that it was not enough for me to understand what the law said. The hard work was writing, leaving all those terms that can scare the user away in a much more helpful, familiar, and human way.</p><p>In the analyses, people claimed to know the law, but this did not make them understand how they should act in a practical way. So my focus was to “translate” the GDPL into clear instructions that told not only how but also why Compliance tools were essential and the consequences of not complying.</p><h4>#4. Be straightforward</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*Wr0kIvw5CDgAvPiibZAL_g.gif" /></figure><p>One of the ways I found to “translate” the law into the product and provide clear instructions was to be as transparent as possible. And if that meant having more text on the screen, that was fine.</p><p>We understand that we were working on education and adaptation, so a transparent text, very explanatory, with no implied information, was our bet.</p><p>We really worked on the standardization of terms, a safe tone of voice, and even used indicative icons on all screens with a Compliance tool. Those details helped users to become more and more familiar with the subject.</p><h4>#5. Work together with other areas</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*y-ukQcKK6capyeV490AGNw.gif" /></figure><p>Many times, the designer, the person responsible for the Legal perspective, and I sat down together to write. This was super valuable as it helped us standardize terms and expressions across the tools.</p><p>These moments also helped me better understand some legal terms and translate them into simpler terms without involving the company in legal matters.</p><p>And last but not least, it accelerated the process of “selling the UX Writing strategies” to the DPO. If it were up to the Legal team, they would put the entire law text into the product 😬 So, we worked together to show everyone the importance of a simple, concise text and its reasons.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53b3bca0d9d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-rd/5-coisas-que-aprendi-com-compliance-53b3bca0d9d5">5 coisas que aprendi com Compliance</a> was originally published in <a href="https://medium.com/design-rd">Design RD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Criando um processo de trabalho entre UX Writers e UX Designers]]></title>
            <link>https://medium.com/design-rd/criando-um-processo-de-ux-writing-257ac67c076f?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/257ac67c076f</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[processo-de-trabalho]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Thu, 15 Oct 2020 18:54:06 GMT</pubDate>
            <atom:updated>2021-09-08T14:11:48.754Z</atom:updated>
            <content:encoded><![CDATA[<h3>Creating a work process between UX Writers and UX Designers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DcIbTzqVkLeZ9F5lfWVuhQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thomaskinto?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thomas Kinto</a> on <a href="https://unsplash.com/s/photos/work-together?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Fellows UX Writers,</p><p>Have you ever felt like you were being included too late in the design process?</p><p>Or were you presented with a shiny navigable prototype without having had a chance to understand the discovery process or participate in solution ideas and discussions?</p><p>Have you ever been called just to proofread the text? 👀</p><p>If you feel like you still don’t have space in the Design team or that people still don’t know what you do as a UX Writer… Do not be sad! I’ve been through this, and I’m sure most UX Writers out there too!</p><p>Wipe these tears and read this because I will tell you about my way of adjusting my work until I reach what I consider to be a process that works with our designers here at RD Station.</p><h3>Challenges</h3><h4>Big team with different types of people</h4><p>In our Design Chapter, as in any group of human beings, there are people with the most different personalities (thankfully, right?). Here we have people who like to work more collaboratively, others who prefer to work individually with timely meetings. Some have a greater textual “maturity,” and others are still working on it, and this implies a more dedicated look or not over the content…</p><p>In other words, it is practically impossible for you to have a single way of working with your design team. You can’t expect people to adapt to your way of working, and you will have to <strong>be flexible and get to know as much as possible all the people on your team</strong> and pick out these nuances in each one. Sometimes, this will determine the level of depth your work should have with each of them.</p><h4>Different types of requests</h4><p>Cool! We know we have a diverse work team. But what about our demands? Here at RD Station, we have several Squads, and they bring different types of requests with varying degrees of urgency, so the way of acting also needs to be personalized.<br>There are more dense works, such as redesigning or creating new features, and more punctual demands, such as improvement of some component, instructions, or error message. <strong>Depending on the type of demand, you will also need to make your acting more flexible.</strong></p><h4>Project entry time</h4><p>I was the first UX Writer here on RD Station, and it took a while for people to get to know me and understand what I do. I was often included in a project or demand too late, making it difficult for further development, questions, and exchanges with the team.</p><p>Sometimes, the work of UX Writing was perceived as a review of the texts or just a validation of what was proposed, and if there was something really wrong with them, I was expected to point out.</p><p>Here comes the one thing that I used to repeat a lot on the team: <strong><em>don’t forget about me!</em></strong> And that was very necessary in the beginning.</p><p>People didn’t have the experience of working with someone in my field, so they ended up forgetting to include me in the demands 😭 but over time, and a lot of insistence, it became more natural.</p><h4>Tools</h4><p>I wouldn’t say it’s the most important thing, but creating some UX Writing guides for the team can make your role more solid.</p><p>I developed a writing style guide, glossary, content testing guide, framework for creating texts for the product, which made the perception of my work greater.</p><p><strong>People came to talk about these materials. </strong>I was able to speak about them and share knowledge with the company. All of this helped strengthen relationships and make people understand my scope of work.</p><h4>Open your horizons</h4><p>At RD Station, I had numerous opportunities for professional growth. I <strong>learned a lot</strong> about UX Research, Compliance, Data, and more, and I always took the UX Writing vision to these areas of knowledge.</p><p>These opportunities were precious for me, and, again, they helped to consolidate UX Writing as an area that doesn’t need to be closed in the product text. Our perspective on flows and overall content is very valuable for the most diverse areas.</p><h3><strong>Lessons</strong></h3><p>With time, the team and I got in tune, and after the adaptation phase, we learned a lot from each other.</p><ul><li>Working in a team with different people, I needed to create different work models. With some people, I do 60-minute meetings, and in that time, we solve a demand. I have weekly syncs with others, where we discuss in more depth, do planning together, and even do UX surveys.</li><li>I always tried to clarify that the type of demand or the amount of text involved was not a determinant of the time needed to develop the work. So it was essential to have this lined up because people think that because it is, for example, a button label, the work will be “quick.”</li><li>The sooner the UX Writing person is included in the development process, the better. Understanding problems is faster, doubts are resolved more shortly, the conversational flow becomes more cohesive, and the whole user experience is more likely to be better.</li><li>Working together has the potential to raise the UX Writing bar for everyone. Designers start to understand better the nuances of Writing, and with time, they bring a much deeper look over the words we use. And from the Writing perspective as well: being able to participate in the initial conversations makes it possible to understand better our clients, the business objectives, metrics, and specifics of Design decisions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/202/1*CjnpSHIIJAmRZlUnC7B03Q.gif" /><figcaption>Teamwork!</figcaption></figure><p>So don’t be discouraged, the path of UX Writing is beautiful, and it’s just getting started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=257ac67c076f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-rd/criando-um-processo-de-ux-writing-257ac67c076f">Criando um processo de trabalho entre UX Writers e UX Designers</a> was originally published in <a href="https://medium.com/design-rd">Design RD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[O que aprendi como UX Writer de um Design System]]></title>
            <link>https://julia-goncalves.medium.com/ux-writing-e-design-systems-84ee0c894785?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/84ee0c894785</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writer]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Mon, 31 Aug 2020 22:09:50 GMT</pubDate>
            <atom:updated>2021-09-11T14:43:59.485Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX Writing for a Design System: What I Learned</h3><h4>From a UX Writer’s perspective, the pains and joys of documenting a Design System.</h4><figure><img alt="Placa de lego azul, com uma peça de lego laranja sobre ela." src="https://cdn-images-1.medium.com/max/1024/1*C10bK59VyfYM31Hho3QDcA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@glencarrie?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Glen Carrie</a> on <a href="https://unsplash.com/s/photos/lego?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplas</a>h</figcaption></figure><p>This story is a continuation of the conversation about Design Systems that I started <a href="https://medium.com/design-rd/o-redesign-na-resultados-digitais-e-a-realidade-do-design-system-115dd224fc5c">here</a>.</p><p>How I helped build the Design System with the RD Station Design team and what an exciting learning experience it has been!</p><h3>Organization</h3><p>Here at RD Station, I work on the Design Ops team, and one of our big projects is the development of a Design System… and things can get pretty busy.</p><figure><img alt="Vemos um personagem da série The IT Crowd olhando para tela do computador e falando &quot;ajude me! ponto de exclamação&quot;." src="https://cdn-images-1.medium.com/max/498/1*wUIwhAdWF5s-J845OEDtYA.gif" /></figure><p>A critical point for me has always been to keep the requests organized. Luckily, we work well aligned with daily meetings and a very up-to-date Kanban, making it very easy to keep track of components in the backlog, those that are being designed, and those that are already under development on the front-end.</p><p>Keeping this routine is super important for a few reasons: you can study the components at the moment they are being created, and you can signal early on if you have any impediment from the writing part.</p><p>Another really cool point of working with the components from the beginning is that, as the UX Writer has a broader view of the product, it is possible to give opinions and bring valuable ideas to designers, who are often focused on just one use case of that component. You have a lot of chances to know more use cases than anyone else on the team.</p><p>Finally, I like to review and give help in writing the component documentation. It makes me understand even more about the application of each component.</p><h3>Tools</h3><p>Here we work with <a href="https://www.figma.com/">Figma</a>, <a href="https://storybook.js.org/">Storybook</a>, and <a href="https://zeroheight.com/">Zero Height</a>.</p><p>Before joining the team, I had never had contact with either of these tools, but I could count on the team to quickly learn some things that help me daily.</p><p>It is not necessary to understand them in detail, but this lets you contribute more actively to Design System construction.</p><h4>Figma</h4><p>In Figma, I created a branch of the writing style guide focused on components. In this component writing guide, I have mapped the main components and defined how texts should be constructed for them and use cases for what to do and what not to do.</p><p>Figma makes it much easier for people to learn best practices since they are in it all day long and don’t need to access another tool or document.</p><h4>Storybook</h4><p>Engineering uses Storybook to consume components. Therefore, the documentation in it needs to be 100% correct.<br>The Storybook needs to be updated when any changes are made to the component. Updates are performed on Github. As a result, I also learned how to submit PRs (pull requests), which is basically how I let front-end developers know about something that needs to be updated.</p><h4>Zero Height</h4><p>We use Zero Height to present the Design System to the entire company. It has a friendly interface, and the Figma integration makes it all easy.</p><p>Arranging everything on this platform helped us ensure that what people are using to create the screens are the latest versions of the components. In Figma, if the administration is not very well done, sometimes people end up using components that have expired.</p><h3>You will often have to redo</h3><p>When it comes to updating, it is pretty normal for some component’s definitions to be revised, and sometimes this will spill over into your work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*Zm--pSqGr4P0ulHCaY6Wjw.gif" /></figure><p>But don’t be frustrated! For me, this is one of the beauties of participating closely in the construction of a DS documentation. A few years ago, it was unthinkable to have someone looking at the text of this type of product, so it is a step forward to see a DS born already with the participation of a UX Writer.</p><p>Changes can often come from you. Fresh eyes make a difference, and, at the end of the day, a DS documentation has to be understood by everyone. It can’t be a developer-only product. Your role in this is important. Making documentation accessible is very important for the company as a whole.</p><h3>Highlights</h3><ul><li><strong>Beyond components:<br></strong>As I said earlier, I created the text definitions for components, but that went further. Within the Design System, we also have the guidelines for Localization and Accessibility, for example, which was an opportunity to learn a lot.</li><li><strong>Use cases:<br></strong>The more use cases you can present, the better for the Design System. Describe each component in detail, but make sure to provide a visual example of how it relates to your product. You will use real texts in these examples instead of the infamous Lorem Ipsum.</li><li><strong>Make it easier to read:<br></strong>A “TL;DR” is quite valuable for anyone wanting an overview of a component. A quick introduction with the main points about each element: what it is for, use cases, points of attention, etc.</li></ul><p>Have you ever participated in the process of creating a Design System as a UX Writer?<br>Tell me how it was!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/76/0*gDUPKUu4WlkaFrK7" /><figcaption>O UX Collective doa US$1 para cada artigo publicado na nossa plataforma. Esta história contribuiu para o <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: uma comunidade de desenvolvimento profissional para pessoas Pretas que são designers digitais em San Francisco. Por serem designers de um grupo pouco representado, membros do BABD sabem o que significa ser “o único” em seus times de design e em suas empresas. Ao se juntarem em comunidade, membros compartilham inspiração, conexão, mentoria, desenvolvimento profissional, recursos, feedback, suporte, e resiliência. Silêncio contra o racismo sistêmico enraizado na sociedade não é uma opção. Construa a comunidade de design na qual você acredita.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84ee0c894785" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Como testar textos para produto?]]></title>
            <link>https://julia-goncalves.medium.com/como-testar-copy-para-produto-78402f919add?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/78402f919add</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[content]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Mon, 27 Jul 2020 17:50:17 GMT</pubDate>
            <atom:updated>2020-09-01T12:27:15.190Z</atom:updated>
            <content:encoded><![CDATA[<h3>Como testar textos para produtos?</h3><h4>Uma série de modelos voltados para a realização de testes e investigações de conteúdo.</h4><figure><img alt="ilustração surrealista onde uma mão cinza estilizada escreve um texto em um papel, e um de seus dedos é um olho de cor verde." src="https://cdn-images-1.medium.com/max/912/1*_6GVkZsDgmb3A1WlhK_YIA.png" /><figcaption>Illustration by <a href="https://www.behance.net/nsnva">Olga Nesnova</a><br>from <a href="https://icons8.com/">Icons8</a></figcaption></figure><h3><strong>Por que testar conteúdo?</strong></h3><p>Pense nessa etapa como uma prototipação da conversa que devemos ter com as pessoas usuárias do produto. Logo, teste para:</p><ul><li>Estabelecer uma estrutura para nossas conversas com as pessoas, criar padrões.</li><li>Entender as palavras que precisamos usar para que as pessoas nos entendam.</li><li>Entender as informações e emoções que as interfaces precisam transmitir. O que apresentamos nas interfaces são as informações que de fato precisam estar sendo mostradas (se falta ou se tem demais) e como elas estão fazendo as pessoas se sentirem. Elas estão com pouca confiança, por exemplo? A partir disso, temos uma visão melhor do que e como comunicar.</li></ul><h3><strong>O que testar primeiro?</strong></h3><p>O teste e mensuração da efetividade de um conteúdo acontece sempre do macro para o micro.</p><p>Na etapa macro, estaremos pensando em perguntas do tipo:</p><ul><li>Nossas escolhas de frases-chave e de palavras no geral estão atacando os pontos de dor?</li><li>O que destacamos no produto se relaciona com a linguagem das pessoas que usam nossos produtos, e com o que marketing também destaca?</li><li>A pessoa usuária tem contexto suficiente para percorrer nossos principais fluxos de tarefas?</li><li>No geral, as pessoas compreendem o que estamos comunicando em cada tela e qual é a sua função?</li></ul><p>Na etapa micro, tentaremos responder a:</p><ul><li>Nossos CTAs são claros, efetivos e motivadores?</li><li>Nossos comandos fornecem informações suficientes para que as pessoas passem por pontos de fricção ou de confiança em nossos fluxos de tarefas?</li><li>As pessoas usuárias entendem nossos rótulos, títulos, instruções e funcionalidades?</li></ul><figure><img alt="ilustração surrealista onde uma cobra estilizada segura uma lupa sobre um olho de cor azul" src="https://cdn-images-1.medium.com/max/912/1*4CIlXWKJsC5KbP7WWK5qow.png" /><figcaption>Illustration by <a href="https://www.behance.net/nsnva">Olga Nesnova</a><br>from <a href="https://icons8.com/">Icons8</a></figcaption></figure><h3>Legibilidade x Leitura x Compreensão</h3><p>Podemos investigar a eficiência de um texto quanto a sua legibilidade, a facilidade de leitura e de compreensão.</p><h4>Legibilidade</h4><p>A legibilidade de um texto nos fala sobre a capacidade da pessoa de enxergar o seu texto.</p><p>Quanto mais rápida for a decodificação dos caracteres em conceitos, melhor é a sua legibilidade.</p><p>Alguns fatores irão influenciar nessa capacidade, tais como a fonte, o corpo, a largura, o ângulo, o estilo (bold, maiúsculas), a cor, o contraste da forma da letra com seu plano de fundo, o comprimento das linhas, o entrelinhamento, a medida do espaçamento e das margens. Tudo isso tem enorme peso na legibilidade de um texto.</p><h4>Facilidade de Leitura</h4><p>Já a facilidade de leitura irá medir a complexidade das palavras e da estrutura da frase em uma parte do conteúdo.</p><p>A suposição por trás dessa métrica é que frases complexas são mais difíceis de analisar e ler do que frases mais simples.</p><h4>Compreensão</h4><p>Por fim, o nível mais denso é o da compreensão textual, que irá depender muito mais do que apenas habilidades de alfabetização, mas também nível de escolaridade e conhecimento prévio. A capacidade de compreensão do texto mede a assimilação das palavras e ideias presentes no texto objetivamente.</p><p>Ou seja, se uma pessoa entende o significado pretendido de um texto e tira as conclusões corretas sobre ele.</p><p>No caso de conteúdo instrucional ou orientado para a ação, também queremos que elas possam executar as ações pretendidas após a leitura do texto.</p><ul><li>Todos esses aspectos devem ser considerados ao realizar testes para texto em UX. O que você está buscando investigar com o seu teste? A facilidade de leitura apenas, ou a compreensão também?</li><li>É muito importante a definição clara do público-alvo do teste, e que ele de fato represente a pessoa usuária real. Evite testar internamente, pois a carga de conhecimento prévio pode ser muito grande e comprometer os resultados, com exceção para casos em que a dúvida possa estar impedindo a finalização do produto que será levado para teste.</li><li>Delimite bem o conteúdo a ser testado. Quanto menor o escopo melhor, no caso, quanto mais quebrado for o texto melhor. Você pode testar linhas de texto mesmo. E lembre-se sempre de contextualizar a pessoa que irá responder, e explicar o que espera-se dela.</li><li>Reforce que responder “não sei” é possível. Uma resposta chutada não é interessante para a investigação. Se a pessoa não souber responder ou completar a tarefa, pergunte sobre o que ela desejava encontrar naquela tela, por exemplo. Explore o momento.</li></ul><p>Organizei os testes de acordo com os objetivos, mas você também pode aplicá-los de acordo com o momento do produto. Segue abaixo as sugestões:</p><p><strong>Descoberta:</strong></p><ul><li>Card Sorting</li><li>Google Trends</li></ul><p><strong>Exploração:</strong></p><ul><li>Marca Texto</li></ul><p><strong>Validação:</strong></p><ul><li>Cloze</li><li>Usabilidade</li><li>Teste A/B</li></ul><p><strong>Iteração:</strong></p><ul><li>Usabilidade</li><li>Teste A/B</li></ul><h3>Legibilidade: verificação de contraste</h3><p>Para checar a legibilidade de um texto temos algumas ferramentas prontas, como a do <a href="https://contrastchecker.com/">Contrast Checker</a>.</p><p>É muito importante sempre estar atenta a isso. Não deixe essa responsabilidade apenas nas mãos de quem está desenhando a interface, nós writers somos responsáveis por todos os aspectos do conteúdo, inclusive do cheque de contraste.</p><h3>Leitura: índice de leitura</h3><p>Calcule o índice de leitura do texto criado para investigar se o seu conteúdo é de fácil leitura ou não.</p><h4><strong>Aplicação</strong></h4><p>Escolha o fragmento de texto a ser testado.</p><ol><li>Conte as <strong>palavras</strong> do parágrafo;</li><li>Conte as <strong>frases</strong> <em>(cada frase termina por ponto)</em>;</li><li>Divida o número de palavras pelo número de frases. Assim, você terá a <strong>média da palavra/frase</strong> do texto;</li><li>Some a média da palavra/frase do texto com o número de <strong>polissílabos</strong><em> (mais de três sílabas)</em>;</li><li>Multiplique o resultado por 0,4 <em>(média de letras da palavra na frase de língua portuguesa)</em>;</li><li>O produto da multiplicação é o índice de leitura.</li></ol><h4><strong>Pontuação (quanto menor a pontuação, melhor)</strong></h4><ul><li><strong><em>1 a 7:</em></strong><em> história em quadrinhos (nenhum ou pouco texto)</em></li><li><strong>8 a 10:</strong> excepcional</li><li><strong>11 a 15:</strong> ótimo</li><li><strong>16 a 19: </strong>pequena dificuldade</li><li><strong>20 a 30:</strong> muito difícil</li><li><strong>31 a 40: </strong>linguagem técnica</li><li><strong>acima de 41: </strong>nebulosidade</li></ul><p>Para textos em inglês, temos ferramentas prontas como o <a href="https://readable.com/">Readable</a>, mas para português ainda desconheço algo automatizado.</p><p><em>[Atualização] A querida leitora </em><a href="https://medium.com/u/6e178526e262"><em>fernanda voicic</em></a><em> trouxe uma </em><a href="https://docs.google.com/spreadsheets/d/1_jvitjNxyqew8DFvIDB3O3tmG_2KzLJ3ff6qqPmtl2c/edit"><em>ferramenta</em></a><em> bem interessante para textos em português. Ainda não usei, mas acredito que vale a pena!</em></p><h3>Compreensão: teste marca-texto</h3><p>O <a href="https://userresearch.blog.gov.uk/2014/09/02/a-simple-technique-for-evaluating-content/">teste de marca-texto</a> nos mostra o quanto as pessoas se sentem confiantes em relação ao seu conteúdo. Ele nos ajuda a perceber o impacto que determinado texto tem sobre nosso público-alvo.</p><h4><strong>Aplicação</strong></h4><p>Escolha duas cores de canetas marca-texto, uma para “mais confiante” e outra para “menos confiante”.</p><p>Peça para que a pessoa participante leia o texto selecionado e marque as partes que a fizeram se sentir mais ou menos confiantes com as cores adequadas.</p><p>Outros valores podem ser empregados aqui além da confiança, como familiaridade e utilidade, por exemplo.</p><figure><img alt="folha de papel com texto em inglês. o seu conteúdo de texto está marcado com as cores verde e vermelho." src="https://cdn-images-1.medium.com/max/1024/1*8A5109uo3gXe0Unp_Enb-w.jpeg" /><figcaption>Highlighter Testing</figcaption></figure><p>Agora pergunte às pessoas sobre o que elas destacaram, por exemplo: “Você marcou isso como “útil”, por quê?” Para qualquer termo ou frase que elas marcarem negativamente, pergunte quais palavras elas usariam para explicá-lo melhor.</p><p>Se não for possível realizar o teste presencialmente, você poderá usar o Google Docs e pedir para que as pessoas usem o marcador da própria ferramenta. 😉</p><p>Algumas das perguntas que podemos responder aplicando esse método:</p><ul><li>Esse é o fluxo correto de informações que a pessoa usuária precisa ter do começo ao fim?</li><li>Quais são os pontos de contato realmente necessários? O que devemos dizer às pessoas a cada momento?</li><li>A estrutura que desenhamos corresponde ao modelo mental delas?</li><li>Como elas pensam ou falam?</li><li>Que princípios de conteúdo podemos seguir quando projetamos essa experiência?</li></ul><h3>Compreensão: teste de cloze</h3><p>O <a href="https://www.nngroup.com/articles/cloze-test-reading-comprehension/">teste de Cloze</a> é um instrumento para avaliar a habilidade de compreensão de leitura, com ele verificamos se o texto é fácil de ser lido e compreendido. Trata-se de um ótimo recurso para descobrir se o seu público-alvo realmente entende o que você escreve.</p><h4><strong>Aplicação</strong></h4><p>Selecione o texto a ser testado e substitua cada palavra a ser testada por espaços em branco. Peça a cada participante que leia os textos selecionados e preencha os espaços em branco com suas melhores sugestões sobre as palavras que faltam.</p><p>Confira se as palavras que você havia sugerido batem com as que foram escolhidas. São permitidos sinônimos e erros de ortografia (na verdade, se um sinônimo se repetir, talvez seja essa a palavra que você estava procurando). Se seus participantes obtiverem uma pontuação média de 60% ou mais, seu texto é compreensível para esse perfil.</p><figure><img alt="ilustração surrealista" src="https://cdn-images-1.medium.com/max/912/1*m8v7834Gb6PDeL6ox5E5TA.png" /><figcaption>Illustration by <a href="https://www.behance.net/nsnva">Olga Nesnova</a><br>from <a href="https://icons8.com/">Icons8</a></figcaption></figure><h4><strong>Usabilidade</strong></h4><p>Ok, as pessoas conseguem ler e compreender os textos apresentados, mas será que eles de fato estão sendo lidos? Para isso o ideal é formular um <a href="https://www.nngroup.com/articles/usability-testing-101/">teste de usabilidade</a> focando no conteúdo.</p><h4><strong>Card Sorting</strong></h4><p>Ainda não tem conteúdo? Não tem problema! A técnica de <a href="https://brasil.uxdesign.cc/card-sorting-como-descobrir-o-modelo-mental-de-organiza%C3%A7%C3%A3o-de-conte%C3%BAdo-18e9a50121aa">card sorting</a> pode ser ótima para começar a estruturação.</p><h4><strong>Google Trends Research</strong></h4><p>Ótima ferramenta para descobrir termos preferidos dentro do universo do produto.</p><h3>UX Content Scorecard</h3><p>Para finalizar, uma ferramenta poderosa elaborada pela <a href="https://www.amazon.com.br/Strategic-Writing-UX-Torrey-Podmajersky/dp/1492049395">Torrey Podmajersky</a> para você testar conteúdos, o UX Content Scorecard!</p><p>Para avaliar como está a experiência, existem certos critérios que devem ser levados em consideração para verificar se ela está sendo “boa” ou não. Vamos chamar esses critérios de Heurísticas de conteúdo.</p><p>Aqui eles estão organizados em uma tabela formando o <a href="https://drive.google.com/file/d/1FRFf7M8mMNay-rF3Z2-M8UXDPCID53pS/view?usp=sharing">UX Content Scorecard</a>.</p><h4><strong>Quando usar:</strong></h4><p>Quando não se tem certeza sobre o que deve ser priorizado em melhorias de conteúdo de UX.</p><h4><strong>Como usar:</strong></h4><p>Escolha uma parte da experiência, uma tarefa a ser cumprida, por exemplo, e pontue de acordo com os critérios, onde 10 pontos significa que a experiência atinge 100% do critério. Se o critério não se aplica, então deixe em branco.</p><p><em>Pontuação é sempre algo subjetivo. Tenha em mente que os pontos não são uma avaliação absoluta, dessa maneira evitamos o viés de classificar algo como sendo uma experiência “boa” ou “ruim”.</em></p><p><em>Essa pontuação tem o objetivo principal de </em><strong><em>priorizar o que deve-se melhorar na experiência</em></strong><em>.</em></p><p>Se você tem alguma técnica para testar conteúdo, compartilha também!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/76/0*iv-nrOs5HAuHAyQS" /><figcaption>O UX Collective doa US$1 para cada artigo publicado na nossa plataforma. Esta história contribuiu para o<a href="https://medium.com/uxmpretas"> UX Para Minas Pretas</a> (UX For Black Women), uma organização Brasileira focada em promover equidade para mulheres Pretas na indústria de tech através de iniciativas de ação, empoderamento, e troca de conhecimento. Silêncio contra o racismo sistêmico enraizado na sociedade não é uma opção. Construa a comunidade de design na qual você acredita.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78402f919add" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[O Redesign na Resultados Digitais, e a realidade do Design System.]]></title>
            <link>https://medium.com/design-rd/o-redesign-na-resultados-digitais-e-a-realidade-do-design-system-115dd224fc5c?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/115dd224fc5c</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[resultados-digitais]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Tue, 07 Jul 2020 13:05:09 GMT</pubDate>
            <atom:updated>2021-09-08T17:00:47.289Z</atom:updated>
            <content:encoded><![CDATA[<h3>The RD Station redesign and the reality of building a Design System.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5lLGYJXaxAKqdevef94-QQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@halacious?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Halacious</a> on <a href="https://unsplash.com/s/photos/design?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In 2019, RD Station began taking the first steps towards redesigning its products and building its Design System 2.0. We dreamed big, studied a lot, faced reality, learned quickly from our mistakes, and calibrated the target, and today, it makes us very proud to see what we’ve accomplished.</p><p>It was a long, tortuous path with some obstacles. We learned many lessons, and that&#39;s what we&#39;re going to share!</p><h3>Structuring the Design Ops team</h3><p>One of the first moves that RD Station made as soon as the redesign project began was to structure the Design Ops team (we called it Kondo).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cyV2Fhv4mLNTIrhOHfMKKA.jpeg" /><figcaption>Organizing like Marie Kondo</figcaption></figure><p>RD Station’s Ops team includes designers, researchers, and UX writers. They are responsible for coordinating and organizing the Design Chapter, promoting internal training and awareness, raising UX debts, and designing the new Design System, the foundation for our new look.</p><p>One of Ops’ intrinsic roles, in addition to practical and technical day-to-day initiatives, is to engage the Chapter and align expectations regarding the project. Without that, we could create the most fantastic Design System, but it wouldn’t meet the needs of designers and therefore wouldn’t be used.</p><p>A Design System that is not regarded as useful by the Design and Development teams is bound to be just another tool that no one uses. And the result is a non-standard product and a lot of work for developing screens and features.</p><p>We always tried to bring the designers and engineers to work closely with us in creating the DS. Their different visions and needs were precious to us. This proximity was crucial in defining the redesign roadmap, prototyping and testing.</p><h3>Getting to know (better) our customers and the challenges ahead</h3><p>Due to a company’s strategic decision, we hired a specialized agency to help us work faster on this project. That’s when the Kondo team, still with only three people (Designer, UX Writer, and Product Manager), embraced another goal: to bridge the gap between designers and the contracted agency.</p><p>It took months of research, a lot of conversation, and interviews with customers. Both the agency and the design team had a very up-to-date view of the difficulties, concerns, and objectives of customers with our products. This phase was essential for us to “land” on the mission that lay ahead.</p><p>Early on, it was clear that it was essential to understand the brand for the Redesign’s success, how it positions itself, its personality, and how it relates to customers, how our entire ecosystem works. After all, a redesign doesn’t just affect the product. Indirectly, it will affect many areas like Branding, Marketing, and Customer Success, for example. Placing a third party at this same level of knowledge became a big challenge, and this was also a significant learning experience for the team.</p><p>This project’s level of responsibility and scale needed organization and planning to ensure maximum alignment between our team and the agency. As the project developed, we realized that our efforts should be focused on this planning.</p><p>The partnership with the agency was precious, as we had no idea of ​​the challenge it would be to carry out a complete redesign. Still, from the moment the team became more influential, more confident, and “tied the house,” we were able to walk alone, and that was when we decided to take a step back and discontinue the partnership with the agency.</p><p>It was not an easy decision. We debated a lot internally about that decision. But today, the Kondo team is much bigger, with more responsibilities, challenges, and the RD Station redesign continues at full steam.</p><h3>Tools and remote work</h3><p>Without a shadow of a doubt, we could say that the redesign project and the Design System construction would’ve been a much more complex task if we didn’t have the tools we have at our disposal today.</p><p>Here at RD Station, we use Figma, Miro, and Zoom to work daily. These tools make it possible to run everything without almost any difficulties in communication and creation, as our team is split between the cities of Florianópolis and São Paulo, everyone working remotely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2QHlDpPMdqyRPFllfn9BUg.png" /><figcaption>Miro board for sharing ideas and presentations</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*oxH7c38p9o8_frsvKlQxfA.png" /><figcaption>Another meeting at Zoom with part of the Design team</figcaption></figure><p>Everything could be easily shared, and with the team’s engagement, it was like everyone was in the same room creating together. And often this happened, even remotely, for example, in the so-called “Redesign weeks,” when we elected a product feature to be remodeled. In a smaller group of designers, we carried out studies, raised problems, solutions, technical feasibility, prototyping, and, finally, tests and validations with clients.</p><p>This routine of “Redesign weeks” also involved a crucial ritual for us. We presented, discussed, and evaluated everything as a team. This worked out so well for us that it even improved the Chapter’s atmosphere. It brought the team together, made us get to know each other better, have more empathy, and even organized and accelerated the development of the DS and the project as a whole.</p><p>Another initiative we had, this time targeting the entire company, was to create a newsletter to publicize all the advances we were making. The redesign project was critical to everyone. Managing the anxiety and giving more insight into what was going on behind the scenes was fundamental — receiving each feedback after a newsletter was excellent and further confirmed the importance of the Design Chapter at RD Station.</p><h3>Technology as a prioritization rule</h3><p>One of the crucial points that drove us forward in the deliveries was the very clear definition of how far the redesign project would go. After that definition, we started to feel like we were getting somewhere.</p><p>One of the beacons we established for us was technology. It was out of our scope if the solutions bumped up too much in technology and took too much development time. An example of this would be creating new tools in the product: if that were the case, it would be for the future and not for now.</p><p>This definition helped us better prioritize what we would tackle, keep our feet on the ground, and have more accurate deadlines. The idea was to solve what we have available today and not predict future problems.</p><p>When you’re immersed in a redesign and full development of a Design System, it’s tempting to embrace the world and have thousands of ideas that would make the product even more unique, but that would possibly take a long time and demand a headcount much bigger.</p><h3>The light at the end</h3><p>Always keep an eye on what actually makes sense for YOUR product. It’s charming to want to make a very complete Design System and a grandiose redesign, but make sure that makes sense for your product. Stick to your reality, your use cases.</p><p>A Design System does not have to have every single component in the world but rather be helpful and practical for people who work with the product daily. It is not simplistic to close the scope and work as best as possible with what we have at our fingertips today. When we created this mindset, everything started to work faster in RD Station.</p><p>If your company’s reality is a bit like ours here, work with a lean scope, bring your team closer — make everyone buy the idea and get excited about it — do your best with the deadline that you have and never forget to share!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/1*9EL19ynHh5qItRRi48MC9g.png" /><figcaption>O Design System da Resultados Digitais</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=115dd224fc5c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-rd/o-redesign-na-resultados-digitais-e-a-realidade-do-design-system-115dd224fc5c">O Redesign na Resultados Digitais, e a realidade do Design System.</a> was originally published in <a href="https://medium.com/design-rd">Design RD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How becoming a mom made me a better UX Writer]]></title>
            <link>https://uxdesign.cc/how-becoming-a-mom-made-me-a-better-ux-writer-3cd3f873e2d8?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cd3f873e2d8</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[motherhood]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Fri, 13 Mar 2020 18:45:46 GMT</pubDate>
            <atom:updated>2021-09-09T10:49:10.036Z</atom:updated>
            <content:encoded><![CDATA[<h4>After motherhood struck, I realized that some techniques we use as UX Writers, I already applied in real life with my children at home. And that made my transition to UX writing so much easier.</h4><figure><img alt="Illustration of a woman holding a baby in her arms. Little pink hearts float in the air." src="https://cdn-images-1.medium.com/max/1024/1*-LnLQbMFfeMCFUgij3rL2A.png" /><figcaption>illustration by <a href="https://icons8.com/">Ouch.pics</a></figcaption></figure><p>Children, like users, are taking their first steps into the world with you by their side. Or in our analogy, into a whole new product. It is not always easy, but you will be there to guide them and to make sure that their adaptation experience is as smooth as possible.</p><blockquote>After all, UX writing is all about creating a conversation between your product and your users, always valuing purpose, conciseness, and clarity.</blockquote><p>And motherhood is undoubtedly, among many things, one big lesson on communicating.</p><p>You gotta learn how to communicate with your baby (and once they start talking, they never stop). But most of all, after you become a mom, you have to learn how to communicate with the world around you, and reach out in times of need.</p><p>So, this is what I’ve learned so far from walking down the paths of UX and Motherhood…</p><h3><strong>Maintain a consistent experience</strong></h3><p>In the same way that the user needs to have a consistent experience throughout the product, creating a <a href="https://www.kidspot.com.au/parenting/toddler/toddler-development/why-routine-and-structure-benefits-your-toddler/news-story/fe84fec963d779fd4f032b312f182ebe">routine</a> with children is essential.</p><p>They need a routine, they need to know what will happen throughout their day. This guarantees less anxiety, and gives them more confidence.</p><p>The same thing happens with the person using a product. He or she needs to continue advancing through the product, knowing what to expect. Scares or uncertainties are terrible for the user’s experience and can cause them to get stuck at one step or even give up on your product altogether.</p><h3><strong>Find out what the user wants and the easiest and fastest way to get them there</strong></h3><p>With kids it is not always easy to know what they want at any given time. And if you don’t quickly find out what it is, prepare for the crying!</p><p>The same dynamic occurs with users. You must first really <a href="https://uxdesign.cc/how-to-know-your-users-needs-2d24fb92a01e">understand what he or she wants</a> to achieve in order to provide the best possible experience quickly and easily.</p><h3><strong>Use the correct tone of voice</strong></h3><p>The <a href="https://medium.com/deliveroo-design/how-to-use-voice-and-tone-in-ux-writing-a66981c78d20">voice of the product</a> must always follow the voice of the brand. One does not separate from the other. Our job is to adjust it to the different moments of the product.</p><p>At home with a child is the same thing. If you yell at a child during a time of stress, what good does it do? Using the<a href="https://www.huffpost.com/entry/5-tips-for-staying-calm-with-children_b_5516908"> right tone</a> for each situation is very important.</p><p>It’s the same with users. The correct tone of voice in an error message, notification or button ensures that the right action is taken with more confidence. In addition, it is the tone of voice that will give the product its soul. If it’s nice, direct, good-humored…</p><h3><strong>Use clear and accessible commands</strong></h3><p>Clarity is key to any conversation.</p><p>A child is not born knowing how to speak, and moreover, he or she is not born knowing what you are saying. Gradually they start to understand commands, and the consistency of these basic commands allows us (in our own way) to have a conversation with them.</p><p>The same is true for users, especially if they are new to your product. They need very <a href="https://www.nngroup.com/articles/ui-copy/">clear and consistent commands to move on</a>. Gradually they will start to understand “our language” and follow in an intuitive way.</p><h3><strong>Learn how to edit</strong></h3><p><a href="https://raisingbliss.com/how-to-say-no-to-your-child-in-a-positive-way/">Saying no to a child</a> is not always an easy task, but a very necessary one.</p><p>We must do the same with text. <a href="http://uxwritinghub.com/3-microcopy-rules-every-ux-writer-must-know/">Editing</a> is essential for the commands to be assertive. Say no to what is not necessary so that the message is always understood.</p><h3>Take breaks and take care of yourself</h3><figure><img alt="Illustration of a woman waving to a dog. The dog has a tiny envelope in his mouth with a heart drawn." src="https://cdn-images-1.medium.com/max/1024/1*JrT1vsHe812r00D5Jldlfw.png" /><figcaption>illustration by <a href="https://icons8.com/">Ouch.pics</a></figcaption></figure><p>You can apply all this to your work, to your family, and I’m sure you’re gonna do just fine. But the last thing that I want to point out is this: have empathy.</p><p>This may sound trivial when we talk about UX, and UX writing, but what I wanna stress here is you have to have empathy with yourself.</p><p><a href="https://www.ted.com/talks/robert_waldinger_what_makes_a_good_life_lessons_from_the_longest_study_on_happiness">Care for yourself first</a>. If you’re not ok, how can your family be ok, and how can you give your best at work?</p><blockquote>At the end of the day, if you’re not ok, nobody is ok.</blockquote><figure><img alt="Photo of the writer&#39;s two children, a girl and a boy." src="https://cdn-images-1.medium.com/max/1024/1*KwcBR8YxQ6u8GVLZqhVI3g.jpeg" /><figcaption>My beta testers ❤️</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cd3f873e2d8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-becoming-a-mom-made-me-a-better-ux-writer-3cd3f873e2d8">How becoming a mom made me a better UX Writer</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[Como vive uma UX Writer na Resultados Digitais]]></title>
            <link>https://medium.com/design-rd/como-vive-uma-ux-writer-na-resultados-digitais-dccdc3e1d8b6?source=rss-5dd0ee7972a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/dccdc3e1d8b6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[resultados-digitais]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Julia Goncalves]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 13:35:25 GMT</pubDate>
            <atom:updated>2021-05-04T17:51:23.755Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Oi! Eu sou UX Writer na RD Station, e vou compartilhar um pouquinho do meu dia a dia, o que eu faço, como eu vivo, o que eu como… </em>😜</p><p>Antes de me tornar uma UX Writer, eu trabalhei por 7 anos em agências de publicidade como redatora fazendo spots para rádio, anúncios de revista, jornal, PDV, promoção, blogs, redes sociais… enfim, fiz de tudo um pouco.</p><p>Mas foi quando eu entrei para uma startup que eu comecei a trabalhar com UX designers e a estudar o que era experiência do usuário, isso em 2016.</p><p>E desde então eu venho desenvolvendo textos para produtos digitais e eu amo o que eu faço e recomendo! ❤️</p><figure><img alt="Lê-se em inglês tudo o que temos são palavras, tudo o que temos são mundos." src="https://cdn-images-1.medium.com/max/1024/1*wrqqPGdOLT8MKDX1U4imWA.jpeg" /></figure><p><strong>O que é UX Writing para você?</strong></p><p>Pode arriscar, não tem certo nem tem errado!</p><p>As realidades das empresas mudam, existem empresas com times de UX já bem estruturados, outras que ainda estão num estágio inicial, e como você consegue desenvolver UX Writing no seu dia a dia pode mudar bastante.</p><p>Aqui na Resultados Digitais a escala é relativamente grande.</p><p>Eu sou a única UX Writer para 15 <strong>designers</strong>, num universo de quase 200 pessoas no time de produto. Então aqui eu já levanto o primeiro ponto de atenção: se você trabalha com times grandes, organizar bem as demandas é algo muito importante.</p><p>Eu conto com um PM que me ajuda nessa tarefa, e nós trabalhamos com Kanban. Eu já tentei lançar formulários para os designers organizarem as demandas, mas isso ainda não pegou 😣 Nessa experiência de tentativa e erro de organização, o que eu tenho feito é dividir a minha agenda para dar vazão aos meus projetos paralelos, como o <strong>Guia de estilo de escrita</strong>, e às demandas pontuais dos designers.</p><p>Mas eu não trabalho só com designers. E aqui vem o segundo ponto de atenção: eu trabalho com pessoas de várias áreas, desde o time de suporte, product marketing, branding até sucesso do cliente.</p><p><strong>E porque que eu preciso dessa linha direta com todas as áreas?</strong></p><p>Porque o tom de voz da marca deve ser um só.</p><p>O texto do branding é pensado para sensibilizar o ser humano, em como eu gero uma conexão emocional entre a minha marca e as pessoas, o do marketing é desenvolvido para engajar, que a pessoa vire um cliente e ele se mantenha assim. Já o do UX Writing é concebido para guiar o usuário dentro do produto.</p><figure><img alt="menino gritando em um microfone" src="https://cdn-images-1.medium.com/max/1024/1*rdMNyB_1bSPfYi-FwvKgUg.jpeg" /></figure><p>Mas o produto é o mesmo, então é essencial que todas essas áreas conversem para que a história seja consistente em todas as etapas de contato com as pessoas. Eu não posso falar com um tom de voz num email marketing, outro nas redes sociais, e um terceiro dentro do produto.</p><p>E mais do que isso, eu preciso entender a fundo o meu usuário, como ele pensa, como ele age, como ele usa a ferramenta, e isso pode vir do time de Sucesso do Cliente e do Suporte, por exemplo.</p><p>E aí quando você entende essa relação de quase simbiose entre as áreas fica mais fácil entender a real importância de um bom relacionamento entre as áreas, seja qual for a sua empresa.</p><p>E como nós, UX Writers, podemos fazer o nosso trabalho da melhor maneira a ajudar o time, a empresa, e os usuários?</p><p><strong>Imersão na empresa e nos produtos</strong></p><p>Eu busquei participar de conversas com os usuários, corri atrás dos tickets do suporte, tudo isso com a intenção de entender os diferentes contextos, o universo semântico e as perguntas que eles faziam a cada etapa da experiência. E vale lembrar sempre: não é o que eu acho que funciona. É se funciona para o nosso usuário.</p><p><strong>Linha direta com outros times além de Design</strong></p><p>Colegas do Marketing, Branding, Sucesso do Cliente e Suporte podem ser grandes fontes de insights e verdadeiros parceiros para entender a fundo o usuário. Criar uma atmosfera de colaboração entre todas as áreas que impactam no produto pode parecer difícil dependendo da empresa em que você está trabalhando, mas acredite, no fim todo mundo sai ganhando.</p><p><strong>Ferramentas</strong></p><p>Uma das primeiras entregas de um UX Writer é um Guia de estilo de escrita. Ele me ajuda a não me tornar um gargalo para o meu time, e dar mais velocidade e autonomia para os designer. Quanto mais prático melhor, com exemplos do que fazer e do que não fazer (seu time vai agradecer!)</p><p>Para fechar, se você é UX Writer, quer ser ou quer ter um no seu time, lembre-se que o nosso objetivo no fim do dia é facilitar o diálogo entre um sistema e uma pessoa, e que esse diálogo deve ser legal, uma conversa de verdade…</p><p>Quando a pessoa entende o que o seu produto está “dizendo”, e consegue alcançar os seus objetivos então a gente tá no caminho certo.</p><p>Afinal, o intuito do UX Writing deve ser sempre o de ajudar as pessoas a alcançarem seus objetivos, buscando entender como elas se sentem, o seu vocabulário e a forma como elas raciocinam.</p><p>E se isso tudo acontece, e você ainda consegue se distinguir da concorrência, então parabéns!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*orrE1qHuo7-y83EyORQ2Dg.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dccdc3e1d8b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-rd/como-vive-uma-ux-writer-na-resultados-digitais-dccdc3e1d8b6">Como vive uma UX Writer na Resultados Digitais</a> was originally published in <a href="https://medium.com/design-rd">Design RD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>