Structured Failure Analysis

Origin. The structure appears across traditions. After Action Review (Western military), Hansei (Japanese reflective practice), Five Whys (Toyota). The pattern persists because experience does not automatically become learning — humans confabulate, blame, rationalize. Correct lessons require structured extraction.

Mechanism. Outcomes happen but lessons do not self-extract. Without structure, post-outcome reflection produces vague insights, blame assignment, or comfortable narratives that protect ego. Structured analysis forces a causal walk: what was intended, what occurred, why the gap, what changes. The structure prevents collapse into either excuse-making or blame. The discipline is evidence-based gap analysis, not storytelling.

Procedure. Convert experience into actionable lessons through systematic gap analysis. (1) State the intended outcome explicitly — what was supposed to happen. (2) State the actual outcome — what did happen. (3) Analyze the gap through systematic questioning — trace causation without assigning blame. (4) Identify specific, actionable lessons — not vague resolutions but concrete changes. (5) Institutionalize the changes — modify procedures, train, update documentation. The discipline is maintaining the causal walk without collapsing into narrative.

Applies to. Post-project review. Incident analysis. Any situation where outcomes have occurred and lessons should be extracted. Learning from failure. Learning from success (which also requires analysis — success can happen for wrong reasons).

Limitations. Requires psychological safety — if people fear blame, they hide information. Requires honesty about what was actually intended (post-hoc revision of intentions defeats the method). The causal walk can become mechanistic ritual if not genuinely pursued. Some outcomes have causes too complex or too external to yield actionable lessons.