Catalogue Assumptions Constraints and Operational Dependencies
Systematically extract every underlying assumption regarding customer behaviour, problem severity, and access logistics. Highlight resource, legal, regulatory, or timing constraints that could impede execution or skew evidence gathering.
Isolating unvalidated beliefs and operational blockers exposes the fragile elements of the discovery strategy before fieldwork begins. It prevents wasted momentum by ensuring critical dependencies and compliance hurdles are addressed proactively.
A prioritised matrix categorising assumptions by impact and risk level, coupled with a transparent list of delivery constraints and access dependencies. The record must clearly indicate which assumptions, if proven false, completely destroy the venture value proposition.
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 single assumption, if invalidated tomorrow, renders this entire venture concept unviable?
- 2
What regulatory, compliance, or privacy constraints restrict your ability to record or utilise customer data?
- 3
How have you accounted for founder bias when categorising an item as an established fact versus an unproven assumption?
- 4
What operational dependencies could bottleneck target recruitment, and what back-up sourcing channels exist?
- 5
How do you plan to stress-test financial willingness-to-pay assumptions without pitching a premature solution?