The 4-Level CI Maturity Model
| Level | Name | Characteristics | Improvement Rate |
|---|---|---|---|
| 1 | Reactive | Problems are hidden or blamed on individuals. Improvement happens only during crises. “That’s just how it is here.” | 0–0.5 suggestions/person/year |
| 2 | Event-Driven | Kaizen events happen quarterly. Improvements are made during events but backslide between them. “We do lean when the consultant comes.” | 1–3 suggestions/person/year |
| 3 | Systematic | Daily improvement cadence. Suggestion system with rapid response. Problems are welcomed because they drive learning. Leaders coach instead of direct. | 10–20 suggestions/person/year |
| 4 | Self-Improving | Operators drive improvement without management prompting. Standard work is updated by the people who do the work. The system improves itself. | 20+ suggestions/person/year |
Most Western manufacturing facilities operate at Level 1–2. Toyota operates at Level 4. The gap is not tools — it is culture.
Psychological Safety: The Foundation
No improvement system works without psychological safety. If operators fear punishment for surfacing problems, they will hide problems. If supervisors fear blame for reporting misses, they will massage the numbers. If engineers fear looking incompetent for asking questions, they will make assumptions.
✅ Signals of Safety
- Operators pull andon without hesitation
- The Pitch Board has red blocks — and no one is punished for them
- Supervisors say “I don’t know” and ask for help
- Suggestions are implemented quickly and the suggester is credited
- Mistakes are discussed as system failures, not personal failures
- New employees are encouraged to question “why do we do it this way?”
❌ Signals of Fear
- Operators never pull andon — “it’s not worth the hassle”
- Pitch Boards are always green (because misses are not recorded honestly)
- Supervisors have all the answers (because admitting ignorance is career risk)
- Suggestions go into a box and nothing happens
- “Who did this?” is the first question when a problem is found
- New employees learn to keep quiet within the first week
The Suggestion System That Works
Most suggestion systems fail because they are slow (3-month review cycle), bureaucratic (committee approval required), and disconnected (the suggester never hears what happened). A system that generates 20+ suggestions per person per year has these properties:
| Property | What It Means |
|---|---|
| Small scope | Suggestions target the operator’s own work area. Not “redesign the factory” but “move this bin 2 feet closer to eliminate reaching.” |
| Fast response | Team lead reviews within 24 hours. If it can be done in the area, implement within the week. No committee. |
| Implementation rate ≥80% | Most suggestions are implemented. If most are rejected, people stop suggesting. Lower the bar for approval. |
| Visible tracking | A board in the area shows: suggestions submitted, status, and who implemented them. Transparency builds trust. |
| Recognition, not reward | Public thank-you, name on the board, mention in the standup. Not cash bonuses (which create gaming) but genuine recognition. |
💡 The 80% Rule
If your suggestion implementation rate is below 50%, your system is generating cynicism, not improvement. Every rejected suggestion teaches the submitter “don’t bother.” Fix this by: (1) coaching people to submit smaller, more implementable ideas, (2) giving team leads authority to approve and implement without management sign-off, (3) following up with every submitter, even for rejected ideas, with a genuine explanation.
From Events to Daily Practice
The transition from Level 2 (event-driven) to Level 3 (systematic) requires shifting from periodic kaizen events to daily improvement practice:
| Event-Driven (Level 2) | Daily Practice (Level 3) |
|---|---|
| Improvement happens during 3–5 day kaizen events | Improvement happens every day during normal work |
| Led by lean team or external facilitators | Led by team leads and operators with coaching support |
| Big projects, big results, big backslide | Small experiments, small results, sustained progress |
| Improvement is a separate activity from work | Improvement IS how work is done |
| 5–10 improvements per year per area | 100+ small improvements per year per area |
The mechanism for daily practice is coaching: a 15-minute daily conversation between coach and learner at the process, working on the current improvement target. Toyota Kata provides the structure.
🎯 The Bottom Line
CI culture is not about posters, slogans, or kaizen events. It is about creating conditions where every person improves every day. Psychological safety is the foundation (people must feel safe to surface problems). The suggestion system is the mechanism (small ideas, fast response, high implementation rate). Daily coaching is the cadence. And visible tracking closes the loop. Measure your culture by suggestions per person per year and implementation rate — if those numbers are low, fix the system before adding more lean tools. Next: Sustaining Gains — the systems that prevent improvement backslide.
Stop reading, start modeling
Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.