<?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 Aleksandra Selezneva on Medium]]></title>
        <description><![CDATA[Stories by Aleksandra Selezneva on Medium]]></description>
        <link>https://medium.com/@Textoin?source=rss-4f77f45ac439------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ON3s-yUPH39tmZCfNrO8Dg.jpeg</url>
            <title>Stories by Aleksandra Selezneva on Medium</title>
            <link>https://medium.com/@Textoin?source=rss-4f77f45ac439------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:20:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Textoin/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[Always check what story do you accents tell]]></title>
            <link>https://medium.com/@Textoin/always-check-what-story-do-you-accents-tell-5be9ab90d8eb?source=rss-4f77f45ac439------2</link>
            <guid isPermaLink="false">https://medium.com/p/5be9ab90d8eb</guid>
            <dc:creator><![CDATA[Aleksandra Selezneva]]></dc:creator>
            <pubDate>Wed, 29 Jan 2025 16:57:20 GMT</pubDate>
            <atom:updated>2025-01-29T16:57:20.782Z</atom:updated>
            <content:encoded><![CDATA[<h3>Always check what story do the accents tell</h3><p>Imagine there’s a taxi app. Some user casually opens it to take a ride home. However, today is not a good day. Some roads in the city happen to be closed. Unfortunately, fate has put the user exactly in the closed zone from which it’s impossible to leave. Here comes our heroic app and generously offers to find the nearest place the driver can stop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oD3TYTnuPbWquEb_b_TQdA.png" /></figure><p>The eternal flow the user is accustomed to changes. That’s why the app should somehow reflect that. Let’s imagine, it shows a pop-up when the user opens the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uPigPW0dUHsCFjn6ucy7Vg.png" /></figure><p>What could go wrong? Well, to put it mildly, users are bad readers. I wouldn’t even use the word ‘readers’: in interfaces, they are more likely to be called ‘scanners’. Imagine a typical user of a taxi app: they have a cup of latte in one hand, a child in the other and ‘should I buy those towels?’ in head. Would they read the pop-up with all the respect it deserves? Not really.</p><p>What the users do, they scan the screen and read the most active elements. Headers, subheaders, buttons if you are lucky enough. So in fact, for the real user our screen looks more like that:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PNVJFWcn94N-AqQdu-EpVA.png" /></figure><p>The user got wrong main idea. Well, the roads are closed, it’s true. But that wasn’t the main point. The main point was that the app has found the spot to leave. In fact, the app helped the user, but the pop-up sounds restrictive. It looks like the app forbids you from going anywhere. In reality, on the opposite, it helps the user.</p><p>What if we changed the accents a little bit in order for them to reflect the caring nature of the app?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kbufvc8O5gvdQmI6-Lzkrg.png" /></figure><p>Why is the second one better:</p><ol><li>It highlightes the possibility instead of the restriction.</li><li>The flow becomes smoother. After the user presses the button, the app takes them to the nearest spot. It’s much more expected in the second variant.</li></ol><p>That’s why I always check which story do the accents tell. It’s perfect if you catch the main purpose of the product communication from the accents only.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5be9ab90d8eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product character: a tool that saves time and energy]]></title>
            <link>https://medium.com/@Textoin/a-character-for-a-product-a-tool-that-saves-time-and-energy-cc8fd717ba69?source=rss-4f77f45ac439------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc8fd717ba69</guid>
            <dc:creator><![CDATA[Aleksandra Selezneva]]></dc:creator>
            <pubDate>Wed, 22 Jan 2025 17:29:46 GMT</pubDate>
            <atom:updated>2025-01-29T18:41:18.572Z</atom:updated>
            <content:encoded><![CDATA[<p>When a large product becomes a chaotic mass of random decisions, it’s a time-consuming pain. Can we add a joke? How do we address the user? Do we EVER use passive voice? Can we make the heading more quirky? Endless discussions drain time and energy. The texts are endlessly rewritten.</p><p>If stylistic battles are so draining, why not create a tool that helps?</p><h3>Character is an abstract, but important category</h3><p>I don’t harbor illusions that we can weave a truly authentic character into lines of code. Companies will remain companies, even with the flirting around humanity, friendliness, and other virtues. At the very least, text alone will not achieve this.</p><p>Nevertheless, a character — or a model of one — can be a useful tool.</p><h4>The Benefits</h4><ol><li><strong>Better Writing:</strong><br>The best texts often come when you think, “How would I say this to a friend?” Here, you could ask, “How would this character say it?”</li><li><strong>Easier Decision-Making in Teams:</strong><br>In large companies, it’s easier to explain and pitch decisions when there’s a consistent analogy or coherent picture. Character can be one of these tools, alongside editorial policies, guides, or even playful aids like tarot cards.</li><li><strong>Streamlined Discussions:</strong><br>Instead of endless debates about whether a phrase should be humorous, serious, or playful, discussions can be directed into a single manageable stream defined by the character.</li></ol><h3>Don’t create from scratch: observe first</h3><p>I’m convinced you can’t “invent” a character by locking yourself in a meeting room. The word “invent” feels presumptuous, artificial, and false. Instead, observe, collect, and formalize.</p><p>A service isn’t born in the moment — it already exists. It has a history, shaped by people with particular views. It already interacts with users, and certain communication styles have already developed. Observing these elements can help crystallize a character.</p><p>However, there’s a temptation to create a plastic, shallow caricature: “We’re friendly, human, approachable, but not overly familiar. We’re helpful, innovative, and cool.” Such descriptions are often a fear-driven patchwork to avoid missteps, not a true character.</p><p>A genuine character must have conflict, history, and depth — a core from which everything grows.</p><h3>Example: Yango</h3><p>Here’s the core of restrictions and premises that we (the art director and I) identified for Yango</p><ol><li><strong>Mass Appeal</strong><br>The tone needs to remain neutral to address a wide audience. This likely means avoiding something overly bold or edgy.</li><li><strong>Engineering Background</strong><br>The product was created by people steeped in the exact sciences. To understand this, observe how these people speak and what kinds of questions they ask.</li><li><strong>Dynamic</strong><br>Within Yandex, the Taxi unit is considered one of the fastest-moving and most hectic. It’s constantly changing and adapting, often under pressure. The product operates at the intersection of real-world dynamics — roads, people, and speed — which are never straightforward or easy.</li><li><strong>Short Interactions</strong><br>Most user interactions with Taxi are brief and practical — people step outside into the cold, order a ride, and quickly get in. The ride itself is not the highlight of their day.</li></ol><p><strong>Result</strong><br>This character values precision, system-building, and thorough planning but is constantly challenged by the fast-paced environment. It must balance careful reasoning with the need to adapt quickly — a tough balance to maintain.</p><h3>Avoiding being a Mary Sue</h3><p>A critical part of this work is removing unnecessary positive adjectives. It’s easy to fall into the trap of adding excessive “sweetness.”</p><p>The fewer adjectives, the better. Actions speak louder. A character is defined by their actions.</p><p>For example, instead of saying a character is “friendly and innovative,” show their friendliness and innovation through how they act or solve problems.</p><h3>Try to write whole paragraphs in the character’s voice</h3><p>To bring a character to life in interface phrases, it can be helpful to develop a corpus of texts. Imagine how the character would talk about their technology or themselves. It’s like training neural networks with vast text datasets — editors can train themselves in the same way. These corpora can then feed into interface designs.</p><h3>Consider the UX scenarios</h3><p>A critical part of the process is creating a “snapshot” of the application: documenting what already exists.</p><ul><li>I reviewed the latest versions of the app on iOS and Android, taking screenshots of various elements. While testers could assist, it’s best to personally explore the app to get a feel for its “body.”</li><li>Include all system notifications. Designers may not always consider these, but they’re part of the user experience too.</li><li>Break the collected elements into user flows. You’ll quickly notice which paths are well-trodden (frequent interactions) and which are for specific audiences, like loyal users or those with unique needs.</li></ul><p>This snapshot reveals inconsistencies and overlaps, serving as a foundation for building a glossary. For example:</p><ul><li>When to use quotation marks.</li><li>Consistent naming conventions for locations, features, or user actions.</li></ul><h3>The Final Outcome: a constructor</h3><p>People have a natural way of speaking, but they adjust based on the situation and the audience. Similarly, the application should have a consistent tone (its “base”) and adapt for different scenarios.</p><ul><li><strong>Base Tone</strong><br>This includes the core principles and sensitive topics:</li><li>Should the tone be imperative?</li><li>Should we use the first person (“we are searching for a car”) or keep it impersonal (“searching for a car”)?</li><li>These foundational rules apply to all scenarios.</li><li><strong>Adapting to Scenarios</strong><br>For example, if a long-time user is upgraded to a better car at no extra cost, the message can be slightly more personal. The base tone remains intact, but the syntax and word choices reflect warmth and gratitude.</li><li>Even in emotional messages, the structure prioritizes clarity: essential information first, emotions second. For instance:</li><li>Information in the first sentence.</li><li>Emotions afterward.</li></ul><p>Limit exclamation marks to maintain professionalism — one per screen is enough. This avoids overly exuberant messaging.</p><h3>Iteration and Evolution</h3><p>Whenever a new user situation arises, a corresponding tone adaptation is developed and built upon the base tone. For instance, handling premium tariffs requires creating a new layer in the tone system, firmly rooted in the base rules.</p><h3>Foundation and Core</h3><p>Creating a character cannot be done in isolation. This process requires collaboration with influential figures such as art directors, chief editors, and marketing leaders. Their support ensures the ideas are adopted across the organization.</p><p>The goal is to create a shared framework — a common ground for discussions and decisions. This avoids confusion and ensures alignment, even in a large company.</p><h3>Closing Thoughts</h3><p>This process cannot succeed in isolation. Share your ideas widely, defend them, and ensure they are embraced across the organization. When successful, this framework creates a shared language for everyone to build upon, aligning diverse teams around a unified vision.</p><p><strong>Simplicity is Okay</strong><br>A character doesn’t have to be flashy or bold. Subtlety can work well, especially when the approach suits the product.</p><ol><li><strong>Subjectivity Remains:</strong><br>No matter how much you formalize things, tone and voice remain subjective. You’ll still encounter questions like, “Is this too bold? Too soft? Is it just right?” Disputes are inevitable, but having a formalized tool agreed upon by the team makes negotiations easier.</li><li><strong>A dedicated person needs to own this process.</strong> They need both authority and freedom to make decisions. Without trust, the task becomes arduous. That person will likely be unpopular with parts of the team because their job will involve saying, “No, we’re not writing it this way. Why? Because I decided so.”</li><li><strong>Not Everyone Will Like the Character</strong><br>It’s impossible to create a character everyone loves — and that’s okay.</li><li><strong>Character Evolves</strong><br>Once a character is defined, it starts aging immediately. Everything changes, and clinging to the past is unnecessary.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc8fd717ba69" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>