The Kaizen Mindset
Why small improvements compound into transformative change.
1What Is Kaizen?
Kaizen (改善) means "change for better" in Japanese. In Lean, it refers to continuous, incremental improvement—small changes made constantly by everyone.
This is different from innovation or transformation:
- Innovation: Big jumps, high risk, occasional
- Transformation: Massive change, disruptive, rare
- Kaizen: Small steps, low risk, continuous
Kaizen isn't dramatic. One percent improvement per week. A small tweak to the process. A minor automation. Nothing that makes headlines. But compound one-percent improvements over a year and you get 68% better. Do it for five years and you're unrecognizable.
Toyota famously receives around one million improvement suggestions from employees annually. Not million-dollar ideas—small improvements to daily work. Most are implemented. This relentless accumulation of small changes created a manufacturing juggernaut.
The Compounding Effect
1% improvement per week, compounded over a year, is 68% improvement. Over five years, it's over 1,000%. Small improvements aren't small—they're the most reliable path to large gains.
2Everyone Improves
Kaizen is not a management initiative. It's not a special team's responsibility. It's everyone's daily work.
In traditional organizations, improvement is delegated:
- Process improvement teams redesign workflows
- Six Sigma black belts run projects
- Consultants analyze and recommend
The people doing the work execute decisions made by others.
In Kaizen culture, the people doing the work improve the work. The developer who notices a slow test fixes it. The QA engineer who spots a recurring bug type suggests a linting rule. The ops engineer who's tired of manual deployment writes automation.
This works because:
- Proximity: The person closest to the work knows it best
- Volume: Everyone improving beats a few specialists improving
- Speed: No waiting for improvement projects—just improve
- Ownership: People care more about improvements they created
Management's job isn't to improve processes—it's to create conditions where everyone can improve. Remove barriers. Provide time. Celebrate improvements. Fix the environment, not the work.
A developer suggests adding a pre-commit hook to catch a common error. The team discusses for 5 minutes, agrees, and implements it that day. One fewer recurring bug. Time spent: 2 hours. Value: ongoing.
A developer has an idea for improvement. They submit it to the Process Improvement Request form. It goes to a committee. The committee meets quarterly. The idea sits for 4 months before rejection. The developer stops suggesting.
3Improvement as Daily Work
The biggest Kaizen mistake is treating improvement as separate from work.
"We'll improve our process after this deadline." "We need to schedule an improvement sprint." "Add it to the backlog—we'll get to it."
These statements guarantee that improvement never happens. Something urgent always appears. The deadline passes and another arrives.
Improvement must be built into daily work.
Practical approaches:
- Improvement time: Reserve 10-20% of capacity for improvement work, every sprint
- Boy Scout rule: Leave the code better than you found it, every change
- Retrospective actions: Make improvement items first-class work, not afterthoughts
- Pair on improvement: Two people tackling a pain point together
- Fix it now: When you spot something wrong, fix it immediately if it takes under an hour
The test: If someone asked "What did you improve this week?", could every team member answer? If not, improvement isn't embedded in daily work.
The 1-Hour Rule
If an improvement takes less than an hour, just do it. Don't file a ticket. Don't request permission. Don't wait for a planning session. One hour of improvement now beats a ticket that sits for months.
- Kaizen is continuous, incremental improvement—not occasional transformation
- Small improvements compound into massive gains over time
- Everyone improves, not just specialists or managers
- Improvement must be built into daily work, not scheduled separately
- Create conditions for improvement rather than doing improvement to people