Already running Kepner-Tregoe? Good — keep it.
Kepner-Tregoe is one of the most widely adopted structured problem-solving methods in business. It's also, by its own design, built to strip intuition out of a decision. That's not a flaw — it's the gap CU-BOM was built to fill.
What Kepner-Tregoe actually does
The Kepner-Tregoe method runs four sequential processes: Situation Appraisal (clarify and prioritize the problem), Problem Analysis (find the root cause), Decision Analysis (score alternatives against weighted criteria), and Potential Problem Analysis (anticipate what could go wrong and plan mitigations). It's a rigorous, rational, fact-based system, and it's used across manufacturing, IT, and healthcare precisely because it's rigorous.
What it says about itself
Documentation on the method is explicit about its scope: it aims to "minimize biases and enhance clarity" through structured, fact-based reasoning rather than emotional or intuitive judgment. That's a deliberate design choice. It's also, by the same account, a limitation — the framework "may overlook the emotional and subjective dimensions of decision-making, which are crucial in certain contexts," and its rigidity can be a poor fit for fast-moving or ambiguous situations.
Where CU-BOM sits
CU-BOM doesn't run a second Situation Appraisal or a competing Decision Analysis next to your first one. It plugs into the gap KT names in its own documentation — the intuitive and emotional dimension a purely rational framework isn't built to check.
| Already covered by Kepner-Tregoe | What CU-BOM adds on top |
|---|---|
| Situation Appraisal — clarify and prioritise the problem | A psychological-safety check: will your team tell the truth about the situation, or perform for leadership? |
| Problem & Decision Analysis — score options against weighted criteria | The DWA Protocol's blind-ballot gut check against that same score, and a rule for when the divergence means the matrix missed something |
| Potential Problem Analysis — anticipate what could go wrong | The Premortem's "it already failed" framing, which surfaces risks people won't name in a normal risk register |
| None — KT has no live-crisis or funnel-design component | The Structural Pause and the Friction Dial, for situations KT was never scoped to cover |
The practical version
If your team already runs KT training, keep using it for Decision Analysis and Potential Problem Analysis — that's what it's for, and it's good at it. Add the safeguard check from whichever CU-BOM tool matches the moment: a Premortem before a launch, a blind ballot on top of a KT scoring matrix for a high-stakes vendor call, a Structural Pause when a KT session gets derailed by a heated argument.