<?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 Beatriz Arias on Medium]]></title>
        <description><![CDATA[Stories by Beatriz Arias on Medium]]></description>
        <link>https://medium.com/@beatriz-ari-ple?source=rss-a77c53531b81------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*K4zFHxUg-xX7z1-OrT9dTQ.jpeg</url>
            <title>Stories by Beatriz Arias on Medium</title>
            <link>https://medium.com/@beatriz-ari-ple?source=rss-a77c53531b81------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:13:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@beatriz-ari-ple/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 survive as the only UX writer in the team]]></title>
            <link>https://medium.com/design-bootcamp/how-to-survive-as-the-only-ux-writer-in-the-team-cc9907c8d25?source=rss-a77c53531b81------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc9907c8d25</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[tips-ux-writing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[big-tech-layoffs]]></category>
            <dc:creator><![CDATA[Beatriz Arias]]></dc:creator>
            <pubDate>Mon, 20 Feb 2023 11:48:33 GMT</pubDate>
            <atom:updated>2023-02-22T05:35:44.745Z</atom:updated>
            <content:encoded><![CDATA[<h4>Surf the wave with these 4 hints</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*pQgPcKf1kNdrMZ_Nf-AK7w.png" /><figcaption>Pic by Linus Nylund on Unsplash</figcaption></figure><p>Back in the days, it wasn’t unusual to land on a company that was officially welcoming their first (and only) UX writer. The tech teams demanded someone to write the product content, design the workflows, and smooth all-things UI copy with data, research, product, design, and engineering. And so the adventure began, and teams started to grow slowly.</p><p>These days, the financial recession is pushing tech companies to shorten their headcount. Now, there’s a different reason why we find UX writers that are alone in their teams or more outnumbered as ever. And they’re probably not used to being on their own.</p><p>In any case, <strong>surviving as the only UX writer can be overwhelming. I’ve experienced this a few times during my career. So here they are 4 basic hints</strong> (that have at least worked for me) to surf the wave with success.</p><h4>Hint #1: Set expectations</h4><p>Most important when the company has never worked with a UX writer before, but always nice to have on hand: <strong>create a document that clarifies what UX writers do and how</strong>. It’s also very useful when onboarding new team members and when going on tour to other teams.</p><p>This document can be a sort of introduction to the basics of UX writing, and it’s also nice to personalise it with the company values, voice, and different tones, when possible.</p><p>This presentation needs to be agreed with the whole design team, and <strong>I’d suggest something that covers essential topics</strong> like the difference between UX writing and copywriting; the ways we can contribute to the product; the explanation of the different content levels where UX writing can be helpful… Save it somewhere where you can easily access it, and share it in case of emergency.</p><blockquote>A document about what UX writers do, and how, will save you precious time in explanations (and help you backup your decisions).</blockquote><h4>Hint #2: Invite others to join</h4><p>This might be a bitter pill to swallow (as writers, we have our ego) but <strong>you’re not going to be the only one writing the product content. And, truth being said, you don’t need to be</strong>.</p><p>Before UX writers existed, designers, product managers, and sometimes even engineers were in charge of the UI copy. Now, our job is also to give all these people in the company the right tools and guidance so they can be guest stars in the field. You may be surprised to see how eager people are to learn new things. Plus, they will start valuing your work much more after trying to do it themselves.</p><blockquote>Prioritisation will be your best friend, and you’ll have to choose your battles wisely.</blockquote><p>Depending on the project needs, you may want to jump in earlier in the process, or not. Depending on your workload or the deadline, you may be able to do it, or not.</p><blockquote>Making a toolkit accessible to everyone allows you to lead the craft while at the same time leave others the room to join in confidence.</blockquote><p>I find the following tools especially useful:</p><ul><li><a href="https://hemingwayapp.com/">Hemingway editor</a> (by Adam &amp; Ben Long)</li><li><a href="https://readabilityguidelines.co.uk/">Readability guidelines</a> (by Sarah Winters and the Content Design London)</li><li><a href="https://cardsforhumanity.idean.com/">Cards for humanity</a> (by Idean)</li><li><a href="https://drive.google.com/file/d/18CHoCRR_i0jNhtrxBeJtoU52Jwst4jvX/view">Content heuristics</a> (by Bobbie Wood for the UX Content Collective)</li><li><a href="http://www.workwithjane.com/">Microcopy canvas</a> (by Jane Ruffino)</li></ul><h4>Hint #3: Explain your workflow</h4><p>When landing in a new company, study the current workflow before trying to force major changes -there’s always a process. If there used to be a team of UX writers, but now the task force has been reduced, adapt the workflow to the new situation.</p><blockquote>Above all things, you must show the team how you work -and how to work with you.</blockquote><p>Some UX writers like to have a request template to fill in all the requirements for the project. Others prefer to jump in an introduction call. Whatever way you choose, be flexible. It’s not only about your preferences but about what works best for the team. Everyone will be adapting to a new situation and things take time. Move on and, the more you work together, the better your value will be shown.</p><p><strong>It’s advisable that the workflow covers the whole process: from the strategy starting point, to the ideation and prototyping, to the implementation, localisation and handoff of the copy</strong>. I once worked with a brilliant service designer that helped me to work on a RACI chart.</p><blockquote>Defining the responsible, accountable, consulted and informed roles for each task is a great exercise to foster collaborations. When everyone is aware, communications run smoothly: no taking things for granted, no misunderstandings.</blockquote><p>To document your workflow, use a tool that works for the entire company: Confluence, Notion, Drive… wherever the team saves things, that’s the place. Remember your colleagues are your users, and apply the same usability principles you master with words. Don’t push it too hard; A cute presentation can be as beautiful as useless if not everyone can access it.</p><h4>Hint #4: Share the projects overview</h4><p>Being the only UX writer will also turn you into the most wanted person sometimes. This isn’t as nice as it sounds. Everyone will be asking you about the status of their project, or dropping you a question or new requirement out of the blue. And you probably won’t even remember what they’re talking about in the first place, because your brain has lots of projects going on.</p><blockquote>Especially when you are alone, the ability to organise, manage and document projects becomes essential.</blockquote><p><strong>Invest the time to find the management tool that fits the best for you and your team, and redirect all the project status questions there</strong>. I personally find the Notion-Jira mix very useful, because it connects me with the agile system and the sprints. In my experience, the right tool will be the one that everyone can access and that allows you to gather all the information without having to duplicate efforts.</p><p>No wish to sugarcoat it, but uncertain times also lead to exciting opportunities. <strong>I’ve learnt the most in my career when having to navigate as the solo UX writer in a team</strong>. DM me if you have any other hints you’d like to share!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc9907c8d25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-to-survive-as-the-only-ux-writer-in-the-team-cc9907c8d25">How to survive as the only UX writer in the team</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Key naming architecture: choose your player]]></title>
            <link>https://beatriz-ari-ple.medium.com/key-naming-architecture-6e9af6e0eb91?source=rss-a77c53531b81------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e9af6e0eb91</guid>
            <category><![CDATA[key-architecture]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[naming-conventions]]></category>
            <dc:creator><![CDATA[Beatriz Arias]]></dc:creator>
            <pubDate>Wed, 11 Jan 2023 22:34:00 GMT</pubDate>
            <atom:updated>2023-01-11T22:34:00.326Z</atom:updated>
            <content:encoded><![CDATA[<h4>The 3 approaches every UX writer should know about</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gPzDwfE5i6GFn946XK6XEQ.jpeg" /><figcaption>Picture by Mourizal Zativa | Unsplash</figcaption></figure><p>Creating the keys (the unique identifiers that we set for a text and its translations) is maybe one of the most unknown tasks of us, UX writers. In some cases, it might not even be considered a UX writer task. Depending on the company, engineers may be the ones taking care of this last step of our content journey.</p><p>I’ve seen lots of approaches to key naming architecture during my career. In this article, <strong>we’ll go through the most common solutions and some benefits and risks</strong> when using each of them.</p><blockquote>Communication between UX writers, engineers, and designers is the most important aspect that influence the setting of a key naming architecture, as well as the tools used both for design and localisation. The balance between workloads on each team and the speed of release are also crucial details to take into account.</blockquote><p>Spoiler alert before getting started: there’s no right or wrong in any of these key naming architectures. Every team should just choose whatever it feels better -and then continue evolving as the product needs also change.</p><h4>Approach #1. Focus on the placement</h4><p>A key name that you can almost immediately locate in the product, without even having to read the value. How cool does it sounds? Taking a look back to the days when key names could be anything random ending with the word <em>key</em>, this looks like a UX writer’s dream come true.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gjl4SoVAcHab3x6_4jZcyQ.png" /><figcaption>Example of how the layers can be defined and named</figcaption></figure><p>With this solution, you can <strong>define as much layers as you want for your architecture</strong>, and you can name them as you prefer. Under each one of the layers (except for the content specific which is, of course, specific)<strong> there will be a closed list of placements</strong> that, again, can be named whatever you want. Yet, it’s advisable that all the names of the placements follow the same structure used by the rest of the teams -bonus track if it’s also consistent with your design system!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZ7zljkbPiDvJmjtb3SHqA.png" /><figcaption>Following the example above, this is how the keys for these 3 pieces of content could look like</figcaption></figure><p>Whenever there will be content that could appear exactly the same in more than one touchpoint, like forms or error messages, you can always use a <em>common</em> layer instead of a <em>touchpoint</em> layer for the key (this could be named <em>error </em>or maybe<em> form </em>on your list). On the contrary, if you want to show different content for the exact same placement, you can add a <em>content condition</em> layer to kind of duplicate key (this is useful for example in case we want to a/b test some content, so for example we would just add <em>control</em> and <em>variation</em> at the end).</p><h4>Benefits</h4><p>A great benefit of this key naming approach is flexibility. <strong>When detaching the key name to the value, the copy linked to this key can change as much as needed</strong>. It will always fit, there will be no mismatching or eventually, there will be no need to change a key in the code. This <strong>gives UX writing full ownership on the content and further edits will come without dependencies</strong> from engineering.</p><h4>Risks</h4><p>The downside of this recipe is that <strong>it can become overly specific. It’s easy to fall victim to an exhausting exercise of adding more and more layers to be as accurate as possible</strong>. That will result in long key names for a copy that has just a couple of words. Going too deep also means that maintaining the architecture will become quite complicated.</p><p>Another risk of this type of key architecture is that it’s difficult to keep consistency. Yes, you may have a closed list of names for each layer, but that list will eventually grow and change as the product does. Everyone needs to be aware of the new additions and review the list every time they create a new key. If you decide on this type of naming architecture, <strong>be ready to spend a lot of time on creating the keys, especially when a large team is involved</strong>.</p><blockquote>Focusing on the placement of the key is probably the most complete approach, but it comes with a high cost. Ultimately, all the effort relies on the UX writer, and it’s unlikely that any design tool plugin can keep track of an overly specific architecture.</blockquote><p>The question is: is it worth it? Localisation tools already offer us other resources such as tags and/or screenshots attached to every key, which allow us to easily identify the key placement.</p><h4>Approach #2. <strong>Focus on the value</strong></h4><p>If keys are linking the content to the code, doesn’t it make sense to put the focus of the name on the value -aka the actual content? It may look like a rollback to the old times, but here we are talking about <strong>describing the value with a sensitive key name</strong>, not copy-pasting it. The goal is to give a general idea of the value it holds and omit the <em>key</em> suffix at all costs.</p><p>When using this approach, no matter which the placement is: when the content is the same, the key is the same. The localisation tool and/or CMS will storage other types of context we’d like to add to the key. And when a content needs to change for only one of the placements, a new key will be created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gp8GqvKeNpBcGBiItChLpw.png" /><figcaption>Example of how the key names would be when using the value focus architecture</figcaption></figure><h4>Benefits</h4><p>This is <strong>a simple yet convenient solution (usually the preferred one among engineers) that allows us a fast response</strong>.</p><p>Of course <strong>with this naming architecture, the key will be useless the moment we decide to change the value</strong>. But this doesn’t have to be a problem if there’s a commitment from the team to clean this key everywhere it’s located, and create a new one following the same rules.</p><h4>Risks</h4><p>A downside of this this type of architecture is that it sacrifices the readability of the key names, especially in those cases where the copy is very long. However,<strong> the thing I fear the most when using this solution is the nightmare of duplicating keys</strong>.</p><p>Trying to find balance between not strictly following the value the key holds but at the same time coming up with a unique key name can be hard. Yes, there are ways to avoid this issue, but it is also tedious to review and switch key names when that happens.</p><blockquote>After being against this solution for a long time, I have finally come to terms with it. The simplicity it brings to the process compensates other upscale but harder-to-maintain systems. As long as there exists smooth communication between UX writing and engineering, it will be a flexible and agile way.</blockquote><h4>Approach #3. Automation</h4><p>Plugins connecting design and localisation tools have taken <strong>UX writing to a higher level. One of the many benefits they bring to the table is to automate the key generation</strong> for any text in the design.</p><p>Depending on the tool, <strong>there are different default options offered to decide on the key architecture. What all the options have in common is that the patterns are based on the artboard, group, layer, and other design element names. </strong>They can be combined, selected, and sometimes customised until finding the most convenient naming convention for you. Then, this architecture will be saved for your project, to keep consistency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sPqS02E3JrCM4crh54QHdQ.png" /><figcaption>The most used localisation and design tools and their default naming conventions</figcaption></figure><h4>Benefits</h4><p>Of course you can use a plugin and still manually change the key names, to keep your own specific architecture. However, <strong>taking advantage of this resource will (as all automations do) make your life easier. It will save you time, allowing you to prioritise other tasks that bring more value</strong>.</p><h4>Risks</h4><p>The engagement of designers when using this solution is mandatory. Because any mess in the designs will be automatically transformed into a mess in the key names. <strong>All artboards, group names, element names, etc. must be accurate because those will be the ones ending up as key names.</strong></p><p>Not necessarily a risk, but more a recommendation when associating the key creation to a tool, is to <strong>use a convention that can be scalable. This way, it would be easily to change a tool without having to change the logic</strong> behind the key architecture.</p><blockquote>When having a solid design system and an engaged design team, the automation of the key naming architecture is ultimately one of the best ways you can choose to explore.</blockquote><p>Thank you for reading this far! Now, I can’t help but wonder… <strong>what’s <em>your favourite choice</em> when it comes to key naming architecture?</strong> I’d love to learn other options and to hear any strong opinions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e9af6e0eb91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrating UX writing with the Agile Methodology]]></title>
            <link>https://medium.com/badiapp/integrating-ux-writing-with-the-agile-methodology-6727baac7aa7?source=rss-a77c53531b81------2</link>
            <guid isPermaLink="false">https://medium.com/p/6727baac7aa7</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-design]]></category>
            <dc:creator><![CDATA[Beatriz Arias]]></dc:creator>
            <pubDate>Fri, 13 Mar 2020 14:51:50 GMT</pubDate>
            <atom:updated>2020-03-13T14:51:50.825Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A content designer taking notes on a board" src="https://cdn-images-1.medium.com/max/1024/1*LvWQlg8VQKHiyhadqHUW8g.jpeg" /></figure><h3><strong>What it’s like to be a writer in tech</strong></h3><h4>Including content in sprints</h4><p>Having ownership of product content goes far beyond writing copies, managing translations, and uploading them to a CMS. It means <strong>providing the team with a content process -a whole strategy- that fits within the fast decision cycles of the sprints</strong>. Is it possible to do so? How to avoid clashing priorities? Can we skip obstacles and drive progress? <strong>Here’s what works for me: get involved in the overall process, build consensus, and make decisions.</strong></p><p>Even though writing may actually be the most important part of our tasks, it only takes up a small percentage of our time. Besides the word choice, we take care of <strong>content handoff in a method that was first conceived for software development</strong>, and that’s not always easy. After more than 5 years of working in cross-functional teams, I find the following very helpful.</p><h4><strong>1. Control the content process from beginning to end</strong></h4><p>As a UX writer, you can be asked about any copy, in any language, in any placement of the user journey, at any time. Either in production or in progress, or maybe for an a/b test. And you have to be ready to answer. This is only possible if you <strong>control the process</strong>. That will also mean you’ll have to <strong>take responsibility for every last detail</strong> but, wasn’t this what we wanted? Now that said, how exactly can we manage to do that?</p><h4>Murder lorem ipsum</h4><p>The first step of the content process should be, of course, developing the source content. When it comes to product writing, <strong>the content-first approach brings</strong> (besides all the benefits we already know) <strong>the opportunity to control the content from scratch</strong>. It will always be easier to follow -up on something that came from you and your team in the first place.</p><p><strong>This stage should ideally take place before the sprint is planned</strong>, so when the time comes for the team <strong>to evaluate and estimate efforts</strong>, they can do so having the final design and content and, in if any changes are needed, they can adapt better.</p><h4><strong>2. Provide the identifiers and be a part of the naming convention</strong></h4><p>Once the source content is decided, the second step is the handoff. Each small part of the content has its identifiers or, in other words, the way this content is going to be called from the code. <strong>If we want to be a real part of the process, we cannot confine ourselves to words</strong>. And at the end of the day, isn’t code a language?</p><p>While waiting for the translations to be ready, <strong>providing the team with the names of identifiers (also called keys or strings) -it will help them save time in development</strong>. This should be ready by the time they start coding and ideally left in the user story along with the rest of the requirements: technical documentation, source content, design and assets, workflow diagrams, etc. While this is something useful for the team in general, it also <strong>allows us writers to keep track of our content</strong> once it becomes code.</p><p>I find this naming convention part especially helpful. Since each platform usually follows its own rules, most of the times the same content has a different string for each of the platforms. However, <strong>when UX writers provide the strings, there is one single source of truth for all platforms</strong>, which reduces the effort needed to find content in the product, enable easier code reviews, helps to fix issues, avoids naming collisions, etc.</p><h4><strong>3. Move fast and test things</strong></h4><p>Whether you are using an in-house team of translators or you work with a translations software, <strong>upload the languages as soon as you get them. This stage also needs to take place during the development part of the sprint</strong> so the testing can be properly done. The QA team can even look for misplaced languages, spelling mistakes -if they speak the language, of course- or untranslated strings. Why lose the opportunity to test the content along with the functionality? We can even test the content ourselves, depending on the resources of the team. This way, <strong>by the time the release candidates are made we can be sure there won’t be any last-minute changes that will delay the process</strong>.</p><p>After that, the only thing left in the process is to start all over again (aka iterate). And each time it should get easier to find what to change and how, since we have being part of the process.</p><h4><strong>Consider problems from multiple angles</strong></h4><p>I warned about it at the beginning of this article: all these things go far beyond writing. Writing in tech means working in cross-functional teams. <strong>As UX writers and Content Strategists, we have to be aware of the needs that everyone has and work <em>with</em> them</strong>. Designers cannot start from a blank space and fill the prototypes with <em>lorem ipsum</em>. Developers need to have everything clear and decided by the time they start coding. QA teams need to have enough time to test the release candidate, especially for apps that have to be sent to the stores.</p><p>On the other hand, it is also necessary to <strong>promote an understanding of our discipline among the different profiles of the team</strong>. Having the ability to mentor others in the work we deliver can be as important as doing our work. Issues will arise but with empathy and communication, all of them can be easily solved.</p><p>Putting yourself in other people’s shoes requires being able to set aside the time and space to learn from other disciplines -and be willing to do so! The benefit that awaits is priceless, though. You’ll earn the respect of your teammates and you’ll grow as a professional along the way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6727baac7aa7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/badiapp/integrating-ux-writing-with-the-agile-methodology-6727baac7aa7">Integrating UX writing with the Agile Methodology</a> was originally published in <a href="https://medium.com/badiapp">badiapp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>