In the Analyze phase, we understand why is the problem occurring. We start with step seven. Identify performance gaps. In this step, we try to understand the sources of variation and waste. We also do root cause analysis and identify the potential causes of the problem. The root causes that we identify in this step are known as trivial many exists.

The tools include brainstorming fishbone diagram, Five Eyes, affinity diagram, and value stream analysis. Step eight, ascertain critical root causes. In this step, we use graphical tests and identify what insights do these graphs and data reveal on the root cause. We focus on getting a shortened list of critical root causes. These are also called as critical access. The tools include data stratification, and multi voting.

Step nine, validate root causes. In this step, we confirm if the root causes have a significant impact on the problem. In other words, we validate the root causes. Our objective is to boil down to just three to six root causes of the identified list of trivial many root causes. These three to six root causes are called as vital few access. The tools include hypothesis testing, and then have a tollgate review meeting with the champion to demonstrate that the team understands the root causes and impact of the problem.

The team is now set up to build the future state.