Sometimes a problem becomes so apparent and pressing, that it requires the immediate and full attention of subject matter experts to solve it. This might be something like a sudden, unexplained increase in the number of product defects. It might be a spike in customer complaints or safety violations. In these cases, a Kaizen event may be exactly the right approach to getting the problem resolved very quickly.
Even if the issue is not as urgent as the ones listed above, a Kaizen event might be in order if the issue’s impact is significant enough to justify diverting resources from other tasks for a few days. This might apply to issues related to pull through, or a specific waste that is contributing to substantial expense.
There are some issues that are simply too complex and widespread that a Kaizen event isn’t the right approach. Before deciding to deploy a Kaizen event, consider whether improvement is possible in three to five days. If that seems like a stretch, another improvement methodology is probably in order.
Kaizen events are an excellent way to teach people how to improve using the PDSA cycle. Allowing employees to focus on improvement for a few days gives them an intensive improvement experience and it reinforces the skills that are necessary to see an opportunity for improvement to fruition. This is helpful for people who are new to the Kaizen mindset, and as a periodic skill refresher for veterans.
Cross functional collaboration can be difficult when people are pulled in different directions with competing priorities. A Kaizen event removes these barriers and puts everyone to work on the same problem at the same time - with the added benefit of building relationships that can encourage cross functional collaboration long after the event ends.
Kaizen events are an important tool in the improvement toolbox. They aren’t right for every job, but they are particularly well suited to situations like these.