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

Dilip Chetan is a research leader with experience in helping develop a broad array of products. Using insights gleaned from research, he guides companies in broadening their customer base and increasing their revenue by leveraging product strategies tailored to meet market needs. He also trains Product Managers in conducting research on their own. Check out his award-winning book "Ignite Your Research Mojo" on Amazon.

Dilip Chetan

<p>Even the most creative product manager in the world would do well to get direct input from their customers now and again. Interviewing your customers is the best way to keep track of the market. Often, your customers will tell you things you haven’t even thought about. They are also likely to tell you some things you know, but they may frame them in ways you’ve never thought of before. The value of anecdotes from customers is captured in this quote:</p>
<blockquote><p>The thing I have noticed is when the anecdotes and the data disagree, the anecdotes are usually right. <cite>Jeff Bezos</cite></p></blockquote>
<p>Before you start interviewing your customers, keep this in mind  &#8211;  the success of a customer interview hinges on one crucial technique, and the sooner you master it, the better off you’ll be. What is it?</p>
<p><em>Listening.</em></p>
<p>That’s what you do in an interview, you listen. Most people think an interview is all about asking questions. But if you don’t listen, why bother asking questions?</p>
<p>In order to listen of course, you need to get the customer talking. And in order to do that, you need to ask good questions. Here’s a quick overview of how you can conduct an effective interview.</p>
<h3>Before the Interview</h3>
<ul>
<li><strong>Know your participants</strong> before you do the interview. Do some research on them, look them up on LinkedIn and Google them.</li>
<li><strong>Define clear goals</strong> of your interview and align your interview questions to these goals. Make sure your questions yield answers that are actionable. And watch out for leading questions (questions where you <em>lead</em> your participant to answer in a particular way).</li>
<li><strong>Pilot the questions </strong>with some test subjects first. Believe me, you’ll have plenty of changes to make after your pilot.</li>
</ul>
<h3>During the Interview</h3>
<ul>
<li><strong>Your interview is a conversation</strong>, not just a Q&amp;A. And while you have to make sure you stay on target, you should also have enough flexibility built in to allow your participants to freely express themselves. Let them talk. That’s where the interesting insights come from. Make them feel comfortable. Remember that legendary smile of yours? It’s a good time to flash that!</li>
<li><strong>Keep your goal in mind</strong> at all times. Don’t get distracted. Your participant doesn’t know your goals, but you do. They can stray wherever they want but you need to bring them back.</li>
<li><strong>Watch out for biases</strong>. I could write a book about this  but I’ll follow my own advice and stay focused. I will tell you this &#8211;  if you don’t think you’re biased, think again</li>
<li><strong>Never do an interview by yourself</strong>. Have a note-taker with you. It could be a designer or an engineer. Involving them in the interview will make your job that much easier.</li>
</ul>
<p>How many interviews should you conduct? I’d recommend a minimum of 6–8 per user type. With interviews, you can keep doing them until you reach “knowledge saturation” &#8211; until you feel that you’re not learning anything new any more.</p>
<h3>After the Interview</h3>
<ul>
<li><strong>Have your team with you when you begin your analysis</strong>. You are still the owner of this research study and it’s up to you to ensure that the findings from your interviews are actioned. But it’s also your responsibility to make sure other stakeholder perspectives are considered, and not just your own.</li>
<li>Remember that <strong>every interview is like a case study</strong>. This is a qualitative technique, so technically, you can’t aggregate your findings. You should never represent findings from an interview in the form of percentages, because your sample size is too low. But you can look for patterns, in fact that’s where interviews are most useful. They go deep into causal factors. And while you want to retain the richness of information, you also want to identify patterns. That’s when the interview findings become actionable.</li>
<li>Lastly, make sure that you <strong>come up with a plan to act on what you find</strong>. This goes back to the goal of the interview (the very first step). You need to tie everything you find back to the original objectives of the interview. Your research isn’t complete until your findings make it into your backlog.</li>
<li>To finish up, make sure you<strong> produce a report </strong>on what you did and save that for posterity. It doesn’t have to be a detailed report. Just enough that people who read it know what happened and how certain decisions were made.</li>
</ul>
<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>

Want to be a More Effective Product Manager? Interview Your Customers

Dilip Chetan

Comments

Read next