Problem-First Curiosity Rule
Discover real problems before committing to a solution
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 97%
The Problem-First Curiosity Rule contrasts two innovation postures. An intellect-first posture begins with something the creator knows how to build and then searches for people who might accept it. A curiosity-first posture explores behavior, anomalies, frustrations, and emerging use cases until a meaningful problem becomes visible. Only then does the creator design or adapt a solution. The process reduces attachment to an initial idea and makes surprising evidence useful rather than inconvenient. Justin TV illustrates the mechanism: broad experimentation exposed strong gaming behavior, which supported a more focused streaming product. The reusable rule is simple: do not ask where your solution can be inserted; ask what people need solved and let evidence shape the solution.
Origin
Extracted from Marketing Against The Grain through the hosts' contrast between carrying a solution into the market and using curiosity to discover problems worth solving.
Core principles
- 01Start with observation rather than a predetermined answer.
- 02Treat unexpected behavior as evidence of an unmet need.
- 03Use curiosity to uncover problems people already experience.
- 04Delay commitment to a solution until the problem is understood.
- 05Economic value follows useful problem solving.
How to run it
- 1
Suspend the solution
Set aside the product or tactic you are predisposed to use so it does not dictate what you notice.
Pro tip Write down your preferred solution and explicitly label it as a hypothesis.
Watch out Hidden attachment can make every observation look like validation.
- 2
Observe behavior
Look for repeated workarounds, frustrations, unusual adoption patterns, or communities using tools in unexpected ways.
Pro tip Behavior is often stronger evidence than stated preferences.
Watch out Do not generalize from a single colorful anecdote.
- 3
Ask why repeatedly
Investigate why the behavior occurs and what outcome people are actually trying to obtain.
Pro tip Separate the immediate complaint from the deeper desired outcome.
Watch out Stopping at the first explanation may produce a superficial problem statement.
- 4
Validate the problem
Confirm that the need recurs across people or situations and matters enough to motivate action.
Pro tip Look for existing time, money, or effort already spent on workarounds.
Watch out Interest in discussing a problem is not the same as demand for solving it.
- 5
Shape the solution
Design the smallest response that addresses the validated problem, then let results guide further development.
Pro tip Preserve flexibility until a reliable use pattern emerges.
Watch out Avoid adding features unrelated to the demonstrated need.
In the wild
Justin TV began with a broad live-streaming experiment. After the service opened to more users, the team noticed that people particularly liked streaming games and commenting on them. That observed behavior informed the pivot toward Twitch.
→ A curiosity-led experiment revealed a focused community problem and supported a billion-dollar category.
A software team notices customers exporting data every Friday and rebuilding the same report in spreadsheets. Instead of promoting an unrelated dashboard feature, the team studies the workflow and creates a scheduled report around the repeated need.
→ Observed behavior leads to a solution tied to an existing problem.
Common mistakes
Searching for excuses to build
Treating a preferred solution as inevitable turns discovery into confirmation theater.
Mistaking novelty for need
An unusual behavior is only an opportunity after its underlying problem and recurrence are established.
Ignoring inconvenient evidence
Signals that contradict the original thesis may reveal the strongest opportunity.
Is it for you?
Best for
It is best for founders, product teams, marketers, and creators exploring uncertain opportunities.
Not ideal for
It is not ideal when the problem and required solution are already fixed by regulation or a precise specification.
From the transcript
“You have a solution and you go looking for a problem.”
“When you're curious, you are out there trying to discover a problem that needs solved.”
“Go out there, be curious and find problems and go solve those problems.”
From the episode
Curiosity is a Billion Dollar Skill