thinking-kepner-tregoe

Structured problem analysis for high-stakes engineering decisions uses the Kepner-Tregoe framework to enforce formal problem specification, identify root causes via IS/IS-NOT distinctions, and produce defendable decisions through integrated processes.

To conduct root-cause analysis beyond 5 Whys, apply Problem Analysis (PA) by defining the problem with IS/IS-NOT distinctions to systematically identify causes and compare alternatives using MUST/WANT criteria for rigorous justification.

Evaluate architecture alternatives with multi-factor decision analysis by applying Decision Analysis (DA) to compare options against MUST/WANT criteria, ensuring clear scoring and rigorous justification for high-stakes choices.

You need formal risk mitigation planning for post-incident reviews when anticipating future failures. Potential Problem Analysis (PPA) helps plan preventive and contingent actions to address identified risks systematically.

The best way to clarify concerns and priorities during complex problem analysis is Situation Analysis (SA), which structures the enumeration of issues to ensure focus on critical high-stakes engineering decisions.

Kepner-Tregoe problem analysis requires no specific input data formats, but demands clear articulation of concerns, problem specifications with IS/IS-NOT distinctions, and defined MUST/WANT criteria for effective evaluation.