Chaos rarely comes from 50 problems. It usually comes from 3 problems that show up 50 different ways.
If your week is full of urgent pings, late tasks, rework, and "can you jump on this," you do not need more hustle. You need a fast way to pick the right problem and fix the cause, not the symptom. This issue is a simple routine you can run in 15 minutes with any team, in any industry.
The play
- Goal: Identify the highest-impact problem and the real cause behind it.
- Time: 15 minutes.
- People: 2 to 4 people closest to the work.
- Inputs: A list of issues with counts from the last 2 to 4 weeks.
Examples of inputs: late shipments, defects or rework, customer tickets, vendor misses, approval delays, project handoff delays.
Step 1 (5 minutes): Run a mini Pareto
Pareto is a quick way to decide what to fix first. In many systems, a small number of causes drive most of the problems. So instead of spreading effort across 10 issues, you identify the biggest driver and start there.
How to do it:
- Pick a time window (last 2 to 4 weeks).
- List problem types.
- Count how often each type happened.
- Sort highest to lowest.
- Pick the top 1 problem type. Not three.
Example:
- Vendor delays: 22
- Missing parts: 9
- Wrong labels: 6
- System errors: 3
Start with vendor delays.
Step 2 (7 minutes): Do 5 Whys on the top problem
Pick the top category from your Pareto and ask "Why?" until you reach a cause you can control.
Rules that make this work:
- No blame. Only process, tools, inputs, and constraints.
- Each "why" must be a fact you can verify.
- Stop when the next action is clear and within your control.
Mini example: approval delays
- Why are approvals late? Requests sit unassigned.
- Why unassigned? No single intake owner.
- Why no intake owner? Requests come through email, chat, and hallway asks.
- Why multiple channels? No standard intake path.
- Why no standard? Nobody defined the rule or built a simple intake form.
No standard intake process and no single owner.
Step 3 (3 minutes): Create one 48-hour countermeasure
Do not create a big project. Create one change you can implement in 48 hours.
Good countermeasures look like:
- Add a checklist at the point of error.
- Add a required field in the system.
- Define a standard work step and the owner.
- Create a trigger and escalation rule.
- Add a supplier confirmation step with a cutoff time.
Bad countermeasures look like: "Be more careful." "Remind the team." "Try harder."
Countermeasure example for approval delays: one intake form, one daily 10-minute triage owner, and an auto confirmation message with a clear SLA.
Copy and paste template
Use this every week.
Root cause sprint
- Time window: last _____ weeks (2 to 4)
- Pareto list: problem type + count, sorted highest to lowest
- Top problem we are solving (pick 1): _____
- 5 Whys: why 1 → why 2 → why 3 → why 4 → why 5
- Root cause (controllable): _____
- Countermeasure (one change in 48 hours): _____
- Owner: _____ Due date: _____
- Success metric (pick 1): reduce X from ___ to ___, improve Y from ___% to ___%, or cut cycle time from ___ to ___
- 7-day check: did it hold? Yes / No. If no, run 5 Whys again on what failed.
Common traps that make this fail
- Picking multiple "top problems" and fixing none.
- Doing 5 Whys without facts.
- Stopping at a people explanation instead of a process explanation.
- No owner, no deadline, no metric.
Try this this week
Run this once with your team and you will feel the difference immediately.
If you try it, comment "ROOT" and share your top problem type. I'll reply with 3 practical countermeasure ideas you can implement fast.
Lior Zaken
Operational Excellence & Continuous Improvement