post

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Successful product management in companies where it’s least understood

Measuring critical user journeys – Javier Andrés Bargas-Avila (UX Director, Google)

A new way to look at applied experiments

Product survey findings: Only 15% of users are embracing AI features 

Building high-performing product teams: The PDLC approach

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

Overcoming the 20% feature usage challenge

Product Management

Three product leaders to learn from at #mtpcon inside Pendomonium

Emily brings nearly 15 years of product management experience to her role as Managing Director for Mind the Product. While she has worked across a variety of industries, she will always have a soft spot for the travel industry where she spent most of her early career building software for airlines and developing a leading consumer travel app, TripCase. Emily is passionate about the craft of product management and loves talking about new ways to make products people love.

Emily Tate

<p>Researchers often have concerns about what will happen when “other people” go out and do work with users. But the demand for research far outweighs the supply of researchers, and everyone wins when more people are enabled to do research themselves. At #mtpcon San Francisco, Steve Portigal, Principal at Portigal Consulting, tells us how to quickly level up our research skills as product managers across the lifecycle of a research effort.</p>
<p>Steve tells us how to be more effective in the three main elements of research: planning research, conducting research, and acting on research.</p>
<h2>Planning Research</h2>
<p>Ultimately, our goal is to learn from interactions with our customers. However, we typically focus on researching only if our product is usable or if people like the thing we’re making. In research we should be looking at broader questions, and proper planning will help ensure we are getting the answers that we need.</p>
<h3>What are we Trying to Accomplish?</h3>
<p>Research planning should include three areas:</p>
<ul>
<li>Business question: What challenge does the business face?</li>
<li>Research objective: What do we hope to learn to help us answer that business question?</li>
<li>Participant questions: What questions can we ask customers to help us achieve that research objective?</li>
</ul>
<p>We often skip straight to writing participant questions without addressing the other two areas, and end up with unfocused interviews that don’t fully get us the answers we’re looking for.</p>
<h3>How are we Going to Accomplish it?</h3>
<p>Steve highlights a few considerations when planning how to go about research.</p>
<ul>
<li><strong>What method of research should I use?</strong> It is easy to conflate “research” with “testing” and only focus on validating what we already have. But there are many research methods we can use.</li>
<li><strong>Who should I learn from?</strong> You don&#8217;t have to focus only on the people who are already using your product. Think about who else in the customer journey might have insights that could have an impact on your understanding of the customer&#8217;s needs.</li>
<li><strong>How should I interact with them?</strong> Remote work is easier than ever, so it is tempting to think using collaboration tools like Zoom or Skype are enough. But you learn so much by pushing yourself outside your comfort zone and interacting with people in <em>their</em> environment. Make sure you spend at least some portion of your research in the field.</li>
</ul>
<h2>Doing Research</h2>
<p>Steve provides some tips for talking to your customers once you&#8217;ve planned your research.</p>
<ul>
<li>Specific questions are better than general questions. The more specific you can be, the better a user will be able to answer.</li>
<li>Don&#8217;t ask users what they do. Ask them for an example of a time they have done something, and then ask if it was typical.</li>
<li>Ask follow up questions to get to specifics. If a user gives you general answers, asking for stories or examples will help you move beyond surface level and into deeper insights.</li>
</ul>
<p>He also highlights some common mistakes we make in understanding our role as an interviewer.</p>
<ul>
<li>Don&#8217;t provide the answer in the question. You may want to try to provide some examples to help guide the user, but this ends up tainting their response.</li>
<li>Don&#8217;t try to build rapport by telling the participant ways you are just like them. This removes the focus from the user and pulls it back to you. Hold off on sharing your experiences and just continue asking them questions.</li>
<li>Don&#8217;t become the expert. Users will often ask questions like: &#8220;Is this feature going to be in the next version?&#8221; Answering this, even if you know the answer, will change your role from researcher to expert and it is very difficult to get back into research mode. Ask: &#8220;Why is that important to you?&#8221; instead.</li>
<li>Don&#8217;t correct the user. You&#8217;ll have users mispronounce your product name, or ask for features you already have, or any number of things that you will want to correct them. Don&#8217;t do it. This, again, makes you the expert and harms the research.</li>
<li>Use the language they use. Don&#8217;t add acronyms they haven&#8217;t mentioned, or try to sound smart by using terminology they&#8217;re not using. Let them be the expert.</li>
</ul>
<p>Your goal in interviewing is to make the user comfortable. Your aim should be to move from &#8220;Question-Answer&#8221; to &#8220;Question-Story&#8221;. Continuing to ask questions and follow ups will help you build that rapport.</p>
<p>Steve also recommends recording your interviews. We can&#8217;t take notes fast enough to capture everything, so our notes become filtered versions of what we heard. Having a recording to return to gives you the full context and allows you to revisit the interview with fresh eyes.</p>
<p>When interviewing, it is important to avoid bias and try to look to new situations as learning. We also need to have empathy for the people we&#8217;re interviewing. But we are all human, and our own feelings can creep into our interactions. When you feel yourself moving into a judgmental mode:</p>
<ul>
<li>Hear your own judgement</li>
<li>Refute the assertion</li>
<li>Use new data to flesh out your new thinking</li>
</ul>
<p>Stress also hinders empathy. So make sure you plan your research in a reasonable manner so you&#8217;re not trying to do too much in too short a timeframe.</p>
<h2>Acting on Research</h2>
<p>Once you talk to people and write up your key takeaways, you are not done. Truly getting to new insights is a combination of analysis and synthesis.</p>
<ul>
<li><strong>Analysis</strong> is breaking out larger pieces into smaller pieces, such as breaking out the insights you heard in interviews.</li>
<li><strong>Synthesis</strong> is combining those smaller pieces into larger ones to gain new understanding, such as taking the insights from multiple interviews and bringing together common themes.</li>
</ul>
<p>When doing synthesis, you should go back to your business problem and what your stakeholders were looking for in the beginning. This will make sure you&#8217;re pulling the insights that will help answer the questions you were trying to understand. You should also make sure you&#8217;re presenting the information in a way that your stakeholders can consume to avoid research being dismissed.</p>
<p>Research is very important, but also very difficult. Being intentional in how you plan, do, and act on research will help to ensure you are get value out of the time you spend on it, and help you truly to understand your customers, and build products that solve their problems.</p>
<div class="g g-21"><div class="g-single a-170"><a class="gofollow" data-track="MTcwLDIxLDEsNjA=" href="https://www.pendo.io/pendomonium/"><img decoding="async" src="https://www.mindtheproduct.com/wp-content/uploads/2024/06/MTP-Footer_ad.png" /></a></div></div>

core/freeform

Product Management Conference

Product teams in flux – Pendomonium+#mtpcon roadshow: Berlin

AI in practice at Berlin’s leading companies – Pendomonium+#mtpcon roadshow: Berlin

AI in practice at Amsterdam’s leading companies – Pendomonium+#mtpcon roadshow: Amsterdam

Product teams in flux – Pendomonium+#mtpcon roadshow: London

AI in practice at London’s leading companies – Pendomonium+#mtpcon roadshow: London

What’s next for product management in 2024? Nichole Mace (SVP Product and User Experience, Pendo)

Navigating your product career – Ken Chin (CPO, Spark Networks)

Perspectives from an unconventional CPO – Yuelin Li (CPO, Onfido)

The future of product management – Trisha Price (CPO, Pendo)

The future of product management in 2024 and beyond (Brian Walsh, SVP Product, Pendo)

Great User Research (for Non-Researchers) by Steve Portigal

Emily Tate