Discovery – Learning vs. Insights

Marty Cagan, who popularized the term product discovery, clarifies a common confusion: learning is valuable, but the real goal of discovery is to gain insights, which are learnings a team can act on. He explains that most discovery work reveals that a solution doesn't work, and only occasionally yields insights that fix the problem, shift strategy, or even trigger a vision pivot. He then argues that the purpose of a product team is not to learn but to solve hard problems customers love and that work for the business. Learning is only the means. Teams often become enamored with techniques like personas, design thinking, or jobs-to-be-done without turning them into outcomes. He concludes that OKRs should measure business results, not learning activity, and discussions with leadership should center on insights and results.

01Key takeaways

• Treat discovery as a search for insights, meaning learnings you can actually act on, not just accumulated knowledge.
• Expect most discovery work to show your solution is not working well, and use that as a cue to look for the fix.
• Escalate insights with broad impact into product strategy, and recognize rare profound insights as grounds for a vision pivot.
• Remember that learning is the means; the team succeeds only when it solves the customer's problem in a way that works for the business.
• Avoid falling in love with any single technique; judge it by whether it leads to successful products.
• Set OKR key results around business outcomes rather than measures of how much the team is learning, and frame leadership discussions around insights and results.

02Key sections

Defining the problem with discovery

Cagan notes that discovery has broadened from requirements gathering to collaborative solution finding, but rebranding and confusion have crept in.

Learnings versus insights

Insights are learnings that can be leveraged; discovery mostly produces evidence that solutions fail, with occasional fixes, strategic insights, or vision pivots.

Learning is the means, not the end

A product team's purpose is to solve hard customer and business problems, so being good at learning alone does not make a strong team.

Techniques should serve outcomes

Personas, design thinking, jobs-to-be-done, and Agile can all add value, but teams often obsess over the technique instead of the problem.

Keep OKRs on business results

Teams should not make learning activity their key results; key results should reflect business outcomes.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

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