Lesson 1 of 23 · 7 min read

Kaizen in the office: small improvements, every week

In Lean: Kaizen, respect for people

In one minute

Kaizen is the habit of improving work through many small changes, made continuously by the people who do the work. A change you can try this week, check, and undo if it fails teaches you more than a large project that arrives next year. Its partner idea is respect for people: the people closest to the work see its problems best, and when something goes wrong you look for the cause in the process, not in a person. Together they turn everyday annoyances into a steady flow of small fixes.

The idea

There are two broad ways to improve how an office works. One is the big project: a new system, a reorganisation, an outside review. It takes months, needs a budget, and is decided far from the desk where the problem happens. The other is the small step: someone notices a recurring annoyance, changes one thing about how the work is done, and checks a few weeks later whether it helped.

Small improvements, every week (in Lean: Kaizen) is the second way, done as a habit rather than an event. The word is Japanese and means roughly "change for the better". In Lean practice it means continuous, incremental improvement that everyone takes part in.

Small steps suit everyday frictions for four reasons.

  • They are cheap to try and easy to undo. If changing a form makes things worse, you change it back. Nobody has to defend a sunk investment.
  • Feedback is fast. You learn in days or weeks whether a change worked, and that shapes the next one.
  • The people who do the work own them. A fix designed by the person who lives with the problem fits the real work, including the exceptions nobody wrote down, so it is more likely to last.
  • They add up. In many offices, time leaks away through dozens of small frictions: the reminder chased by hand, the file that is never where it should be. No project reaches them all; a weekly habit can.
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

Big projects still have their place. A system that cannot do what the work needs may have to be replaced. But waiting for the big project is no reason to leave small problems alone meanwhile.

Look at the process, not the person (in Lean: respect for people) is the other half. It is not about being polite. It means two practical things. First, the people doing the work are the experts on where it hurts, so improvement starts by asking them and letting them try changes. Second, when something goes wrong, the question is what in the process let it happen: the unclear form, the rule nobody owns, the hand-off with no checklist. Blaming a person changes nothing about next month, and it teaches everyone to hide problems. A hidden problem cannot be fixed.

The hardest part is often noticing. Frictions that repeat every week become "just how it is". A useful habit is to write a friction down the moment you feel it, before it fades back into normal.

Example

Illustrative example, not a real company.

A payroll team spends the two days before every monthly run chasing managers by email for overtime approvals. The big-project answer is a new time-tracking system, which sits on next year's budget list.

The small-step answer starts now. A payroll specialist replaces the improvised chasing emails with one calendar reminder, sent to all managers a week before cut-off, listing exactly what payroll needs. After the next run the team checks: fewer chases, but approvals for managers on leave are still late. The next step is a rule that a named deputy may approve when the manager is away. Each change is small, reversible, and made by the people who live with the problem.

Nobody asked which manager was slowest. The question was what in the process made approvals arrive late.

Common mistakes

  • Waiting for the big fix. Holding every improvement until a new system arrives leaves months of avoidable friction in place.
  • Treating Kaizen as only a suggestion box. Ideas sent upward for someone else to judge are not the same as the people doing the work trying a change and checking it.
  • Blaming a person. "If they were more careful" is a wish, not a change. Ask what in the process makes the mistake easy.

Words to know

  • Small improvements, every week (in Lean: Kaizen): small, continuous changes to how work is done, made by the people who do it.
  • Look at the process, not the person (in Lean: respect for people): trust the people doing the work to improve it, and look for causes in how the work is set up.

Check your understanding

3 questions. Answer them all, then check. You can try again as often as you like; nothing about your attempts is kept.

Question 1 of 3In an HR team, offer letters regularly go out with the wrong start date and have to be reissued. Which response is most in the spirit of Kaizen?
Question 2 of 3Expense claims keep coming back to employees. Which explanation does not respect people in the Lean sense?
Question 3 of 3Why do small, frequent improvements usually work better than rare big projects for everyday frictions? Select all that apply.

Choose all that apply.

Loading…

Try it on your own work

Describe one recurring task that wastes your time, and see these ideas applied to it.

Where this comes from

Continuous improvement and respect for people are usually described as the two foundations of the way of working developed alongside the Toyota Production System, and both run through the wider Lean tradition that grew from it.