What Is Continuous Improvement?
Continuous improvement (CI) is the belief that every process can be made better, and the discipline to actually do it — systematically, repeatedly, forever. It is not a project. It is not a department. It is a way of operating where everyone from the CEO to the newest operator is expected to improve something.
The difference between organizations that talk about CI and organizations that do it comes down to one thing: do they have a structured method? "Try harder" is not a method. PDCA is.
The Five Models
1. PDCA (Plan-Do-Check-Act)
Created by Walter Shewhart and popularized by W. Edwards Deming, PDCA is the universal foundation. Every other CI model is essentially a variation of PDCA.
Plan: Study the current state. Identify the gap. Hypothesize a root cause. Design a countermeasure. Predict what will happen.
Do: Run a small-scale test. Not a full rollout — a controlled experiment. One line, one shift, one week.
Check: Measure the results against your prediction. Did it work? By how much? Were there unintended consequences?
Act: If it worked, standardize it. Update SOPs. Train the team. If it didn’t work, analyze why and plan the next cycle.
The Most Common PDCA Mistake
Skipping "Check." Teams implement a change (Do), assume it worked, and move on (Act) without measuring. Six months later the problem is back and nobody knows why. The Check step is where learning happens.
2. DMAIC
DMAIC is the Six Sigma version of PDCA with more statistical rigor. Use it for complex, data-heavy problems where you need to prove the root cause with data, not just intuition.
| DMAIC Phase | PDCA Equivalent | Key Tools |
|---|---|---|
| Define | Plan | Project charter, SIPOC, VOC |
| Measure | Plan | Data collection, Gage R&R, baseline metrics |
| Analyze | Plan | Pareto, fishbone, regression, hypothesis tests |
| Improve | Do | DOE, pilot testing, poka-yoke |
| Control | Check + Act | Control charts, SOPs, audits |
3. A3 Thinking
Named after the A3 paper size (11″×17″), A3 is Toyota’s approach to structured problem solving. The discipline is fitting the entire problem — background, current state, root cause, countermeasures, action plan — onto a single sheet. If you can’t explain it on one page, you don’t understand it well enough.
Left Side (Problem Understanding)
Background → Current Condition → Goal → Root Cause Analysis
Right Side (Solution)
Countermeasures → Action Plan → Follow-up → Results
The real power of A3 isn’t the template — it’s the thinking process and the coaching dialogue. A manager reviews the A3, asks questions ("How do you know this is the root cause?"), and sends the person back to go deeper. It develops problem-solving capability in your people.
4. Kaizen Events
A kaizen event (also called a kaizen blitz or rapid improvement event) is an intense 3-5 day focused improvement on a specific process. The team pulls people off the line, empowers them to make changes in real time, and delivers measurable results by Friday.
| Day | Focus | Deliverable |
|---|---|---|
| Monday | Train, observe current state, collect data | Current state map, baseline metrics |
| Tuesday | Analyze root causes, brainstorm solutions | Root cause analysis, future state vision |
| Wednesday | Implement changes, trial runs | Physical changes on the floor |
| Thursday | Refine, standard work, training | New SOPs, trained operators |
| Friday | Measure results, present to leadership | Before/after data, sustainability plan |
5. Daily CI (Everyday Improvement)
Daily CI is where the culture lives. It’s not a formal event — it’s operators and supervisors making small improvements every day as part of their normal work. A suggestion system, a "fix it now" board, or a 15-minute daily stand-up where the team picks one thing to improve today.
The 1% Rule
One small improvement per team per day. That’s 250 improvements per team per year. Across 10 teams, that’s 2,500 improvements annually. Most won’t be dramatic, but the cumulative effect is transformational — and the culture shift is even more valuable than the individual changes.
When to Use Which Model
| Situation | Model | Duration | Team Size |
|---|---|---|---|
| Quick shop floor problem | PDCA | 1 day – 2 weeks | 1-3 people |
| Complex quality issue with data | DMAIC | 2-6 months | 4-6 people |
| Structured problem with coaching | A3 | 2-4 weeks | 1-2 people + coach |
| Major process redesign | Kaizen Event | 3-5 days intensive | 6-12 people |
| Building improvement culture | Daily CI | Ongoing forever | Everyone |
Key Characters in CI
✅ CI Culture
- Everyone expected to improve something
- Problems are welcomed as improvement opportunities
- Leaders ask "What did we learn?" not "Who screwed up?"
- Standard work exists so you can see the deviation
- Small experiments happen daily
❌ CI Theater
- Improvement is the CI department’s job
- Problems are hidden until they explode
- Leaders blame people for variation
- No standard work so "better" has no baseline
- Big projects once a year with no follow-through
🎯 Key Takeaway
PDCA is the engine. A3 develops your people. Kaizen events create breakthroughs. DMAIC handles the complex stuff. Daily CI builds the culture. You need all five — but if you can only start with one, start with PDCA at the team level and build from there. The goal is not perfection. The goal is a system that gets better every day.
Put these frameworks into action
SymplProcess gives your team the daily tools to execute: shift reports, operating rhythms, bottleneck analysis, and continuous improvement tracking.
Try SymplProcess Free →