Root cause and problem register
Pareto, Ishikawa and 5 whys to reach root causes; every To-Be change will trace back to this register.
Command: /ef:root-cause · Methodology: Is2Be Process · Phase: Phase 3 · Analysis
When to use it
Section titled “When to use it”After the value analysis (and handoffs and risks, if they apply).
It’s working if
Section titled “It’s working if”- It separates symptom from cause.
- Each cause states its level of evidence and how to verify it if it’s a hypothesis.
- Common causes that explain several problems show up: the levers for the To-Be.
Where it fits
Section titled “Where it fits”- Before: Value and waste analysis, Handoff analysis, Risks and controls
- After: To-Be options
Requirements
Section titled “Requirements”-
Your AI connected to the service with your licence key (how to connect).
-
The project set up once with
/ef:setup. -
The outputs of the previous steps (see Where it fits).
How many problems does it analyze in depth?
Those that make up ~80% of the impact in the Pareto, plus risk or compliance problems even if they weigh less.
What if a root cause is out of scope?
It’s still recorded and flagged; widening the scope is the sponsor’s call, via a PDR.