How Exceptional Product Managers discover unmet customer needs
summary
Has done 500+ interviews across 10 countries and reports product teams that generated between $300M and $10B. Recommends spending 10x more time digging into problems than sketching solutions, using open-ended scripts, observing customers in their environment, and validating qualitative findings with surveys. Targets for discovery are 5–12 customers to capture about 70% of needs. Uses tooling like order.ai to record and transcribe sessions, avoids leading questions and friendly-only customers, and warns not to interview prospects in the sales funnel.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 3:51The role of a product manager
- 5:50Compelling problems
- 6:18Competition
- 6:51Becoming profitable
- 7:34Being an agile expert
- 9:01Why new products fail
- 9:36Unmet customer needs
- 10:17Dont build products based on ideas
- 11:46Why is this a bad idea
- 13:14Dont visit the same friendly customers
- 15:08Ask questions leading questions
- 17:08Discover unmet customer needs
- 19:16Deepen understanding customer problems
- 21:42Create a discussion guide
- 23:27Example
- 24:28Understand how they solve the problems
- 24:47Willingness to pay
- 25:42Observe the unspoken
- 26:24Make it a habit
- 27:14Words of caution
- 27:33Qualitative research
related talks
29mWhat 200+ PMs Taught Us About Product Management in Real Life
44mPressing questions in Product Management
39mWhat does a 'good' product manager look like, anyways?
59mProduct Manager or Unicorn
01h 00mCracking the Product Manager Interview
51mCareer In Product Management
38m"Who do I innovate for?" A Product Manager's perspective!
52mFueling Innovation: Embracing a Product Mindset for Non-Product Heads