Kaikaku - Quantum Change (Part 2)

Kaikaku: How do we do it?  What’s it worth to us?

Let me open with an apology.  Back in December 2013, I promised that my next post would be about how to conduct a Kaikaku event and what you could expect from one.   Then life got in the way.  To keep my word, here is the follow-up post.

 ---- 0 ----

Dr. Deming used to say that 85% of all problems are the result of poor systems (systemic failures).  Three years before his death, he adjusted that figure to 95%.  If systemic problems are so frequent, Lean needs a tool to improve them.  That tool is Kaikaku [radical, or "quantum leap" change].

Who?

Because Kaikaku events solve problems with whole systems, they cross-disciplinary lines, so a Kaikaku event must have representatives from the system's process Suppliers, the Process performers, and process Customers.  That usually makes up a pretty large group.  

It's not uncommon for Kaikaku events to take a year or more, but most last 3-6 months.   Before you start thinking “Who won’t I miss?”  STOP!  You want to put your best people on a Kaikaku team, as they will be solving a longstanding problem that spans multiple disciplines. You'll want someone representing you that others will respect and can articulate your discipline's concerns and needs.

What?

The team will first completely document the existing process.  There are a number of useful tools for doing this, e.g. swim lanes, flow charts or, my personal favorite, an adaptation of Makigami. 

Using different colored 3” x 3” Post-It® Notes to represent every discipline involved, we create a single flowchart.  This is far more difficult that you’d think.  The reason is that, while many will assure you they know the whole process inside & out, I’ve yet to find a single person who actually does.  There are often steps performed inside one discipline that those outside that discipline never see.

Modified Makigami example below.

Once we’ve finished the modified Makigami, the team cycles back through to count the number of process steps and the number of times colors change from one process step to the next.  This is critical, since the more process steps, the longer the process Cycle Time; and because color changes represent handoffs between disciplines, and every one represents an opportunities drop the baton.

As the Kaikaku team is eliminating steps and handoffs, they are not only looking to streamline the process, but to make it more robust.

As stated earlier, a Kaikaku event can take 3-6 months; sometimes more.  It’s rare for the participants to be able to quit their day jobs and sequester themselves for that long, so teams usually meet at regular times to report on progress made against assignments handed out at the previous meeting.  

Although long, the results of a Kaikaku justify their expense.  The outcome is a process (system) that has been Beta tested - often more than once – proven to work flawlessly, documented completely, trained to all users and, only then, is it made the new standard.

Kaikaku embodies the meaning of Toyota Principle #13: “Make decisions slowly by consensus, thoroughly considering all options; implement decisions rapidly.”

So, that’s a thumbnail of Kaikaku.  Give it a try.

Meanwhile, Get Lean, Stay Lean.