Book summary · Kaizen and problem solving · Intermediate
Toyota Kata: summary and review
Managing People for Improvement, Adaptiveness and Superior Results
By Mike Rother. First published 2009.
The short answer
Mike Rother reports five years of research (2004 to 2009) into the routines of thinking and managing behind Toyota's improvement, then turns them into two practice routines. The improvement kata moves a process toward a target condition through small experiments. The coaching kata has a manager ask five questions at the process, usually daily, to build that skill in others. His claim is that improvement comes from practiced habits, not from tools or events. It is a research report: the later Practice Guide is the how-to.
Read it if
- You supervise or manage an area and keep running improvement events whose results fade within weeks.
- You want a daily coaching routine for team leaders that is more specific than 'go to the gemba'.
- You lead continuous improvement and want a way to teach scientific thinking to engineers and supervisors.
Skip it if
- You want a first lean book. It assumes you already know why flow, standard work and problem solving matter.
- You are looking for a tool to solve one defect with an unknown cause. Kata builds a thinking habit; it is not that tool.
When it pays off: After you have a stable area and a handful of lean basics (5S, standard work, a visible measure), and when the question has become why improvement stops when the facilitator leaves. Read it before you appoint coaches, not after.
The core ideas, in plain language
- 1
Improvement is a skill built by practice
A kata is a routine you repeat until it is habit. Rother's point is that scientific thinking is taught by daily practice with a coach, not by an event or a training class. Practitioner Mark Rosenthal calls it a routine for a thinking pattern, not a new technique.
- 2
Four steps toward a challenge
Understand the direction or challenge, grasp the current condition with facts, set the next target condition, then experiment toward it. Rosenthal suggests a target condition about two weeks away for a process that runs every day, with a calendar date, not 'in two weeks'.
- 3
A target condition describes how a process runs
It is a description of the process functioning in a certain way by a date. One summary notes that tools such as kanban or leveling appear as target conditions that give direction, not as installs.
- 4
One obstacle at a time, with a prediction
The learner's storyboard holds the target condition, the current condition, a record of experiments, and an obstacle list. The learner works one obstacle, states what they expect from the next step, and reports what happened.
- 5
The coach develops the learner
The coach asks five questions at the storyboard, usually daily and for about 20 minutes or less. Coach Steve Kane's lesson: developing the learner is the job, and hitting the target is a by-product.
- 6
Improvement belongs to supervisors and engineers
A summary of the book reports Rother's finding that most cost and quality improvement at Toyota comes from team leaders and engineers, with operators contributing through suggestions.
How to use it on Monday morning
- 1
Pick one daily process and write the challenge
Choose one cell or process that runs every day and has a number you can read daily, such as first-pass yield or output per hour. Write the challenge in one sentence with the supervisor.
- 2
Grasp the current condition by watching and counting
Watch the process for a few cycles, then chart the last week of the number. Write only what you observed and measured, not suspected causes.
- 3
Set a target condition with a calendar date
Set it about two weeks out, written as how the process will run (for example, changeover done in a set time on most runs). Put the date on the storyboard. If you miss it, reset the target; do not move the date.
- 4
List obstacles, pick one, run the first experiment
Brainstorm obstacles with the team and list them. Pick a small one. Write the next step, what you expect to happen, and the date you will check.
- 5
Hold a short coaching cycle at the board
Meet at the same time each day for about 10 minutes at the board. Before coaching others, the coach should practice as a learner on a real problem. Ask the five questions and hold back suggested answers.
What to be careful about
A research report, not a manual
Rother wrote the 2017 Practice Guide because the 2009 book is a high-level summary. A reviewer of the guide notes that many managers assume the five questions are the whole coaching method. Budget for the guide.
It is Rother's model of Toyota, not Toyota's own method
Rother's research notes that Toyota people had difficulty explaining their own thinking patterns, so the kata are his reading of them. David Devoe argues that Toyota does not use scripted starter routines or coaching cycles to deploy strategy, and that presenting kata as the Toyota way can mislead people into thinking they are learning TPS. Rother's framing is an adaptation for organizations without Toyota's structure.
Coaching quality decides the result
Practitioners report common failures: coaches who lead learners to answers, coaches who skip their own practice, and coaches so focused on the five questions that they miss that data are being used to support an assumption.
It does not replace problem-solving tools
Kata teaches the pattern of thinking, not a method for analyzing a defect. When you need to find the cause of a quality problem, you still use something like A3 or five whys. Rosenthal sees kaizen events as a possible kickstart for kata, not something kata replaces.
Toyota Kata compared with The Toyota Way
Choose Toyota Kata when you already believe in Toyota-style management and want a daily practice routine your supervisors can run. Choose The Toyota Way when you need the philosophy and vocabulary first.
Read the summary of The Toyota Way.
What to read next
- The Toyota WayIt supplies the management philosophy that the kata routines try to make practicable.
- Managing to Learn: Using the A3 Management ProcessA3 is the other coaching format common in Toyota-style companies.
- Gemba KaizenIt covers 5S, waste removal and standardization, the basics a kata learner's process needs first.
Same topic (kaizen and problem solving): Kaizen: The Key to Japan's Competitive Success, Gemba Kaizen, Managing to Learn, Understanding A3 Thinking.
Tools and templates on LeanSuite that go with it
- Coaching kata templateA learner storyboard with target condition, current condition, obstacles and PDCA cycles, plus the coach's question card.Open
- PDCA templateRecords each experiment on one page.Open
- Daily kaizen routineA 10 to 15 minute routine at the board that pairs with the daily coaching cycle.Open
- A3 problem solving templateFor the root-cause work kata does not teach.Open
Book details
| Title | Toyota Kata: Managing People for Improvement, Adaptiveness and Superior Results |
|---|---|
| Author | Mike Rother |
| First published | 2009. McGraw-Hill, published August 2009. A Spanish edition (Profit Editorial) appeared in 2017. The separate Toyota Kata Practice Guide followed in 2017. |
| Edition shown | Hardcover, first edition, McGraw-Hill, 2009 |
| ISBN-13 | 978-0071635233 |
Details checked against public records on 7 October 2026. Other editions have other ISBNs. We carry no affiliate links.
FAQ
Questions about Toyota Kata
More lean books
- The Machine That Changed the World
- Lean Thinking
- Lean Production Simplified
- Toyota Production System
- Workplace Management
- The Toyota Way
- Kaizen: The Key to Japan's Competitive Success
- Gemba Kaizen
- Managing to Learn
- Understanding A3 Thinking
- Learning to See
- Making Materials Flow
- Creating Level Pull
- Value Stream Mapping
- Creating a Lean Culture
- The Lean Manager
- Gemba Walks
- Introduction to TPM
- Out of the Crisis
- Zero Quality Control
- Understanding Variation
- The Six Sigma Way
- Lean Six Sigma
- The Goal
- Getting the Right Things Done
- Hoshin Kanri for the Lean Enterprise
- A Revolution in Manufacturing
- Factory Physics
Back to the lean books hub for reading paths and filters.
Rather see it on your own problem?
Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

