Start Here!

System Kaizen

As you start to prepare for your Kaizen event, or if you’re thinking about developing a higher level Kaizen program, you should consider the differences between System Kaizen and Point Kaizen. In a recent meeting with my boss, we decided I needed to put together the 2012 Kaizen Rolling Schedule. An example of System Kaizen, the Kaizen Schedule design should show all the days of a month in one long column; each column contains one month; and the entire year fits on one page. The reason the schedule is important when it comes to System Kaizen is that the schedule itself becomes the driver for the process of continuous improvement, and a trigger for individual Kaizen events.

It’s easy to put together a schedule, and regardless of the design you choose, it will only become a trigger when the content of the schedule is communicated. System Kaizen is accomplished in an organized manner and designed to address system-level issues in an organization. It is an upper level strategic planning method that results in a series of planned Kaizen events over a period of time. This is in contrast to Point Kaizen that generally happens as a result of an immediate identification of a cellular or workstation problem that is addressed within a few days or a few hours.

All best!


In Category: Continuous Improvement, Gemba, Kaizen, Plan Do Check Act, Point Kaizen, System Kaizen, TQM


Show 0 Comments
No comments yet. Be the first.

Leave a Comment