<?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 Elina Aleynikova on Medium]]></title>
        <description><![CDATA[Stories by Elina Aleynikova on Medium]]></description>
        <link>https://medium.com/@aleynikova.elina?source=rss-ed8e7735e749------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*u19virHr83VEGGG_p031og.jpeg</url>
            <title>Stories by Elina Aleynikova on Medium</title>
            <link>https://medium.com/@aleynikova.elina?source=rss-ed8e7735e749------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:16:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aleynikova.elina/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[       ?]]></title>
            <link>https://medium.com/@aleynikova.elina/-e817b9f3b7b2?source=rss-ed8e7735e749------2</link>
            <guid isPermaLink="false">https://medium.com/p/e817b9f3b7b2</guid>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <category><![CDATA[toxic-relationships]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[abuse]]></category>
            <dc:creator><![CDATA[Elina Aleynikova]]></dc:creator>
            <pubDate>Fri, 13 Dec 2024 13:02:03 GMT</pubDate>
            <atom:updated>2024-12-13T13:02:03.179Z</atom:updated>
            <content:encoded><![CDATA[<p>When did we reach the point where it’s acceptable and even necessary to talk about domestic violence, but workplace abuse is something we’re expected to stay silent about? Why does the unwritten rule still exist: “Don’t badmouth your former employer”? Why is honesty seen as a threat instead of a crucial step toward improving workplace culture?</p><p>This culture of silence strangely protects abusers. You leave a toxic company to start fresh but are expected to stay quiet — about the yelling, manipulation, or burnout. The logic goes: if you speak up, a potential employer will think you’ll do the same about them. But you know what? That’s not how it works.</p><p>Someone who speaks honestly about their work environment is not a problematic employee. They’re someone who wants to work in a place where personal boundaries are respected. Where it matters how people are treated. If everyone stays silent, toxic culture will never change — it will only grow stronger.</p><p>The recent case of the Indian startup YesMadam is another reminder that workplace abuse can take many forms. Employees were asked to take a stress test, and those who “didn’t meet the standards” were simply fired. This decision sparked criticism and drew attention to the issue, which is a positive step. Stories like this need to be highlighted.</p><p>I hope that one day we’ll be able to talk openly and without fear about toxic behavior at work. Because honesty isn’t a weakness — it’s the path to creating environments where personal boundaries are respected and people are truly valued.</p><p>Speaking out about toxicity is normal. Staying silent and covering it up? Not anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZA4_493RPxAiNxIfHpqvog.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e817b9f3b7b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Critical Factors in Why Defining User Scenarios is Key to Product Quality]]></title>
            <link>https://medium.com/@aleynikova.elina/from-layouts-to-user-scenarios-ux-design-8489a3c415cb?source=rss-ed8e7735e749------2</link>
            <guid isPermaLink="false">https://medium.com/p/8489a3c415cb</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Elina Aleynikova]]></dc:creator>
            <pubDate>Tue, 23 Apr 2024 11:17:18 GMT</pubDate>
            <atom:updated>2026-02-19T12:47:08.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LDEVS2dxhxmoOMaXRvkjcw.png" /></figure><p>In the process of product development, designers strive to create layouts that are both visually appealing and functional.</p><p>This means that each layout should not only be aesthetically pleasing, but also user-friendly, accessible, and provide effective user interaction with the product.</p><p>Nevertheless, I often face a repeated issue in the design process that affects the quality of the product and leads to increased costs and development time.</p><p>Layouts are often designed and discussed separately, without considering their relationship with other product elements. This can lead to additional adjustments during integration, problems with interface consistency, and other unexpected issues.</p><p>Today, I’d like to discuss the benefits of a different design approach. This method involves creating “chains” of layouts, or user scenarios, and demonstrates why it’s beneficial for each team member and the entire business.</p><p>Non-obvious (or obvious) advantages of designing user scenarios ⬇️</p><p>1️⃣ <strong>Testing Assumptions</strong><br>Scenarios help verify and test assumptions about how users will interact with the product, and allow the identification of potential issues at early stages.</p><p>2️⃣ <strong>Unnecessary Steps and Obstacles</strong><br>Scenarios help identify unnecessary actions and obstacles that complicate the use of the product, which directly affects the user experience and reduces the time needed to complete tasks.</p><p>3️⃣ <strong>Team Communication</strong><br>Scenarios provide a common language for everyone on the team, from analysts to developers and testers. They serve as a visual basis for discussions, minimizing the risk of misunderstandings and errors in project development.</p><p>4️⃣ <strong>Documentation</strong><br>Scenarios serve as documentation of how a user interacts with a product. This not only helps the team understand what the end goal of each design element should be but also simplifies the process of ensuring that all elements work together properly.</p><p>5️⃣ <strong>Closed Cases</strong><br>When creating user scenarios, designers consider all potential cases and touchpoints. This approach ensures that all necessary elements for performing user tasks are present and that the user path is carefully planned.</p><p>6️⃣ <strong>Foundation for the Future</strong><br>Understanding potential product use cases can help prevent errors and reduce the risk of costly changes in the future.</p><p>7️⃣ <strong>Loyal Customers</strong><br>Thanks to carefully developed user scenarios, the product becomes intuitively understandable and convenient to use, which meets the needs of users and increases their loyalty.</p><p>P.S: Scenarios are a process. Scenarios often change based on testing, feedback, or new processes, and that’s okay 😉</p><p>Join the discussion and share your experience! 💬 Do you create User Scenarios?</p><p>💜<a href="https://elina-aleynikova.com/"> My portfolio and CV </a><br>💛 <a href="https://www.linkedin.com/in/elina-aleynikova/">My LinkedIn</a></p><p>Welcome 🤗</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8489a3c415cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Our Figma Sticker System Revolutionized Team Collaboration ]]></title>
            <link>https://medium.com/@aleynikova.elina/figma-organisation-stickers-7a0cbb88ab51?source=rss-ed8e7735e749------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a0cbb88ab51</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Elina Aleynikova]]></dc:creator>
            <pubDate>Fri, 15 Mar 2024 08:50:58 GMT</pubDate>
            <atom:updated>2024-08-23T10:20:50.656Z</atom:updated>
            <content:encoded><![CDATA[<p>During our team’s work, we encountered a problem: each designer had their own method for formatting design files, scenarios, and layouts., which slowed down our collective work. The solution was to create a guide that unified our approaches and methods of work.</p><p>One of the elements of unification was a sticker system. It helped us standardize the work on the layouts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQAErPVtZnr3u9ftRPKLxA.png" /></figure><p>How does it work?</p><p>💎 Primary Stickers (UX comment, User action, Component behavior): Describe the key aspects of the design</p><p>🔄 Temporary Stickers (Open UX question, Question to PM, Comment for future): Act as internal notes, record current issues, and notify planned changes</p><p>🔗 Informational Stickers (Link to functional requirements, Link to Jira issue): Provide a link between the design and the tasks and documentation</p><p>🕵️ Research Stickers (Good, Bad): Record marks made during the analysis of references</p><p>This system significantly improved our workflow and the experience of colleagues from other departments who interact with our projects 🌪️🔥</p><p>Join the discussion and share your experience! 💬 How do you describe user behavior and interface elements in your projects?</p><p>💚 <a href="https://www.figma.com/file/FfPPxQZ4dY501A8e3CZu0D/UX-Design-Guide?type=design&amp;node-id=552%3A70166&amp;mode=design&amp;t=w7TqheAjK2ZGYXNa-1">UX Design Guide</a> <br>💜 <a href="https://elinaaleynikova.notion.site/Elina-Aleynikova-c92abb277e5a41b2abeea5d49d9f439c">My portfolio</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a0cbb88ab51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One-to-One Meetings: My Experience, Mistakes and Hacks]]></title>
            <link>https://medium.com/@aleynikova.elina/one-to-one-meetings-my-experience-mistakes-and-hacks-f20e76c000f3?source=rss-ed8e7735e749------2</link>
            <guid isPermaLink="false">https://medium.com/p/f20e76c000f3</guid>
            <category><![CDATA[one-to-one]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Elina Aleynikova]]></dc:creator>
            <pubDate>Sun, 04 Feb 2024 13:12:36 GMT</pubDate>
            <atom:updated>2024-02-04T13:34:37.349Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lDLLJHWGXfN4y0XNmtWTpQ.jpeg" /></figure><h4><strong>🦕 </strong>What 1:1 are and why they’re necessary</h4><p>At my last job, I became the lead of UX design, assembled a remote team, set up work processes, cultivated a friendly work environment, and together we achieved excellent results. Today, I would like to share my experience in conducting 1:1 meetings.</p><p>One-to-one is a regular private meeting between a lead and an employee. Its purpose is to enhance communication, identify needs, provide feedback, and discuss personal development, problems, or suggestions. I recommend this methodology to every manager to try.</p><p>Meetings remain crucial, even in an environment with open communication, a friendly atmosphere, and opportunities for personal or team discussions. Not everyone feels comfortable sharing their thoughts in general meetings, and some employees may hesitate to bring up certain topics in personal conversations.</p><h4>👋 <strong>How to conduct 1:1 meetings</strong></h4><ol><li>One-to-ones are scheduled in advance, allowing both the employee and the lead to prepare. Typically, I review notes from previous meetings to recall our discussions, track the employee’s progress, plan the meeting, and formulate questions. If there were no previous meetings, you could begin with the second point.</li><li>I prepare an individual set of questions for each employee, taking into account their qualifications, motivation, and current responsibilities. For example, it is important to ask a new employee how they are adapting to the team and the project. For someone who has embarked on a new role, it’s essential to determine how they evaluate their performance and whether they enjoy their current duties.</li><li>In the meeting, the lead’s main responsibilities are to foster a safe environment, ask questions, listen. with an employer we have to collaboratively find solutions, and outline an action plan. If the problem falls entirely within the lead’s competence — solve it, (it’s crucial to keep agreements and solve problems discussed with you). If there has been a previous 1:1 meeting with the employee, review the key points from that meeting, discuss any progress, and be sure to acknowledge the employee’s achievements.</li><li>At the end of each meeting, I requested feedback from employees regarding my performance and the effectiveness of the 1:1 sessions. This helped me improve the quality of our future meetings and pinpointing areas for my personal development.</li></ol><h4><strong>📆 Regularity</strong></h4><p>The meeting typically lasts about an hour, and we hold it every three months. We’ve experimented with different intervals and found this to be the optimal frequency for our team. However, every team is unique, so it’s worth exploring various frequencies to determine what works best for your team.</p><h4>🧠 <strong>My mistakes or what I would change</strong></h4><ol><li>Previously, I kept notes only for myself. Now, I would create a shared board for both the employee and myself. This way, we can make notes during our meetings, and the employee will always have access to it.</li><li>I used to start 1:1 by asking questions and then developing the conversation. Now, I would begin by asking the employee if there’s something they wish to discuss during the meeting.</li><li>I used to schedule meetings a week before each 1:1. Now, I would plan all one-to-ones a year in advance. This will allow employees to see the full schedule of meetings, always be aware of the next 1:1 date, and have more time to prepare.</li></ol><h4><strong>👀 My hack</strong></h4><p>A list of 100 questions for one-on-one sessions has frequently come in handy. It’s not always easy to remember all the crucial questions to ask. Occasionally, I’ve used pre-made questions or remembered what I wanted to ask while reviewing the list. The questions are grouped by themes: career growth, job satisfaction, team, company, work-life balance. Usually, I covered all these topics during 1:1 meetings.</p><h4><strong>📍Conclusion</strong></h4><p>I’d be happy to write more about methodologies, my experiences, UX, and service design, so let me know if you found this useful! If you have additions from your experience as an employee or leader, share them, I would appreciate it! A big thanks for reading 👉 💖 👈</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f20e76c000f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>