Kepner-Tregoe Problem Analysis

Structured engineering methodology to isolate root causes by contrasting affected and unaffected elements. Follow this Kepner-Tregoe problem analysis workflow during critical system or process failures.

6 time blocks, 60 minutes in total.

Time blocks

Write the Precise Problem Statement: 10 min
Specify the exact object affected and the specific defect observed
Build the IS and IS NOT Matrix: 15 min
Document what, where, when, and extent is and is not affected
Isolate Distinctions and Recent Changes: 10 min
Note unique characteristics of the IS compared to IS NOT
Deduce Potential Root Causes: 10 min
Draft causes based on how identified changes produced the defect
Test Causes Against Matrix Facts: 10 min
Eliminate causes requiring extra assumptions to explain the facts
Plan Field Verification: 5 min
Verify the most probable cause through direct testing before acting

About this routine

Developed by Charles Kepner and Benjamin Tregoe in 1959, Kepner-Tregoe problem analysis is a systematic technique for solving complex operational issues. Rather than jumping directly to solutions, this framework forces teams to define exactly what is happening alongside what could be happening but is not.

By comparing the problem across four specific dimensions (what, where, when, and extent) against comparative elements that remain unimpacted, you reveal crucial distinctions. Identifying recent changes connected to those distinctions uncovers candidate root causes without relying on guesswork.

This 60-minute sequence guides you through bounding the issue, testing candidate causes against known facts, and confirming the true cause before making costly fixes.

Why this routine works

Prevents jumping to premature conclusions during operational outages
Isolates true root causes using comparative facts rather than opinions
Reduces troubleshooting time by narrowing scope systematically
Provides clear written documentation for post-incident reviews

FAQ

What is Kepner-Tregoe problem analysis?

It is a systematic root cause methodology developed in 1959 that isolates issues by systematically comparing facts about what is affected against what is not.

How does Kepner-Tregoe differ from Fishbone diagrams?

While Fishbone diagrams brainstorm broad categories of potential causes, Kepner-Tregoe uses a strict IS and IS NOT comparison matrix to eliminate causes that contradict facts.

How long does a Kepner-Tregoe problem analysis take?

A focused session takes 60 minutes to define the problem matrix, evaluate potential causes against facts, and outline verification steps.

Sources

The Rational Manager, Charles H. Kepner & Benjamin B. Tregoe
Kepner-Tregoe Problem Analysis Methodology, Kepner-Tregoe Official Literature