Kepner-Tregoe Method
A structured problem-solving and decision-making methodology using systematic analysis to identify root causes and evaluate alternatives.
Also known as: KT Method, Kepner-Tregoe Analysis, KT Problem Analysis
Category: Frameworks
Tags: problem-solving, decision-making, analysis, frameworks
Explanation
The Kepner-Tregoe (KT) method is a structured approach to problem-solving and decision-making developed by Charles Kepner and Benjamin Tregoe in the 1960s. It provides four distinct analytical processes that can be used independently or together to address complex issues systematically.
**The four processes**:
1. **Situation Appraisal (SA)**: Clarifying and prioritizing concerns
- Break complex situations into manageable components
- Set priorities based on urgency, seriousness, and growth potential
- Determine which analytical process to apply to each concern
2. **Problem Analysis (PA)**: Finding the root cause of deviations
- Define the problem precisely using IS/IS NOT comparisons
- Identify distinctions and changes that could explain the deviation
- Develop and test possible causes against the specification
- Verify the true cause
3. **Decision Analysis (DA)**: Making choices
- Clarify the purpose and establish objectives (musts vs. wants)
- Generate alternatives
- Evaluate alternatives against objectives
- Assess risks of the best alternatives
- Make a balanced choice
4. **Potential Problem/Opportunity Analysis (PPOA)**: Protecting plans
- Identify what could go wrong (or right) with a plan
- Determine likely causes of potential problems
- Take preventive actions
- Prepare contingent actions and triggers
**Strengths of the KT method**:
- Highly structured, reducing the chance of overlooking important factors
- The IS/IS NOT technique in Problem Analysis is particularly powerful for isolating root causes
- Provides a common language and framework for teams
- Separates problem analysis from decision-making, avoiding premature solutions
**When to use it**: Complex technical problems, high-stakes decisions, situations where systematic analysis is more appropriate than intuition, and when teams need a shared analytical framework.
Related Concepts
← Back to all concepts