Problems vs. Solutions

Jens-Fabian explains how delivering a product that solves user problems requires understanding the problem first, writing it down, and getting cross-functional buy-in that this is the right problem to work on.

Lenny provides a process for how to construct problem statements, with examples for good and bad versions. He then provides insights on how to build Alignment across teams around the problem statements, and how to make sure you continuously pay attention to the problem and whether you're solving it.

Shishir explains how to frame problems, and provides 3 techniques for expert framing: eigenquestions, diagramming, and leveraging your team's input.

Tal explains why hypothesis statements are important - "clear learnings come only from clear hypotheses." He then goes on to explain where they come from, how to add support to them, and how to use them as connections between problems and solutions.

While many product teams separate product discovery into problem space and solution space, Marty argues that breakthroughs often happen when we break down that wall. With technology products, exploring potential solutions deepens your understanding of the problem in unexpected ways. Marty claims that most product efforts fail due to lacking a good enough solution, not lack of demand. Therefore, teams should spend most of their discovery time on developing the solution through collaboration between product, design and engineering. Great products come from the interplay between value, Usability and feasibility, not just defining the problem for engineering to solve.