<?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 Sofya Bourne on Medium]]></title>
        <description><![CDATA[Stories by Sofya Bourne on Medium]]></description>
        <link>https://medium.com/@sofyabourne?source=rss-bc0ccce22a4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*M4LoePLWfZdDmpQYhL3-nw.jpeg</url>
            <title>Stories by Sofya Bourne on Medium</title>
            <link>https://medium.com/@sofyabourne?source=rss-bc0ccce22a4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:33:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sofyabourne/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[The year of AI through a User Researcher’s eyes]]></title>
            <link>https://sofyabourne.medium.com/the-year-of-ai-through-a-user-researchers-eyes-c77eb682d9d4?source=rss-bc0ccce22a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c77eb682d9d4</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[articial-intelligence]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sofya Bourne]]></dc:creator>
            <pubDate>Sat, 30 Dec 2023 02:17:26 GMT</pubDate>
            <atom:updated>2024-01-08T16:21:24.577Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DjBrRLwqR6v6I1wv" /><figcaption>Photo by <a href="https://unsplash.com/@and_machines?utm_source=medium&amp;utm_medium=referral">and machines</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It was early March, and I was sitting by a rooftop pool in Santiago, Chile, showing my husband ChatGPT for the first time. I’d been hearing about it for a few months, but it was around that time that my social feeds suddenly became overrun with thought leaders peddling the latest prompt hacks and telling me I was already using ChatGPT “wrong”. I created an account and was instantly hooked.</p><p>Fast forward nine months, and every tech meetup I go to in New York nowadays is chock-full of AI VCs and AI entrepreneurs. There’s been an explosion of AI startups, and even my least tech-savvy relatives have played with ChatGPT or Bard by now.</p><p>2023 has truly been the year of AI. Or, perhaps, the <em>first</em> year of AI is a more appropriate way to describe it — the cat’s out of the bag, there’s no going back.</p><p>I’ve been fascinated by this awesome tech both as a user and as a UX professional, so I thought it would be fun to pull together some thoughts and observations on generative AI as a year-end post.</p><p>It’s the end of December, I’m halfway through my two-week holiday, so I’m keeping this very light and loose with <strong><em>two highlights</em></strong>,<strong><em> two lowlights</em></strong> and <strong><em>two questions</em></strong> for 2024. Oh, and there’s <strong><em>a fun bonus</em></strong> right at the end: the most delightful AI user experience I came across this year. I hope it delights you, too!</p><p>Let’s start with some of the things I’ve loved about generative AI this year.</p><h3><strong>Highlight 1: It helped me conquer quantitative data</strong></h3><p>Earlier this year, I had to learn Looker and work with large volumes of quantitative data in Google Sheets for an analytics-heavy project I was working on. It was the first research project I led while having access to ChatGPT, and I quickly found that having an AI companion by my side as I mounted those steep learning curves significantly accelerated my progress.</p><p>With the help of ChatGPT, I was able to bypass hours of digging through Google and YouTube to understand how certain features in Looker work, brush up on statistics (grad school flashbacks! FUN!), and easily decipher some new business and finance jargon I was encountering in my research.</p><p>I also began to leverage ChatGPT to write Google Sheets formulas and custom Looker queries, something that’s now become habitual whenever I’m working with quantitative data.</p><p>Previously, I’d always struggled to reconcile my strong belief in the power of mixed methods with my limited ability to use mixed methods in my work, largely due to my qualitative research skills being more developed than my quantitative skills. ChatGPT helped me narrow this skills gap significantly this year and did so much quicker than I expected.</p><h3><strong>Highlight 2: It helped me sharpen and refine my thinking and communication</strong></h3><p>“Does this make sense?” is something I now ask AI on a regular basis. I also frequently use it to help me think through possible blind spots, assumptions and biases in my thinking.</p><p>As a researcher on a distributed team, I often miss the physical proximity of my team members to sense check my reasoning or understanding of a new topic and poke holes in my ideas in an ad hoc manner, on the fly.</p><p>This is also true for my personal life. I’ve spent most of 2023 travelling, which meant being away from my friends and community. Being able to brainstorm approaches to difficult conversations or sense-check my read on some interpersonal situations with a neutral third party has been extremely useful in this context.</p><p>I now regularly use AI tools like ChatGPT and Pi.ai as a cognitive checks and balances system of sorts. They don’t always get things right, and, of course, hallucinations and the fact that they’re not, you know, <em>human</em>, limit how much they can help in certain situations. But the fact remains: these tools have helped me think and communicate better this year.</p><p>There are also ways in which I wanted to use AI tools this year but couldn’t because the technology is just not quite there yet.</p><h3><strong>Lowlight 1: AI for user research is still pretty useless</strong></h3><p>The promise of AI as part of the user research practice is enormous and <strong><em>so</em></strong> <strong><em>exciting,</em></strong> but I’m yet to see it materialize in reality.</p><p>The research platform I use for my job rolled out AI features as early as June. I even joined their user research efforts as a participant ahead of the release because I <em>really</em> wanted their AI tooling to be good.</p><p>Sadly, despite much fanfare, the performance of these features has been disappointing. Even basic tasks like generating interview summaries or grouping coded data by meaningful themes are a tall order at the moment, with results often lacking any utility to my research process.</p><p>Not to mention that what I <em>really</em> want to use AI for as a user researcher isn’t interview summaries at all. The future I get excited about is when AI tools can be leveraged to augment user research in ways only a machine can do, like quickly trawling through vast amounts of customer data held across multiple siloed departments and tools to identify patterns and trends in customer needs that any one person would be unable to find.</p><p>I’m sure this will be a reality soon enough, but we’re not there yet, and that’s disappointing.</p><h3><strong>Lowlight 2: AI tools usability still has ways to go</strong></h3><p>Every AI tool I’ve tried this year has had a laundry list of usability quirks and pain points that need resolving.</p><p>To give just one example, I find it incredibly annoying that ChatGPT can’t remember what we talked about between conversations. And while it does save every chat in a side panel in chronological order unless told otherwise, it lacks a system for keeping track of these chats. Sure, I can name them, but am I really going to scroll through months of saved conversations to find the one I’m looking for? Is anyone?..</p><p>Pi.ai, on the other hand, won’t let me create separate conversations at all. So it <em>can</em> remember what we talked about days and weeks ago, but now <em>I</em> definitely don’t. Asking it to remind me of a vague idea or a random thought I mentioned to it some weeks ago is still, sadly, a bit of a hit-and-miss — sometimes, it does remember that specific part of our ongoing discussion; other times, it does not.</p><p>These are just two personal pet peeves that are top of mind for me as I write this post, but the reality is that the user experience of all AI tools is still in its infancy, especially if we consider the challenge of mass adoption. Sure, 100 million people use ChatGPT daily, but if AI tools are to live up to their potential, companies will need to figure out how to make them usable not just by early adopters and tech enthusiasts but by everyone, everywhere. How does the user experience of AI tools need to evolve for adoption to break the first billion users? What about to reach the next billion after that?</p><p>This brings me to two broader questions I’m looking forward to exploring more in the new year.</p><h3><strong>Question 1: How can we better align user expectations with AI capabilities?</strong></h3><p>I suspect that the frustration I feel when I want an AI tool to help me 10x my capabilities, but all it can produce is a half-coherent summary of an interview transcript is a manifestation of some fundamental AI UX design principle we’re yet to define.</p><p>I’ve actually seen this in my own work before. When I was leading user research for an AI-powered biometric experience, one sentiment I kept encountering in user interviews was the persistent expectation among participants that our tech was doing something way more sci-fi-y and futuristic than what it was actually doing.</p><p>What generative AI tools can do <strong><em>is</em></strong> incredible and <strong><em>is</em></strong> the closest we’ve come to the realm of sci-fi in real life. But their amazing abilities are also precisely why it’s so easy for users to imagine AI capabilities to be way more advanced and broad than they are at present. This mismatch between users’ expectations and the reality of AI capabilities can lead to user frustration, disengagement and mistrust of AI tools.</p><p>The concept of AI explainability is nothing new, but the more UX professionals get pulled in to work on AI-powered experiences, the more central I expect it to become to our work, given how critical it is to our ability to design experiences that feel safe, reliable and trustworthy <em>as well as</em> easy, quick and delightful.</p><h3><strong>Question 2: How will user-centered design evolve in the age of AI?</strong></h3><p>Since the early days of UX as a distinct area of software development, our purpose as designers and researchers has been to figure out how to enable humans to interact better with machines. But now the machines themselves are changing. Suddenly, they can speak our language — <em>all</em> of our languages, in fact — in an increasingly naturalistic way. We can now talk to computers much like we talk to other humans, without resorting to predetermined commands or buttons. What’s more, each human-AI interaction is hyper-personalized and unpredictable, resulting in a multitude of possible user journeys and experiences. How do we design for <em>that</em>?</p><p>This fundamental transformation of the very nature of the relationship between humans and machines is bound to lead to major shifts in user-centered design and research practices.</p><p>But this is no cause for panic. Instead, let’s get <em>curious</em>.</p><p>How can we expand our focus from guiding users’ interactions with machines to guiding machines to better interact with humans? How can we better understand and inform the design of AI models that will power the experiences we build? How can we help ensure that the new AI experiences are not just easy and delightful but also safe and trustworthy? How can we learn to work with new stakeholders in our organisations? How can we adapt our methods and practices to an entirely new set of possibilities and constraints inherent to AI-powered experiences? There’s so much to figure out for us as UX professionals!</p><p>I hope 2024 will be the year we start engaging with these questions in order to collectively set the right precedents for what user-centred design looks like in the age of AI.</p><p>This post is already long enough, but I wanted to share one utterly delightful AI experience I stumbled upon this year before I wrap up. I won’t go into describing it to you because I think everyone needs to experience it for themselves. All I’ll say is that no other AI experience I’ve tried this year has inspired me to envision the amazing possibilities of the future we’re all hurling towards more than this one.</p><p>Sounds intriguing? Here’s what you need to do to try it out for yourself:</p><ol><li>Download the Pi.ai app on your phone.</li><li>Start a chat — you’ll see a little phone button in the text input bar (an <em>interesting</em> choice for a mental model to leverage in the design of this particular feature, but that’s a topic for another time).</li><li>Press the phone button, and have fun!</li></ol><p>What have been your highs and lows of exploring generative AI tools this year, whether you’re in the UX field or not? Let me know in the comments below, or message me on LinkedIn to chat more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c77eb682d9d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to debug participant recruitment in B2B user research]]></title>
            <link>https://medium.com/researchops-community/how-to-debug-your-b2b-research-participant-recruitment-ac8be0eab0f2?source=rss-bc0ccce22a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac8be0eab0f2</guid>
            <category><![CDATA[b2b-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[participant-recruitment]]></category>
            <category><![CDATA[product-research]]></category>
            <category><![CDATA[market-research]]></category>
            <dc:creator><![CDATA[Sofya Bourne]]></dc:creator>
            <pubDate>Wed, 26 Jul 2023 18:25:46 GMT</pubDate>
            <atom:updated>2023-10-03T15:51:55.492Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*adjcOjY10jLssqrKJNSilA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@curranrob?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Rob Curran</a> on <a href="https://unsplash.com/s/photos/crowd?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a> with some color circles added by the author.</figcaption></figure><p>Finding the right people for research is the bane of every user researcher’s existence. There is so much that goes into successful recruitment: from identifying the right sample size and characteristics to writing an air-tight screener to scheduling and managing all the participants. But this challenge takes on a whole different flavour in a B2B SaaS setting, where the users of your product are professionals working within complex and multifaceted business entities.</p><p>Ever since I shifted focus from end-user (i.e., consumer) to business customers in my role as a user researcher at a B2B scale-up, I’ve been working to improve and ease the research recruitment for my product organisation.</p><p>Here are the <strong>three main recruitment challenges</strong> I’ve encountered and <strong>two ways to address them</strong> in a B2B SaaS environment where direct sales is the main customer acquisition channel.</p><h3>Challenge 1: The potential participant pool is very limited.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xHLPHqGW8Oa8haTbZlzJXw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@randyfath?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Randy Fath</a> on <a href="https://unsplash.com/s/photos/solo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>With B2C user research, the starting point for your sample is the general population, i.e., <em>millions</em> of individuals who already use or could potentially use your product or service. This is your starting point for recruitment: the point from which you begin to niche down to find the right people with the right characteristics for your research topic.</p><p>With B2B user research, your potential participant pool is significantly smaller because it is limited by <strong>two factors</strong>:</p><ul><li><strong>Your company’s customer base</strong> made up of companies rather than individuals. This could range from single digits to hundreds of accounts, depending on your stage of growth, but it will not come even close to the size of the general population as a starting point; and</li><li>The specific, often quite <strong>narrow set of participant characteristics</strong> that the users of your product within each company will have to meet. More on this below.</li></ul><p>Now, in spelling out these factors, I’m assuming that your study is focused on your current customers, and of course, there will be times when that’s not the case. For example, if you’re looking to create a completely new product or enter a new market, you may want to recruit professionals in the industry who are not your customers (yet). But in most cases, you’ll want to test new products and features with your existing customer base, and this immediately slashes the potential participants available to you from millions to a few hundred thousand at best.</p><h3>Challenge 2: The sample characteristics are more niche.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDHCCvZ_hGMCtgS-ikwHAw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@pawel_czerwinski?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Pawel Czerwinski</a> on <a href="https://unsplash.com/s/photos/niche?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>With B2B technology, it is not uncommon to have a single product that is bought and deployed to solve several different use cases. In other words, your one product could be solving different problems for different types of businesses <em>and also</em> different problems for different stakeholders <em>within</em> the same business.</p><p>So when it comes to recruiting participants for any given B2B user research project, you need to get extremely clear about two things:</p><ol><li>The <strong>type of businesses</strong> you’re targeting. This can include things like what industries and geographies they operate in, their size, age and technological sophistication, what they use your product for, how important they are to your company’s growth, etc.; and</li><li>The <strong>type of workers </strong>you’re targeting within those businesses. Do you need to speak to the person who bought your product? Or do you need to interview the person who integrated it with their internal systems? Or maybe it’s someone who is the only person in your customer organisation who uses that one high-value but super technical feature on an irregular basis that your product team desperately wants to improve on? If your customers are exclusively small businesses, you might get lucky and have one person wear all those hats, but the minute you start going upmarket, your user personas will multiply.</li></ol><p>Getting super clear and explicit about these two things will be key to the validity of your insights because it will enable you to target the right user personas within your customer organisations while also accounting for the incentives and biases that participants from different personas will inevitably bring to the table.</p><p>But the challenge here is also a mathematical one. The more use cases and user personas you serve, the more varied your sampling needs become. But as highlighted above, your recruitment pool is pretty limited to begin with. So finding the right people in the right customer accounts and having enough of them to run research without returning to the same customers repeatedly becomes a constant balancing act in B2B user research.</p><h3>Challenge 3: Direct access to customers is limited.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-v4AxpWLjI5EeK_H6GXF0Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@philberndt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Phil</a> on <a href="https://unsplash.com/photos/5i0GnoTTjSE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Another participant recruitment challenge unique to B2B SaaS companies is getting access to the right people.</p><p>Firstly, chances are, the person who bought your software for their employer or business — and who is the point contact between your company’s sales team and the customer business — is not actually the user of your product. Or perhaps they’re not the right user. And to find them in the customer org, you have to go through the buyer of your product.</p><p>Secondly, to speak directly to your product customers, you normally need to go through your account teams (eg, folks like account executives and/ or customer success managers), which means that your request for time with the customer competes with business-as-usual account management tasks and critical customer success activities, such as customer escalations.</p><p>Thirdly, recruiting customers via this route means that you’re competing with a sea of other customer communications, such as new features and product announcements, marketing campaigns and customer research requests from other product teams.</p><p>All this can quickly result in three highly unfavourable outcomes:</p><ul><li>The customer experience suffers from communication overwhelm;</li><li>Your recruitment timelines balloon so much that you’re unable to deliver timely insights to support fast-moving product development cycles; and</li><li>Research recruitment comms become hard to distinguish from sales or marketing messages, adversely affecting your ability to recruit and introducing bias into the research process.</li></ul><p>It is important to note that these three challenges will look somewhat different depending on your company’s growth stage and size. The customer acquisition channels in your business also matter because they impact the proximity of your product team to your customers. For example, having a product-led growth channel can alleviate some of these pain points, whereas partnership-led customer acquisition can exacerbate them.</p><p>But here are two solutions that I’ve been working on that are helping to ease the recruitment pain for user researchers and product managers in my org.</p><h3>Solution 1: Build your own research panel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3vtTtObd_5dyZcRMISdSsQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@helloimnik?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nik</a> on <a href="https://unsplash.com/s/photos/build?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This may seem counterintuitive, given that, in theory, your entire customer base is your research panel. But creating a dedicated pool of potential participants has several distinct advantages:</p><ol><li><strong>Participation by consent.</strong> Building an internal research panel enables you to find individuals who are genuinely interested in joining research studies and providing feedback on early and in-flight concepts, ideas, and prototypes. Regardless of what motivates them to do so, these people <em>choose to</em> <em>opt in</em> to be part of a special group of customers who you can co-create your product with, which means you get a significantly more responsive audience for your recruitment while also reducing any potential en masse spamming of your customer accounts.</li><li><strong>Direct access. </strong>Building an internal research panel also enables you to nurture a direct access channel between your product teams and your users. This reduces the time it takes to recruit great participants and the burden both on the researchers and the account teams to manage outreach and recruitment manually via account owners. It also helps to draw clear boundaries between marketing and commercial communications your customers receive from the business and communications about new research opportunities. This sets clear expectations upfront that user research sessions are not sales meetings while also ensuring that your research-related outreach is ethical and privacy-centred.</li><li><strong>Better profiling. </strong>Last but not least, building out a dedicated research panel helps create participant profiles that are tailored to research recruitment needs. At sign-up, you can collect data that about your panel members’ professional roles, responsibilities, and feature awareness to ensure that you reach out to the right personas with the right background for your next study.</li></ol><p>Given that you can rarely go for quantity in B2B research recruitment, your best bet is to go for quality, and building a dedicated research panel enables you and your team to do just that. But while the panel can go a long way to solving some of the common recruitment woes, there’s another aspect to B2B user research that should not be overlooked: strong stakeholder relationships.</p><h3>Solution 2: Build cross-functional relationships</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DE9QCZ9398RuS6ScEgO9pA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@purzlbaum?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Claudio Schwarz</a> on <a href="https://unsplash.com/s/photos/handshake?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>If you’re a researcher in a B2B company, I cannot stress this enough: you have to get to know your customer-facing, frontline teams.</p><ul><li>Make an effort to learn what different people in sales, customer success, and marketing do, how they see, think about and communicate with your customers, how they’re incentivised, and what they care about the most.</li><li>Help them understand your and your team’s role at different stages of product development.</li><li>Find common ground between your disparate objectives and flex that creativity muscle to explore ways in which your skills can be leveraged to benefit both the product and growth parts of the company.</li></ul><p>Building strong, trusting relationships with folks in sales, marketing, and customer success will not only help you get access to the right customers quicker for your next study and build out a strong internal research panel — it will also enrich your own understanding of your customers and your business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac8be0eab0f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/researchops-community/how-to-debug-your-b2b-research-participant-recruitment-ac8be0eab0f2">How to debug participant recruitment in B2B user research</a> was originally published in <a href="https://medium.com/researchops-community">ResearchOps Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 things I learned that made me a better user researcher]]></title>
            <link>https://sofyabourne.medium.com/5-things-i-learned-that-made-me-a-better-user-researcher-8c22c36b7b93?source=rss-bc0ccce22a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c22c36b7b93</guid>
            <category><![CDATA[b2b-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sofya Bourne]]></dc:creator>
            <pubDate>Wed, 02 Mar 2022 09:59:58 GMT</pubDate>
            <atom:updated>2022-03-02T10:11:15.434Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X3AABEFth1rc-laDlwhHmA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sloppyperfectionist?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hans-Peter Gauster</a> on <a href="https://unsplash.com/s/photos/research?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>If in March 2020 you told me that in two years I will be designing and running complex, multi-stream research programmes to support key product initiatives at my org, I’m not sure I would have believed it. Yet here I am, two years into my current user research role, and the first thing on my to-do list for today is to plan out an entirely new way of engaging our customers in user research. Incredible!</p><p>The last two years have been the most intense and exhilarating in terms of professional and personal growth I’ve ever had. I did a lot of things that scared me. And I learned a great deal about leading research projects in a product org that is growing and changing at a breakneck speed.</p><p>To mark my two years, here are 5 things I learned since joining Onfido that made me a better user researcher:</p><h3><strong>1. Prioritise based on risk</strong></h3><p>There are too few user researchers in any single company to answer all the burning questions. And if you ask enough people about what they need support with, you will soon learn that, actually, all the questions are burning. All the questions had to be answered yesterday, or better yet five sprints ago.</p><p>One way I’ve learned to prioritise research work is by engaging with the concept of risk.</p><p>This starts by stepping back and reframing those burning research questions as assumptions. Instead of going into a study with high-level research questions, challenge yourself and your team to articulate spoken and unspoken beliefs about user behaviour and product performance that you hold. Think <strong><em>“We expect people to do X when Y happens”, </em></strong>rather than <strong><em>“How will people behave when trying to do Z using our product?”</em></strong></p><p>As a bonus, articulating assumptions upfront helps you be more vigilant about checking your findings for confirmation bias down the line.</p><p>Once you have your assumptions, consider the following questions for each of them:</p><ul><li>What existing data or evidence do we have to support or refute this assumption?</li><li>How certain are we that this assumption is correct?</li><li>How much of a risk it is to the product / the company / our customers if we are wrong?</li></ul><p><a href="https://www.usersknow.com/">Laura Klein</a> details an excellent workshop for working through this type of prioritisation approach in her book <a href="https://rosenfeldmedia.com/books/build-better-products/">Build Better Products</a> but you don’t always need to workshop it out. Sometimes you just need to put a few minutes aside, take a step back from all the burning questions and think calmly about which of the fires actually need to be put out before their burn your whole product to the ground.</p><h3>2. Invite everyone</h3><p>If you got into user research, chances are you didn’t come to work in your product org because you wanted to embody the archetype of the solitary deep thinker in a tall ivory tower.</p><p>User research is better when it’s collaborative. It is also more impactful when it’s collaborative.</p><p>But it won’t be collaborative unless you, the researcher, make it so.</p><p>When I start a new project, I make a conscious effort to open up my work to anyone and everyone who wants in. Depending on the project, this can look like:</p><ul><li>Getting cross-functional input on research plans and discussion guides;</li><li>Announcing upcoming user research sessions across multiple slack channels;</li><li>Setting up systems for observer sign up if observer spaces are limited, or simply opening calendar invites to everyone who wants to join if they’re not;</li><li>Leveraging <a href="https://medium.com/u/b6661fefc628">Lookback</a> invisible observer functionality to enable everyone who wants to observe to do so and encouraging them to ask follow-up questions during the interviews;</li><li>Sharing high-level takeaways in the team Slack channel after each session, alongside a link to watch the session recording;</li><li>Inviting observers to add to my own takeaways in Slack threads or live debriefs to generate a discussion and hear multiple perspectives;</li><li>Sharing insight summaries with all relevant teams, not just the immediate project team;</li><li>Carefully crafting the comms around the insights in such a way that they were memorable, actionable and easy to digest.</li></ul><h3>3. Be annoying</h3><p>As researchers, we ask questions for a living. Sometimes that means that we’re the annoying person with all the questions — and that’s ok.</p><p>Be the annoying person who asks all the whys.</p><p>Be the annoying person who pushes for something to be done in a certain way because you know it will lead to better data, better insights, better research participant experience.</p><p>Be the annoying person with the follow-up question when the conversation seems to be coming to an end.</p><p>And, perhaps most importantly, be the annoying person who asks for an explanation of something others consider as obvious or basic, even if it feels stupid to ask.</p><p>Because no one else will.</p><p>Because bad product decisions are all too often made based on unspoken, unchallenged and unproven “shared understanding”.</p><p>And because there are truly no stupid questions.</p><h3>4. Get to know your business</h3><p>Product decisions are business decisions. And as much as we as user researchers may want product decisions to be made solely based on our deep knowledge of our users as people, this is not realistic.</p><p>People who make decisions in our organisations juggle UX priorities alongside product performance, team capacity and business targets. So to be an effective advocate in this context, you need to understand how UX insights you’re producing and design decisions you’re arguing for square with all these other priorities.</p><p>I was reminded of this yet again a couple of months with the collapse of my go-to food delivery service just a week before the holiday season. You can have the best UX, run the most incredible product with a great mission, meet real human needs… but if your bottom line is in shambles, you’re in trouble.</p><h3>5. Trust your gut</h3><p>Thinking back to March 2020, and even March 2021, I acutely remember the feeling of muddling through and the overwhelm I felt at having to grapple with uncertainty and complexity of the new products we were building and trying to balance delivering timely, impactful insights with setting up research processes across several new teams.</p><p>To a large extent, that’s where I find myself today as well, although with more knowledge and experience to draw on as I take on new challenges.</p><p>Looking over the last 24 months, I can pinpoint a number of decisions I made that would have benefitted from me simply trusting my gut.</p><p>It’s can be a very uncomfortable thing to do, trusting your gut. But research is both a skill and an art, and sometimes our gut knows best — be it which repository tool to procure, which method to use, which question to ask or when to hold the pause for a few seconds longer and just listen to the human on the other end of the line.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c22c36b7b93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to run a remote diary study]]></title>
            <link>https://sofyabourne.medium.com/how-to-run-a-remote-diary-study-c669e8c02f88?source=rss-bc0ccce22a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c669e8c02f88</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-research]]></category>
            <category><![CDATA[diary-study]]></category>
            <category><![CDATA[research-methods]]></category>
            <dc:creator><![CDATA[Sofya Bourne]]></dc:creator>
            <pubDate>Tue, 23 Nov 2021 18:03:10 GMT</pubDate>
            <atom:updated>2021-11-23T18:03:10.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QI90JswlbdxUzAsEm9Ekew.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@grianghraf?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Grianghraf</a> on <a href="https://unsplash.com/s/photos/diary?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>About a year ago I ran my first remote diary study. The need for this study arose because I wanted to explore a fairly uncommon experience among a fairly specific user group — something that was not possible to meaningfully explore in interviews alone. I was looking to understand how people in this user group thought about a particular concept and the experiences associated with it, in what circumstances they encountered these experiences, how they navigated through them and what their key pain points were.</p><p>A diary study was an ideal format for this type of discovery research as it enabled me to gather near-real-time data about the experience I was interested in. This meant that the data was as close to real-life as I could get in a remote setting, untinted by visual prompts, research session limitations or recollection biases.</p><h3><strong>The methodology</strong></h3><p>I designed the study to run in three stages:</p><ul><li><strong>Initial interviews</strong> to establish rapport and explore research themes at a high level.</li><li><strong>Two-week diary study</strong> with daily entries related to the topic of the study.</li><li><strong>Follow-up interviews</strong> with select participants to dive deeper into the study topic and explore their diary entries in more detail.</li></ul><h3>The tool stack</h3><ul><li><strong>Recruitment:</strong> User Interviews</li><li><strong>Interviews:</strong> Zoom</li><li><strong>Diary Study entries: </strong>Whatsapp</li><li><strong>Participation tracking: </strong>good ol’ Google Sheets</li><li><strong>Analysis:</strong> Airtable + a research repository tool</li><li><strong>Reporting:</strong> Google Slides</li></ul><h3>Key learnings</h3><h4>Use initial interviews to build rapport and set the tone</h4><p>Initial interviews are the perfect opportunity to get to know your participants, understand how they speak and think about the topic of your study, and establish common ground around what is in and out of scope for your research.</p><p>Note, however, that while it’s useful to nudge the participants in the direction that will yield the most valuable data with the least noise through these early conversations, it’s also important to not bias their diary entries — so tread carefully.</p><h4>Meet your participants where they are</h4><p>When designing my study, I reviewed a number of professional diary study tools on the market. But ultimately, I decided to run the study over Whatsapp.</p><p>This was because I wanted to remove as many barriers to participation as possible. Participating in a diary study is already a big ask, and I didn’t want to complicate things for people who signed up to it by asking them to install and learn a whole new way of communicating.</p><p>While my personal preference would have been Signal, I was also aware that most people in my user group wouldn’t be familiar with Signal. To mitigate privacy concerns with using Whatsapp, I created explicit instructions on what kind of data the participants should <strong>not</strong> be sharing during the study (eg, anything that contained their PII) and discussed this with them in detail ahead of time, too.</p><p>Other apps you could consider are MarcoPolo, Slack, Snapchat… There are too many to list, really. But in general, your choice should depend on who your target audience is and which channel you think would be most natural and accessible to them.</p><p><strong><em>Pro-tip:</em></strong> if you use a messaging app like Whatsapp or Signal to collect diary submissions, it can be a good idea to get a separate phone and SIM specifically for research purposes. This prevents research-related communications and data from leaking onto your personal device and makes data management a whole lot easier after the study is over. Factory reset FTW!</p><h4>Overcommunicate your study instructions</h4><p>The quality of the data you get depends on this. At a minimum, you need to be very clear when articulating the <strong><em>what</em></strong> and the <strong><em>how</em></strong> of the diary submissions.</p><p>The <strong><em>what</em></strong> is the overall ask for each diary entry. Depending on the subject of your study, the main ask will look something like this: <em>“Over the next two weeks, every time you do X, submit an entry”.</em></p><p>The <strong><em>how</em></strong><em> </em>is the description of what you expect each entry to look like. Do you want your participants to take photos or videos? Record a voice note? Send a text message? Tell your participants exactly what you expect them to send you in order to make sure you get the right kind of data for your research.</p><p><strong><em>Pro-tip:</em></strong> if you’re dealing with emotions or reactions in your research, try leveraging the power of gifs and emojis as a communication tool. This is a great way to help your participants tell you how they’re feeling about the subject of their diary entries without making the submission process too lengthy or difficult for them. The caveat here is that gifs and emojis don’t always translate across generations or cultures, so again, tread carefully. As a bonus, the gifs and emojis chosen by the study participants can be a powerful tool for communicating user sentiment to research stakeholders.</p><h4>Track study submissions on a regular basis</h4><p>For my study, this meant daily. Tracking submissions on a regular basis enabled me to:</p><ul><li>Make sure I was getting the data I needed throughout the study period,</li><li>Follow up on interesting or confusing entries in real-time, while they’re still fresh in the participant&#39;s mind,</li><li>Nudge people when participation wanes.</li></ul><p>If you make incentives payout contingent on a minimum number of submissions — which is one approach to keep participants active throughout the study — routinely tracking submissions becomes even more important.</p><h4>Start early on the data analysis</h4><p>Even with a small-scale diary study, you are likely to end up with a huge amount of data.</p><p>15 people that participated in my diary study ended up sending through nearly 200 entries over the two-week period. That’s 200 voice notes to listen to and transcribe, 200 text messages to read through, 200 gifs and emojis to interpret. Plus about two hours worth of transcripts for each participant to code. In other words — a bucketload of data.</p><p>Starting on the analysis early can help you make it less of a mammoth task once the data collection is over. And, perhaps more importantly, it will allow you to track emerging themes and trends. This means that you can probe on these while the study is still running, tweak anything that needs tweaking in the study design, get more out of the follow-up interviews if you’re running them, and in general, get more valuable and clear data.</p><h4>What have you found to work well when running remote diary studies? Share your tips in the comments below!</h4><p>For more inspiration and ideas on designing and running remote diary studies, see these articles that helped me:</p><ul><li><a href="https://medium.com/mixed-methods/applying-participant-experience-principles-to-diary-study-design-b389bb40ef57">Applying Participant Experience Principles to Diary Study Design</a> by <a href="https://medium.com/u/8fd34d365a8c">Anya Zeitlin</a></li><li><a href="https://clicked-research.co.uk/2019/03/21/behavioural-studies-using-whatsapp/">Diary studies using WhatsApp</a> by Clicked Research</li><li><a href="https://medium.com/@valsplat/peaking-into-your-participants-life-with-a-diary-study-8da9f1d1b72d">Peaking into your participants lives with a diary study</a> by <a href="https://medium.com/u/156d8726cd00">Valsplat</a></li><li><a href="https://www.nngroup.com/articles/diary-studies/">Diary Studies: Understanding Long-Term User Behavior and Experiences</a> by NN Group</li><li><a href="https://dscout.com/people-nerds/diary-study-guide">How to Conduct a Diary Study: A Start-to-Finish Guide</a> by Dscout</li></ul><p>And many thanks to <a href="https://medium.com/u/8fd34d365a8c">Anya Zeitlin</a> and <a href="https://medium.com/u/eeefad0c4640">Guy Simpson</a> for chatting with me about their approaches and generously sharing their experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c669e8c02f88" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My career pivot into UX research]]></title>
            <link>https://sofyabourne.medium.com/my-career-pivot-into-ux-research-5796da6769?source=rss-bc0ccce22a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5796da6769</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[career-change]]></category>
            <dc:creator><![CDATA[Sofya Bourne]]></dc:creator>
            <pubDate>Fri, 22 Oct 2021 08:56:53 GMT</pubDate>
            <atom:updated>2021-10-22T08:56:53.364Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xCMBh6NitCKKVX-AExpR_Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jannerboy62?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nick Fewings</a> on <a href="https://unsplash.com/s/photos/direction?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Recently I’ve had a few different conversations with folks in my wider network about career pivots. I’ve been a UX researcher at a tech scale-up for nearly two years now but before that, I spent almost a decade carefully crafting a completely different career in humanitarian aid. Making a major change to a career you’ve invested a lot of time and effort into is tough. There are a lot of questions, a lot of uncertainty, and it’s often difficult to even know where to begin. But it is possible and, more than that, it is worth it. So if you woke up one morning knowing in your gut that whatever you do now is just <strong><em>not</em></strong> <strong><em>it</em></strong><em>,</em> this post is for you.</p><p>Between my realising that I needed to change careers and actually making that change lay several years of curious fumbling about mixed with strategic action. It’s impossible to document all the small learnings, micro pivots, aha! moments and happy accidents that made this transition possible. But with the benefit of hindsight, I’ve summarised the four main things I did that helped me the most along the way.</p><h3>1. I examined what kind of work I actually liked.</h3><p>Now, I don’t mean brainstorming job titles. What I’m talking about is taking a close look at the actual tasks and activities we engage in on a daily basis.</p><p>Take UX research, for example. <strong><em>UX researcher</em></strong> is merely a job title. The actual work is in connecting with and talking to strangers on a regular basis, analysing a ton of data and making sense of it all, unpacking and simplifying complex themes for different audiences, telling effective and impactful stories, translating research findings into actionable insights for your stakeholders, understanding and explaining what your findings mean for the business, and so forth.</p><p>That is how granular I had to get to really figure out what I liked and disliked doing with my time. I thought back to all the past projects I’d done and examined (1) what exactly happened, (2) which aspects of these projects I liked or disliked and (3) why.</p><p><strong>This was an important first step because it helped me understand what kind of work I wanted to do more of</strong> — and why exactly I wasn’t happy doing what I did back then. It allowed me to figure out what really fed my curiosity and got me excited about work.</p><h3>2. I made peace with sunk costs.</h3><p>When I started this professional soul searching, I was still paying off my very expensive US bachelor’s degree. I also was just a couple of years out of graduate school — a free but lengthy commitment that cost me two whole years. In other words, I’d put a huge amount of effort, time and money into building a career I no longer wanted. That was a hard pill to swallow.</p><p>I first learned about sunk costs in relation to past achievements and current aspirations from <a href="https://podcasts.apple.com/by/podcast/ignore-sunk-costs/id1345042626?i=1000418698867">Seth Godin’s podcast Akimbo</a>. Godin frames sunk costs as a gift from our former selves. Here’s what he writes about this in <a href="https://seths.blog/2021/05/sunk-costs-creativity-and-your-practice/">a recent blog post</a>:</p><blockquote>Just because you have a law degree, a travel agency or the ability to do calligraphy in Cyrillic doesn’t mean that your future self is obligated to accept that gift.</blockquote><p>To put it bluntly, framing my competencies and experiences in these terms changed everything. <strong>Learning to detach from my sunk costs, while also seeing those years of effort and experience as part of what made me unique, gave me a green light to go ahead and experiment with abandon. </strong>Everything I’d learned and achieved mattered, sure, but it didn’t dictate what I did next.</p><h3>3. I self-educated (on a budget).</h3><p>Eventually, I figured out that design could be a field that would tick a lot of boxes for me. I deliberately say ‘design’ here because, at that point, I didn’t actually know all that much about this field, what kind of opportunities it had, or how my own skills (mostly research and project management) could fit in here.</p><p>So naturally, I did more research.</p><p>I read widely on the subject. I went to meetups, conferences and events. I took every free design workshop and course I could get my eyes on (<a href="https://generalassemb.ly/education?dateType=any&amp;event=true&amp;format=classes-workshops&amp;free=true&amp;topic=4&amp;where=london&amp;workshop=true">General Assembly</a> and <a href="https://acumenacademy.org/course/design-kit-human-centered-design/">Acumen</a> definitely deserve a mention here). <strong>In other words, I did everything I could to learn more about the field and make sense of how my skills could translate to the design world.</strong></p><h3>4. I made small but strategic interim moves</h3><p>Coincidentally, around the same time, I was also tasked with writing <a href="https://www.alnap.org/system/files/content/resource/files/main/ALNAP_Adaptiveness_UCD%20final.pdf">a case study on the application of design principles in humanitarian projects</a>, which meant I got to interview innovation and design practitioners and dig even deeper into the subject. By the time I was wrapping up that case study, I had a good enough understanding of the design field to know that I wanted to get into it and try it out for myself. Learning about design was no longer enough — I needed to get some actual practical experience.</p><p>This was the hardest part.</p><p>In the end, it was through a bit of good timing and a bit of good luck that I found a way in. A tiny design consultancy that I profiled for my case study was looking for a design researcher with experience in humanitarian aid. They needed someone who knew a lot about the aid sector. I needed somewhere I could get practical experience in design. It was a classic win-win situation.</p><p>That role turned out to be perfect as an interim move for two main reasons.</p><p>Firstly, when I started it and for a long while after, I didn’t really know exactly what I wanted to do in the design field. I was equally drawn to product design, service design and user research. To be honest, I was just eager to learn more about everything. And, due to the nature of the projects I worked on and the small size of the team at that agency, I got a chance to try my hand at everything. As a result, <strong>I was able to make a more informed decision about the direction I wanted to go in when it was time to move on.</strong></p><p>Secondly, making this interim move reduced the risk of my experiment. I didn’t have to burn all my bridges all at once. In fact, I remained closely involved in the humanitarian aid sector through the projects I worked on at the agency (which, in the end, only strengthened my resolve to leave, but that’s a different story). <strong>Carving out this safe space for myself to experiment and learn while still leaving room to abort the mission was instrumental to me taking the full plunge once I felt ready to do so.</strong></p><p>As I mentioned at the start, pivoting my career to UX research involved far too many learnings to summarise in a single post. One key thing that I did realise in the process is that all the rules we think exist when it comes to careers and professional growth are made up. <strong>The big secret is that there are no rules.</strong> Everyone makes it up as they go along. And that’s great because it means that any career pivot that you do dream up is possible.</p><p>Get clear on how you want to spend your days, learn everything you can about the field you’re interested in, and then slowly, bit-by-bit — dare I say, <em>iteratively — </em>make the move.</p><p>The most exciting and fulfilling career paths are never, ever linear.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5796da6769" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>