This is an internal operations build, not paid client work.
Root-cause discussions often stop too early: the first plausible explanation becomes the answer, assumptions become facts and the countermeasure treats the symptom rather than the underlying mechanism.
What I designed
a clear problem statement
a visible causal chain through successive why questions
separation of evidence from assumption
space to challenge unsupported causal steps
a route from supported cause to practical countermeasure
How I approached it
The tool deliberately slows down premature certainty. Each step in the causal chain should be explainable and supported before the analysis moves forward.
What the work demonstrates
This is the same evidence discipline I use in workflow diagnostics: facts, evidence, assumptions, inferences and unknowns should not be blended together.
Evidence boundary
This is a method and artefact case study. It does not claim client results, formal regulated RCA assurance or quantified savings.