Summary: How product managers observe and listen to users to gain valuable insights.<br> How do you know what products you should build? What products will delight customers? The answer isn’t a mystery and has been expressed by numerous past guests. One that stands out is Ben Brenton, <a href="https://productinnovationeducators.com/blog/tei-120-product-development-and-management-at-snap-on-with-ben-brenton-phd/" target="_blank" rel="noopener">Chief Innovation Officer at Snap-on Tools</a>, who shared that he takes their product teams to meet with customers four days a week. That is the recurring theme–time with customers to understand what will delight them. It is often expressed as voice of the customer, or VoC, research.<br> My guest has put VOC into practice with great results. She is the Senior Director of Product Management for TeamMate and an award-winning product manager. We discuss VoC tools and the specifics for how product managers can use them, including:<br> <br> * Contextual interviews<br> * Budget-minded usability testing.<br> <br> <br> Summary of some concepts discussed for product managers<br> [2:30] What is your product and who is it for?<br> The product is called TeamMate. It’s a tool to help teams with transparency, consistency, and efficiency in their internal audit process. It’s used by large and small public and private organizations around the world. Internal audit is an independent and objective evaluation of the business organization.<br> [4:50] What tools do you use for Voice of the Customer research?<br> We get feedback from our professional services team when they are implementing the product to new clients, from the sales team when they are doing demos, and from trade shows. We also do surveys and usability testing and hold user conferences around the world. Our biggest conference draws 700-800 customers and includes a usability lab where customers can evaluate prototypes of things we’re thinking about doing. We also run focus groups and are able to get a lot of meaningful feedback in a short amount of time.<br> [7:38] How do you apply contextual inquiry to your work?<br> This is a tool we use when a concept can be open to multiple interpretations. At first, we’re trying to nail down a pain point and we’ll use surveys to do that. From those survey results, we’ll choose customers to go on site and visit. We always send two-person teams, one person who is an active interviewer and someone else who takes notes, pictures, and videos. We want the customer to walk us through the process or pain point, not just tell us. What we find is that what people tell you doesn’t always match with what they actually do.<br> [10:58] What do you do with all of the information you collect on those site visits?<br> Our teams write up their notes but keep the language that the clients used in the interview. We set up an affinity wall that informs the problems we’re trying to solve in the new release or feature. Sometimes those pain points are things that are never spoken aloud. One example of this was a client who had built a knowledge base that she was convinced would transform her team’s process. We got about halfway through and she forgot where she was in the process after she was interrupted by a coworker. We learned that it wasn’t easy to cancel the process and start over again and that led to adding contextual awareness to the next version of the knowledge base. It wasn’t a problem that was identified up front, but something we identified through the contextual inquiry process.<br> [16:11] Do you ever utilize phone calls or web meetings?<br> We do occasionally, but we’ve found that it’s invaluable to sit in front of someone and watch how they work. It’s difficult to replicate over a phone call or web meeting. You can’t really get a sense of someone’s environment and without ...
