What Toyota’s 1992 Booklet Says About Standardized Work and Kaizen Being the Same Thing

Most Lean programs treat standardized work and kaizen as opposites. Standardized work is the rigid part. Kaizen is the creative part. One constrains, the other improves. Pick whichever side you prefer and argue with the other camp at the next conference.

The 1992 Toyota booklet doesn't see them as opposites. It sees them as the same activity, performed by the same people, on the same loop.

The section is called “Dual Dynamics of the Toyota Production System.”

Worth reading slowly:

“Standardized work and kaizen are two sides of the same coin. Standardized work is team leaders establishing procedures and standards for their own teams' work, and it is the teams performing that work in accordance with those guidelines. Kaizen is teams of employees revising their work procedures and standards continually to achieve improvements in efficiency, quality, and working conditions.”

Same teams. Same work procedures. Same standards. The only difference between standardized work and kaizen is which direction the loop is moving in at any given moment. Establishing the standard is standardized work. Revising the standard is kaizen. The standard itself is the artifact that lives in the middle.

This is the sixth and final post in the series on Toyota's April 1992 publication “The Toyota Production System.” A different angle to close on.

Related post: Fujio Cho on Standardized Work: The Foundation for Improvement, Not Control

The misreading

The most common American misreading goes like this: standardized work means following a rigid procedure. Workers do what the document says. Deviation is bad. Compliance is good. Kaizen, when it happens at all, is a separate activity – usually a workshop, often led by an outside facilitator, scheduled quarterly.

In that frame, standardized work and kaizen sit in tension. The standard is what you have to follow. The kaizen is what you do to escape the standard.

The 1992 booklet doesn't recognize that frame. The standard isn't something imposed on the team. The team writes it. The team revises it. The team uses it. The team improves it. The standard is the team's own description of how they currently do the work, and the team is responsible for both following it and changing it.

The booklet is explicit on this point: “An especially important aspect of standardized work at Toyota is that the employees who implement its guidelines are the same people who establish those guidelines.”

That sentence is the whole argument. If different people set the standard than the people who follow it, the system the booklet describes can't function.

Why the standard matters for kaizen

There's an implicit claim in the “two sides of the same coin” framing that's worth surfacing. The standard isn't the enemy of improvement. It's the precondition for it.

If you don't have a current standard, you can't tell whether a change is an improvement. The team that's running its work three different ways across three shifts can't kaizen, because there's nothing stable to compare a change against. Process variation isn't a sign of a creative team. It's a sign of a team that hasn't decided how to do the work yet.

The booklet describes the loop directly:

“Members of the team responsible for the process work with their team leader to figure out how to achieve the new takt time. First, they try to find ways to modify their procedures to streamline the flow of work. If improvements in work procedures are insufficient to achieve the new takt time, the team members consider ways to streamline their work by modifying the equipment.”

Notice what's happening. A new takt time is set – because demand has changed, because sales volume has shifted. The team has to meet that takt time. Their first move isn't to call a workshop. Their first move is to revise their own work procedures. That revision is kaizen, but it isn't called kaizen in the passage. It's called the regular response to a change in conditions.

In Toyota's framing, kaizen isn't an event. It's the ongoing maintenance of the standard against the world the standard is trying to describe.

The platform, not the constraint

Sutherland-shaped move worth naming: the standard isn't a limit on what the team can do. It's the platform that lets them do anything at all.

A team without a standard can't reliably train new members. Can't reliably hand off shifts. Can't reliably troubleshoot quality problems. Can't reliably know whether yesterday's change made things better or worse. The team is doing different work every day, and the variation costs them learning.

A team with a standard, even an imperfect one, has a starting point. They can train against it. They can audit against it. They can experiment against it. They can revise it when conditions change. The standard is what makes the variation in the work the team's choice rather than the team's accident.

Most American organizations that have struggled with standardized work have struggled because they imported the document without the loop. The standard arrived from somewhere else – corporate, an industrial engineer, a consultant – and the team was told to follow it. The team had no role in writing it and no authority to revise it. So the standard sat there, technically in force, practically ignored, while the actual work continued however it actually continued.

That isn't standardized work in the Toyota sense. That's a document on a clipboard.

What the booklet shows

The Dual Dynamics section walks through the four work sheets Toyota uses: the Production Capacity Sheet, the Standardized Work Combination Table, the Standardized Work Chart, and the Operation Standards Sheet. Each does a different job. The Standardized Work Chart, for example, “shows figures for the other two elements of standardized work: takt time and standard in-process stock.” The Operation Standards Sheet “carries step-by-step descriptions of every stage in the work sequence.”

These are detailed documents. The booklet shows photographs of actual examples, hand-written and typed, with diagrams.

What the booklet emphasizes about these documents isn't their precision. It's their authorship.

“The team leader at each worksite is in charge of standardized work for his or her team. He or she assigns work in accordance with the monthly production schedule and with the team's capacity. The standardized work changes in reflection of the monthly changes in production, and employees must be able to respond flexibly.”

The standardized work changes monthly. Sometimes faster. The team writes it, follows it, and rewrites it as conditions move. The document on the clipboard isn't the standard. The team's current best understanding of how to do the work is the standard. The document is a snapshot.

What this means for the series

The series started with the Foreword's claim that the key to maximizing quality and productivity lies in tapping the innate judgment and creativity of employees. Five posts later, that claim looks structurally connected to everything else the booklet describes.

The line-stop rope works because employees have authority to stop production. The kaizen 97% implementation rate works because employees have authority to modify their own work. The leadership shadow works because leaders create the conditions for that authority to be exercised. The one-piece flow works because employees can see and act on problems while the causes are still close. And the standardized work and kaizen loop works because the same employees who follow the standard are the ones who write it.

These aren't separate features. They're the same feature, viewed through different windows.

The booklet doesn't make that argument explicitly. It describes each element on its own terms. But reading the booklet end to end, in 2026, with thirty-plus years of Lean writing behind us, the connective tissue is visible. Toyota's system gives employees the authority to do their work, the responsibility to improve it, and the standard to anchor both. Take any of those three away and the system collapses.

That's the argument the booklet was making, in 1992, in a forty-page document, mostly by showing rather than telling.

Where the series leaves it

I started this series wondering whether a 1992 Toyota document still had something to say in 2026. After reading it carefully and writing six posts about it, my answer is yes, but probably not in the way the booklet's authors expected.

The booklet does describe the mechanisms – the kanban, the andon, the leveling box, the work sheets. Most of those mechanisms are now well-documented elsewhere, often in more depth. A reader who wants to understand how to implement them has better resources.

What the booklet still has to offer is the framing. Toyota in 1992 didn't separate culture from technical practice. They didn't separate leadership from worker authority. They didn't separate standardized work from kaizen. The system was one thing, and the booklet describes it as one thing, even when the description is uneven.

The field has spent thirty years pulling those threads apart, naming them separately, and writing books on each. Useful work, much of it. But the booklet's original framing – that this is all the same activity, performed by the same people, on the same loop – is worth recovering.

If you're a leader trying to build something like what Toyota built, the question isn't which tool to start with. The question is whether your employees have the authority to write their own standards, the responsibility to improve them, and the support to do both.

What standard did your team revise this month, and who decided it needed revising?