How to make Kaizen your company's actual culture
Kaizen reached Japan from the United States. It took root there and not here, and the reason has nothing to do with Japanese culture.
Making Kaizen your company's culture — rather than one more campaign that gets forgotten — takes three things that almost never travel together: assigned time, the power to decide at the station and persistence when things go badly.
Enter your email and you will get an alert when something new is published. Unsubscribe anytime.
If you're missing one of the three, what you've got is a suggestion box with a Japanese name on it.
Where it comes from, which explains a lot
The origin is worth remembering, because it dismantles the cliché that this is "a Japanese culture thing".
After the Second World War, American experts in statistical quality control arrived in Japan with the TWI programmes (Training Within Industry), designed during the war to train supervisors in a hurry. William Edwards Deming and Joseph Juran taught there a set of methods that had been dropped in their own country the moment the wartime urgency ended.
In other words: the Japanese didn't invent the method. They sustained it.
That's the whole difference. And it's good news for you, because it means this doesn't depend on where your factory is.
The three conditions
Time inside working hours. If improvement happens "when we can", it doesn't happen. Fifteen assigned minutes at the end of the shift are worth more than a training day twice a year.
The power to decide at the station. A proposal that needs three signatures and two months teaches one single thing, and it teaches it very well: that proposing is pointless. There has to be a threshold — of spend and of scope — inside which the team decides and acts. Without asking.
Persistence in the bad quarter. This is where you win or lose the whole thing. When output is under pressure, the improvement meeting is the first thing off the calendar. And that decision teaches more than any speech you can make: it says, very loudly, that improvement was a luxury.
| Suggestion box | Real kaizen |
|---|---|
| You propose, someone upstairs decides | The team decides within a threshold |
| Answered in weeks, or never | Applied in days |
| Outside working hours | Assigned time |
| Suspended if the load is heavy | Especially if the load is heavy |
The bridge to 2026
I'll add a fourth condition that didn't exist twenty years ago: the data has to be there without anyone sweating for it.
I've watched many continuous improvement routines die, and hardly any of them died of a lack of will. They died of administrative exhaustion. Somebody had to gather sheets, key them into a spreadsheet and prepare them for Thursday's meeting. And when that person got tired — they always get tired — the cycle stopped.
When the line records what happens on its own, the improvement meeting starts straight in on the discussion. Not on the collecting.
And that, in practice, is what decides whether your improvement routine survives the first heavy month. Which is the only test that counts.