Missed deadline logic tree
This logic tree separates a missed deadline into planning and execution causes. Planning asks whether the estimate and scope assumptions were realistic. Execution asks whether work was blocked or whether capacity, quality, or rework slowed progress. The distinction matters because adding people does not solve an unmade decision, and tighter tracking does not solve a poor estimate. Use actual milestone dates, change records, dependency logs, and defect data to test each branch. A good deadline review identifies the few causal factors that can be changed in the next plan, rather than assigning a generic cause such as poor communication. It gives readers a concise reference they can reuse when discussing the result with colleagues.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Schedule recovery
Key decisions
- Plan: Test estimates and scope assumptions.
- Execution: Test blockers and delivery capacity.
- Learning: Record the evidence before revising the next plan.
When to reuse this
Use in a project retrospective or a schedule-recovery review.
Frequently asked questions
What is a planning cause?
What is a blocker?
Should the tree assign blame?
More project-management examples
Try the diagram makers.
Tweak it with chat, export PNG/SVG, or fork it for your own use case.