<?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 Shai Passal on Medium]]></title>
        <description><![CDATA[Stories by Shai Passal on Medium]]></description>
        <link>https://medium.com/@ShaiPassal?source=rss-1a8f2272b9ef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hE2ndQvPiOUeJ0morVGOlw.jpeg</url>
            <title>Stories by Shai Passal on Medium</title>
            <link>https://medium.com/@ShaiPassal?source=rss-1a8f2272b9ef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:22:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ShaiPassal/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[Talking to Your Product Users? This is the Mistake You Don’t Know You’re Making]]></title>
            <link>https://medium.com/tailor-brands/talking-to-your-product-users-this-is-the-mistake-you-dont-knowyou-re-making-dacf32f6d419?source=rss-1a8f2272b9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/dacf32f6d419</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Shai Passal]]></dc:creator>
            <pubDate>Thu, 21 Oct 2021 04:05:45 GMT</pubDate>
            <atom:updated>2021-10-21T11:51:24.075Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hint: It’s all about the language you’re using</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kMwr1XBVEYASwTKdni0FXw.png" /></figure><p>As a newcomer to the tech/start-up world, one of the first things I noticed was the unique language. I found myself Googling strange words my coworkers used as if they were the ABC’s.</p><p>As time went on, I got used to the terminology and started incorporating it into my everyday life — sometimes without realizing. Whether you’re a product manager, designer, UX professional, product marketer or researcher, I’m going to assume you’ve adopted a similar kind of terminology in your own niche.</p><p>If your role involves speaking with users, this matters in a big way. When talking to users, our goal is usually to gain a better understanding of their characteristics, experience with the product, and wants and needs — and we often make important decisions based on those understandings.</p><p>The problem is, terminology and its effect rarely come to mind when we have these conversations.</p><h3>The Problem With Jargon</h3><p>Every industry (not just tech) has its shared language, as people from the same organization or discipline need an effective way to communicate with each other.</p><p>Jargon and acronyms make communication concise, brief and to the point. Moreover, a shared language provides a sense of belonging, as you speak a language known only to group members.</p><p>That said, while tech-related terms and acronyms can be uniting and succinct for ‘insiders’, who rely on the same cultural references and context, it has the opposite impact on people outside the industry and culture.</p><p>And sometimes, out of habit or without being aware, we communicate the same way with people who don’t have the same context as we do — specifically with our users.</p><h4>Creating bias with language</h4><p>In order for you to get meaningful unbiased input, your users have to feel comfortable opening up and sharing. Using tech-related words, or any high level language that our users may not be familiar with,<strong> can both confuse them and be unclear, and create a sense of hierarchy, in which they are ‘less than’, small and inferior.</strong></p><p>This may unconsciously cause the users to hold back and not share some of their thoughts. After all, who wants to admit their weaknesses when already feeling vulnerable?</p><p><strong>If the feedback provided isn’t authentic, it may lead you in the wrong direction and negatively affect your research findings.</strong> Needless to say, the good experience you want to provide to your users will also be hampered.</p><p>It may sound extreme, but think about it from the users’ side of the table (or Zoom call nowadays):</p><p>Taking part in a user research session (whether an interview, a usability test or other methods) entails being in a vulnerable position.</p><p>First of all, as a user you aren’t in control of the conversation; you’re being asked unexpected questions.</p><p>Second of all, you are expected to admit difficulties that arise when using the product, misunderstandings, and insecurities. These difficulties may clash with your perception of yourself as smart and tech-savvy.</p><p>The users participating in our research efforts are probably nervous, and so we should be decreasing tension, but we accidentally make them feel inferior to us by using language they don’t understand. It’s our responsibility not to overlook this power dynamic.</p><p>For example, have you ever seen users struggling with your product in a usability test, and then when you ask them about it they say something like “I’m tech-savvy, so for me it’s super easy”? This may be because it’s hard for them to admit they struggled.</p><p>These implicit and subtle processes have great impact and therefore should be discussed and thought out when approaching user calls. You don’t want to find yourself making important decisions (or advocating for such) based on biased findings.</p><h3><strong>So What Can You Do About it?</strong></h3><p>In the absence of common ground, we can’t use shortcuts in communication. We have to explain what we are talking about. Here are 3 tips that have really helped me communicate effectively with our users:</p><h4><strong>1. Be genuine and admit when you don’t know the answer</strong></h4><p>You can’t just assume that everyone knows what you mean and share the same knowledge and preconceptions as you. Therefore, you have to make sure you are using words the same way as the user you are talking to, and establish a common vocabulary.</p><p>When you aren’t sure if a word or phrase is commonly used or how it is used, you can ask your user in a humble and curious manner. For example:</p><blockquote>“I’m not sure about the word I’m going to use, can you correct me and offer a better word?” “I’m not sure about this word x, do you know it?” ; or “What would you call this?”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nA9JiLkEKfISk6GeFGh6Cw.png" /></figure><p>This is a method I like to use and one that served me a lot as a psychologist working with clients from different backgrounds, especially with teenagers who have different vocabularies and different ways of using language.</p><p>Being honest and acknowledging what you don’t know is important, as it helps build trust, as well as making sure you are communicating clearly.</p><p>Another advantage of this method is that <strong>it helps you uncover the vocabulary that people use to describe their goals and tasks in your product.</strong> This could be helpful for your UX writing and product marketing efforts.</p><p>The more we understand our users’ way of communication, the more we can provide them a better experience within our product as well.</p><h4><strong>2. Reach out to a friend outside your organization</strong></h4><p>Sometimes, the technical jargon is so common within our day-to-day life that we forget to be critical when using it. For example, I’ve seen usability studies opened with, “Today, we are going to do a usability test” and the users seemed absolutely lost.</p><p>Yes, you should explain what is going to happen in the session, and this is the right professional term, but the person in front of you doesn’t know what that means.</p><p>Before hopping on a call with a user, write down some talking points or questions you’d like to ask. Try to point out words that are “higher” and replace them with a more basic term. To spot words that are jargon in your industry or company, run it by a friend that isn’t from the industry.</p><h4><strong>3. Don’t call them ‘users’ (when you’re talking to them)</strong></h4><p>I know I’ve already said “user” so many times in this post, but I would never say it when I’m talking to the user directly.</p><p>It’s important to use language the way the person you’re communicating with does. “User” may not be a unique or unknown word, but in this context it is jargon. The way tech companies use this word is different from other industries and from the way people refer to themselves.</p><p>In everyday language, the word “user” has negative connotations. As quoted in the Netflix documentary ‘The Social Dilemma’: “There are only two industries that call their customers ‘users’: illegal drugs and software.”</p><p>Moreover, it’s a dry, technical, and extremely impersonal way to refer to a person. So although this is the internal term you use, I suggest you refrain from using it externally.</p><p>Sometimes you do need a way to refer to the person in front of you in relation to the product or the group using the product. So how can you refer to the person you’re talking to instead? One option is ‘customer’ or ‘client’, as these are commonly used in this context.</p><p>Another option is using a descriptive word that is relevant to your market characteristics. For example, Tailor Brands provides a one-stop shop for people starting their own small business. So when I interview people using Tailor Brands, I use words like ‘entrepreneurs’ and ‘small business owners’. Try to listen for ways your audience refers to themselves, and incorporate that in the conversation instead.</p><h3>What’s the Takeaway?</h3><p>Although discussed very little within tech and research, terminology is something we should keep in mind and be critical about. After all, we don’t want language barriers to create a gap between us and our users, just as we don’t want to base our insights on biases.</p><p><em>How do you minimize language-related biases and barriers when you’re conducting product research? I’d love to hear new thoughts and opinions!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dacf32f6d419" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tailor-brands/talking-to-your-product-users-this-is-the-mistake-you-dont-knowyou-re-making-dacf32f6d419">Talking to Your Product Users? This is the Mistake You Don’t Know You’re Making</a> was originally published in <a href="https://medium.com/tailor-brands">Tailor Brands</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Things I Learned from a Diary Study Pilot Test]]></title>
            <link>https://medium.com/tailor-brands/3-things-i-learned-from-a-diary-study-pilot-test-6373d2dffd27?source=rss-1a8f2272b9ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/6373d2dffd27</guid>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[diary-study]]></category>
            <dc:creator><![CDATA[Shai Passal]]></dc:creator>
            <pubDate>Sun, 07 Feb 2021 17:57:23 GMT</pubDate>
            <atom:updated>2021-02-07T17:57:23.730Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 Things I Learned From a Diary Study Pilot Test</h3><h4>Practical ways to gather richer data from the get-go</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*-abUL3d_2cqs4uRShowLaw.png" /></figure><p>As a user researcher at Tailor Brands, I am always looking for ways to better understand who our customers are — what their day-to-day lives are like, why they do the things they do, what motivates them and frustrates them.</p><p>Using generative interviews to achieve this goal has only gotten me so far; mainly, because there seems to be a large gap between participants’ recollection of past experiences, and their actual behaviors in the moment.</p><p>Since I’ve been exploring a process that happens over time (setting up a business), it’s been hard for them to recall specific goals and problems, or elaborate on things that happened — leaving me under the impression that I’m missing out on many relevant issues.</p><p>I was in need of a better suited generative methodology, in order to gain deeper insights into their experience and discover the subtle aspects underlying decision-making. Specifically, my goal was to get a glimpse into users’ lives and natural context, in real time, from remote.</p><p>This is where the diary study came in.</p><h3><strong>Try. Fail. Repeat.</strong></h3><p>In a nutshell, a diary study is a qualitative research methodology, in which participants self-report their day-to-day experiences and activities, over a period of time.</p><p>Sounds like a great fit, right? But even after doing a lot of reading and learning, applying a research method for the first time is intimidating.</p><p>The potential costs of ‘learning in process’ can feel high — especially when the method chosen requires a significant investment of time and money — and you may find yourself spending too much time strategizing the ‘perfect’ approach, without taking the first step.</p><p>Motivated by one of my team’s core values: “Try. Fail. Repeat,” I decided to stop waiting for perfect conditions and just start.</p><p>And so, a pilot study was launched. A pilot study is a unique opportunity to dip your finger in the water and spot problems that may arise before scaling.</p><h4><strong>DIY diaries</strong></h4><p>Choosing a research method: Check.</p><p>Next up: Choosing a tool to capture the diary entries and communicate with participants.</p><p>From classic notebooks to dedicated digital platforms, there are plenty of options to choose from, and this choice should be guided by your goals, budget and participants.</p><p>This pilot study was approached DIY-style, without any dedicated tools. Rather, I chose email and text messages to communicate and collect data.</p><p>Considering participants are already familiar and comfortable with these commonly-used services, the data gathering can fit easily into their routine (increasing the likelihood they stay actively engaged in the study). Emails and texts are also cost-effective and well-suited for smaller budgets.</p><p>The secret sauce of digital diary studies is the ability to moderate simultaneously; after all, the diary entries are received immediately and wait at your fingertips. This allows you to continuously identify and react to issues, eventually leading to higher value logs.</p><h3><strong>3 Ways to Get High-Value Diary Entries</strong></h3><p>Here are my 3 practical takeaways on how to use this secret sauce to facilitate high-value diary entries:</p><h4><strong>1. Take an active role in maintaining motivation</strong></h4><p>Participants’ enthusiasm and motivation tend to diminish over time, as life gets in the way. As we want to maintain high levels of engagement throughout the study, it’s important to help the participants stay in the game by enhancing their motivation.</p><p>How?</p><p><strong>Emotional aspect</strong> — Since participants are putting in the time and effort to document their experiences, a polite ‘thank you’ isn’t enough here. Show your participant you notice and value their work by reading through it (even partially and quickly) and responding accordingly.</p><p>Did your participant share a frustrating situation? An accomplishment? Show genuine interest and caring.</p><p>This is also a great chance to ask relevant follow-up questions and send nudges if needed. Yes, this takes time, but don’t underestimate the power of human connection. Having someone that notices and acknowledges their input will increase participants’ motivation to keep going.</p><p>Being a one-woman team, I provided my personal email and WhatsApp number so I could be reached directly. For bigger teams, I would recommend choosing a specific contact person per participant, to enable that sense of connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*quOQDjrizJqDbFamxvf5gA.png" /></figure><p><strong>Financial aspect </strong>— Optimize the influence of the incentive by dividing it over time. Offer an incentive per diary entry sent or task completed, and explain this to participants from the get-go.</p><p>In my case, I offered $X per entry and an extra $Y for participating in a follow-up interview.</p><h4><strong>2. Strengthen the journaling muscle</strong></h4><p>Unfortunately, not every submitted entry is a good one. Documenting doesn’t always come naturally, even to enthusiastic participants.</p><p>I found myself receiving entries that only entailed a simple description of events and tended to be quite superficial. For example, as a soon-to-be business owner described:</p><blockquote>“My family suggested I set higher prices for my services, so I did.”</blockquote><p>Such descriptions are important, but they’re only one piece of the puzzle we aim to assemble. To collect more pieces, like underlying needs, goals and motivations, we need participants to provide rich, reflective data.</p><p>As the moderator, you can prompt reflective thinking and writing to help participants better analyze and document the situation. Provide the participants with clear questions they can use to respond to different aspects of their experience.</p><p>For example, I used 3 simple questions inspired by CBT key elements, often referred to as the CBT triangle (Beck, 2011):</p><ol><li>What did you <strong>feel</strong>?</li><li>What did you <strong>think</strong>?</li><li>What did you <strong>do</strong>?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IOi1Kr6XYviFfSwVE4RRSw.png" /></figure><p>Following these prompts, the participant reported:</p><blockquote>“I felt happy that my family believed in me, but I also felt like an imposter. I thought that it’s important to show I believe in my service, even though I’m just starting out, but I also wanted to keep the prices attractive so people would go for someone with less experience. I chose to make the prices only a little higher for now.”</blockquote><p>Adding these answers to the logs floated the ‘why’ underlying the actions, and led to higher quality of data.</p><h4><strong>3. The more (recording methods) the better</strong></h4><p>Research participants often try to please or help by focusing on what they think we are interested in, and omitting ‘boring’ or ‘irrelevant’ details.</p><p>This may not be deliberate, but it can greatly affect the data collected and respective conclusions. After all, in a generative research, we aim to explore users’ lives beyond the scope of our specific product. We have to make sure that both we and our participants don’t narrow down the problem-space explored by getting stuck focusing on the product.</p><p>Throughout the pilot study, the written diary entries seemed ‘self-edited’ and polished. They were also quite short. This may have been due to an effort to send out impressive, well-worded logs, but resulted in a non-optimal and skewed outcome.</p><p>A great way to overcome this issue is by encouraging participants to document data through different media types — not only through writing but also via video and voice recordings.</p><p>In these formats, there is a tendency to think out loud freely, and thus the data is more natural and raw. This leaves the ‘picking and choosing’ to us in the data-processing stage.</p><p>Moreover, reassure participants that no detail is too small or too boring. Instead of keeping them guessing, let them know that it’s expected of them to avoid editing their entries or sticking to your product’s perceived scope.</p><h3><strong>Summing Up</strong></h3><p>Here are my two cents. No matter how you choose to approach the diary study, make sure that your process involves helping your participants provide rich and meaningful data.</p><p>Trying, failing, iterating and repeating is a crucial part of the learning process, especially in a relatively new and quickly-evolving field like user research. It’s not about getting every method perfect from the get-go, it’s about being curious and excited to learn.</p><p><em>Which method is next on your to-do list? Is anything stopping you? Share your thoughts in the comments!</em></p><p>References:</p><p>Beck, J. S. (2011). Cognitive Behaviour Therapy: Basics and Beyond (2nd ed.). New York: Guilford Press.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6373d2dffd27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tailor-brands/3-things-i-learned-from-a-diary-study-pilot-test-6373d2dffd27">3 Things I Learned from a Diary Study Pilot Test</a> was originally published in <a href="https://medium.com/tailor-brands">Tailor Brands</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>