STRATEGYOngoing practice

The TPS Maturity Levels Model

Assess where you are, define where to go, close the gap systematically

Problem it solves

unclear strategic direction

Best for

Senior leaders responsible for long-term operational strategy, TPS/Lean directors assessing organizational readiness, and consultants helping organizations plan their improvement journey.

Not ideal for

Organizations just starting with lean who need basic tools first; teams looking for tactical quick wins rather than strategic capability building.

Overview

Why this framework exists

The TPS Maturity Levels Model provides a structured way to assess an organization's current state of TPS implementation and chart a course toward higher levels. The book describes TPS levels from A (beginning) through D and beyond, where each level represents a qualitatively different state of operational capability and thinking.

The model recognizes that organizations cannot skip levels. A company at TPS Level A cannot simply adopt Level D practices. Each level has prerequisites that must be fulfilled before progressing to the next. This prevents the common mistake of copying advanced Toyota practices without having the foundational capabilities to sustain them.

Critically, the model emphasizes that the journey between levels takes significant time and requires instructors who have experience navigating each transition. An instructor who only knows Level D cannot effectively guide a Level A company because they may not understand the intermediate steps required.

Core principles

5 total
  1. You cannot skip maturity levels; each level builds essential capabilities needed for the next
  2. Honest assessment of your current level is the prerequisite for meaningful improvement
  3. The ideal state should be understood but the path must be walked step by step
  4. Instructors must have experience at the learner's current level, not just knowledge of the destination
  5. Progress is measured by capability development, not just metric improvement

Steps

5 steps
  1. Assess Current TPS Level Honestly
    Evaluate your organization against the TPS level criteria by observing actual practices on the gemba. Do not assess based on what policies say or what training has been delivered. Assess based on what actually happens on the shop floor daily.
    Pro tipHave someone from outside your organization do the assessment. Internal teams almost always overestimate their maturity level.
    WarningSelf-deception at this stage undermines the entire improvement strategy. Be brutally honest.
  2. Define the Target Condition for the Next Level
    Based on your current level, define what the next level looks like in concrete, observable terms. Do not aim for Level D if you are at Level A. Focus on what Level B looks like and what capabilities you need to develop to get there.
  3. Identify the Capability Gaps
    Compare your current state to the target condition and identify specific capability gaps. These might include lack of standardized work, insufficient Jidoka capability, absence of production leveling, or inadequate problem-solving skills among front-line leaders.
    Pro tipFocus on people capabilities, not just process capabilities. TPS levels are ultimately determined by the thinking ability of your people.
  4. Build Capabilities Through Practice
    Close the gaps through Jishuken activities, on-the-job training, and guided practice. Each capability should be developed through real application, not theoretical training. Assign qualified instructors who can guide your specific transition.
  5. Reassess and Set the Next Target
    After a period of capability building, reassess your TPS level. If you have genuinely reached the next level, set a new target condition for the level above. This creates a continuous cycle of assessment, improvement, and advancement.
    Pro tipCelebrate genuine level advancement. It takes months or years to move up one level; this is normal and should be recognized as significant achievement.

Checklist

Saved in your browser

Examples

1 cases
Level A Company Attempting Level D Kanban

The book describes situations where companies at the beginning TPS level tried to implement sophisticated Kanban systems because they saw them working at Toyota. Without stable processes, standardized work, or production leveling, the Kanban system created more confusion than improvement.

OutcomeThese companies often concluded that TPS does not work for their industry, when in reality they had simply tried to operate at a level they had not yet earned through foundational capability building.

Common mistakes

3 traps
Attempting to Skip Levels
Copying Toyota's most advanced practices without having the foundational capabilities is the most common failure mode. Advanced techniques like sophisticated Kanban systems require stable standardized work, reliable equipment, and capable problem-solvers as prerequisites.
Overestimating Current Maturity
Organizations commonly rate themselves higher than they actually are because they confuse having tools in place with having capabilities developed. Having Kanban cards on the wall is not the same as having a functioning pull system.
Hiring Instructors Mismatched to Your Level
An instructor who only has experience at high TPS levels may not be able to help a beginner organization because they cannot relate to the challenges of building foundational capabilities. Seek instructors who have experience guiding the specific transition you need to make.

Origin story

How this framework came to be

The TPS Maturity Levels concept emerged from Toyota's decades of experience helping both internal factories and external supplier companies develop their TPS capabilities. OMCD instructors observed that companies at different stages needed fundamentally different guidance and that attempting to implement advanced techniques in immature organizations led to frustration and failure.

Takeuchi describes how he encountered instructors who could describe the ideal state at high TPS levels but could not guide companies through the practical steps needed to move from their current level upward. This insight led to a more systematic approach to assessing maturity and planning the improvement journey.

Source

Traced to primary
Source · BOOK
The Toyota Production System Journey: The Continuously Changing Features of TPS and Lean Thinking
Noboru Takeuchi · 2022
Open source →

Related frameworks

Browse all Strategy →