How Can Product Leaders Support Continuous Discovery?

In a fireside chat at the Product at Heart Leadership Forum, Teresa Torres and Petra Wille discuss how product leaders can help teams adopt continuous discovery. Torres frames discovery as the work of deciding what to build, structured around outcomes, customer opportunities, and rapid assumption testing. She argues the biggest barriers are often organizational: unclear strategy, limited customer access, and lack of interviewing skill. Her core advice is to avoid extremes of doing no discovery or endless research, to keep delivery cadence intact while building weekly habits, and to start with small changes rather than ideological battles. The conversation matters because it gives leaders concrete levers beyond individual contributor practice.

01Key takeaways

• Frame discovery as continuous decision-making about what to build, not a phase before delivery.
• Keep delivery cadence as a constraint while building weekly discovery habits such as customer conversations and assumption tests.
• Communicate strategy concretely: name target customers, value propositions, and the exceptions that deviate from the plan.
• Help individual contributors see how customer value connects to business value and revenue.
• In resistant organizations, start with the smallest habit that fits current appetite for change, not a full framework rollout.
• Avoid ideological battles over labels; focus on the practice and the fast feedback loops it produces.

02Key sections

Defining Product Discovery

Torres describes discovery as the work of deciding what to build, with customers included through feedback loops and assumption testing. Discovery is contrasted with delivery, which builds and maintains the product.

Structuring Discovery Around Outcomes

Torres outlines her structure: start with a desired outcome, map customer opportunities that drive it, then find solutions and test assumptions. Barriers at each level include unclear strategy, limited customer access, and missing tools and skills.

Getting Access to Customers and Reliable Feedback

Torres argues talking to customers is just human conversation that organizations overcomplicate. She stresses that reliable interviewing requires learning to ask non-leading questions that reflect actual behavior.

Avoiding Extremes and Keeping Delivery Going

Teams new to discovery often either research endlessly without shipping or ship without learning. Torres recommends keeping delivery cadence as a constraint and building consistent weekly discovery habits.

Strategic Context and Business Value

Torres emphasizes that leaders must define and repeatedly communicate strategy, including target customers and value propositions. She also argues teams need to connect customer value with business value and understand how the company makes money.

Audience Questions

Answers cover handling people who do not grasp strategy, starting discovery in feature-factory organizations with small steps, upskilling teams, and avoiding ideological debates over labels and frameworks.

03From the post

“In addition to delivering a keynote at the Product at Heart conference (in case you missed it, you can find the video and transcript of that presentation here), conference co-organizer Petra Wille also invited me to participate in a fireside chat at the Leadership Forum event. We discussed a”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.