Disentangle Empirical Signals from Founder Assumptions
Audit the rationale behind each diagnostic score to separate validated skill demonstrations from unverified assumptions. Categorise each capability assessment into proven track record data or unsubstantiated self-belief.
Completing this action eliminates self-delusion from the founder baseline by enforcing strict standards of proof for every claimed competency. It protects the venture from critical operational failures caused by unexamined blind spots, directly enhancing the quality of data-room assets.
The founder must produce a two-column audit table explicitly separating verified evidence signals from unproven assumptions. Each claim marked as evidence must cite a verifiable, third-party artefact or objective milestone metric.
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
What tangible artefact proves that this specific capability is an evidenced signal rather than an optimistic assumption?
- 2
How have you stress-tested the assumption that your prior industry network translates into founder-led sales ability?
- 3
Which score relies most heavily on self-reported preference rather than observed operational performance?
- 4
Why do you treat advisor endorsement as validated capability when execution remains unproven?
- 5
How would removing all assumption-led ratings alter your overall capability baseline score?