Solution-Weighted Discovery
Spend a little time validating the problem; spend most of it winning on the solution
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 90%
Cagan splits discovery into problem discovery and solution discovery, then argues most teams misallocate their budget between them. Because customers buy solutions, not problems, and because competitors are already solving the same problem, the differentiating work is solution discovery. When the founder and most of the company already know the problem, spending weeks re-validating it burns the clock and frustrates leadership without moving you closer to winning.
Origin
Marty Cagan / SVPG coaching. He connects the solution-discovery emphasis to Steve Jobs's description (in the 1995 'Lost Interview') of holding 5,000 things in your head — that, Cagan says, is solution discovery.
Core principles
- 01People don't buy the problem, they buy your solution.
- 02Many products solve the problem your customer cares about; you win only by solving it better.
- 03In the real world the clock is ticking — problem-validation time is time not spent on the winning solution.
- 04Solution discovery is where teams succeed or fail.
How to run it
- 1
Separate the two discoveries explicitly
Name which one you are doing: discovering which problem to focus on, or discovering the solution you'll ship. Teams that blur them default to endless problem work.
- 2
Check who already knows the problem
Ask whether the founder and the company already have high confidence in the problem. If they do, you are re-deriving what leadership already knows, and every week spent doing so is a week of frustration and delay.
Pro tip If leadership's problem conviction is strong, timebox validation to days, not weeks.
Watch out Don't confuse 'the founder is confident' with 'the founder is right' — the test is whether more validation would actually change what you build.
- 3
Timebox the problem, then move
Spend a little time on the problem if you need to, but deliberately preserve the maximum amount of time for solution discovery. The budget, not the activity, is the decision.
- 4
Pour the remaining time into beating every alternative solution
Frame the solution question competitively: many products already solve what the customer cares about, so the only question is whether you solve it better than everybody else. Prototype, test with users, customers, stakeholders and engineers, and iterate.
Pro tip Treat every iteration as a trade-off exercise — Jobs's point that a product starts one way and ends up another is the normal shape of solution discovery, not a sign of failure.
In the wild
A team, believing problem validation is mandatory, spends weeks confirming that customers really have a problem the founder and most of the company already knew about. The founder becomes frustrated because no work has started on the solution.
→ The team burns its only scarce resource — time — on confirming a known premise instead of on the solution work that actually determines whether the product wins.
In the 1995 Lost Interview, Steve Jobs describes the craftsmanship of going from an idea to a product — holding thousands of considerations in your head, making trade-offs with each iteration, so the thing starts one way and ends another. Cagan identifies this as a description of solution discovery.
→ Cagan uses it to show that solution discovery, not idea generation or problem validation, is where product outcomes are actually decided.
Common mistakes
Mandatory problem validation as ritual
Teams treat weeks of problem validation as a required stage regardless of how much conviction already exists. In an unconstrained world it costs nothing; in the real world the clock is ticking and it steals time from the work that differentiates you.
Believing a validated problem means a winning product
Cagan: 'there are many products that are solving what they care about — the real question is do you solve it better than everybody else so that they buy you.' Problem-market fit is table stakes; the solution is the differentiator.
Is it for you?
Best for
Product teams in competitive markets with a founder or leadership team that already has strong conviction about the problem
Not ideal for
Genuinely novel domains or new market entries where the problem itself is unproven and mis-picking it would waste the entire solution effort
From the transcript
“people don't buy the problem they buy your solution”
“the real question is do you solve it better than everybody else so that they buy you and that's where you need to take time”
“if you need to spend a little time on the problem fine but don't spend a lot”
“discovery right there's so there's discovering the problem to solve that you should focus on and discovering the solution that you're going to deliver that…”
“if you use say two weeks of just verifying the same thing the founder already knew that founder is probably very frustrated”
“the whole craftsmanship of going from an idea to a product this is what we call product discovery”
From the episode
The nature of product
Marty Cagan, Silicon Valley Product Group