Using an action plan , you can plan out the corrective steps. Assign someone to monitor and report the progress once the solution is applied. More templates and visual ideas for carrying out a 5 why analysis.
Brainstorming Map Template. Brainstorming Template. Fishbone Diagram. Brainstorming Example. A3 Problem Solving Template. A common, useful and easy to learn approach to understanding how to drive change in your score is the 5 Whys Process. For a general review of using quality process in the customer feedback process see this post: Customer Feedback Management Meets Quality Systems. It is a simple and methodical way to identify the root cause of an issue.
The real value of the process is that it drives you to find and solve the underlying cause of the issue not just the obvious symptom. By solving the underlying cause you ensure that the problem does not happen again. This prevents you having to solve the symptom the problem you currently see in the future; thus saving you time, money and effort every day. Spend some time making sure that you have a good definition of the problem. Simply determine what happened to cause the problem.
Just go one layer at a time here. Stop and ask yourself if the Why you just wrote down is the real and underlying root cause of the problem. Repeat Steps 2 and 3 until you have the final and underlying cause of the issue. Typically you will need to ask the Why question about 5 times to get to the root cause. You do this not to fix the problem you started with the symptom but to prevent the problem from occurring again.
This is the real value of the process. Below is a simple 5 Whys example. Again, and again, and again? They allow you to collect a sample of data related to a particular issue. This data allows you to work out why the problem came about. A RCAT, often known as a root cause corrective action template, usually takes the following simple structure:.
This template structure can be stripped down and pumped up depending on the gravity and size of the problem. You want to record a short explanation, list the potential causes, and report why the solution was or was not successful. For a more complex issue, the report will naturally be more detailed when it comes to recounting the problem, its defects, how often they occurred and why.
Six Sigma is a disciplined, data-driven approach used to eliminate business faults. It's a method proven to provide organisations with both powerful and exceedingly efficient tools. These tools improve how corporations function on a day to day basis. In a nutshell, Six Sigma is all about focusing on how a given project is managed and ensuring systematic improvement of this project.
In short, comparing the difference between expectation and result. For instance, what happened, when and where, and who was impacted. This can be done by analysing the difference between the VOC and the VOP, also known as the voice of the customer and the voice of the process. Figuring out the cause and its concomitant effect can help prevent the problem from recurring.
Likewise, how can this solution be monitored in a way that prevents the problem from rearing its ugly head again in the future? Ultimately, the goal of the Six Sigma Method is to identify as many factors as possible related to the root cause of the problem in the business. These can easily be made with an excel document, a flow chart or a simple word document.
0コメント