Turn discovery notes into problem statement
ent-problem-statementskillsetup L1★1
kalyvask/entrepreneurship-lessons ↗What it does
Turn discovery notes into defensible one-page problem statement
Best for
When a founder has finished a discovery batch and needs to crystallize one sharp problem before designing a solution.
Inputs
- · customer discovery notes, interview transcripts, 3+ named desperate customers with behavioral markers
Outputs
- · 1-page problem statement (who, pain, trigger, frequency, magnitude, alternatives, desperation evidence)
Preconditions
Completed 10+ customer discovery interviews; identified desperation markers in notes
Failure modes
- · Lists 5 pains instead of one (unfocused)
- · Desperate customer is vague ('companies like X' instead of named individuals)
- · Evidence is stated enthusiasm, not behavioral (pre-pay, workaround, unprompted pain)
Trust signals
- · Enforces single pain with highest frequency × magnitude × desperation
- · Three whys cross-check (why solve anything, why now, why you)
- · Evidence audit flags any claim without behavioral proof