Identify Critical Path Bottlenecks and Priority Gaps
Analyse the visual register to pinpoint single points of failure, redundant feature assumptions, and high-risk gaps where evidence is weakest. The founder prioritises the sequence of product validation experiments based on where risk and dependency intersect most acutely.
Highlighting critical path bottlenecks isolates the exact assumptions that pose existential risk to the product build. This empowers the team to allocate scarce technical resources directly to high-leverage risk reduction activities.
A prioritised action list derived directly from the matrix highlighting top-priority assumption gaps, single points of failure, and recommended validation tests. The output must include clear risk ratings and actionable next steps for each critical node.
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 is your plan if the highest-priority assumption on this critical path fails during testing?
- 2
Where are the major evidence gaps where high technical dependency coincides with zero empirical proof?
- 3
How did you decide which assumptions represent redundant feature overlap that can be pruned immediately?
- 4
Why have you prioritised validating an easy UI assumption over a complex backend data dependency?
- 5
How does this prioritised sequence alter your immediate sprint roadmap and capital expenditure plans?