<?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 Sasha Petrov on Medium]]></title>
        <description><![CDATA[Stories by Sasha Petrov on Medium]]></description>
        <link>https://medium.com/@deepnavy?source=rss-4ca85962d928------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y_chrwI4b6vi3O5vX-APrQ.jpeg</url>
            <title>Stories by Sasha Petrov on Medium</title>
            <link>https://medium.com/@deepnavy?source=rss-4ca85962d928------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:26:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@deepnavy/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[How to find Generative AI use cases]]></title>
            <link>https://uxplanet.org/how-to-find-generative-ai-use-cases-b6ee9aff1ea9?source=rss-4ca85962d928------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6ee9aff1ea9</guid>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[generative-ai-use-cases]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Sasha Petrov]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 09:54:12 GMT</pubDate>
            <atom:updated>2023-11-09T09:54:12.093Z</atom:updated>
            <content:encoded><![CDATA[<p>AI, AI, AI, AI, AI, AI… AI is everywhere these days. But identifying the right Gen AI use cases for your product involves a lot of tedious discovery work, product and design hard skills, continuous exploration of what’s possible, and experimentation.</p><h3>Can AI do that?</h3><p>Let’s set the tone with this quote from <a href="https://youtu.be/R-Geamq9xc0?si=NHBd2xrXD7-m2rY8&amp;t=1286">Lenny’s Podcast by Paul Adams</a>, the CPO of Intercom, discussing the product and AI:</p><blockquote>I’d start with what your product does. What is the core premise behind it? Why do people use it? What problem does it solve for them? Go back to basics. And then ask the question, “Can AI do that?” For a lot of SaaS products, the answer is going to be “Yes.” For some, “Yes, it can partially do it.” For others, “It can’t do that, at least not yet.”</blockquote><p>This is a very simplified but working approach. And even further, with the pace of current technological advancements when considering AI use cases, we shouldn’t even limit ourselves to what is currently feasible. It won’t be long before machines are capable of performing most of the mental work on the same level as humans and perhaps even surpassing us. For example, even if AI can’t fully automate a lawyer’s routine work today, a breakthrough in just the coming few months might make it possible. So, a good strategy, at least for small startups who are just starting, is to experiment with what is available today, lay the groundwork, and be ready to accelerate when a new enabling technology emerges.</p><h3>Human judgment and AI</h3><p>Here is another quote from an <a href="https://hbr.org/2023/06/how-large-language-models-reflect-human-judgment">HBR article</a>:</p><blockquote>Artificial intelligences are prediction machines. They can tell you the probability it will rain today, but they cannot tell you whether or not you should pack an umbrella.</blockquote><p>And even Generative AI, despite its seeming intelligence and creativity, is essentially still a prediction machine. However, it is revolutionizing how AI helps in decision-making by changing how humans create and exercise judgment.</p><p>Current AI technology fundamentally lacks the human touch of subjective judgment and personal experience. Machines are very good at processing immense data volumes, recognizing patterns, and making predictions. In contrast, humans excel in reasoning, empathy, and deriving insights from personal experiences. Thus, the optimal decision-making approach is a harmonious fusion of AI insights and human judgment.</p><h3>Augmentation</h3><p>While a complete replacement of humans in work by AI might be possible in the future, it is often counterproductive, unreliable, and potentially unsafe. A synergistic or human-in-the-loop approach is more favorable.</p><p>Many professionals are talking about AI augmentation, which involves enhancing human abilities by automating or assisting with certain aspects of a task. AI provides tools or insights that help humans carry out their roles more efficiently and effectively. It primarily works in the background, processing data and offering suggestions based on predefined parameters. Human intervention remains essential, with AI providing additional support.</p><p>For instance, in the legal world, one task that lawyers often have to undertake is legal research. With augmentation, they would be able to do the following:</p><ul><li>A legal AI assistant can sift through vast amounts of case law, statutes, and legal articles to generate a list of potentially relevant citations and precedents for a particular case the lawyer is working on.</li><li>The human lawyer then reviews the generated list, selecting the most relevant cases and incorporating them into their legal arguments.</li></ul><h3>Co-creation</h3><p>Some people differentiate a co-creation mode of operation with AI, which involves a collaborative effort between humans and AI to produce a result or output. Both entities engage in a dialogue or iterative process where input from one influences the decisions or actions of the other. There is a dynamic and often real-time exchange between the human and AI. The AI may offer suggestions, but it also learns from human feedback and adjusts its actions or outputs accordingly.</p><p>Consider a graphic designer working with an AI to design a poster. The designer may provide a theme or mood, and the AI generates a design. The designer gives feedback, such as “make it brighter” or “use a different font,” and the AI iteratively adjusts the design based on that feedback. <a href="https://openai.com/dall-e-3">Dalle 3</a> is a great example of this.</p><h3>The process of finding AI use cases</h3><p>Finding generative AI use cases is not a fancy job, as it requires a lot of tedious work that often has nothing to do with AI. You need to reevaluate and sometimes even define the goals, conduct research, and communicate with stakeholders while diving deep into business problems. No one enjoys doing it, and everyone wants to build things. But I’m certain that even if you are an established, well-functioning company, your CJM is outdated, and you lack a holistic vision of how the business operates.</p><p>The rough process of finding an AI use case is as follows:</p><ul><li>Define the problem and goal.</li><li>Map the current reality.</li><li>Map the future reality.</li><li>Identify potential AI use cases.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5gHUKBmP2UXAi2kXUUrsLw.png" /><figcaption>The process of finding AI use cases</figcaption></figure><h4>Define the problem and goal</h4><p>It all starts with analyzing the current process in your company, finding the problem you want to solve, and determining the end goal you want to achieve. Addressing the right problem is crucial. AI, and Generative AI in particular, is not a magic pill; it’s just a tool that can help you solve the problem.</p><p>Also, it is useful to ask yourself the following questions about the selected problem and a hypothetical AI solution:</p><ul><li>Why is this problem important?</li><li>What are your expectations and objectives?</li><li>How will it improve the user experience?</li><li>Why is it important for the business?</li><li>Why is now the right time?</li></ul><p>If you want to go even deeper, use <a href="https://uxplanet.org/the-5-whys-how-to-make-the-most-of-this-method-10c07885d9e">the 5 whys method</a> for each individual question.</p><h4>Map the current reality</h4><p>There are many ways you can explore the current state of things in your company and product. I prefer mapping exercises. You can check out the overview <a href="https://www.nngroup.com/articles/ux-mapping-cheat-sheet/">here</a> to choose the method that will work for your case:</p><ul><li>Empathy mapping</li><li>Customer journey mapping</li><li>Experience mapping</li><li>Service blueprinting</li></ul><p>A timeless book is <a href="https://www.oreilly.com/library/view/mapping-experiences-2nd/9781492076629/">“Mapping Experience” by Jim Kalbach</a>, which I can’t recommend enough. You can read <a href="https://www.uxmatters.com/mt/archives/2016/09/mapping-experiences.php">an excerpt from the previous edition</a>, but I highly recommend reading the entire book to become proficient in mapping. He also adds these types of maps to the toolset:</p><ul><li>Mental model maps</li><li>Ecosystem maps</li></ul><p>You can also check out my guide on <a href="https://petrov.substack.com/p/find-new-opportunities-with-experience">finding new opportunities with an experience map and CJM</a>, which will work well for discovering AI use cases. Simply modify the “How might we” question to focus on using Generative AI to find a solution.</p><p>In my experience, a hybrid map works best. First, you need to define the scope of your map (a specific part of your product or business that you’ll research) and the user, whether they are internal or external. It is crucial to choose a point of view, as the role of a person in the potential solution is important. We want to augment, not replace, the human.</p><p>So there can be the following lanes:</p><ul><li>Phase</li><li>Action (task)</li><li>Touchpoint</li><li>Pain point</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Kwu948Ovx944rSrp.png" /><figcaption>A sketch for a possible hybrid map</figcaption></figure><h4>Map the future reality</h4><p>Our products and companies are not perfect, so building the future state of your product is a good way to align everyone on the future vision. It helps us find ways to improve the company, document all possible ideas in one place, and have a holistic view of the business. Even in small teams, the insights about the current process are often siloed. Don’t worry about AI here, as there are numerous ways we can improve the process even without it. You can find more details on how to map the future state <a href="https://www.nngroup.com/articles/journey-mapping-approaches/">in this article</a>.</p><p>This step is very time-consuming and difficult to organize, so it is optional if you want to benefit from Generative AI quickly.</p><h4>Finding the Generative AI case</h4><p>When you’re finished with the tedious research and discovery work, that’s when the exciting part begins. However, there is no magical algorithm for identifying a specific Generative AI use case for your problem. To connect the dots, you simply need to familiarize yourself with the capabilities of Generative AI by researching the field, keeping up with the latest news, and experimenting with new products.</p><p>If you’re new to Generative AI, <a href="https://research.aimultiple.com/generative-ai-applications/">this list</a> is the most comprehensive one for Generative AI use cases, which will give you a good starting point.</p><p>However, I have personally developed a few simple rules when considering use cases for Generative AI, particularly when using mapping techniques:</p><ul><li>Identify a task and its associated pain point.</li><li>Can this task be broken down into smaller tasks?</li><li>Is there a simple solution that doesn’t require AI?</li><li>Is AI truly necessary for this?</li><li>Can AI effectively perform this task?</li><li>Are there any ethical concerns related to using AI in this context?</li><li>What data is required for this to be successful?</li><li>What data do we currently have?</li><li>What level of augmentation is needed? (Does it require a full review and corrections, or just a pick/approve scheme?)</li></ul><p>Go through the entire map and address this task/pain point combination. The pain point is particularly important. Our goal is to solve genuine problems with AI rather than simply creating flashy and useless AI tools.</p><p>Add the following lanes to our hybrid map:</p><ul><li>Data</li><li>Non-AI solutions</li><li>Generative AI use cases</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9INzVeJX98zE2cbS.png" /><figcaption>A hybrid map with additional lanes</figcaption></figure><h3>AI use case finder tool</h3><p>So I wondered, can I use Generative AI to automate the process I described and help people find Generative AI use cases for their task/pain-point pair?</p><p>I’ve created a small tool that takes a simplified version of a User journey map, which I called a task map, and analyzes it to find applicable AI use cases.</p><p>You can try it out <a href="https://ai-use-case-finder.streamlit.app/">using this link</a>.</p><p>Here is the GIF preview:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*fBPrqPcgPb2vO1bsSK8RRw.gif" /></figure><p>It’s not a finished tool, and I must say it doesn’t deliver satisfactory results yet compared to what I would expect from an AI expert. However, it’s already something. I believe that with some fine-tuning using real-world task -&gt; pain point -&gt; generative AI use case scenarios, it has the potential to generate suggestions that are just as good as those from a mid-level AI consultant.</p><p>I would greatly appreciate your help in experimenting with this tool. I encourage you to test it on your data. I’ve also included a rating system that can help me identify good answers to fine-tune the datasets if this idea proves to be valuable.</p><p>The key to finding the right AI use cases is deep research of your field, sphere of interest, or product, as well as ongoing education on new technologies and continuous discovery. This constant work can help you connect the dots. For more inspiration, check out this <a href="https://www.youtube.com/watch?v=5p248yoa3oE">video about the opportunities of AI by Andrew Ng</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6ee9aff1ea9" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/how-to-find-generative-ai-use-cases-b6ee9aff1ea9">How to find Generative AI use cases</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prompt to product]]></title>
            <link>https://uxplanet.org/prompt-to-product-7d72c456ccc6?source=rss-4ca85962d928------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d72c456ccc6</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[future]]></category>
            <dc:creator><![CDATA[Sasha Petrov]]></dc:creator>
            <pubDate>Mon, 03 Apr 2023 21:44:17 GMT</pubDate>
            <atom:updated>2023-04-03T21:44:17.080Z</atom:updated>
            <content:encoded><![CDATA[<h4>Imagining the future of product development and design and considering the things a product person can do to be a part of it</h4><p>To set the stage, I’d like to share a thought-provoking quote from Lex Friedman about the future of AGI (Artificial General Intelligence) from <a href="https://youtu.be/L_Guz73e6fw?t=55">the podcast intro with Sam Altman</a>:</p><blockquote>…Soon, nobody knows when, but many believe that it can happen within our lifetime. The Collective intelligence of the human species begins to pale in comparison by many orders of magnitude to the general superintelligence in the AI systems w build and deploy at scale.</blockquote><blockquote>This is both exciting and terrifying. It is exciting because of innumerable applications we know and don’t yet know that will empower humans to create to flourish to escape the spread of poverty and suffering that exists in the world today and succeed in this old all too human pursuit of happiness. It is terrifying because of the power that super-intelligent AGI wields to destroy human civilization, intentionally or unintentionally. The power to suffocate the human spirit in the totalitarian way of George Orwell’s 1984 or the pleasure fuelled mass hysteria of a brave new world where, as Huxley saw it, people come to love their oppression to adore the technologies that undo their capacities to think.</blockquote><p>The pace of technological advancement is truly unprecedented. I’ve never seen anything like this before in my life. I don’t consider myself a flashy AI evangelist. Still, given all of the OpenAi’s and myriad other AI startup breakthroughs, I wouldn’t be surprised if we witnessed things in the coming year that seemed unimaginable in fantasy novels.</p><p>Like Lex Friedman, I’m excited and terrified as a person and professional by all the latest advancements and the possibilities that lie ahead, imaginable and unimaginable. And I keep asking myself a question. What can I do to ride this AI wave or at least not be entirely dragged by it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IR9PXV6Wv8PpPO75FlCL4w.png" /><figcaption>A person typing a prompt to create a product</figcaption></figure><h3>The future of prompt to product</h3><p>Overall, I’m pretty optimistic about the potential of LLMs and AI. Seeing Greg Brockman demonstrate what GPT-4 could do <a href="https://www.youtube.com/live/outcGtbnMuQ?feature=share&amp;t=974">on a recent developer livestream</a> — like turning a simple sketch into a fully functional app — really got me thinking about all the exciting possibilities that lie ahead.</p><p>Imagine you’re a product manager, designer, or founder with an idea to test:</p><ul><li>You write a simple PRD with a basic product description, user stories, and hypothesis and then submit it to an AI tool. Let’s call it ‘Prompt to Product.’</li><li>With just a click of a button, the tool generates a working app and deploys it to your local host server.</li><li>You test the app and identify issues, which you describe to the tool as you would to a developer, and continue to dialogue with the tool until satisfied.</li><li>Then you ask the tool to deploy the app to the testing environment.</li><li>When your app is online, you use another tool called ‘Prompt to Test’ to conduct unmoderated user testing with external users. Just upload a list of emails and pick the hypotheses to test, and ‘Prompt to Test’ handles the rest of the testing process.</li><li>Shortly, ‘Prompt to Test’ provides you with general observations and suggestions for improvement, which you can accept or modify.</li><li>You might involve a designer and an engineer to make your product even better and optimized for scale.</li><li>The designer can tweak the UX using text prompts and image sketches.</li><li>The engineer can look at the code to fix potential database issues and add privacy improvements, for example, all with a couple of prompts and little to no coding interventions.</li><li>After running through some tests, your product is ready for release to the world.</li><li>And the best part? You accomplished all of this in just one week with a couple of back-and-forth prompts!</li></ul><p>And that’s just what I was able to imagine. Just think of all the things we don’t know are technically possible yet that will emerge in the coming months and years.</p><p>The future is looking bright for product people, founders, and creatives. With the advancements in technology, you won’t even need someone to write code for you to bring your product to market. The “why” behind your product will become even more important, if not paramount, than the “how.”</p><p>Of course, the downside is that there will inevitably be a lot of crappy products and copycats. Still, on the bright side, it will also unleash human creativity, resulting in diamonds shining through the barrels of mud.</p><h3>Current reality</h3><p>However, let’s take a closer look at these tools now. It’s still necessary to have coding skills and a certain level of familiarity with the technology or framework you’re working with to ensure your app works as intended.</p><p>But the process has become significantly more accessible, as you mostly need to understand the general principles and approaches of how to make digital products and a lot of patience to debug the code written by tools like ChatGPT. But with each consecutive prompt, you can create a viable prototype to test your idea with the world.</p><p>Moreover, here are a few examples of how you can utilize these tools:</p><ul><li><a href="https://medium.com/codingthesmartway-com-blog/mastering-chatgpt-build-your-own-calculator-web-app-in-minutes-d6f0cc3c8ffa">create a calculator in minutes</a>;</li><li><a href="https://www.codingthesmartway.com/effortlessly-create-a-full-stack-web-application-with-chatgpt/">create a basic full-stack web app with ChatGPT</a>;</li><li><a href="https://bootcamp.uxdesign.cc/i-made-a-flappy-bird-clone-with-gpt4-and-midjourney-in-under-an-hour-and-you-can-do-it-too-7847bc509431">create a simple game in Unity using GPT-4 and MidJourney</a>;</li><li><a href="https://youtu.be/6gibI4Fo1R8">a software engineer can approach solving a problem with ChatGPT</a>.</li></ul><p>And you can find dozens of articles online that teach you how to create better prompts for coding with ChatGPT, such as the ones linked <a href="https://betterprogramming.pub/10-tips-for-improving-your-coding-with-chatgpt-3e589de3aff3">here</a> and <a href="https://medium.com/@tanyamarleytsui/coding-with-chatgpt-b50ab3fcb45f">here</a>.</p><p>Oh, I almost forgot to mention that tools like Copilot X take this process to the next level by eliminating the need to switch between your IDE and browser.</p><h3>How to ride the wave</h3><p>When I began writing this article, the main focus was on the question, ‘Should product people code?’ but as I dug deeper, it led me down a rabbit hole of envisioning the future of AI.</p><p>So, the answer to whether product people should code is a resounding “yes.” And I want to emphasize that they should not only know how to code but also be able to code themselves. Because until there are tools like ‘Prompt to product,’ you need to fix some minor things yourself to get the prototype running.</p><p>Indeed, as these ‘prompt-to-product’ solutions become more sophisticated, product people will require fewer and fewer coding skills. However, gaining foundational knowledge will help you better understand the systems. And in a future where anyone can create a product with a single prompt, having this knowledge may provide a competitive advantage.</p><p>Going back to the question I posed at the beginning of this article — “What can I do to ride this AI wave or at least not be entirely dragged by it?” — I have a solution, at least for the beginning of the 2023 version of myself. I hope you’ll find it helpful too.</p><p>My plan as a product manager who has transitioned from product design and has an engineering background is as follows:</p><ul><li>Refresh my coding skills.</li><li>Build small practical tools with the help of LLMs or so-called ‘front-ends’ for LLMs.</li><li>Improve my prompt design skills, especially for professional needs.</li><li>Gain a better understanding of how LLMs work.</li><li>Go deeper into recent AI research papers beyond those trends that lie on the surface (this is tricky).</li></ul><p>I find it interesting to rewatch old sci-fi movies about AI, especially at this point. So, I’ll wrap up this article with a movie recommendation: ‘Transcendence,’ starring Johnny Depp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h7Cc6ZAnYkrj012t.jpeg" /><figcaption>A scene from the movie ‘Transcendence‘</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d72c456ccc6" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/prompt-to-product-7d72c456ccc6">Prompt to product</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 ways to involve your team in continuous product discovery]]></title>
            <link>https://uxplanet.org/5-ways-to-involve-your-team-in-continuous-product-discovery-fb972ed858dd?source=rss-4ca85962d928------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb972ed858dd</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Sasha Petrov]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 09:36:54 GMT</pubDate>
            <atom:updated>2023-03-20T09:36:54.335Z</atom:updated>
            <content:encoded><![CDATA[<h4>Maintaining continuity in the discovery process, communicating your insights regularly, and working collaboratively can help you and your team empathize with your users more and ultimately build better products.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UIE2hSsypAN0Y_UhoxNyrQ.png" /><figcaption>Two people sitting together, one of them holding a mobile phone and talking hand-drawn</figcaption></figure><p>Observing users interacting with your product or discussing their needs, problems, or desires can be incredibly impactful for building a successful product. I’m sure you know it and already doing it. But do you do it regularly? Do you involve your team in this process? How often do you present the insights?</p><p>Actions speak louder than words. There’s no substitute for actually seeing your users in action. Let’s be honest. No one pays attention to lengthy reports with dense paragraphs and slides. People’s attention spans are so short these days that you need to approach sharing information about your users and involving the team as if you are an internal community or event manager.</p><p>Frequency in the discovery process is key to generating insights regularly and keeping the ‘content machine’ moving:</p><blockquote>At a minimum, weekly touchpoints with customers<br>By the team building the product<br>Where they conduct small research activities<br>In pursuit of a desired outcome</blockquote><blockquote>Teressa Torres <a href="https://twitter.com/ttorres/status/1476255204777639943?lang=en">about continuous discovery</a></blockquote><h3>Invite your teammates to the interviews</h3><p>There are <a href="https://www.producttalk.org/2018/12/engineers-and-discovery/">many reasons</a> why you should involve your teammates and especially engineers, in the discovery process:</p><ul><li>They will hear different insights because they have different perspectives.</li><li>They will help you test the idea in numerous ways, from building a prototype to provident necessary data.</li><li>They will challenge you by asking discomforting questions.</li><li>They will bring an analytical mindset to your product experiments</li><li>Delivery goes smoother when your teammates participate in the discovery process because they already have the context and knowledge of the user.</li></ul><p>And lastly, as Marty Cagan said in his book Inspired:</p><blockquote>If you’re just using your engineers to code, you’re only getting about half their value.</blockquote><p>And personally, I think it relates to every role in the product team and company.</p><p>With this in mind, invite your teammates to join in whenever you have any activities involving users, such as user interviews, user tests, or focus groups. Once a session is confirmed, post a message in your team’s internal communication tool with the dates and times, and ask who would like to join. Let them know they don’t need to do anything specific — they can listen and observe.</p><p>Some people don’t want to participate in these activities; interestingly, these are usually the people who can have the most significant impact from observing users. If you encounter a teammate who is hesitant to join in, contact them directly. Explain to them the significance of such activities and emphasize how enjoyable watching others discuss or interact with your product can be.</p><blockquote><strong>Tip #1. The ideal number of participants in the interview</strong></blockquote><blockquote><em>When it comes to user interviews, it’s generally recommended to limit the number of additional participants to no more than two. However, in my experience, I prefer to have just one extra person present to avoid distracting the user. Interviews can already be quite stressful for people, and being 1-on-1 with someone can be overwhelming enough, let alone with two additional individuals. Moreover, having two people on the call who remain silent can feel a bit awkward.</em></blockquote><blockquote><strong>Tip #2. How to interview with your teammates</strong></blockquote><blockquote><em>During an interview with other teammates, I have a few rules that I like to follow. 1) one person leads the interview; 2) If another person has questions during the interview, they should send them privately in Slack to avoid disrupting the flow; 3) at the end of the interview, I allocate time for other participants to ask questions.</em></blockquote><blockquote><strong>Tip #3. Notes and follow-up discussion</strong></blockquote><blockquote><em>I typically don’t take notes during the interview itself, as I usually record the sessions and later debrief the transcript. However, I do write some key phrases during the interview that can help me delve deeper and ask follow-up questions.</em></blockquote><blockquote><em>If I have a teammate present during the interview, they can take notes instead. Often, we stay on the call after the session is over to exchange our initial impressions, and these can be very useful. In my experience, these first impressions often highlight the most important observations.</em></blockquote><h3>Set up an insights channel</h3><p>Create a dedicated communication channel using Slack or another team messaging platform. Treat it as a community development initiative, so post there regularly. As you do your weekly interviews, create video clips of the most exciting moments and post them to the channel. Add your comments and insights to supplement the clips or ask your teammates to interpret them, it’s always interesting to see how other people think, and it adds an element of interactivity.</p><p>On top of that, you can post weekly or bi-weekly reports that cover the insights and themes you’ve discovered. You can also use the channel to announce upcoming interviews.</p><blockquote><strong>Tip #4. How to make more impactful clips</strong></blockquote><blockquote><em>To make the clips more impactful, you can use text-based audio and video editing software like Descript. Here’s how to make the most of it:</em></blockquote><blockquote><em>Cut out any unnecessary words, sentences, and sounds (such as “like,” “well,” and “um”). When speaking, we often use a lot of filler that doesn’t add much to the conversation.</em></blockquote><blockquote><em>Use audiograms if you don’t want to share video of the user.</em></blockquote><blockquote><em>Add background music to make the clip more emotional and epic — trust me, it’s worth trying!</em></blockquote><blockquote><strong>Tip #5. Debrief within one day</strong></blockquote><blockquote><em>I know it’s not easy, and I don’t always do it myself on time, but it’s important to allocate time to debrief each interview at least one day after the session and to do a weekly overview. By doing this, you won’t create a backlog and will be able to share insights with your team on a regular basis. If you don’t do it right away and let everything pile up, it becomes harder to analyze, and the quality of your research suffers because you may miss important details.</em></blockquote><h3>Watch users’ session recordings</h3><p>Using recordings and replays is a compelling way to gain insights into user behavior. It’s almost like being in the same room as your users, observing how they interact with your site or app. The only drawback is that you don’t know why users do what they do.</p><p>Sometimes it can be overwhelming, especially when dealing with thousands or millions of users, so having a clear goal when reviewing session recordings is essential. Typically, I focus on specific flows, pages, interface elements, or user segments. However, I occasionally like to pick random sessions to uncover unexpected bugs and obstacles that may not have been on my radar.</p><p>If you want to know more about how to start analyzing user session recordings, check out these great articles explaining <a href="https://uxdesign.cc/3-important-steps-in-session-recording-analysis-49b104461dfa">how to pick a specific user segment</a> or <a href="https://www.hotjar.com/blog/session-recordings-user-engagement/">approach session recordings in general</a>.</p><p>As for the process, I set aside at least 2 hours per week to review session recordings. Having uninterrupted time during this process is important, as you can start noticing patterns and trends through many recordings. I also highly encourage designers and engineers to review session recordings for at least an hour weekly.</p><blockquote><strong>Tip #6. The why behind the behavior</strong></blockquote><blockquote><em>If you notice weird behavior in session recordings, it could be a sign that your flows and information architecture are not aligning with users’ mental models. For instance, if you observe users repeatedly going back and forth between pages, scrolling all the way down to the footer to navigate to another page, or frantically scrolling from top to bottom on a page, these could be indications of underlying issues.</em></blockquote><blockquote><em>Make sure you have a place where you document these observations. Take advantage of user interviews as an opportunity to ask why users engage in these unusual behaviors.</em></blockquote><blockquote><strong>Tip #7. How to organize your observations</strong></blockquote><blockquote><em>I organize all of my observations in spreadsheets:</em></blockquote><blockquote><strong><em>1st sheet is for assignments<br></em></strong><em>Columns: user segment or pages/screens, reviewer, date of last review. This is especially helpful when other people are involved in the review process, as it prevents any overlap.</em></blockquote><blockquote><strong><em>A separate sheet for each reviewer<br></em></strong><em>Columns: user email, screen/page, description, type (Bug, behaviour), recording link.</em></blockquote><blockquote><strong>Tip #8. Privacy</strong></blockquote><blockquote><em>It’s important to respect users’ privacy when using session recordings. Make sure to utilize any built-in settings and tools to hide sensitive data from the recordings.</em></blockquote><h3>Collaborate and communicate with empathy maps and user scenarios</h3><p>Continuous product discovery is not only about inviting people to user interviews, communicating research timely and regularly, and establishing an ‘observation’ routine. It is also about collaboration.</p><h4>Empathy maps</h4><p>Empathy map is the go-to tool if you want to put yourself in your user’s shoes. Again Norman Nielsen did a great job of <a href="https://www.nngroup.com/articles/empathy-mapping/">explaining what an Empathy Map is</a>:</p><blockquote>An <strong>empathy map</strong> is a collaborative visualization used to articulate what we know about a particular type of user. It externalizes knowledge about users in order to 1) create a shared understanding of user needs, and 2) aid in decision making.</blockquote><p>Your artifacts should be based on research and real data. However, sometimes to kick things off, you need a starting point. In this case, proto-empathy maps or proto-personas can be useful. These tools can assist in establishing initial hypotheses and guiding future research to get data from potential users.</p><p>Back then, you’d usually have to get a team together to brainstorm empathy maps. But nowadays, the ideation process is much smoother with generative language models. You can use ChatGPT to get some initial ideas to kickstart your empathy map creation process.</p><p><strong>Step 1. </strong>Ask ChatGPT to generate personas for your product</p><figure><img alt="ChatGPT generated answer about personas" src="https://cdn-images-1.medium.com/max/1024/0*v2oq5H02uvgI2MXb.png" /><figcaption>Personas generated by ChatGPT</figcaption></figure><p><strong>Step 2.</strong> Ask ChatGPT to generate an Empathy map for them (I picked only one for demonstration purposes)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sOrm82gjxer2Ya7m.png" /><figcaption>Empathy map generated by ChatGPT</figcaption></figure><p><strong>Step 3.</strong> Assess the results with common sense, then involve your team for further ideas generation and discussion.</p><h4>User scenarios</h4><p>When it comes to communicating with empathy, user scenarios are an excellent tool. Writing user scenarios can help you turn a list of customer needs and product requirements into a format that’s easily digestible and engaging for others to read. The general structure is simple ‘Setup &gt; Action &gt; Result’. And user scenarios make really effective PRDs. <a href="https://productschool.com/the-product-book/">‘The Product Book’</a> provides a great guide on how to craft great user scenarios.</p><p>Let’s return to the ChatGPT magic to generate user scenarios for our product.</p><p><strong>Step 1</strong>: Ask ChatGPT to generate a set of features</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Oos1CvZeCkJf_Q7D.png" /><figcaption>Features generated by ChatGPT</figcaption></figure><p><strong>Step 2</strong>: Ask ChatGPT to create User Scenarios</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PBSg3I_nERKgu6D5.png" /><figcaption>User scenarios generated by ChatGPT (Part 1)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dEd_EXTjp-JGYK93.png" /><figcaption>User scenarios generated by ChatGPT (Part 2)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*LEO4Bw9CdJlVMbxX.png" /><figcaption>User scenarios generated by ChatGPT (Part 3)</figcaption></figure><p><strong>Step 3</strong>: Approach ChatGPT results with common sense</p><blockquote><strong>Tip #9</strong></blockquote><blockquote><em>Feed your real personas and features set to ChatGPT to create a foundation for your entire PRDs. Or use Notion’s new AI feature to help you with that too.</em></blockquote><h3>Create a stakeholders repository</h3><p>Create <a href="https://www.nngroup.com/articles/research-repositories/">a centralized place where all discovery activities and data can be organized</a> and accessible to anyone in the company. It can include:</p><ul><li>User data and contact info</li><li>Hypothesis and insights reports</li><li>Processes and templates</li><li>Interview and session recordings</li><li>Future plans and next steps</li></ul><p>When it comes to a particular tool for a repository, I suggest:</p><ul><li>Notion, where you can create a highly flexible and customizable repository. Check out <a href="https://medium.com/r?url=https%3A%2F%2Fuxdesign.cc%2Fstep-by-step-how-to-build-a-user-research-repository-in-notion-8d96c46a0211">this comprehensive guide</a> on how to set up Notion for user research.</li><li>Specialized research tools, such as Condens and Dovetail. They have fewer customization options but are very convenient as they have premade templates, and all of your raw data, like user interviews or user testing, is stored in one place. Notion has a learning curve compared to them.</li></ul><p>On a side note, tools like Condens and Dovetail haven’t completely changed <a href="https://petrov.substack.com/p/a-simple-guide-to-interviews-thematic">how I approach product discovery and interview analysis</a>, but they speed the process up tenfold. If you don’t put off tagging the themes in your interviews till the last minute, you can draft a preliminary report in no time. These tools are so simple but super powerful. So I encourage everyone to try including something similar to their workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb972ed858dd" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/5-ways-to-involve-your-team-in-continuous-product-discovery-fb972ed858dd">5 ways to involve your team in continuous product discovery</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>