<?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 Omid Fakourfar on Medium]]></title>
        <description><![CDATA[Stories by Omid Fakourfar on Medium]]></description>
        <link>https://medium.com/@notesbyomid?source=rss-59be12d8002b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XNOzJ2qdoMWltSJ1YaPLNA.jpeg</url>
            <title>Stories by Omid Fakourfar on Medium</title>
            <link>https://medium.com/@notesbyomid?source=rss-59be12d8002b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:01:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@notesbyomid/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[Learnings from a visit to the mall: Nurturing Curiosity in User Research]]></title>
            <link>https://medium.com/curated-by-versett/learnings-from-a-visit-to-the-mall-nurturing-curiosity-in-user-research-e06364e38c73?source=rss-59be12d8002b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e06364e38c73</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Omid Fakourfar]]></dc:creator>
            <pubDate>Thu, 26 Nov 2020 17:41:59 GMT</pubDate>
            <atom:updated>2020-11-26T17:41:59.257Z</atom:updated>
            <content:encoded><![CDATA[<h3>Learnings from a visit to the mall: Nurturing curiosity in User Research</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K9oQilclAVGTb9Xj08WdFQ.jpeg" /><figcaption>Busy shoppers wander through a crowded mall (Photo by <a href="https://unsplash.com/@almapapi?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Krisztina Papp</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>)</figcaption></figure><p>Last month, I went to Calgary’s largest shopping mall for the first time since the Covid-19 pandemic hit to purchase gifts for a friend. Chinook Centre is a massive mall with multiple entrances including some through retail stores. Habitually, I chose an entrance through the Gap to enter the mall. As soon as I walked in, I noticed a gentleman wearing a mask and a headset similar to ones worn by FBI agents. He whispered: “32”. I walked through the store and straight into the mall. On the other side of the store, there was a lady with a similar outfit next to the exit. I walked past her and she whispered “31”.</p><p>We are often told as user researchers that good research starts with a solid research plan and hypotheses to validate. These plans typically start with a list of research questions; a list of behaviours that we’ll try to identify and observe. As we meet with stakeholders, product managers, designers, and clients, we narrow down what to look for in our studies. In some ways, we are deciding what we want to see before seeing anything!</p><p>Let’s go back to the mall. It took me a few minutes to realize they were keeping track of the number of customers in the store to ensure proper physical distancing. I immediately thought, couldn’t they somehow automate this? I didn’t walk into the Chinook mall to identify opportunities, nor did I go to the mall to study how businesses maintain physical distancing in their stores. But over the past few weeks, I became curious and started to notice how people have altered their lifestyle to fit the new state of the world.</p><p>I am not suggesting research planning is unnecessary or focused tactical user research is ineffective, but I believe humans live in contexts, not in isolated, controlled environments. Thus, it is crucial to try and fit non-intrusive user research methods like field visits into our toolkit more often. It is important to develop the courage to get out of our (home) offices and observe people where they are with pure curiosity. It is possible that these visits and observations do not immediately appear in reports as action items, but the value this contextual awareness brings is immense.</p><h3>Why is it important?</h3><p>Digital products are almost never used in isolation. Think of the last time you had to book a vacation on Expedia. Chances are you were checking your family’s calendars, communicating with the people who would travel with you to coordinate plans, replying to a friend’s text message while some Netflix show was being played and you were booking the vacation. It is very difficult to replicate such scenarios in user research. Focusing solely on tactical research questions can make us blind to other contextual data.</p><p>This problem is even more critical when working on projects in new industries, with new customer segments, cultures, or geographic locations. It is easy and convenient to generalize our own viewpoint of the world to the new product world and dive right into tactical questions like: how should the brand look? What colours should we use? What should the copywriting look like? How should we design the best checkout experience?</p><p>But that is the wrong approach. Curiosity should come first. There is so much to learn from people’s environments, the context that they live in, and how ordinary things happen in their lives, before getting fixated on product questions. We should get out of our labs more often, go where users are, and observe first hand how they carry out their most routine tasks.</p><h3>Collecting contextual information in organic situations</h3><p>To learn more about the full lives of individuals, we need to find ways to understand their context. Conducting contextual inquiry studies can be costly and time-consuming. However, there are still a few creative ways to capture valuable contextual information organically without breaking the bank.</p><p><strong>1. Watch people living their day-to-day life</strong>: This is an extremely powerful way of understanding people’s culture and behaviours when entering a new market. No matter what product or service you will launch in a new market, it is important to understand how people live their everyday lives. How do they get around their cities? What types of jobs do people have? How do people make daily transactions? What are people’s hobbies? How do people greet each other?</p><p><strong>2. Live the life of the customer</strong>: Living the life of a customer first-hand provides a great foundation for developing meaningful tactical research questions too. Imagine you are working on a project to build an e-commerce platform for an appliance store. It is relatively simple to simulate a customer’s journey over a couple of days.</p><p>• How would you figure out what type/brand of appliances you will need<br>• How would you conduct research to narrow down your options?<br>• How would you make sure your favourite appliances fit in your space<br>• Where would you go to see the appliances? Why?<br>• What questions would you ask the salesperson?<br>• What would happen next?</p><p>As a researcher, you should actually go over these steps and take note of your pain points and unique experiences. That allows you to develop deeper empathy with the target group and identify the specific pieces of their journey that need more exploration or optimization.</p><p><strong>3. Job shadows:</strong> Modernizing an old-school service requires understanding how people’s problem is being solved today, even without technology. If you are building an all-digital insurance provider, you first need to understand how traditional insurance agents and brokers work. This includes how they communicate with customers, how their office is set up, what workarounds they use to overcome daily challenges and more. Coordinating with an insurance agent to simply sit alongside them for a few days and shadow their job provides valuable contextual insights into how their business and the industry as a whole work.</p><p><strong>4. YouTube:</strong> The Covid-19 pandemic caused a few of my travel plans to get cancelled. However, during this time I was amused by the massive breadth of content on Youtube, from people who simply walk or drive in the cities around the globe. While the experience is never the same as being there in-person, these videos provide a fairly accurate presentation of how life looks like in different places. Just tune in to<a href="https://www.youtube.com/watch?v=z1obnaqPgMA"> this video of a person driving in the streets of Tokyo</a> and see how there are dedicated lanes for Mario Karts in the city. This is a fun, free and eye-opening experience!</p><h3>Final thoughts</h3><p>In its early stages, research is often about discovery which requires an open mind. Understanding a user’s context can lead you down unexpected, but valuable paths. The new state of the world, no matter how long it lasts, not only presents an opportunity to simply observe how people carry out seemingly trivial tasks under extreme conditions, but also is a great chance to nurture our curiosity and rethink our standard research processes.</p><p>✌️ <a href="http://versett.com/">Versett</a> is a modern consulting firm helping businesses navigate the changing competitive landscape. Every month, millions of people use the platforms, apps, and tools we have built. Versett works globally and is headquartered in Calgary and Toronto. If you like this post, you’d love working with us! See where you’d fit in at <a href="https://versett.com/">versett.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e06364e38c73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/curated-by-versett/learnings-from-a-visit-to-the-mall-nurturing-curiosity-in-user-research-e06364e38c73">Learnings from a visit to the mall: Nurturing Curiosity in User Research</a> was originally published in <a href="https://medium.com/curated-by-versett">versett</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Product Thinking Organization]]></title>
            <link>https://medium.com/curated-by-versett/product-thinking-at-versett-9312261a3828?source=rss-59be12d8002b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9312261a3828</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-thinking]]></category>
            <dc:creator><![CDATA[Omid Fakourfar]]></dc:creator>
            <pubDate>Mon, 22 Apr 2019 19:52:56 GMT</pubDate>
            <atom:updated>2019-04-22T20:33:30.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVN_gBrNZehktFaeQK-V4Q.jpeg" /></figure><p>At Versett, our team is built on the philosophy of “Learn Better, Faster”. As part of our continuous effort to enhance how we work on projects, one of the concepts that we have been developing is ‘Product Thinking’. This has become somewhat of a buzzword in tech. But there doesn’t seem to be a shared, global definition of what Product Thinking is, so we tried to clearly define what it means. I’ll go over our internal definition, the ways we have incorporated product thinking into our working model, and a few strategies for educating both internal and external teams on the value of it.</p><h3>What exactly is Product Thinking?</h3><p>Product thinking is an overarching term that we use to describe product-defining activities. This requires taking a multi-level view of a problem. You need to consider the holistic nature of products while consistently reminding yourself of the “Why?”. <br> <br>When deep into execution, it’s often challenging to remind ourselves why we are on our current path and whether we are still doing the right thing. So it is helpful to ask questions like:</p><ul><li>Is this decision going to make the product better for the user?</li><li>Do people <em>really</em> need this feature?</li><li>How will people find out about this product?</li><li>Why is this product better than what already exists?</li></ul><blockquote>Product thinking requires taking a multi-level view of a problem, and consistently reminding yourself of the “why”.</blockquote><h3><strong>Product Thinking is a team sport</strong></h3><p>It requires commitment, dedication, and involvement from all members of the team. Each team member should take full ownership of the product they are working on. At Versett, our team is organized into three high-level disciplines: Product, Design and Engineering. Product thinking impacts each of these disciplines in different ways.</p><ul><li>Product managers should think about what’s best for the product as a whole, not just the project.</li><li>Engineers should think about how they will measure the usage and success of each feature they develop.</li><li>Designers should think about how a user will find and interact with a feature they are designing.</li></ul><p>Particularly, we adopted a few strategies to build our product thinking muscles:</p><ul><li>We take a multidisciplinary approach to building products. We always try to incorporate thinking from other domains. We don’t always need to reinvent the wheel — the answers might already be out there.</li><li>We work iteratively and try to fix things based on feedback, data, and analytics. We constantly ask ourselves, “What’s an experiment that will move us in the right direction?”. We constantly measure our progress, either through analytics or user research, and then pivot our efforts based on findings.</li><li>We consider the business and user points of view simultaneously by having a strategic lens and considering both perspectives to answer: Why are we building this product? Are we solving the right problem? Are we solving it for the right people?</li></ul><h3><strong>It’s a journey, not a destination</strong></h3><p>Effectively implementing product thinking initiatives requires support, commitment, and a shared understanding with regards to its definition, benefits, and strategies. Listening to a presentation or reading this article will not make anyone a product thinker. At Versett, we encourage and empower our team members to just keep practicing. We constantly remind and challenge one another. We are all still learning and continuously improving, but we put together a few strategies that we have found helpful.</p><ul><li>We ran our entire team through an “Intro to Product Thinking” workshop, collected their feedback and incorporated them into our definition to make sure everybody across the board is on the same page when talking about product thinking.</li><li>We included this introduction in our onboarding resources for new hires.</li><li>In the future, we plan to include the same material in our client onboarding resources too, to help build a shared vocabulary and way of thinking.</li><li>We communicate and share knowledge regularly. The key to a successful product thinking initiative is being open about it across the organization. We talk about it during our weekly meetings and we share related resources with the broader team.</li></ul><p>Do you practice product thinking in your organization? Have you used any other strategies to integrate product thinking into your working model? We would love to have a conversation and learn more. Leave a comment below!</p><p>✌️ <a href="http://versett.com/">Versett</a> is a product design and engineering consultancy. If you like this post, you’d love working with us. See where you’d fit in at <a href="https://versett.com/">https://versett.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9312261a3828" width="1" height="1" alt=""><hr><p><a href="https://medium.com/curated-by-versett/product-thinking-at-versett-9312261a3828">Building a Product Thinking Organization</a> was originally published in <a href="https://medium.com/curated-by-versett">versett</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clients and UX Research: Love at First Sight]]></title>
            <link>https://medium.com/curated-by-versett/https-medium-com-curated-by-versett-clients-and-ux-research-love-at-first-sight-3e51e9641db7?source=rss-59be12d8002b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e51e9641db7</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Omid Fakourfar]]></dc:creator>
            <pubDate>Fri, 06 Apr 2018 17:20:43 GMT</pubDate>
            <atom:updated>2018-04-06T17:20:43.401Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QWahUAzeIcuZW9hD7UYbXA.jpeg" /><figcaption>Image Description: Two heart-shaped balloons on a pink background. Image Credit: Photo by <a href="https://unsplash.com/photos/1GRvY9WUu08?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Akshar Dave</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>At Versett, we strive to evolve our UX Research practice everyday. It’s still a fairly new addition to our tool belt but we’ve already experienced successes, along with our share of challenges and roadblocks. We have employed a number of research methods across different projects including both in-person and remote methodologies. We’re still learning while trying to better integrate UX Research into our processes, particularly how to involve stakeholders in usability testing sessions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FkQOxxwjjuTB7O%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FkQOxxwjjuTB7O%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FkQOxxwjjuTB7O%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="241" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c37ae6531b7f45c1db7e61cb224b621/href">https://medium.com/media/0c37ae6531b7f45c1db7e61cb224b621/href</a></iframe><p>As ideal as it sounds, it’s actually quite challenging to involve stakeholders in testing sessions, especially within our own industry (client based design agencies) for a few different reasons:</p><ul><li>Our clients are from all around the world. From Vancouver to Toronto, New York City to Paris. This means that someone, either the client or the researcher, would have to travel every week if they’d like to observe ideal, iterative usability testing sessions. Proposing this to clients who might already be hesitant about user research can be a really tall order.</li><li>In-person observation takes time. Just take into account the number of hours that the client would have to commute back and forth from their office to your testing lab. Inevitably, there are always no-shows in each round of testing as well. Needless to say, those hours add up pretty quickly, too.</li><li>Although we always produce video highlights for all our usability studies to try and engage the stakeholders as much as possible, we can never really know if they will take the time to watch the videos.</li><li>Finally, it is not only about external stakeholders’ involvement, but also that of the internal team. Oftentimes, especially in fast-paced projects, researchers need to sell UX research and testing both externally AND internally to the design team. Because, let’s face it, more research means more work for the designers, so you will have to prove the value of research to the designers, too.</li></ul><p>That’s why we started running live, moderated remote usability studies for one of our New York City-based clients in the travel industry. That is, instead of running the tests in person or on online platforms (e.g. usertesting.com), we ran them in real-time via a video conferencing app and asked all the stakeholders to join the call as well.</p><p>Since the audience for our target platform was very niche, we asked our client team to recruit the right participants while making sure that none of them had any previous experience working with the tool before. They were all potential buyers of the tool, however, which made their feedback even more valuable.</p><h3>Ask for an opportunity, and seize it</h3><p>Does this (involving stakeholders in usability studies) still sound super idealistic? Initially, it did to us as well. While it seemed like something that we came across in user research articles and wondered, “How would that even be possible within the agency world?” we discovered that it <strong>is</strong> possible. Here is how you might approach it:</p><p>Once you hear statements like <em>“We are not sure about how users will respond to this change”</em> from the client, that should<strong> </strong>light up the “usability testing” bulb in your mind. This is an opportunity to steer the conversation towards usability testing and propose running at least a single round of study to figure out the pain points with your product. Make sure to mention that these studies will have a very quick turn-around time, will involve the stakeholders, and will gather unbiased feedback from the people who are ultimately going to use the product.</p><p>Basically, you are asking your client to give you a chance. Next, your job is to take this chance and get the client excited about research insights, and more importantly, improved product usability.</p><h3>A few housekeeping items</h3><p>Planning for a live remote test is pretty similar to any other remote or in-person study. The only difference is that the researcher needs to send the participant and all the stakeholders the proper link and credentials to the call (either on Skype or Zoom or any other platform) beforehand. We also recommend reminding them the day before.</p><p>During the session, you will send out your prototype links to the participants and ask them to share their screen and think out loud while they are going through the tasks. A few housekeeping items to note:</p><ul><li>Introduce everyone present on the call to the participant right off the bat so that they are not intimidated by the number of callers.</li><li>As always, make it clear to the user that you will be testing an early prototype, and any honest feedback is much appreciated and impactful. Mention that none of the callers have been involved in the design of the product, therefore the user doesn’t need to worry about hurting anyone’s feelings!</li><li>Ask your client to help you take notes if they aren’t already doing so. This will help them stay engaged (instead of muting the conversation and watching Youtube videos instead!).</li><li>Ask your client to be a “fly on the wall” during the test. However, make sure you give them enough time to ask any follow-up questions they might have, but <em>only after the study tasks are wrapped up</em>. They probably have better contextual knowledge about the area they are working on and might be able to actually transform your pure usability study into a contextual inquiry session.</li></ul><h3>Lather, Rinse, Repeat</h3><p>Test fast and often: it’s one of those cliché statements that you read in every user research book, but we actually managed to achieve that with live, moderated remote usability studies.</p><p>We followed our test sessions with quick, 15-minute debriefs involving the client, UX researcher and our product designers. During this conversation, we quickly went through all our notes, and identified the pain points and the action plan for the following days. Designers worked during the next few days to implement the feedback and present the new screens for review during our weekly call with the client.</p><p>Because of the super fast-paced nature of the studies, there is no need (and frankly no time) for extensive, 100-page reports. Instead, you can actually ask the client to help with writing the report by taking notes throughout the studies. As noted earlier, this also helps keep them more engaged with the study. All you have to do as a researcher is to gather people’s notes and points of view, eliminate the ones that may have been biased, and compile them into a more readable format. Easy, breezy.</p><p>Within three weeks, we were able to run three rounds of usability studies and iterate on our designs — something that I couldn’t imagine being possible within the agency world.</p><h3>The opportunity… seized!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-KsP6sJK2VJIzuP4y5pBg.jpeg" /><figcaption>Image Description: Low angle view of confetti against sky. Image Credit: Getty Images.</figcaption></figure><p>Perhaps the greatest benefit of involving the client isn’t actually about test findings or design tweaks — it’s about experiencing what a testing session looks like. Moreover, clients generally appreciate when the study plan is kept short and focused. Despite running our tests on a very small piece of the product, each session still took about an hour and already seemed to be tiring the participant and stakeholders. God knows how the session would have unfolded had we wanted to tackle the whole product and ask all of our clients’ questions in one go.</p><p>Versett is based out of Calgary, New York and Toronto, our client was based out of New York, and the participant was from Amsterdam. To accommodate our participants, the session was scheduled for a very early 5 AM MST (my time)! But I had to seize the chance, and it was worth sacrificing some sleep for it. The client was happy with the outcome and they even suggested integrating the same technique into other pieces of product:</p><blockquote><em>“As it relates to user study sessions, we would love to go off the success of our first run, and study the designs for the next project too!”</em></blockquote><p>Do you have experience involving clients in the UX Research process? I would love to hear from you!</p><p>✌️ <a href="http://versett.com/">Versett</a> is a product design and engineering studio. If you like this post, you’d love working with us. See where you’d fit in at <a href="https://versett.com/">https://versett.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e51e9641db7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/curated-by-versett/https-medium-com-curated-by-versett-clients-and-ux-research-love-at-first-sight-3e51e9641db7">Clients and UX Research: Love at First Sight</a> was originally published in <a href="https://medium.com/curated-by-versett">versett</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Testing Case Study: Reaper Pie for iOS ]]></title>
            <link>https://medium.com/curated-by-versett/reaper-pie-usability-case-study-7e1cb2f5d576?source=rss-59be12d8002b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e1cb2f5d576</guid>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[pizza]]></category>
            <dc:creator><![CDATA[Omid Fakourfar]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 17:47:35 GMT</pubDate>
            <atom:updated>2017-10-04T18:16:56.844Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mtGcNw5aS0WQ9Lthvm6gtA.png" /></figure><p>At Versett, we’re committed to building products that are interesting and different. As designers we strive to design intuitive digital products, but admittedly we know that “we are not our users”. Even after conducting user interviews, completing ethnographic research studies, and collecting survey responses to figure out what users want out of a product, there is often a wide gap between what people “say” and what they actually “do”. That’s why we have been working hard to integrate usability studies into the early stages of our process.</p><p>Reaper Pie is a pizza delivery app — but it’s not like your run-of-the-mill Domino’s or Papa John’s. Instead of forcing the user through a tedious, multi-step process of selecting from a plethora of crusts, sizes, sauces, and toppings, our friends at Reaper Pie have streamlined the experience. Reaper has funnelled the endless options down to 3 popular pizzas, with a single size, a single crust, and a fixed price. It sounded like a neat idea, so we partnered with them and our team went to work designing the visuals of the Reaper Pie iOS app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0dUGKG_1emqIIfO6FWodig.png" /><figcaption><em>There are actually more than 1 million unique ways to make a 2-topping pizza on Papa John’s Pizza website. Is that necessary… or even helpful? </em>The<em> </em><a href="https://www.amazon.ca/Paradox-Choice-Why-More-Less/dp/149151423X"><em>paradox of choice</em></a><em> says no. Sometimes “more is less”. Ironically, when faced with too many options, we often tend to stick with what we know and are less inclined to try new variations.</em></figcaption></figure><p>We first defined our user base for the app. We sat down with the Reaper Pie team and identified the following two groups of users as our target audience.</p><ol><li>Tech-savvy college kids and university students who need a bite as fast as possible while doing homework and cramming for their exams.<br><em>Note: I worked as a pizza delivery driver and can confirm this user group!</em></li><li>We also wanted to make sure we were not limiting our user base too much, so we considered older adults who want to satisfy their late night pizza cravings.</li></ol><p>Then, our design team started putting together the visuals of the app in Sketch. Based on our target groups, we included some unique features in the app that would set us apart from other pizza joints.</p><ul><li>All pizzas are the same size and same price so that users can order their pizza fast, without having to go through the hassle of culling endless options.</li><li>There are only a limited number of pizza types: all standard varieties and users already know what to expect when they order them. Reaper will only have Cheese, Pepperoni, and Hawaiian pizzas along with a “Surprise” pizza option.</li><li>There are no hidden fees (e.g., taxes, delivery, etc.). If you order two pizzas, you will pay 30 bucks. Not a penny more.</li><li>Why not make it a nostalgic experience? Users can play an arcade game within the app while waiting for their order.</li></ul><p>The designs were then handed-off to Reaper Pie’s developer and the first working prototype was born. We then ran it on TestFlight and conducted our first round of usability studies to get some feedback from users “in the wild”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*TMRnM6zZ8PCkx8WpxPcKQg.gif" /></figure><h3>Usability Study</h3><p>It’s important to explicitly define research questions before getting started with usability studies. Research questions help us focus our attention to specific aspects of the product that we need feedback on. Generally, we don’t want to get into too much detail when it comes to usability studies. We also need to make sure we focus on the prototype itself and avoid overgeneralizing the observations. Thus, we identified the following two research questions for this round:</p><ul><li>The general idea behind the app is a fairly novel concept. How do people react to the idea of quick ordering and delivery with limited options? We will address this question based on qualitative data from general user comments while working with the app.</li><li>How do people go about adding pizzas to the order and checking out? We were interested in identifying the potential pain points by taking note of user comments during the checkout process.</li></ul><h4>Methodologies</h4><p>To address our research questions and recruit the right participants for our studies, we decided to run the studies in two different settings.</p><p>We used <a href="http://usertesting.com/">usertesting.com</a> as a platform to run remote usability studies on the older adult audience, and we went in the field (in this case, the University of Calgary campus) and ran studies with university students.</p><ul><li><em>Remote Testing: </em>Scheduling participants for in-person usability sessions is often challenging and time consuming, and there is always the possibility of no-shows. However, being able to hear a user’s thought process and verbal feedback is a critical piece of data gathering in research studies. Fortunately, <a href="http://usertesting.com/">usertesting.com</a> handles recruitment and execution of studies in a very short amount of time and even allows researchers to recruit specific groups of users. We used this platform to recruit 5 users aged 40+ from Canada and ran our usability study sessions remotely.</li><li><em>In-the-field Testing: </em>There is no place better than a university campus library to interview students about a product that is going to be built with them in mind, especially if it’s on the first day back at school. As a proud University of Calgary alumni, I went back to the Taylor Family Digital Library at the University of Calgary and asked 6 students to help test our app.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DjIRBl4MJWkphcsHXBiZig.jpeg" /><figcaption>Taylor Family Digital Library at University of Calgary where we ran our in-the-field testing sessions.</figcaption></figure><h4>Findings</h4><p>In both studies, most users said they liked the “visuals”, “graphics”, “vibe” and “fonts and colours”. One senior user said it was the “most unusual looking app I have ever seen” (in a good way!).</p><p>Students spent far less time in the app than their more mature counterparts. This could be an effect of the remote tests however, where people are generally more tempted to explore the app since nobody is “watching” them. Conversely, the students really wanted to finish the tasks as quickly as possible.</p><p><strong>Context of Use</strong></p><p>All of the students mentioned that they usually order pizza when they are in a group and not when they are by themselves. This has an impact on how they see themselves using some of the app features (listed below).</p><p><strong>Pizza Size</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n_r6sEmgzb3DkfILHGxQIw.png" /><figcaption>There was no indication of pizza sizes in the original design.</figcaption></figure><p>Many users had a hard time figuring out how big the pizzas were and how many people an individual pizza could feed. Based on the $15 price tag, they guessed that the pizzas were pretty big and could probably feed 2 adults. Students, in particular said they usually order pizza to share with friends. This proved to be consistent with the results from the remote test, where users found it important to know how big the pizzas were. There was a wide variation on the number of pizzas users ordered for a group of 8 people (2, 3, 4, 5, 8).</p><p><strong>Checkout Process</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ynVOIvV--RzCSWQEXE5NRQ.png" /></figure><p>One very common problem was that when users entered information like their credit card, address, etc. and then needed to go “back” to the main order screen, they seemed worried that they might lose their information (“Does that save it? I wanna go back, will the address still be there?”).</p><p>There was also no indication of missing fields when users forgot to enter required information. These lack of error states caused some frustration as users had to visually search for the reason why the “Place Order” CTA was not activated.</p><p><strong>Surprise Pizza</strong></p><p>Quite unexpectedly, the surprise pizza didn’t have the “wow factor” for students. In fact, most of the comments were negative regarding the feature.</p><p>One user emphasized on ordering pizza for group gatherings. She would order pizza for her parties and ask for everyones preference before ordering, so there would be no point for her to order a “surprise” pizza.</p><p>Another user thought the surprise pizza, “is to compensate for a lack of pizza options”. He mentioned that as a first time user, he might get a surprise pizza but as a regular customer, he couldn’t see himself ordering it often.</p><p>Another user was also adamantly against the surprise pizza because she didn’t know what to expect from it. If it’s a random pizza out of the three existing types, she didn’t want to run the risk of getting Hawaiian because, “nobody likes Hawaiian!”. She was also nervous she might get a totally random pizza not listed in the 3 original options, “what if I get a pizza with anchovies?!? Ewww!”</p><p><strong>Arcade Game</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9bNtWwwVsnsJRSyIs0vNpw.png" /></figure><p>Much like the surprise pizza, the in-app game also fell short in providing the intended moment of delight for most of the students. One user commented:</p><blockquote>Because I usually order pizza for our group gatherings, I wouldn’t play while my friends are there.</blockquote><p>Another user mentioned that he doesn’t have anything against the game, but that, “…it’s pointless. At a party, are you going to sit down and play by yourself?”.</p><p><strong>Copywriting Consistency</strong></p><p>There seemed to be some unfamiliarity in terms of referring to a pizza as a “pie”. One user even asked “does each pizza come with a pie?”. There was also some inconsistency in the app tutorial which used both “pizza” and “pie”.</p><h3>Implementing Feedback</h3><p>Based on the above findings, we put together an action plan to address some of the challenges that the users faced:</p><ul><li>Based on numerous comments, the most critical issue was that the price and size of pizzas needed to be more clear. To address this, we included both on the menu.</li><li>Changed “Surprise” pizza to “Mystery”, both to make sure that it is consistent with the tutorial instructions and hoping that it will be less confusing — no anchovy pizzas!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8f1YmhcqLJIhPJAT7nL4Qg.png" /></figure><ul><li>We also need to re-assure the user that closing the order panel isn’t going to cancel their order or delete their information. So we changed “Close” to “Save”.</li><li>Added “FREE” as a default for delivery that is persistent on the receipt to re-assure users that there are no hidden fees involved.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHU054NuZyfB2k0C3XphUA.png" /></figure><ul><li>To keep the copywriting consistent, we changed all instances of “Pie” in descriptions and the app tutorial to “Pizza”.</li><li>We made sure to highlight missing fields and provide error states within the checkout process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*esh8g50sNoz99z6vNQNU4A.png" /></figure><ul><li>We still need to figure out how we can incentivize the game. For example, the game could involve playing with the people who are also waiting for their pizza in close proximity to a users’ location.</li></ul><h3>Next Steps</h3><p>We are still working closely with the Reaper Pie team to further enhance the experience. Reaper will be launched soon in Edmonton, Canada. Follow them on <a href="https://www.instagram.com/reaperpie/">Instagram</a> to learn more about what they’ve got cooking! 🍕</p><p><em>Versett is a product design and engineering studio. If you like this post, you’d love working with us. Have a project? Let us know at </em><a href="http://versett.com/"><em>http://versett.com/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e1cb2f5d576" width="1" height="1" alt=""><hr><p><a href="https://medium.com/curated-by-versett/reaper-pie-usability-case-study-7e1cb2f5d576">Usability Testing Case Study: Reaper Pie for iOS 🍕</a> was originally published in <a href="https://medium.com/curated-by-versett">versett</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Travel Bots: Are we there yet?]]></title>
            <link>https://medium.com/curated-by-versett/travel-bots-are-we-there-yet-aa7f9073401a?source=rss-59be12d8002b------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa7f9073401a</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Omid Fakourfar]]></dc:creator>
            <pubDate>Tue, 08 Aug 2017 21:23:32 GMT</pubDate>
            <atom:updated>2017-08-08T21:23:32.839Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PLXbLY5N3WIszLqt79f7_w.jpeg" /></figure><p><em>Conversational user interfaces are becoming increasingly popular in travel, but do customers actually use them? In this report we explore the state of chatbots and their effects on mobile booking behaviour.</em></p><h4><a href="http://versett.com/chatbot">Download the complete 16-page whitepaper here</a></h4><h3>Booking travel on mobile devices</h3><p>Booking travel can be one of the most tedious tasks to execute on a smartphone. There are countless configuration options to choose from: hundreds of flights, hundreds of hotels, hundreds of car rental options, and so on. In the context of business travel, this problem gets even more serious.</p><p>There are additional factors for business travellers; Factors like corporate travel policies, whether a flight is refundable, and other restrictions. In addition to company specific constraints, some business travellers might also have their own personal preferences for travel: some might prefer window over aisle seats, or seek out specific hotels that offer loyalty program points.</p><p>Given the complex nature of booking travel online, integrating all possible options into mobile apps or mobile versions of websites hasn’t been overly successful. In a recent survey, we asked participants how they usually booked their travel. It was reported that 22 out of the 28 participants had used desktop versions of travel booking websites, while only 15 had used a mobile booking option.</p><p>The remaining bookings were completed via a travel agent, or other services. These results seem to indicate that people still prefer not to take the perceived risk of booking their travel via smartphones and prefer to use the desktop version of websites instead. Based on a <a href="https://ssl.gstatic.com/think/docs/the-new-multi-screen-world-study_research-studies.pdf">report</a> published by Google in 2012, 47 percent of users’ daily media interactions happen on handheld devices. However, planning trips was categorized as a “more complex” activity which is often initiated on a PC or laptop (more than any other type of activity).</p><h4>Chatbots to the rescue?</h4><p>The landscape has started to shift with the introduction of chatbots. Chatbots are applications that simulate having a conversation with another human. With chatbots, instead of going to a website and browsing options in different menus and filters, one can have a natural conversation with a robot to complete booking. The robot is powered by a set of rules, and is presented to the user via a familiar chat interface similar to text messaging. In a perfect world, the chatbots are so well-implemented that users are unable to distinguish a conversation with them from that with an actual human. A user specifies their preferences and limitations, and the bot will find the best match based on the presented constraints. Ideally, the user will not have to do any extra searching, or dig into numerous distracting options to find their perfect booking.</p><p>However, there is still a long way to go before travel bots have widespread adoption. In the aforementioned survey, only 1 out of 28 respondents reported using a travel bot to book a trip. That being said, since they are comparatively newer products, it is not perfectly clear if users prefer them over similar apps and websites. In addition, we still do not have a clear understanding of 1) how people interact with bots, 2) what they are looking for in travel bots and 3) the potential areas for improvement.</p><p>To answer these questions, we designed and ran a usability study to observe user behaviours while using chatbots, and compared user experience with bots to the mobile version of a travel booking website. In particular, we conducted this study with the following goals in mind:</p><ul><li>Conversational User Interfaces have become very trendy recently. We wanted to assess the effectiveness of these interfaces before digging deep into implementing them for commercial use.</li><li>We were interested in figuring out whether chatbots perform better than their counterparts (mobile versions of travel booking websites) in terms of 1) total time of booking process, 2) interaction pain points.</li><li>We were interested in observing how people interact with chatbots linguistically.</li><li>Finally, we wanted to figure out the conditions and scenarios in which one interface might perform better than the other. Ultimately, these observations can help us to come up with a set of design implications for future product development.</li></ul><h3>How we designed the study</h3><p>We designed a study where participants used two different interfaces to arrange travel bookings in different scenarios. To achieve a clear understanding of behaviours on different interfaces, we came up with 3 types of scenarios and tasks for this study:</p><ol><li>Booking a simple, round-trip flight on both interfaces as a warm-up task.</li><li>Booking a business trip with more restrictions on the flight options.</li><li>Booking a personal vacation consisting of a flight and a hotel booking.</li></ol><p>We arrived at this three-category schema of scenarios to mimic the types of possible bookings for an individual, while keeping in mind the restrictions within our interfaces.</p><p>We studied two types of interfaces: chatbots and mobile versions of travel booking websites. After careful consideration of numerous products, we picked “HelloGBye” iOS application as our target chatbot. <a href="https://www.hellogbye.ca/">HelloGBye</a> is an AI-controlled chatbot that allows users to book flights and hotels by means of a conversational interface. We chose this application primarily because it has no human involvement in the booking process and performs adequately in terms of understanding users’ queries. For the mobile website, we picked Air Canada’s website which offers the same options (booking flights and hotels). Participants interacted with both interfaces via an iPhone 7 mobile device.</p><p>We designed a within-subject study wherein each participant completed the tasks using both interfaces. All participants began by working through the first task on both interfaces as a training task. They then executed the second and third tasks either on the mobile website or the travel bot. The order in which they used the interfaces was counterbalanced using a 2x2 latin square across participants to eliminate the learning effect.</p><h3>Our participants</h3><p>We recruited eight participants (2 female, 6 male) through ads on social media and email lists. Participants’ age ranged from 20 to 37 (median: 31) and had different occupations including: Computer Science student, editor, arts and culture consultant, paramedic, electronics engineer, graphic designer and mechanical engineer. Five participants reported traveling six to ten times per year, while the other three reported traveling two to five times per year. Five participants had booked trips via handheld devices and four had used conversational interfaces before (all with the intent of initiating technical assistance, i.e. on internet providers’ websites).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7hYsa56mBtXzIynZu4qicQ.jpeg" /><figcaption>The usability study session setup. We recorded participants’ interactions with the interfaces via Mr. Tappy camera.</figcaption></figure><h3>Here’s what we found</h3><p>The purpose of this study was not to define a clear winner for travel booking scenarios. Rather, we tried to look at the pros and cons of chatbots, compare them with the mobile version of a website, and attempt to derive some design implications from our observations. Although there are existing design guidelines for conversational user interfaces (e.g., by <a href="https://conversational-ux.mybluemix.net/design/conversational-ux/">IBM</a>), we were interested in validating those guidelines (particularly within the context of travel chatbots) by running a usability study. Overall, we found that people normally <strong>do not</strong> trust chatbots, probably because of the poor experience they have had with chatbots in the past. However, there is great potential for further development of chatbots. In the following sections, we review some of the key findings from our usability study. Later, we will introduce some design implications and food for thought in terms of further development in this area.</p><ol><li><strong>People do not trust chatbots… yet.</strong></li></ol><p>The highlight of our study was the conclusion that people generally do not trust bots. They expressed this either explicitly in their post-study comments or indirectly while doing the tasks. The lack of trust is likely due to users’ previous experiences with other chatbots. Some reported having frustrating experiences with chatbots in the past, while others did not expect the bot to understand their queries at all. This was also reflected in the users’ moment of surprise when they could effectively communicate with the bot in some instances.</p><p>As an example, when participant 2 was asked about why he did not enter all the travel requirements into the conversational interface and instead chose to narrow down the results via the menus, he mentioned:</p><blockquote><em>“I thought it would overload the chatbot, speaking from previous experience. I don’t trust chatbots. I don’t trust their command of language. I try to keep it as plain and straightforward as possible.”</em></blockquote><p>In another instance, participant 4 wanted to book a business class flight for task 2. He was actually surprised that the bot understood his query:</p><blockquote><em>“I want business class” [entering query]… “And I’m not expecting it to understand me though”… [bot understands the query and returns business class results]… “Now I’m impressed!”.</em></blockquote><p><strong>2. Users are upfront with bots.</strong></p><p>All of the participants tried to enter all the required information, or all the information they expected the bot to understand, up front. As participant 4 pointed out:</p><blockquote>“<em>With interacting with the chatbots, I’m just gonna give them the information that I know they need to know right off the bat… Instead of doing this in multiple texts”.</em></blockquote><p>Then they filtered the search results via the menus and options in the following screens. In some instances, though, they were forced/prompted to go back and enter new queries. If the follow-up queries worked, they were surprised and impressed since it was an unexpected result. This point is illustrated in the following vignettes:</p><blockquote><em>“It’s nice that the bot has found an option to Vancouver and from Vancouver to Calgary. Not just my last request.”</em> — Participant 3.</blockquote><blockquote><em>“I think it was good that you didn’t have to restart every time. I think I managed twice to add more details and it fixed it so that worked. I didn’t think that would work but it did.</em>” — Participant 6.</blockquote><p><strong>3. Bots should respond in a more human-like and personalized tone.</strong></p><p>The HelloGBye chatbot is quite limited in responding with a personalized tone, thus failing <a href="https://conversational-ux.mybluemix.net/design/conversational-ux/">IBM’s</a> “Personality” design practice. While other chatbots are able to personalize their responses, either by calling the users’ name or providing personal suggestions, the HelloGBye bot only responds to queries with “OK. I’ve found these options”. It also does not clearly indicate errors or the queries it has not understood. Instead, it only returns results based on the last query it has understood.</p><p><strong>4. Bots are not faster than websites.</strong></p><p>Participants entered an average of 3 queries to accomplish each task using the travel bot (sd. 2.03, med. 2). However, as mentioned earlier, they did not enter follow up queries in any cases unless their initial query had failed, returned unexpected results, or they were prompted by the study coordinator to do so (i.e., they did not purposefully use queries to narrow down the search results).</p><p>On average, it took 499 seconds for the users to go through the first task (simple flight booking) via the travel bot and 198.875 seconds via the mobile website (60% faster).</p><p>Similarly, it took them 508.125 seconds on average to go through the second and third tasks (complicated flight and vacation bookings) via the travel bot, compared to 461.875 via the mobile website interface which is 10% faster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8eXFPO9Y5Ww0ggeZJyKfpA.png" /><figcaption>Distribution of completion times across the two interfaces. It generally took the participants longer to complete the tasks via the chatbot interface.</figcaption></figure><p>Finally, participants rated the possibility of them using a travel bot in future on a likert scale of 1 (not likely) to 5 (very likely) as 3.75 (sd. 0.88, med. 4) on average, which does encourage further research and development in this area.</p><h3><strong>Looking to the future</strong></h3><p>Our study provides some of the first findings on the effectiveness of travel chatbots compared to mobile websites. As discussed earlier, there are certainly shortcomings with current travel bots. Due to the general lack of trust towards chatbots, even newer and more effectively executed travel bots will likely have a hard time attracting users. However, new advancements in Machine Learning and Natural Language Processing techniques can help shape a brighter future for chatbots.</p><p>To summarize our findings and guide the design of future chatbots, especially for travel booking scenarios, we outlined a set of design implications based on the observations from our study. These are in line with existing efforts by <a href="https://conversational-ux.mybluemix.net/design/conversational-ux/">IBM</a> in compiling a set of design guidelines for conversational user interfaces.</p><p>It is worth noting that we were interested in observing user interaction with chatbots (while letting the users know in advance that that they were interacting with bots and not humans), the challenges users faced during the interaction, and the workarounds they came up with to finish tasks. Further studies may investigate usability of other chatbots, compare them with human powered conversational interfaces, or study them in other contexts.</p><p><strong>Using bots only to enter the initial query: </strong>Currently, in line with our findings, it appears that users generally use chatbots to enter all the information about their query up front. As a result, a conversational interface (either in form of text or speech) could possibly substitute or complement numerous form elements that are normally used as data input mechanisms. The transition from form elements to conversational interfaces will surely take some time, but we’ve already started to see some development with personal assistants such as Google Home, Apple Siri, and Amazon Echo.</p><p><strong>Conduct research on Machine Learning techniques and wait for the right time: </strong>While there is great potential for travel bots down the road, it looks like it is still not <em>the </em>time to launch a chatbot-only app. Users do not trust bots yet and there are still no well-defined, globally-accepted design guidelines for bots. This has resulted in each bot following its own path in designing interactions which can cause unexpected outcomes and frustration for users.</p><p>One thing that is clear, though, is that chatbots will become increasingly more intelligent and more able to effectively understand users’ queries. To achieve this, we suggest that designers, developers, and researchers put more emphasis on research in Machine Learning and Natural Language Processing techniques. As competition rises between well-designed chatbots, those without a completely intelligent back-end will undoubtedly struggle to survive.</p><p><strong>Personalize chatbots: </strong>One of the shortcomings of existing bots is that they often provide very generic responses to every user. This could lead users to believe that the bot is not personally responding to them, decreasing its legitimacy. To overcome this issue, we suggest that chatbots be designed in such a way that ensures:</p><ul><li>That they ask about user preferences beforehand or “learn” preferences (e.g., window or aisle seat preferences, dietary restrictions, etc.) via Machine Learning algorithms and apply this knowledge in future responses.</li><li>That they provide answers in a more personalized, human-like tone instead of generic responses.</li></ul><h3><a href="http://versett.com/chatbot">Download the complete 16-Page Research Report</a></h3><p>Versett is a product design and engineering studio in New York and Calgary, Canada. If you like this post, you’d love working with us. Say hi at <a href="http://versett.com/">http://versett.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa7f9073401a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/curated-by-versett/travel-bots-are-we-there-yet-aa7f9073401a">Travel Bots: Are we there yet?</a> was originally published in <a href="https://medium.com/curated-by-versett">versett</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>