<?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 Barnali Banerji on Medium]]></title>
        <description><![CDATA[Stories by Barnali Banerji on Medium]]></description>
        <link>https://medium.com/@barnali.banerji?source=rss-517219634e30------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tYiki4jfHLLl2sci</url>
            <title>Stories by Barnali Banerji on Medium</title>
            <link>https://medium.com/@barnali.banerji?source=rss-517219634e30------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:12:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@barnali.banerji/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[Betas can present opportunities to engage with the user and showcase UX impact]]></title>
            <link>https://medium.com/@barnali.banerji/betas-can-present-opportunities-to-engage-with-the-user-and-showcase-ux-impact-1e960bedf71e?source=rss-517219634e30------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e960bedf71e</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Barnali Banerji]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 12:47:12 GMT</pubDate>
            <atom:updated>2019-06-24T12:47:12.249Z</atom:updated>
            <content:encoded><![CDATA[<p>I recommend 3 best practices to do that</p><p>· do a phased beta</p><p>· Seek feedback from users</p><p>· create an on-demand dashboard connecting product and user experience</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*3mzBWhOMSsxbRhAH-rK9XA.png" /></figure><p>Historically, user feedback incorporation ceases long before the beta test begins. Beta tests are primarily used to identify bugs. Also, most betas are a one-shot program — a two-week period after the roadmap for MVP/MLP is done.</p><p>I recommend that we<strong> keep on seeking feedback from users during beta testing</strong>: In lieu of talking to the user, some companies use analytics to track user behaviour around key design elements or moments of truth. That’s where it stops. That approach doesn’t help us understand the ‘why’ or user perceptions or emotions. To learn more about the ‘why’, engage with beta testers through surveys and call backs to chat with them about their experience.</p><p>I also recommend, spreading your beta budget out and doing the test in phases. So, do a beta, but <strong>make it iterative with frequent releases and updates built into the plan. </strong>This will help you to take action on the feedback you collect and immediately monitor for impact. Tangible improvements can be made long before we must ship to market/partners.</p><p>Finally, and thirdly, <strong>take all this analytics data</strong> (product bugs, behavioural) <strong>and user data</strong> (demographics, context of test, perception) <strong>and pull it together in a single dashboard so everyone can make holistic connections </strong>about how the test is working. You will unleash a culture of collaborative problem solving among your stakeholders and team.</p><p>A <strong>tangible benefit of this approach</strong> <strong>for UX practitioners</strong> <strong>is, the ability to build a business case to justify UX resource deployment</strong> through tracking improvements in perception and behaviour in iterative tests. If you engage with your users as they try out your product, you can easily show the link between low faith in the product vision/value proposition and a user not finding UI landmarks/experiencing the moments of truth as intended. This allows you to build a business case for UX refresh and move towards a better experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e960bedf71e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to ‘know your customer’]]></title>
            <link>https://medium.com/mcafee-design/how-to-know-your-customer-15a8e38588ee?source=rss-517219634e30------2</link>
            <guid isPermaLink="false">https://medium.com/p/15a8e38588ee</guid>
            <category><![CDATA[customer-centric]]></category>
            <category><![CDATA[customer-stories]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Barnali Banerji]]></dc:creator>
            <pubDate>Wed, 15 May 2019 20:13:31 GMT</pubDate>
            <atom:updated>2019-05-15T20:13:31.731Z</atom:updated>
            <content:encoded><![CDATA[<h4>5 tips on uncovering the ‘whys’ behind customer behavior</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*6_FChIStB3jgaiYsWVdKNQ.png" /></figure><p>There’s a magic mantra circulating through boardrooms, whiteboards, and laptops alike:</p><p><strong>‘know your customer’</strong></p><p>This is the first step towards building product features that create relevant experiences, increase revenue, and reduce churn.</p><p><strong>But how do we put this mantra into practice?</strong></p><p>To know your customer, you need to first understand 2 things…</p><ol><li>How your customer behaves</li><li>Why your customer behaves that way</li></ol><p>You can learn about customer behavior through analytics. <em>But to understand why your customer behaves that way, you must talk to your customer.</em></p><p>It’s never easy talking to a stranger. The ‘why’ questions can be the hardest to answer. So, here are some tips to help you uncover the ‘whys’ behind customer behavior in a way that will benefit both you and your organization.</p><h3>Tip 1: Find a way to talk to people outside your organization</h3><p>Even if you have no budget, don’t resort to only talking with people inside your organization.<strong> </strong>People within your organization usually share a certain degree of group thinking, beliefs, product understanding, and world view. Instead, go to public places and engage people who have free time. This could be a grocery store checkout line, a shopping mall, or a food court.</p><h3>Tip 2: Don’t influence the customer</h3><p>Ask questions that are <em>open-ended and non-leading</em>. For example, if you ask someone how a product improves their life, you’re giving a cue that you’re only interested in learning about improvements–the good stuff. Instead, ask, “how are you using the product?”</p><h3>Tip 3: Let your questions emerge in response to what the customer says</h3><p>This is the most difficult part — getting a stranger to open up and share personal stories with you. The customer will have to think deeply and articulate their feelings. To get to this level of exchange, you need to have a real conversation. <em>You must truly listen. </em>Don’t ask a question and think about how you will respond. Don’t worry about what your next question should be. The trick is to <em>keep the larger objectives of the conversation in mind and simply listen.</em></p><h3>Tip 4: Make customers comfortable so they can speak freely</h3><p>Even if customers say things which you find puzzling or silly, be careful not to make the customer feel stupid or patronized. Question and probe all you want, <em>but please don’t judge.</em></p><h3>Tip 5: Align with your team to understand what customer behavior you want to learn about</h3><p>This could mean looking at the analytics data or (gasp!) asking someone on a cross-functional team.<em> </em>Without this step, you may still uncover interesting insights through a great customer chat, but your learnings likely won’t benefit your business goals.</p><h4>Use these tips to help uncover the ‘whys’ behind customer behavior in a way that truly benefits your organization.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15a8e38588ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mcafee-design/how-to-know-your-customer-15a8e38588ee">How to ‘know your customer’</a> was originally published in <a href="https://medium.com/mcafee-design">McAfee Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>