Comparison

Kaizen vs Lean vs Six Sigma for office teams

By KaizenProof · Updated

In short

Kaizen is the practice of improving work through many small changes made continuously by the people who do it. Lean is a wider management system, derived from the Toyota Production System, that improves the flow of work towards the customer by removing waste. Six Sigma is a data-driven method for reducing variation and defects in a repeatable process, usually run as a project by trained specialists.

They are not rivals. Kaizen is how improvement happens day to day, and it sits inside Lean. Six Sigma brings statistics for problems where the cause is hidden in variation. Most office problems are recurring annoyances with a findable cause, which is Kaizen's ground.

The Plan, Do, Check, Act cycleA circle in four parts, in order: Plan, Do, Check and Act. An arrow leads from Act back to Plan, so the cycle starts again.PlanDoCheckAct

The Plan, Do, Check, Act cycle

  1. PlanUnderstand the problem
  2. DoMake one change
  3. CheckSee whether it held
  4. ActKeep it, or go again

Kaizen, Lean and Six Sigma side by side

Kaizen, Lean and Six Sigma compared for office work
KaizenLeanSix Sigma
What it isA habit of small, continuous improvementA management system for flow and valueA statistical method for reducing defects and variation
The question it asksWhat small change can we try this week?Where does the work wait, move or pile up?What makes the result vary, and by how much?
Who does itEveryone, on their own workTeams and their leads, across a value streamTrained practitioners (belts) with the process owner
Size of a changeSmall, cheap, easy to undoSmall to large redesigns of a flowA project, typically weeks to months
Typical tools5 Whys, PDCA, standard work, a team boardValue stream map, the 8 wastes, pull, visual managementDMAIC, measurement system analysis, control charts, hypothesis tests
Data neededWhat the team can see and countLead time, process time, queue sizesEnough measurements for statistics
Office exampleThe weekly report nobody reads is stoppedInvoice approval redesigned so invoices stop queueingErrors in a high-volume claims process traced to one input field

What Kaizen is

Kaizen is a Japanese word usually translated as "change for the better" or "improvement". In management it means continuous improvement through many small steps, owned by the people closest to the work. Masaaki Imai's 1986 book, Kaizen: The Key to Japan's Competitive Success, brought the term into Western management.

Daily Kaizen makes small changes part of normal work; a Kaizen event gathers a team for a few days on one process. The lesson Kaizen in the office explains the idea, and Kaizen event vs daily Kaizen compares the two formats.

Small steps add upMany small fixes, each one checked, instead of one large project. A fix that slips is caught at its check-in and stops counting.

Illustrative, no real data

What Lean is

Lean is a way of running work that starts from what the customer values and removes everything else. It grew from the Toyota Production System; the word "lean" was coined by John Krafcik in 1988 and spread with the 1990 book The Machine That Changed the World. Lean's main lenses are value, flow and the 8 wastes.

In offices, Lean is most useful where work crosses teams and tools, because that is where it waits. A request that needs ten minutes of work can take a week; Lean asks why, as the lesson on lead time vs process time shows.

Follow one item through the people and tools it touchesA swimlane map of one request, before and after the team removed a step and asked for the missing details up front.

Illustrative example, not real data

A process map before and after removing a stepA swimlane map with three lanes: requester, manager and finance, drawn twice. Before: the requester sends a request, the manager approves it, finance checks it and sends it back because bank details are missing; the requester fixes the details, the manager approves again, and finance pays. Each move between lanes is a handoff where the item waits in a queue. After: the request form asks for bank details, the approval that had never refused a request is removed, and finance checks and pays. One handoff, no rework loop.BeforeRequesterManagerFinanceRequestApproveCheckFix detailsApproveagainPaysent backAfterRequesterManagerFinanceRequest withbank detailsApproveremovedCheckPayA process map before and after removing a stepA swimlane map with three lanes: requester, manager and finance, drawn twice. Before: the requester sends a request, the manager approves it, finance checks it and sends it back because bank details are missing; the requester fixes the details, the manager approves again, and finance pays. Each move between lanes is a handoff where the item waits in a queue. After: the request form asks for bank details, the approval that had never refused a request is removed, and finance checks and pays. One handoff, no rework loop.BeforeRequesterManagerFinanceRequestApproveCheckFix detailsApproveagainPayAfterRequesterManagerFinanceRequest withbank detailsApproveremovedCheckPay
  • A triangle marks a handoff, where the item waits in a queue.
  • Red, dashed boxes are rework: the same work done twice.
  • The approval removed had never refused a request. Removing it is a reversible trial, agreed with whoever owns the control.

What Six Sigma is

Six Sigma is a method for reducing defects by reducing variation, developed at Motorola in 1986 by the engineer Bill Smith. Its name comes from statistics: a process at six sigma produces about 3.4 defects per million opportunities. Projects follow DMAIC: Define, Measure, Analyse, Improve, Control.

Six Sigma pays off when a process runs at volume and its errors have causes no one can see by looking: thousands of claims, payments or orders where the error rate moves and nobody knows why. It needs data and trained people. Lean Six Sigma combines the two: Lean for flow, Six Sigma for variation.

Which one does an office team need?

  • Start with Kaizen when the problem is a recurring annoyance someone can describe in a sentence: the same figures copied every month, the same question answered every day, an approval nobody needs. A 5 Whys and one small change usually reach the cause.
  • Add Lean when the problem is time across teams: requests that wait for days, work that bounces between tools. Map one real item, measure waiting against working time, and remove the queues.
  • Call for Six Sigma when the problem is an error rate in a high-volume process, the obvious fixes have failed, and you have the data. That is a project, not a weekly habit.

Whatever the method, two rules hold. Ask whether a step should exist at all before improving or automating it. And check after a week and a month that the change held, using PDCA, because a fix that slips back saves nothing.

Where KaizenProof fits

KaizenProof is a Kaizen tool for office teams that uses Lean's vocabulary. A person describes a recurring friction, the product names the kind of waste in plain words, asks why one question at a time, asks whether the step should exist, writes a countermeasure, and checks at day 7, 14 and 30 whether it held. It is not a Six Sigma tool: it does no statistics and draws no control charts.

Questions

Is Kaizen part of Lean?

Yes, in most practice. Lean is the wider system; Kaizen, continuous small improvement by the people doing the work, is how Lean organisations improve day to day.

Is Six Sigma better than Kaizen?

Neither is better; they fit different problems. Six Sigma suits error rates in high-volume processes with data. Kaizen suits the many everyday problems whose cause the team can find by asking why.

Do office teams need a belt certification to do Kaizen?

No. Kaizen is meant to be done by everyone on their own work. Belts belong to Six Sigma projects.

Sources

  1. Masaaki Imai (Wikipedia)
  2. The journey of Kaizen Institute (Kaizen Institute)
  3. Lean manufacturing (Wikipedia)
  4. Six Sigma (Wikipedia)

Try it on your own work

Pick one task that wastes your team's time every week. Describe it in a sentence; KaizenProof names the waste, asks why until you reach the cause, and writes the fix. No account is needed to start.