Understand the work
Distinguish incident response from problem management. Learn the lifecycle, evidence standards and when an investigation is ready to close.
FOUNDATIONS20 MIN READING
Start with fundamentals →Academy / Learning paths / Edition 2.2
From recurring incidentsto better systems.
Learn what problem management does, which technique to use, and how to test a conclusion before treating it as a fact. Original capybara explainers meet professional, evidence-led examples.
START HERE_
Choose your learning path.
You don't need to register or tell us about your problems. Follow a route at your pace; the site does not measure progress or store answers.
Improve your reasoning
Match a real problem shape to an appropriate technique, examine competing explanations and practise professional decisions.
METHODSCASE REASONING
Find the right tool →THE LEARNING ROUTE_
Five chapters. One way of thinking.
Problem management fundamentals
Problem versus incident, known error, workaround, long-term control, verification and useful measures.
Read Chapter 01 →Technique Pathfinder
When to use 5 Whys, Fishbone, Pareto and Kepner–Tregoe—and when to choose something else.
Read Chapter 02 →Four professional case studies
Payments, warehouse quality, facilities operations and a migration decision. All examples are fictional and explicitly show their evidence.
Read Chapter 03 →Practice without giving us data
Work through eight reasoning challenges. Reveal worked explanations locally in the page; there are no scores, forms or uploads.
Read Chapter 04 →Evidence Lab: guided simulations
Study three fictional operational investigations. Inspect evidence, choose a reasoning path, reveal its consequence and compare the debrief.
Read Chapter 05 →THE THINKING DISCIPLINE_
Six moves to repeat.
01Observe
Describe the deviation without explaining it away.
02Scope
Establish where, when and how often it occurs—and where it does not.
03Hypothesize
Map plausible causes without voting them into facts.
04Test
Find evidence that could support or contradict the explanation.
05Control
Reduce harm now; plan a durable correction separately.
06Verify
Define the outcome and observation period before declaring success.
OUR STANDARD_
A persuasive story is not proof. Every example distinguishes observed facts, working hypotheses, proposed actions and outcomes that still need verification.
NEW / EVIDENCE LAB_
Make the next judgment yourself.
Reading a finished case builds understanding. The Evidence Lab adds three staged scenarios in which you inspect records, weigh competing explanations, reveal consequences of your choices and finish with a verification-focused debrief.
FOLLOW THE EVIDENCE_
Examine the details, challenge your first explanation and compare the consequences of each choice. The goal is defensible reasoning, not guessing correctly.
BUILD ON THE ORIGINALS_
The four familiar methods are still here.
Prefer the capybara stories first? Visit the original Technique Library. Need a definition? Open the glossary.
WHAT THESE LESSONS ARE BASED ON_
Methods, attribution and boundaries.
This independent learning resource is not affiliated with, endorsed by or a substitute for certification or formal training from PeopleCert, ASQ or Kepner–Tregoe. The professional scenarios and numbers are invented for teaching; external references inform the method descriptions, not the fictional outcomes.
- PeopleCert — ITIL 4 Practitioner: Problem Management (problem management purpose, workarounds, known errors).
- ASQ — Quality Tools (cause-and-effect diagrams and Pareto analysis).
- Kepner–Tregoe — Methodology FAQ (a family of structured thinking processes, not one matrix).
- AHRQ — Kepner–Tregoe Matrix (IS / IS NOT distinctions).