By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres asked members of the Continuous Discovery Habits community to share early mistakes they made when adopting continuous discovery. Three practitioners describe their missteps: a PM who ran discovery without bringing executives along, a PM who pushed for customer interviews without first earning stakeholder trust, and a VP of Product who tried to implement every discovery practice at once. The article matters because it shows that discovery failures are common and mostly stem from communication, change management, and pacing rather than the methods themselves, and that recognizing these patterns early can save teams trouble.
01Key takeaways
- Communicate discovery results and their potential value to decision-makers early, not just the final recommendation.
- Explain the purpose of customer interviews to stakeholders before pushing to start them, and address their concerns seriously.
- Challenge stakeholder assumptions respectfully, since they may know the domain but not how to build successful products.
- Build opportunity solution trees from actual customer input rather than internal guesses about needs.
- Adopt continuous discovery incrementally, focusing on a few habits per quarter instead of everything at once.
- Test assumptions with cheap, rapid methods like prototypes rather than jumping to building an MVP.
02Key sections
- Communicating discovery results
- Leann Schneider ran discovery beyond the solution executives requested and found opportunities they didn't expect. Her lack of stakeholder communication led to resistance until a designer packaged the findings visually.
- Earning trust for customer interviews
- Sebastian Wramba pushed hard for weekly customer interviews without explaining the goal to a skeptical organization, which backfired. He learned to take stakeholder concerns seriously while still challenging their assumptions.
- Pacing the adoption
- Jelena Stajic tried to implement every continuous discovery element at once, overwhelming her team. She also built an opportunity solution tree from internal guesses rather than customer evidence.
- Testing assumptions versus building MVPs
- Jelena realized that testing assumptions differs from building minimum viable products, and her team shifted toward rapid prototype tests and simulations.
- Focusing on a few habits at a time
- Jelena recommends starting with core practices like interviewing and opportunity solution trees, then choosing one to three areas to improve each quarter.
03From the post
“You’ll often hear Teresa say that there’s no single right way to do continuous discovery. Something she might not say as often (that’s just as true) is that there’s no single wrong way to do discovery, either. Because discovery involves changing the way you work on”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.