Clarify the Intent of Problem Identification
Frame the precise scope of this intervention to avoid vague customer complaints and isolate a single painful operational friction. Define clear success criteria and boundaries for the problem-scoping exercise before collecting market data.
Defining the task scope prevents the founder from pursuing broad, untreatable market observations. It establishes clear boundaries for the Problem Identification Stage, ensuring all subsequent validation work directly supports a razor-sharp venture hypothesis.
The founder produces a written mandate defining the exact problem domain under investigation and explicit criteria for passing this stage. This document must state what is explicitly out of scope for the current sprint.
Five questions an expert would ask when reviewing your output
Use these to challenge assumptions, pressure-test your logic, and check the quality of this action's output in the context of the parent task and wider venture development.
- 1
Why have you chosen to bound this specific problem area rather than addressing the wider workflow?
- 2
What concrete failure criteria will tell us that this problem is too trivial to build a venture around?
- 3
How does isolating this specific friction fit into your broader thesis for the sector?
- 4
What prior assumptions about this problem domain are you deliberately setting aside for this intervention?
- 5
Where does this problem definition draw the line between a minor operational inconvenience and an existential business risk?