Throughout all the things I’ve talked about in this series; mission, vision, strategic plans and kanban there’s a underlying concept. We want to improve. We want to be better in achieving our vision.
If you want to improve you will have to be great in fixing problems. Not only fixing the problems but the actual underlying reason for the problem to occured in the first place.
Root cause analysis is a powerful tool for doing that. This is what I talk about in this presentation.
Here’s all the post in the series (the links will work as I post them):
- ca 10 minutes on Mission statements
- ca 10 minutes on Vision statements
- ca 15 minutes on Strategic plans
- ca 15 minutes on Impact mapping
- ca 15 minutes on kanban
- ca 10 minutes on root cause analysis (this post)
- ca 10 minutes on effective meetings
Please read the reason and ideas behind the entire series in the first post.
In the presentation I give a very short introduction and just dive right into an made-up example that we did in our office. This will actually show you most of the practices you will need to know to create a root cause analysis map.
After that there’s a short discussion on what makes Root Cause Analysis work. To me that is three things:
- A Root Cause map is big and visual
- This exercise is done together, collaborative (for best result)
- The focus should be to fix the system, not to blame the people.
Here’s a good article, should you want even more to read.
You can see the presentation here:
And find my slides here:
Published byon Last updated