Stop causal reasoning at process/structure level in post-action reviews — never at personal adequacy or character level

Why This Is a Rule

Post-action reviews have two possible endpoints for causal reasoning. Process level: "This output was late because the review stage took 5 days instead of 2, and the review stage was slow because the gate criteria weren't defined so I kept re-reviewing." This terminates at a structural cause and suggests a structural fix (define gate criteria — Check 3-5 yes/no gate criteria at each pipeline stage transition — any "no" keeps the output in its current stage until addressed). Character level: "This output was late because I'm bad at time management / lazy / not disciplined enough." This terminates at an identity judgment and suggests no fix — you can't structurally improve "being a bad person."

The character-level endpoint is a causal reasoning trap: it feels like an explanation but produces no actionable improvement. "I'm lazy" doesn't tell you what to change. "The review stage lacks gate criteria" tells you exactly what to change. The rule enforces termination at the process level — the level that produces actionable improvements — and prohibits descent into character attribution.

This is the same principle behind aviation's blameless investigation culture: when a plane incident occurs, the investigation asks "What process or system failed?" not "Who was inadequate?" Blameless investigation produces systemic improvements that prevent future incidents. Blame-based investigation produces cover-ups, defensiveness, and no systemic learning.

When This Fires

• During any post-action review or retrospective of output quality
• When self-evaluation of a failed output starts producing character judgments
• When asking "What went wrong?" and the answer veers toward personal inadequacy
• Complements Open weekly planning by reviewing plan vs. actuals — identify the single biggest gap without judgment, then make one structural fix (weekly plan-vs-actual review) with the analytical discipline for interpreting the gaps

Common Failure Mode

Character attribution loop: "The presentation was bad because I'm not good at public speaking." This feels true and explanatory but provides no structural intervention. The process-level version: "The presentation was bad because I didn't rehearse, the slides had too much text, and I didn't have a clear opening." Each of these is a fixable structural problem. The "not good at public speaking" label obscures these specific, addressable causes.

The Protocol

(1) In post-action review, ask "What caused the outcome?" and keep asking "Why?" at each answer. (2) When the causal chain reaches a process or structural factor (missing checklist, undefined criteria, wrong sequencing, insufficient preparation time), stop. This is the actionable cause. Design a structural fix. (3) If the causal chain reaches a personal trait ("I'm disorganized," "I procrastinate," "I'm not creative enough"), you've gone too far. Back up one level to the process factor that the trait is associated with: "I'm disorganized" backs up to "My filing system doesn't match my retrieval needs." "I procrastinate" backs up to "The task had no clear next physical action (Capture actions as specific next physical steps (not "handle client project" but "email Sarah the revised timeline") — eliminate re-processing at execution time)." (4) Every review should produce at least one structural improvement, never a character judgment. (5) The framing is: "What process would have produced a better outcome?" not "What kind of person would have produced a better outcome?"