← More Toolbox Talks
📱
Best viewed in landscape & full screen
Rotate your phone sideways, then tap the button below for the best experience. You can also swipe left/right to navigate slides.
Continue without full screen
📋 Toolbox Talk  ·  Continuous Improvement

Kaizen & PDCA:
Better Every Day

Kaizen means continuous improvement through small changes made by everyone. PDCA — Plan, Do, Check, Act — is the cycle that keeps each change honest.

✅ Updated October 2026📚 Lean & continuous improvement🏭 Warehouse · logistics · manufacturingukworkrights.co.uk

Talk 3 of 7 in the Continuous Improvement series  ·  a working method, not legal guidance

What it is

Small changes, made by everyone, all the time

  • Kaizen is a Japanese word usually translated as change for the better, or continuous improvement
  • It means many small improvements made by the people doing the work, rather than waiting for one big project
  • PDCA is the cycle every improvement goes through: Plan, Do, Check, Act
  • PDCA is linked to W. Edwards Deming, who built on Walter Shewhart's earlier cycle; some call it PDSA (Plan, Do, Study, Act)
  • A Kaizen event (or blitz) is a short, focused workshop where a team improves one process
  • Everyday Kaizen and Kaizen events work best together

The idea in one line

Every process can be improved, and the people closest to the work are best placed to improve it.
Why it matters

Why small beats big

  • Small changes are quick and cheap to try, and easy to undo if they don't work
  • Lots of small gains add up over a year to a big difference
  • People own the changes they suggested, so the changes stick
  • PDCA stops guesswork: you check that a change worked before rolling it out
  • Problems get fixed while they are small, before they become incidents or complaints
  • It builds the habit of questioning 'how we've always done it'

Try, learn, repeat

A change that didn't work is not a failure if you checked it properly. You know something you didn't know before, and the next cycle starts from there.
How to do it

The PDCA cycle

1
Plan

Describe the problem with facts and find the cause (see the Root Cause Analysis talk). Decide the change, how you will measure it, and what 'better' looks like.

2
Do

Try the change on a small scale — one shift, one line, one week — and record what happens.

3
Check

Compare the results with the plan. Did it work? Any side effects on safety, quality or other teams?

4
Act

If it worked, make it the new standard and share it. If not, adjust it and go round again.

Measure before you change

Without a 'before' measure you can't tell whether a change worked. Keep it simple — a tally chart for a week is often enough.
How to do it

Running a Kaizen event

1
Choose the scope

One process, one clear problem, and a sponsor who can approve changes.

2
Pick the team

People who do the job, someone from the steps before and after, and a facilitator.

3
Understand it

Go and see, map the current process and gather the facts.

4
Improve it

Find causes and test changes on the spot, using PDCA.

5
Standardise it

Write the new method, train people, and report back to the sponsor.

6
Follow it up

Review the action list at set points afterwards until every action is closed.

⚠ Most events fail after the event

Keep one action list with an owner and a date for every item, review it weekly, and close actions where everyone can see.
Worked example  ·  Warehouse

Damaged cartons at goods-in

  • Plan: goods-in logged damaged cartons every day; a week of tallying showed most damage happened when pallets were broken down on the floor
  • Change agreed: a pallet-height table at the breakdown point, so cartons are not dropped or dragged
  • Do: one table, one shift, for two weeks, still tallying the damage
  • Check: damage at that point went down, and staff reported less bending
  • Act: tables at every breakdown point, written into the goods-in standard

What changed

The fix came from the people unloading, the tally showed it worked, and it reduced bending as well as damage.
Worked example  ·  Manufacturing

A five-minute daily improvement meeting

  • What we saw: small niggles on a packing line — labels jamming, a bin in the wrong place — were mentioned but never fixed
  • The team started a five-minute stand-up at the line board each morning
  • Every idea went on a card that moved through Plan, Do, Check and Act columns
  • Anything needing engineering or safety sign-off was passed on with a named owner, not left on the board
  • Each Friday the team looked at what had reached Act

What changed

Small fixes happened within days, people saw their ideas being acted on, and the board showed the backlog honestly.
Common mistakes

What goes wrong

  • Skipping Check — rolling a change out because it 'feels better'
  • Plan turning into a talking shop — weeks of planning for something you could test in a day
  • No follow-up after a Kaizen event — the action list is forgotten
  • Ideas disappearing into a box — people stop suggesting when nothing comes back
  • Changing several things at once, so nobody knows which one worked
  • Changing a safe system of work without checking the risk assessment first

⚠ Watch for this

If the same problem keeps coming back, part of the cycle is being skipped — usually Check or Act.
Try it this week

One PDCA card

1
Pick one niggle

Something small that annoys the team every shift.

2
Plan it

Write the problem, the change and the measure on one card.

3
Do it

Try the change for a few days.

4
Check and Act

At the next briefing: keep it, change it or drop it.

Bring it back

Put the card up where everyone can see it. One finished cycle teaches more than ten ideas on a list.
Over to you

Discussion questions

  • What is one small change that would make your shift easier?
  • What happened to the last idea you suggested?
  • How do we know whether a change actually worked?
  • Who has to approve changes here, and how quickly can that happen?
  • What would make you more likely to suggest an improvement?

For the presenter

Answer the second question honestly. If ideas have been ignored before, say what will be different this time — and then make it different.
Quick check

Check your understanding

1
What does PDCA stand for?

A) Plan, Do, Check, Act    B) Prepare, Deliver, Control, Audit    C) Plan, Decide, Change, Agree

2
What is the main idea of Kaizen?

A) One big change a year    B) Many small improvements by everyone    C) Changes decided by managers only

3
In which step do you compare results with the plan?

A) Do    B) Check    C) Act

4
What most often makes a Kaizen event fail?

A) Too many sticky notes    B) No follow-up on the actions    C) Too few managers

Answers

1 A  ·  2 B  ·  3 B  ·  4 B
Common questions

Frequently asked questions

What is the difference between PDCA and PDSA?
They are the same cycle. Deming preferred 'Study' to 'Check' to stress learning from the results, not just inspecting them. Use whichever your workplace uses.
How long does a Kaizen event take?
Often a few days for a focused team, but the follow-up afterwards matters more than the event itself. Many improvements need no event at all — just a PDCA card.
Do we need approval for every idea?
Agree simple rules: small changes within the team's own area can be tried straight away, while anything affecting safety, quality or other teams goes to the right person first. Clear rules speed things up.
For whoever runs this talk

Delivery notes & attendance record

Suggested length: 10–15 minutes. A toolbox talk is a short briefing on one topic, given by a supervisor or team leader to the people doing the work.

Before you start

Bring cards or sticky notes and a board or wall split into four columns: Plan, Do, Check, Act.

How to run it

Explain Kaizen and PDCA (slides 2 to 4), use one worked example, then ask everyone to write one PDCA card before they leave.

Where this fits

Talk 3 of the Continuous Improvement series. Root Cause Analysis (talk 4) is how you do the Plan step properly.

The worked examples are illustrations to start a discussion, not real case studies or measured results.

Attendance record
TopicKaizen & PDCA: Better Every Day
Date
Site / location
Delivered by
Actions agreed
Next talk due
Attendees
NameSignature

Use the Print handout button to print this record. General guidance on a working method — not legal, health and safety or HR advice. Before changing how a job is done, check the risk assessment and safe system of work for that job, and involve the people who do it.

Continuous Improvement series

Keep
improving

Seven short talks that build on each other. Run them in order, or pick the one your team needs next.

Next talk
Root Cause Analysis
ukworkrights.co.uk/toolbox-rootcause.html
After that
Standard Work
ukworkrights.co.uk/toolbox-standardwork.html
The full series
All 7 talks
ukworkrights.co.uk/toolbox-talks.html#continuous-improvement
This talk
Kaizen & PDCA
ukworkrights.co.uk/toolbox-kaizen.html

General guidance on a working method — not legal advice · Updated October 2026 · © UK Work Rights Ltd · Company No. 17228507 · ICO Registration No. ZC239465 · Registered office: 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ  ·  hello@ukworkrights.co.uk
Directed and published by Matt Thompson, founder
Content is produced with AI assistance.