Missed Deadline Logic Tree

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.

유형 의사결정 트리표준 Howard-Raiffa / CART-sklearn / taxonomy엔진 schematex-decisiontree업데이트됨 2026. 9. 24.

요청 내용

“A logic tree for a missed project deadline: split into Plan and Execution, then include estimate realism, scope changes, dependencies, approvals, capacity, quality, and rework.”

그렇다면Add a supplier dependency branchAdd a decision date to every blocked-work outcome

이 도면에 담긴 내용

그 이면의 의사결정을 읽어 보세요.

01Plan

Test estimates and scope assumptions.

02Execution

Test blockers and delivery capacity.

03Learning

Record the evidence before revising the next plan.

Use in a project retrospective or a schedule-recovery review.

모든 의사결정 트리 템플릿 보기 →

자주 묻는 질문

What is a planning cause?

An issue in estimates, scope, staffing assumptions, or sequencing before work began.

What is a blocker?

A dependency, decision, approval, or constraint that prevents progress.

Should the tree assign blame?

No. It should organize evidence about conditions and decisions.