Problems vs. Solutions
Intro to Problems vs. Solutions
- PM 101: Define the Problem Before the Solution
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.
How to Define Problems
- A Three-Step Framework For Solving Problems 👌
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.
Mapping Problems to Solutions
- That’s Not a Hypothesis
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.
- Discovery – Problem vs. Solution
Marty argues that you need to spend as much, or more time on defining a solution than on mapping out a problem space, because "the vast majority of product efforts fail not because of demand, but because they can’t come up with a solution good enough to get people to switch." He then argues that defining solutions needs to be a collaborative process between product, design, and engineering.