Audit Technical Inputs and Market Evidence
Collate all existing experimental data, TRL assessments, freedom-to-operate reviews, and customer discovery findings relevant to the target application. Identify missing evidence gaps and assemble the requisite technical and commercial domain experts.
Gathering these verified inputs grounds the intervention in rigorous empirical reality rather than founder optimistic bias. It establishes a trustworthy baseline against which progress and technical translation can be objectively judged.
Compile a structured Input Inventory containing verified lab logs, IP assessments, third-party benchmark reports, and documented customer interviews. Highlight explicit evidence gaps that require immediate testing or external validation.
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 gathered data points rely on internal testing versus independent third-party validation?
- 2
How recent and reproducible is the experimental evidence supporting your core technical claim?
- 3
What critical assumptions in your data room lack empirical backing from external pilots?
- 4
How robust is your freedom-to-operate assessment around this specific technical application?
- 5
What key technical or commercial inputs are currently missing, and how will their absence skew your decision?