Identify Assumptions Constraints and Dependencies
Identify the critical assumptions regarding team capacity, operational constraints, and technical dependencies required to sustain the operating cadence. The founder explicitly audits tooling requirements, leadership bandwidth, and cultural readiness before implementation.
Articulating assumptions and constraints exposes hidden operational risks that could disrupt team momentum. It protects the parent task by ensuring the designed cadence is realistically executable given the venture's resource limits.
The founder must produce an exhaustive inventory of operational assumptions, key tool dependencies such as reporting dashboards, and bandwidth constraints. This must highlight potential single points of failure across key team members or missing data pipelines.
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 critical reporting or data dependency is currently missing that could undermine your weekly performance review?
- 2
Which key leadership role represents a single point of failure in maintaining this operating rhythm?
- 3
Why do you assume your team has the capacity to prepare required pre-reads without impacting customer delivery?
- 4
How does your cadence adapt if key leadership bandwidth is suddenly consumed by an unexpected crisis or fundraise?
- 5
What cultural constraints or past team behaviours pose the greatest threat to adhering to this rhythm?