Audit Signals to Separate Fact From Assumption
The founder reviews every data point and conclusion within the scorecard to categorise inputs as verified evidence, weak signals, or unproven assumptions. They rigorously test whether positive signals are backed by repeated user behaviour or merely optimistic qualitative feedback.
This action purges unverified founder bias and false positives from the diagnostic process. It ensures the resulting strategic decisions are anchored purely in demonstrated market behaviour.
The founder must submit an Evidence vs Assumption Register detailing the source and validation strength for every key insight. Every claim of customer delight or market pull must be tied to behavioural data or contract renewals.
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
Which key claims in your PMF narrative rest entirely on interview quotes rather than contract renewals or product usage?
- 2
How do you know that customer retention was driven by product value rather than high switching costs or inertia?
- 3
What assumptions regarding customer acquisition cost are disguised as validated metrics in your data?
- 4
How have you stress-tested the assumption that your strongest customer segment is large enough to support your target scale?
- 5
Where have you mistaken pilot enthusiasm for long-term commercial intent?