Root Cause Analysis — Eliminate the Loss, Not the Symptom
Teach your team to kill the problem where it actually lives
An eight-hour live intensive that takes a team from a vague complaint to a verified root cause and a systematic action plan they can defend in front of any leadership team. Built from seven years of eliminating losses on real production lines — not from a textbook.
- Duration
- 8 hours
- Delivery
- Live on Microsoft Teams
- Format
- Max 15 attendees
- Level
- All levels — no prior Lean experience required
- Language
- English (Arabic on request)
Overview
Most teams are extremely good at reacting. A line stops, the crew swarms it, the line restarts, and everybody moves on. Three weeks later the same line stops for the same reason — and nobody calls that a failure of the investigation, because there never really was one.
Root Cause Analysis is the discipline that ends that cycle. Over eight live hours we take your people through the complete chain: frame the loss in numbers, collect evidence before it evaporates, map every plausible cause, drill past the comfortable answer, prove the root cause instead of asserting it, then design countermeasures that are written into the standard so the loss cannot quietly grow back.
This is not a lecture. Every hour ends with the group doing the work on a real case — and in a company room, that case is one of your own losses. Participants leave with completed templates, a one-page A3 they have actually written, and a routine their team can run the following Monday without any further support.
What you will be able to do
- Write a problem statement in numbers that a plant manager cannot argue with.
- Separate symptom, cause and root cause under real time pressure.
- Run a Five Whys that goes deeper instead of sideways — and know exactly when to stop.
- Build a cause-and-effect tree that survives a hostile challenge.
- Verify a root cause with evidence instead of defending it with opinion.
- Choose countermeasures that the next shift cannot quietly undo.
- Write a one-page A3 and present it to leadership in five minutes.
- Install the audit routine that stops the loss from growing back.
The eight hours, hour by hour
- 1Hour 1
Frame the loss, not the feeling
- Turn a complaint into a measurable problem statement
- Is / Is-Not: draw the boundary around the failure
- Quantify the loss in money, time and units
- 2Hour 2
Go and see before the evidence evaporates
- Gemba discipline: what to capture in the first thirty minutes
- Preserving the failure state instead of resetting it
- Interviewing operators without leading the answer
- 3Hour 3
Map every plausible cause
- Ishikawa done properly: the six M categories
- Cause-and-effect logic trees
- Separating correlation from causation
- 4Hour 4
Drill past the comfortable answer
- The three traps that make a Five Whys fail
- Branching whys: when one answer has two parents
- The stop rule — how you know you have hit the root
- 5Hour 5
Prove it, do not assert it
- Turn-it-on / turn-it-off verification
- Pareto and data checks that confirm or kill a hypothesis
- Writing the falsification test before you run it
- 6Hour 6
Design systematic actions
- Containment vs corrective vs systemic action
- The countermeasure hierarchy — why training is the weakest fix
- Poka-yoke and standard work that hold without supervision
- 7Hour 7
Live case — your own loss
- The full chain applied end to end by the group
- Coaching on the real data you brought
- Peer challenge: defend your root cause
- 8Hour 8
Make it stick
- Ownership, KPI and audit routine
- The one-page A3 you will actually use
- Presenting the investigation to leadership in five minutes
Who it is for
- Production, quality and maintenance engineers
- Line leaders, supervisors and shift managers
- Continuous improvement and operational excellence teams
- Anyone who owns a KPI that keeps missing its target
Tools you will use
- Is / Is-Not
- Ishikawa (6M)
- Five Whys
- Loss Tree
- Pareto
- Fault Tree
- A3
- Poka-Yoke
- PDCA
- Standard Work
Questions
No. The workshop starts from the problem, not from the jargon. Experienced practitioners get depth in hours 4–6; newcomers get a complete, usable method by hour 8.
The workshop is deliberately live and interactive — the value is in the coaching, the challenge and the group work. Templates, canvases and the workbook are yours to keep.
Yes — that is exactly what a company room is for. Send the loss you want to attack when you book and it is built into hours 7 and 8.
Microsoft Teams, a working microphone and one hour of preparation reading sent three days before. A camera is strongly encouraged — the group work depends on it.
Yes. Every participant who completes the eight hours receives a RootSym certificate of completion.
The moment your payment clears you receive a personal joining page. It opens once and reveals the Microsoft Teams link — so save it straight to your calendar.
Pricing
Company room
500 JOD
up to 15 attendees · ≈ 33.33 JOD per seat
A private room for your team — same eight hours, your data, your losses.
Book a company roomUpcoming live dates
- Sunday 8 November 202612:00 · Asia/Amman · 15/15
Included with every seat
- Live eight-hour session on Microsoft Teams with Rand
- RootSym workbook, templates and cause-mapping canvases
- A worked investigation on one of your own losses
- Single-use joining link issued the moment payment clears
- Certificate of completion
Bring RootSym to your team
A private eight-hour room, capped at fifteen people, built around the losses that are actually costing you.