<?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 Pchelova on Medium]]></title>
        <description><![CDATA[Stories by Julia Pchelova on Medium]]></description>
        <link>https://medium.com/@pchelova.julia?source=rss-b08a3a4738cc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y3wOtMs5vEFbFwwA8AUdWA.png</url>
            <title>Stories by Julia Pchelova on Medium</title>
            <link>https://medium.com/@pchelova.julia?source=rss-b08a3a4738cc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:28:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pchelova.julia/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[Continuous Discovery Habits: How to Deal with User Interviews]]></title>
            <link>https://medium.com/design-department/continuous-discovery-habits-how-to-deal-with-user-interviews-a5945bdccfa?source=rss-b08a3a4738cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5945bdccfa</guid>
            <category><![CDATA[collaborative-work]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[continuous-discovery]]></category>
            <dc:creator><![CDATA[Julia Pchelova]]></dc:creator>
            <pubDate>Tue, 30 May 2023 09:05:23 GMT</pubDate>
            <atom:updated>2023-05-30T09:05:23.777Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YtKk06o6OMv9RuXDSLjTMw.png" /><figcaption>The path through obstacles</figcaption></figure><p>Product teams need to keep in touch with customers on a regular basis — it’s simple. However, the world works differently. Despite the fact that the product community as a whole supports the development of products under the guidance of the customer, it is still difficult for most companies to implement this operating model when flexible teams independently make decisions about what to create next based on research and insights. We want to tell you how a B2B product has implemented a modern technology called Continuous Discovery.</p><h4>Problem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Wg4_9eMhAZ_aHJHjxgwx0A.png" /><figcaption>Wasting time</figcaption></figure><p>We are faced with the fact that conducting interviews with our users has become very labor-intensive. We need to notify our users about the problem we want to discuss, write to everyone, and arrange a meeting, among other things. It is not profitable for us to pay for companies that help in hiring respondents or use other resources.</p><h4>Saving Time and Resources</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*dhbiRtkGY_mVdM4wTMxbTg.png" /><figcaption>Reference to Theresa Torres’ book “Continuous Discovery Habits”</figcaption></figure><p>The product manager of our team advised the design team to read “Continuous Discovery Habits” by Teresa Torres and consider whether we can use continuous research in our process. This approach is convenient because, once we have made an effort to create an environment for constantly hiring our users for interviews, the team no longer needs to spend resources on finding respondents and sending invitations. This becomes an automated process.</p><h4>Collaborative Efforts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SXeKlWB6-FC4SymKGpldAQ.png" /><figcaption>Upgrading workflow</figcaption></figure><p>We started our work on the implementation of this research by discussing with analysts, developers, product managers, and designers whether this process is suitable for us at all and whether it is worth investing effort in it. For the research, Teresa suggests creating a trio from the product team members — 1 PM, 1 designer, 1 developer. In our case, we wanted to include an analyst in this process. However, the planning of the research part has been postponed until we figure out how it will work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*FonVTX1Nir6jnx0KqNXtNw.png" /><figcaption>Recruiting users for research</figcaption></figure><p>We organized a meeting with the development team, demonstrated our idea, and asked them to consider how we could implement a separate pool of users into our database, add and remove users from there, and send them invitations every 30 days. Those who have already been contacted should be marked in the database to avoid spamming them with an invitation to an interview for the next 30 days. While the developers were thinking about the database architecture, the designers were creating a user flow to cover all the corner cases. By the next iteration, the analyst had applied the user flow, the tester had applied the requirements, and the designer already had layouts in which the user could independently include themselves in the pool of loyal users who would help to develop our product. The last stage was verifying the invitations, which we decided to send directly to the application for better conversion with the marketing department.</p><h4>Database Development and Adaptability for Panel Users</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Y9tKbFPmGG7PYeOdYctE9A.png" /><figcaption>Reducing the scope of tasks</figcaption></figure><p>The difficulties during the implementation stage were mostly related to the development and adaptability of our database for panel users. For all the features we were unsure about, we decided to try with an MVP and added an additional column to the database, along with an “if-else” condition when sending invitations from our admin panel.</p><h4>Results</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*z31g5NNs41MLMtqh0OzOsQ.png" /><figcaption>Improving the result</figcaption></figure><p>During the week, over 30 respondents responded and almost all of them were hired. The collection of contacts for the product manager took only 15 minutes… whereas before the changes it would have taken several days of focus.</p><p>Our future plan is to add additional columns to display the context for determining the target audience for any specific research.</p><p>Feel free contact us in case of any questions!</p><p>Lead Product Designer <a href="https://medium.com/u/a7b66e14951d?source=post_page-----aae832c1afc0--------------------------------">Bjorn the UX Dog</a>: mkinezumichg@gmail.com | <a href="https://dribbble.com/marinamelnik91">dribbble</a></p><p>UI designer <a href="https://medium.com/u/c2b1672d462?source=post_page-----aae832c1afc0--------------------------------">Alexandr</a>: aminibaev@hotmail.com | <a href="https://dribbble.com/minik">dribbble</a></p><p>Product Designer <a href="https://medium.com/u/b08a3a4738cc?source=post_page-----aae832c1afc0--------------------------------">Julia Pchelova</a>: pchelovajul@gmail.com</p><p>Product Designer Aleksandr: alecchernov@gmail.com | <a href="https://www.facebook.com/alecchernov">facebook</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5945bdccfa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-department/continuous-discovery-habits-how-to-deal-with-user-interviews-a5945bdccfa">Continuous Discovery Habits: How to Deal with User Interviews</a> was originally published in <a href="https://medium.com/design-department">Design Department</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empty states]]></title>
            <link>https://medium.com/@pchelova.julia/empty-states-5ed0874e9120?source=rss-b08a3a4738cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ed0874e9120</guid>
            <category><![CDATA[empty-state]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[ux-process]]></category>
            <category><![CDATA[error-handling]]></category>
            <dc:creator><![CDATA[Julia Pchelova]]></dc:creator>
            <pubDate>Mon, 13 Jun 2022 06:19:13 GMT</pubDate>
            <atom:updated>2022-06-13T06:19:13.985Z</atom:updated>
            <content:encoded><![CDATA[<p>Empty states are moments in a user’s experience with a product where there is nothing to display.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eJxJWsUWiWzcAq-1oTIxiw.png" /><figcaption>Cover for Empty states article</figcaption></figure><h4>Intro</h4><p>Creating empty states was the first task in my new position. I was so nervous and excited that I did my best to cope with this task.</p><p>We have the usual parts of the hiring application, such as Positions, Candidates, Offers, and so on. How I saw the work on this task - I have to go through the main parts of the site and put the “No data” text on a blank page. This text should also go with an attractive image, a description of the reason for the lack of data, and a CTA button. But I actually worked on this task for 2 months instead of a couple of weeks. Let me get this straight why it’s not so easy.</p><h3>Empty state types</h3><p>Empty states include the following designs:</p><ul><li><strong>Onboarding </strong>- the user really doesn’t see anything on the page because he has just signed up, configured the application, and so on</li><li><strong>User actions </strong>-<strong> </strong>here the user may see an empty page due to incorrect filters or due to a completed task</li><li><strong>Handling errors </strong>-<strong> </strong>usually, these are 400 and 500 errors, unstable Internet connection, the permissions issue</li></ul><p>So, I divided my work into three tasks related to these points, researched well-known design systems to clarify how they handle this, prepared mood board with interesting ideas. And I started with the onboarding. Because we have received requests from users to reduce the time from familiarization with the system to the creation of the first object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cGLSkUiKxlKYAJpB" /><figcaption>Empty state mood board on Miro</figcaption></figure><h3>Onboarding</h3><p>The first impression is so important. That’s why the design has to help to organize the basic first interaction between the user and the interface.</p><p>Onboarding can have the following designs:</p><ul><li><strong><em>Checklist</em></strong>. This helps the user to see his progress and awaken in him the motivation to complete the adaptation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*whrshaUbkigCktk26rBcSw.png" /><figcaption>Onboarding UX tool - Checklist</figcaption></figure><ul><li><strong><em>Modals</em></strong><em>. </em>This onboarding tool completely captures the interface screen. It seems best to use it sparingly or save it when there are necessary inputs that the user must complete before using your product</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ROZkjCQwfXeqVtD3FUMBsA.png" /><figcaption>Onboarding UX tool - modals</figcaption></figure><ul><li><strong><em>Guidance</em></strong><em>. </em>This is the most frequently used type for empty states. This explains what will be in the space after it is filled with data, and gives recommendations for the next step</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n30KmI_0VdPlmvPHltdUJQ.png" /><figcaption>Onboarding UX tool - guidance</figcaption></figure><ul><li><strong><em>Starter content</em></strong><em>. </em>Providing high-quality initial content helps users visualize what the product is for and what will happen next</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6qn5s0ZARgZjwygwm828tw.png" /><figcaption>Onboarding UX tool - <em>Starter content</em></figcaption></figure><p>I chose the <em>Guidance</em> for my task. I described the main action that the user should perform and added the CTA button. My team decided that this is a more cost-effective way of dealing with onboarding. The user has a button that helps him achieve the first goal and feel involved in the process. For the user’s onboarding, make it easy for them to get to what they want or need to do.</p><p><strong>Do:</strong></p><ul><li>Reduce the number of words to make it easy reading and following onboarding instructions</li><li>As a designer, you need to know what will be in your interface to create a clear step-by-step guide</li><li>If the user can create something on your empty page, then put this action in the CTA button. You have to make this action fast to perform. Alternatively, you can lead users to a place where they can create something</li></ul><p><strong>Don’t:</strong></p><ul><li>Don’t include content related to other areas of the interface</li><li>Don’t use professional slang. At this step, the user doesn’t know them</li><li>Don’t include many options in one empty state. If the user can perform more actions, select an important one and point the user to this action</li></ul><h3><strong>User actions</strong></h3><p>For this statement, I’ve included the following designs:</p><ul><li>successful user achievements leading to empty states</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gCUa4_gzB3M9ljt5Td0hOw.png" /><figcaption>Empty state of a successful user action</figcaption></figure><ul><li>unsuccessful user actions that should be displayed on the screen</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fu1QlIPK6LDeInnrKPQV7Q.png" /><figcaption>Empty state of a failed user action</figcaption></figure><p>Empty states should be useful and positive in both cases. The tips should improve the user experience over time. Give users the next step - something to do or interact with.</p><p><strong>Do:</strong></p><ul><li>Empty states should be replaced by an object that usually appears</li><li>Provide users with feedback based on their actions. The user understands that he has successfully completed the process. The user understands how to proceed in case of an error</li></ul><p><strong>Don’t:</strong></p><ul><li>Never blame the user for mistakes that lead to unsuccessful results and feel like it’s their fault</li><li>Avoid images for empty states showing urgency or confusion</li></ul><h3>Handling errors</h3><p>Empty states appear when data is available, but cannot be displayed to the user for some reason. It is important here that the user understands the problem and, if corrective actions are available, knows what actions should be taken, or has options for solving the problem.</p><p>Errors type:</p><ul><li><strong><em>Systems errors. </em></strong>Most often 404 and 500</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crlRN3Ak7Q83cHFRG4trXA.png" /><figcaption>Example of a 502 bad gateway error that signals to the user that “Something went wrong”</figcaption></figure><ul><li><strong><em>Access denied. </em></strong>The user has no access to view the data</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BJ-ZIeGRV6Ja5MUM4pMkXQ.png" /><figcaption>Empty state of Access Denied</figcaption></figure><ul><li><strong><em>Sign-in required. </em></strong>The user must have additional configuration or registration in the system to view the data</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m_Pr2wvHodxjkHDuxrzH4w.png" /><figcaption>Empty state of <em>Sign-in required</em></figcaption></figure><p><strong>Do:</strong></p><ul><li>Discuss with your team what information is available to users</li><li>If there are corrective actions, give the user an effective next step</li><li>If multiple actions are available to the user, be sure to include a hierarchy so that it is clear which option will be the main action</li></ul><p><strong>Don’t:</strong></p><ul><li>Do not use frivolous expressions such as ‘Oh no!’ ‘Oops!’ and so on. Respect the user and don’t joke</li></ul><h3>Summary</h3><p>We see that empty states are displayed for different reasons and may require different processing methods. It often has a secondary role. With thoughtful design, it becomes an essential part of user-friendly interaction, providing just enough information in context so that users can continue to work productively.</p><p>Strive for a balance between the situation and the content you provide. More content doesn’t necessarily mean it’s the best solution, since having a lot of content on a page increases cognitive load. This is especially true when users are interacting with your product for the first time, so leave the more difficult educational moments for the main functions and more complex situations.</p><p><em>Did you find a typo? Send a screenshot to Telegram: @itsthearcher</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ed0874e9120" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX writing]]></title>
            <link>https://medium.com/@pchelova.julia/ux-writing-e4ec11b106a6?source=rss-b08a3a4738cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4ec11b106a6</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[uxtip]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Julia Pchelova]]></dc:creator>
            <pubDate>Wed, 20 Apr 2022 16:38:09 GMT</pubDate>
            <atom:updated>2022-04-20T16:38:09.592Z</atom:updated>
            <content:encoded><![CDATA[<h4>for non-ux writers</h4><h4><em>Intro</em></h4><p>UX writing is an invisible part of the design process. I’d like to say this part of the process is not widely covered. In my company I partially take responsibility for the UX writing. This fact made me think about the UX writing summary for <em>non-ux writers</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*scYKVv0VWIlCoefKVh95sg.png" /><figcaption>Cover for a UX writing article</figcaption></figure><h3>UX writing preparation</h3><p>When I started this role, I wrote to a colleague on LinkedIn, who works for a big company as a UX writer. He suggested me articles and courses, that he also used. Writing guide by Google Material, Mailchimp Content Style Guide were among them. Also, I decided to read the “Writing for Designers” by Scott Kubie. Then I started to create the UX writing process based on the experience of other companies. Now it consists of the following steps: generation and saving text ideas, composition, editing and checking.</p><h3>Generation and saving text ideas</h3><ul><li><em>Mindmaping.</em> Blank page is similar scare for everyone. When you are starting to generate ideas, the non-liner page helps you more to create connections and break you out of the box. It helps to generate, collect and sort ideas for labels, buttons and other small UI elements.</li><li><em>Inventories.</em> It would be useful to keep a place with rules for interface text. It should include a glossary, writing guides, writing style, punctuation, voice and tone. All of these established rules will be good bases for new text cases. You shouldn’t create inventory from scratch. Research all of the design systems, because some of them have open information about their writing rules.</li></ul><h3>Composition</h3><ul><li><em>Rough-in</em>. Take text and put it in the mockups or near. The design of the user interface can affect the length or even the wording of your text. This is a good way to test your text in the environment</li></ul><h3>Editing and checking</h3><ul><li>Check gramma and punctuation</li><li>Make edits according to your <em>Inventories</em></li><li>Apply for feedback</li></ul><h3>Example</h3><p>I share some UX writing rules that have been proven as useful to me</p><h4>Good interface text</h4><ul><li>It’s clear for a beginner</li><li>Preserves equality. Read from the male, then from the female person</li><li>It sounds natural. Make communication with the interface as simple as a conversation between people</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HnNRHOtCE38pcaSBSdfbLQ.png" /><figcaption>Better experience for buttons</figcaption></figure><ul><li>Cares about feelings. Make sure that the text doesn’t evaluate feelings</li><li>Consistently. In the explanation, we put the actions exactly in the order in which the person will perform them</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-fenpnhxMkUu5QFC5_uYpQ.png" /><figcaption>Better experience for user actions</figcaption></figure><ul><li>Agreed. Consistency of blocks with the header</li><li>Uniformly. If one item in the list begins with a verb or noun, then the rest are in the same form</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JOHpWQ5WAaxuUW26avMIfw.png" /><figcaption>The best experience for reading bullet points</figcaption></figure><ul><li>Validations. Not just to pronounce the rules for filling in the fields, but to give valuable advice</li><li>The text does not repeat the function. We do not pronounce the function of the element in the text if it is familiar.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6mGYK_TT1uIPhEi9EZFa8w.png" /><figcaption>Better experience for search input</figcaption></figure><ul><li>Without empty words. Check whether each word in the text has some meaning</li></ul><h4>Two ways to create a bad experience</h4><ul><li>Make it <em>unclear</em> ⤑ abstract, inconsistent</li><li>Make it <em>unpleasant</em> ⤑ assessments of feelings, inappropriate delights, gender negligence</li></ul><h3>Conclusion</h3><p>To sum up, I advise you to find your own online tools for checking grammar, spelling and punctuation for each language. But it’s better to improve your grammar and have a proofreader over you. Your eyes may get blurred and you may miss a mistake.</p><p><em>Did you find a typo? Send a screenshot to Telegram: @itsthearcher</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4ec11b106a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>