Map Operational Triggers, Business Rules, and Exceptions
The founder systematically maps the end-to-end user and system steps, detailing explicit decision logic and business rules at every junction. They identify potential failure points, system timeouts, and edge cases that could break the operational flow.
Completing this action exposes all hidden operational logic, conditional paths, and system failure modes before writing code. It guarantees that the MVP architecture accounts for real-world complexity, preventing costly mid-build rewrites.
A detailed flowchart or logic matrix detailing every state transition, conditional decision gate, automated action, and manual fallback. The output must explicitly document at least three non-happy path edge cases and their respective remediation loops.
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 precise triggering event initiates this workflow, and what system checks must occur before proceeding?
- 2
Which business rules within this flow rely on unvalidated assumptions about user behaviour or external systems?
- 3
How does the system gracefully handle unexpected user drop-off or external API failures at each step?
- 4
What is the highest-volume edge case you have identified, and why is your proposed resolution optimal?
- 5
Where in this sequence does manual intervention become necessary, and how does that impact scalability?