<?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 Eshita Priyadarshini on Medium]]></title>
        <description><![CDATA[Stories by Eshita Priyadarshini on Medium]]></description>
        <link>https://medium.com/@e.priyadarshini?source=rss-32b07b449a4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*AY_ngYB1D2LYSJQt2SBAlw.jpeg</url>
            <title>Stories by Eshita Priyadarshini on Medium</title>
            <link>https://medium.com/@e.priyadarshini?source=rss-32b07b449a4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:05:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@e.priyadarshini/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[Are you taking the user feedback that matters?]]></title>
            <link>https://medium.com/@e.priyadarshini/are-you-taking-the-user-feedback-that-matters-f25ef1b460d5?source=rss-32b07b449a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f25ef1b460d5</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Eshita Priyadarshini]]></dc:creator>
            <pubDate>Wed, 04 Sep 2019 05:44:34 GMT</pubDate>
            <atom:updated>2019-09-04T05:44:34.469Z</atom:updated>
            <content:encoded><![CDATA[<p>“The app is looking great, I have shown it to my friends &amp; family who say that this is exactly what they need.’’ says someone excited about an app he is building and could not wait to get feedback from the real users “But they were also saying that why is there so much white space in your app”. “What is the question you asked them” I was curious. “What is your opinion about increasing productivity through this app” said the product owner.</p><p>I am a big advocate of taking early feedback for ideas and products; However, I am a bigger fan of “asking the right question to the right user”.<strong> </strong>Building products in isolation may cost time and resource but talking to anyone or asking leading questions in the name of user feedback can misinform the product owner and cost some precious user love.</p><blockquote><strong>In fact, while taking feedback a product, one should something unique about human psychology that, even with the best of their intentions, people may say something else but behave completely different inside the product.</strong></blockquote><p>In the above case, a general query about the app may give some confidence to the enquirer <a href="https://www.spring.org.uk/2008/03/attitude-behaviour-gap-why-we-say-one.php">but it will not signal whether users will use it</a>. Depending on the mood at the moment, people may give generic answers to the interviewer, sometimes to please them or to evade them. They may even express opinions formed on hearsays or half known facts.</p><blockquote><strong>For anyone, the purpose of collecting feedback for a feature or a product is to understand its workflow efficacy in meeting the end goal of a user. To do that, it is imperative to collect dependable user feedback that can leads to informed decisions.</strong></blockquote><p>As a user research leader, I believe everyone in the product team should talk to the user and take feedback as often as needed. Hence, I have compiled here an “everyone’s everyday guide to talk to the user”. This guide is aimed to be a process lean checklist, to help any one, a CEO, a senior leader, a product manager, a designer or a user researcher to collect consumer’s insights in an objective manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-cHNg5Ef-AT3xRd4sIp3g.png" /></figure><h3><strong>Find the right user</strong></h3><p><em>Anecdote — Hey, since you head the sales team look at my app and tell me what you think of the product that I am building for on ground sales operations?</em></p><p>Imagine building a product to improve the productivity for on ground sales staff who spend a lot of time meeting their customers. The product owner meets a friend who heads sales for a region to get his feedback on what he is building. Will his friend be the “right user” to talk to?</p><h4><strong>Who is the right user to talk to?</strong></h4><ul><li><strong>Prospective User-</strong> someone who will use your product or feature daily or frequently in future</li><li><strong>A pro user </strong>— uses your or competitive product daily or frequently</li><li><strong>A frustrated user </strong>— has abandoned your or competitive product in the last few weeks because of critical issue/s</li></ul><h3><strong>Ask the right questions</strong></h3><p><em>Anecdote — do you think it is helpful if technology can help reduce your effort and you can track your users progress on your phone? How do you think it will help?</em></p><p>This question is presumptuous that the user is comfortable using a tech product and that he will, most probably, find it valuable to use. It also put pressure on the user to give the “right answer” to the interviewee, not an objective one. How will you express through a “right question”?</p><h4><strong>What constitutes of a right question?</strong></h4><ul><li><strong>Define a goal, sequence questions- </strong>define a goal, e.g what is the ease of finding a movie theater on our website?<strong> </strong>Start by asking broad questions, follow up with specific ones. E.g How do you book tickets for a movie? When online, how do you find which theater to watch it at?</li><li><strong>Don’t guide, observe-</strong> Asking question is not always necessary. You could implicitly define start and end goal for user in a workflow and request them to go through it. Observe users’ behaviour &amp; pain-points as he completes the task. Do not tell him how to complete the task as it makes the user feel inadequate and defensive</li><li><strong>Don’t ask leading questions</strong> — do not tell them what they couldn’t do on the product; don’t ask questions to confirm your own bias; do not assume user’s feelings. e.g do you feel frustrated since you could not find the filter? Reframe by asking what concerns do you have since its difficult to find the filter?</li></ul><h3><strong>Arrive at the right answers</strong></h3><p><em>Anecdote — I have spoken to many users; all of them say the same thing</em></p><p>Warren Buffet famously said “ what the human being is best at doing is interpreting all the new information so that their prior conclusion remain intact”. Typically, when we talk to multiple users on several days, we are bombarded with a lot of information. We may be susceptible in formulating an easy theory based on quickly found evidence and call it a day. So if you think most of the users said the same, have you considered that the only answers you remember are the confirming ones?</p><h4><strong>How to arrive at the right answers?</strong></h4><ul><li><strong>Write down the answers — </strong>document them in a doc, makes notes or record audios or videos to go over later.</li><li><strong>Compare answers from different users — </strong>choose the preferred medium to compile user stories and observations together. Consider building an<a href="https://uxmastery.com/disruptive-innovation-design-process/ideas-and-insights-wall/"> insight wall</a> or keeping a handy<a href="https://uxdesign.cc/the-rainbow-sheet-a-visual-method-for-research-analysis-a7e7d2011058"> rainbow sheet</a> to help the entire team view your findings.</li><li><strong>Synthesise, prioritise — </strong>spend some time to go through you findings, draw conclusion per observation and pain-point. To prioritise which is the most critical pain-point should you solve first, arrange your observation on a simple matrix like below on Miro boards or whiteboard</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ViTA4Xz5NqXQr3aiBy7g3g.png" /></figure><p>This guide is aimed to collect insights from planned or impromptu discussions with the users while one is building a product or a feature. Often for certain products or situations it may be more complicated to find what users truly desire. In such case a user researcher will deploy more mature method of collecting user insights, recording them and synthesising them.</p><h4>Read further</h4><p><a href="https://www.userinterviews.com/ux-research-field-guide-chapter/find-good-research-participants">Find Good Research Participants</a></p><p><a href="https://uxdesign.cc/asking-the-right-questions-on-user-research-interviews-and-testing-427261742a67">Asking the right questions during user research, interviews and testing</a></p><p><a href="https://usabilitypost.com/2009/07/27/how-to-observe-the-user-and-tap-into-the-experience/">How To Observe the User and Tap Into the Experience</a></p><p><a href="https://www.nngroup.com/articles/leading-questions/">Avoid Leading Questions to Get Better Insights from Participants</a></p><p><a href="https://www.interaction-design.org/literature/article/how-to-do-a-thematic-analysis-of-user-interviews">How to do a thematic analysis of user interviews</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f25ef1b460d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>