Audit Discovery Data for Bias and False Positives
The founder systematically examines the discovery questions asked and responses received to flag leading prompts, polite agreement, and unrepresentative sampling. They isolate instances where enthusiasm was mistaken for genuine urgency or willingness to pay.
Completing this action isolates corrupted or unreliable data points caused by poor questioning or flawed sampling. It prevents the venture from building strategy on false validation, directly safeguarding capital and resource allocation.
The founder must deliver an annotated discovery log highlighting leading questions, hypothetical queries, and false-positive commitments. The output must clearly classify data points as high-risk, compromised, or methodologically sound.
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
Where in your interview scripts did you ask leading questions that implicitly prompted the participant to validate your solution?
- 2
How many of your 'validated' customer problems rely on prospective statements about future behaviour rather than past actions?
- 3
What evidence proves your interview sample represents actual economic buyers rather than overly polite, unrepresentative friendly contacts?
- 4
How did you filter out false positives caused by participants trying to avoid hurting your feelings during discovery sessions?
- 5
Which specific responses were categorised as positive signal despite lacking evidence of actual pain or willingness to pay?