FOCUS-ROI 3D Root Cause Mapping
A calm, structured way to explore what sits beneath a problem through Dig, Direction, and Difference.
FOCUS-ROI 3D Root Cause Mapping
A calm, structured way to explore what sits beneath a problem through Dig, Direction, and Difference.
Purpose
The 3D Root Cause Mapping guide helps teams uncover what really drives an issue.
Not to fix it straight away, but to see it clearly.
It invites calm exploration before solutioning, revealing what lies beneath the surface so teams can later act with focus and confidence using the wider FOCUS-ROI framework.
“We’re not looking for blame or quick fixes.
We’re mapping what’s really happening.”
How it fits in FOCUS-ROI
Within the FOCUS-ROI ecosystem, 3D Root Cause Mapping belongs primarily in the Explore stage. It can be used at any time when clarity fades.
It works alongside other tools:
- 4C Tool helps you see what type of problem you are in
- 3D Root Cause Mapping helps you explore why it exists
- ABCD Value Mapping shows how value behaves around it
The tool is reflective and simple. Its main function is to help people slow down long enough to see real patterns.
All problems have layers
Most problems are not flat.
They have history, movement, and hidden links.
3D Root Cause Mapping helps you explore those layers from three angles:
| Dimension | What it explores | What it reveals |
|---|---|---|
| Dig | Look beneath the surface | What drives or triggers the issue |
| Direction | Trace where causes lead | How influences connect or flow |
| Difference | Notice variation and perspectives | What stands out or changes the picture |
Together, these dimensions turn linear “why” questions into a map of insights.
It is not about how deep you dig, but what you discover when you pause and look around.
How to use on a whiteboard
1.Start with the issue
Write one problem or observation in the centre of the board.
Keep it short, factual, and neutral. Avoid framing it as a complaint.
Example:
“Customer feedback response times are slow.”
2.Dig
Ask alternating Why and How questions to explore what sits beneath the surface.
Write insights around the main issue. Draw lines or arrows where things connect.
Do not chase a single cause. Follow what feels significant.
Example:
“Why are response times slow?”
“How does workload affect it?”
“Why are priorities unclear?”
3.Detect direction
Trace where causes and effects lead.
Look for flows between people, steps, or systems.
Circle clusters or loops that seem to keep the issue alive.
Example:
“Requests from sales go to three inboxes. Delays happen before anyone owns them.”
4.Identify difference
Bring in other voices.
Ask what others see that you might not.
Notice contrasts between perspectives or patterns that do not quite fit.
Example:
“Support feels overloaded, but data shows half the requests are repeats. There is a difference in perception.”
5.Step back and see the map
Pause and look at the board as a whole.
Ask:
- What themes keep appearing?
- Where does energy or confusion collect?
- Which insights feel closest to a root cause?
Example:
“Unclear ownership appears everywhere. That seems to be the true pattern.”
The goal here is to surface signals, not solutions.
Seeing patterns
When the board feels complete, step back and describe what you see.
- Are there repeating loops?
- Are causes mostly structural, cultural, or process-based?
- What patterns seem to sustain the problem?
You are not solving yet. You are building clarity.
That clarity becomes the foundation for meaningful action later in FOCUS-ROI.
Examples in use
| Situation | Observed issue | What the team found | 3D insight | Next step (FOCUS-ROI) |
|---|---|---|---|---|
| Slow customer responses | Replies delayed across teams | Ownership unclear; overlapping inboxes | Direction – request flow friction | Clarify process in Shape stage |
| Recurring meeting overruns | Meetings always run long | No clear purpose; updates drift | Dig – hidden status assumptions | Redefine structure in Validate |
| Low engagement in feedback survey | Few responses, vague comments | Timing clashes with deadlines | Difference – priority mismatch | Adjust schedule in Prioritise |
| Quality issues in product handoff | Errors between design and dev | Different templates; no shared definitions | Difference + Direction | Co-create SOPs in Execute |
| Team stress and backlog buildup | Workload feels unmanageable | Multiple urgent requests; unclear priorities | Dig + Direction – systemic overload | Use ABCD Value Mapping |
Reflection prompts
Use these to close a session or revisit later:
- What surprised us most beneath the issue?
- Which causes are within our control, and which are not?
- Where do patterns repeat across different problems?
- Who else should we involve to see the full picture?
Make it yours
Translate the intent, not just the terms.
Adapt the three dimensions to fit your culture or language.
| Dimension | Meaning | Your team’s word |
|---|---|---|
| Dig | Look beneath the surface | |
| Direction | Trace how influences connect | |
| Difference | Notice variation and perspective |
Remember
Every problem has layers.
Dig, Direction, and Difference help reveal what sits beneath.
The goal is exploration, not blame.
When the root cause becomes clear, FOCUS-ROI helps turn that insight into action.
Return of Impact begins with understanding.
FOCUS-ROI 3D Root Cause Mapping
A calm way to explore what lies beneath, before deciding what to do next.