🔍 Introduction to the Tool

Kepner-Tregoe Problem Analysis (KTPA) is a systematic method for identifying the true cause of a problem by comparing what is happening with what should be happening. It helps teams avoid assumptions and jump-to-solution thinking by asking structured, objective questions. KTPA is especially effective in project management and internal audit, where decisions need to be supported by logical evidence and clear thinking.

The technique separates the problem from symptoms, sharpens focus, and supports sound root cause analysis.

🧰 Template for Applying the Technique

Use the following steps to apply Kepner-Tregoe Problem Analysis:

• Step 1 – Define the Problem: Describe what is wrong, where, when, and the extent.

• Step 2 – Describe the Problem Clearly:

  • What is happening?

  • What should be happening?

  • Where and when is it happening?

  • Where and when is it not happening?

• Step 3 – Identify Possible Causes: Use distinctions (differences) and changes (what changed before the issue appeared).

• Step 4 – Test the Most Probable Cause: Look for evidence, test assumptions.

• Step 5 – Verify and Take Action.

🏢 Example: ACME Corp – Internal Audit of IT Downtime

At ACME Corp, Internal Auditor Auren was asked to support an audit after frequent IT system downtimes disrupted project workflows. He collaborated with Project Manager Aven, and IT Lead Jesse.

Using KTPA:

• What is wrong? Frequent network crashes in Project Wing C.

• What should be happening? Stable 24/7 connectivity.

• Where/when is it not happening? Only in Wing C, between 1–3 PM.

• What changed? HVAC system was reprogrammed two weeks earlier.

They discovered that new HVAC settings caused brief power fluctuations, affecting the network hub in Wing C. Auren’s audit report included actionable recommendations: install a power stabilizer and update the change control log process.

Conclusion:
Kepner-Tregoe Problem Analysis gave ACME’s audit team a clear, fact-based path to identify the root cause and prevent recurrence—proving its power in project audits and cross-functional issue resolution.