In the first conversation, almost every Plant Manager I have worked with placed their plant at Level 3.
"We have a Daily Management System." Level 3. "We have an Annual Improvement Plan." Level 3.
"We run gemba walks every week." Level 3.
Then we walked the floor together. We attended the Monday morning meeting. We pulled three random Process Indicators from three different lines and traced them back to a target. We asked an operator what the True North goal of the plant was for this year.
By the end of that first day, the conversation had changed. Not because anything was wrong — but because the question itself had become more precise.
The Plant Manager was not at Level 3. The plant had Level 3 components. The plant operated at Level 1.
This is the most consistent pattern I have observed across eight Tier-1 automotive plants where I led the operational excellence implementation: the gap between what is installed and what is operational is enormous. And almost nobody measures it.
A maturity model fixes that. It separates installation from operation, ceremony from substance, board from behavior. Once you know what level you are actually at, every improvement decision becomes simpler — because you stop trying to fix Level 4 problems while your plant is still operating at Level 1.
Here are the five levels. Read them carefully — at the end, you will find a five-minute self-assessment that tells you exactly where your plant operates today.
Level 0 — The Process Is Undefined
The process exists because something is being produced. But nobody could draw it on a whiteboard if you asked them to.
Different shifts run it differently. Different operators run it differently. Different days run it differently — based on who is on vacation, which materials arrived, what the maintenance situation is. There is no documented standard. There is no agreed sequence. The output depends on who is in the building.
At Level 0, the plant is running on individual heroism. The team leader who knows the line keeps it running. When she goes on holiday, output drops. When a new operator joins, the learning curve takes weeks because there is nothing to learn from — only people to watch.
You are at Level 0 if you cannot produce, on demand, a single document that describes how a key process is supposed to be performed.
This is more common than people admit. Many plants have process documents that have not been updated in five years, do not match what the operators actually do, and exist only because an auditor required them. That is still Level 0.
Level 1 — The Process Is Documented
At Level 1, the process exists on paper. SIPOC diagrams have been drawn. High-level process maps have been created. A detailed process map identifies the inputs, outputs, and key steps.
The work has been done — but only the work of documenting. The documents may not match the actual operation. They may not be visible at the workstation. They may not be referenced when problems occur.
A plant at Level 1 has the foundation but not the discipline. The maps exist in a folder on a shared drive or in a binder in the team leader's office. They were written for an audit, for a certification, for a consulting engagement that ended two years ago.
The diagnostic question at Level 1: when was the last time someone updated a process document because the process changed?
If the answer is "I am not sure" or "the documents have not been updated since they were created" — you are at Level 1.
Most plants I work with believe they are above this level because they have done the documentation work. Documentation without maintenance is Level 1. Period.
Level 2 — The Process Is Standardized and Controlled
At Level 2, the process documents are not just written — they are followed.
Standard Work Instructions exist at the workstation, in the language the operator reads, in the format the operator can use during the shift. A Control Plan defines what is monitored, by whom, and how often. When a deviation occurs, there is a defined procedure for what happens next.
The shift from Level 1 to Level 2 is the shift from having a standard to operating against a standard. It requires three things: visible documentation at the gemba, regular audits that verify the standard is being followed, and a feedback mechanism that captures when the standard is wrong and needs updating.
You can recognize Level 2 by walking the line. If the operator can show you the standard work instruction for the task she is performing — and that instruction matches what she is doing — you are at Level 2 at least on that station.
If she cannot show it, or if it is hanging on the wall but she does not consult it, or if what she is doing does not match what is written — you are still at Level 1.
A common failure at this level: standards exist for the easy work and not for the hard work. The simple assembly task has a perfect SWI. The complex changeover, the difficult quality decision, the rare-but-critical equipment intervention — these are run from memory.
Level 2 is process discipline applied uniformly, not selectively.
Level 3 — The Process Is Planned, Organized, and Measured
At Level 3, the plant operates a coordinated system, not just a set of standardized processes.
The Annual Improvement Plan (AIP) is in place — translating the True North goal into prioritized projects with clear ownership and milestones. Resource planning balances workload against demand. Polyvalence matrices identify cross-trained operators who can absorb absence or volume changes. Layout supports the flow, not the legacy. 5S has been implemented and is sustained.
Most importantly, the measurement system at Level 3 begins to differentiate by audience. Operators see Process Indicators (PIs) in their language — kilograms, pieces, minutes. Area managers see Key Performance Indicators as rates and percentages. The Plant Manager sees Key Result Indicators in euros, connected to financial impact.
The cascade exists. Each level can act on what they see.
A plant at Level 3 is doing operational excellence. The Daily Management System (DMS) runs. The Annual Improvement Plan generates projects. Gemba walks happen with purpose. Things improve, year over year.
This is where most well-managed plants in Central Europe operate today. It is good. It is not enough.
The signal that you have reached Level 3 is not the presence of all these tools — it is the integration between them. The DMS escalates problems that connect to AIP projects. The gemba walks verify PI trends that feed KPI dashboards. The True North is referenced when priority conflicts arise, not just at annual planning.
If your tools exist but operate in parallel without informing each other, you are at Level 2 with Level 3 components installed.
Level 4 — The Process Is Visualized and Predictable
At Level 4, the plant becomes legible at a glance.
Visual management is comprehensive — not as decoration, but as operational reality. Standing at any workstation, in any cell, on any shift, you can see within thirty seconds: what is the standard, what is the current state, what is the gap, what is being done about it. The information is where the work happens, not in an office or a meeting room.
But the deeper shift at Level 4 is statistical. Process variation is understood, not just measured. Control charts distinguish common-cause variation from special-cause events. Tolerance bands reflect actual process capability, not aspirational targets. Problems are identified by patterns in data, not by waiting for failure.
At Level 4, the plant has moved from reactive to proactive. A bearing that will fail in three weeks is identified by vibration trend, not by the sound it makes the morning it seizes. A quality drift that will cause a customer complaint in two weeks is identified by SPC alert, not by the return shipment.
This is where the operational excellence investment starts to compound. The same team produces more, with less variation, with fewer interventions, because the system itself is telling them where to look.
Level 4 requires data discipline. It requires team leaders trained in statistical thinking. It requires a measurement infrastructure — typically digital, but not necessarily — that captures enough data with enough fidelity to detect patterns before they become problems.
Most plants believe they have visual management because their boards are colorful. Visual management at Level 4 means an outsider who has never seen the plant can understand the operational state in under five minutes. If that test fails, the boards are decoration. You are still at Level 3.
Level 5 — The Process Is Self-Regulating
At Level 5, the process detects its own deviations and triggers its own corrections.
This is not automation in the conventional sense. A robotic line that runs without operator intervention is not Level 5 — it is automated Level 2. Level 5 is about the management system, not the production system. It means the plant has built mechanisms that absorb variation, identify drift, and initiate response before human attention is required.
Examples of self-regulating behavior at Level 5:
When the morning meeting identifies a deviation, the escalation path is automatic — the right person at the right level is notified within minutes, with the data they need, without anyone having to decide to escalate. When a PI trend crosses a defined boundary, a structured response protocol initiates. When a process step takes longer than its standard time, the team leader receives an alert and the data simultaneously.
Level 5 is what most plants imagine when they envision their future state. It is also what almost no plants outside of specific Toyota facilities and a few elite manufacturers have actually achieved at scale.
Reaching Level 5 in a meaningful way typically requires three conditions that very few plants meet:
First, the plant must operate at Level 4 across all critical processes — not just some. Level 5 cannot be built on top of inconsistent foundations.
Second, the management system must be supported by a digital infrastructure capable of real-time signal aggregation and intelligent response routing. Manual systems cannot self-regulate at the speed and scale required.
Third, the leadership team must trust the system enough to delegate to it — to allow the structured response to happen without intervention, to coach when the system needs adjustment rather than override when it produces uncomfortable signals.
If you are at Level 3 with strong components, Level 5 is two to three years of disciplined work away. If you are at Level 1, it is a journey of five years or more — but every level along the way produces measurable value.
The 5-Minute Self-Assessment
Read each question. Answer honestly. Be specific.
Question 1 — Documentation Can you produce, in under five minutes, the documented process for your three highest-volume operations — and verify that what is documented matches what is actually being done on the floor right now?
If yes → at least Level 1 If no → Level 0
Question 2 — Standard Work Discipline Walk to a random workstation. Can the operator show you the Standard Work Instruction for the task she is performing, and does it match her actions?
If yes for the first three stations you check → at least Level 2 If no for any of them → Level 1
Question 3 — System Integration Take a deviation discussed in this morning's DMS meeting. Trace it to an AIP project, a KPI trend, or a True North impact. Can you do it in under two minutes, using only information that is publicly visible to the team?
If yes → at least Level 3 If no → Level 2 with Level 3 components
Question 4 — Visual Operational State Invite someone who has never worked in your plant — a friend in a different industry — to walk the production floor for fifteen minutes. Can they describe the current operational state, identify which areas are performing well or poorly, and explain what is being worked on?
If yes → at least Level 4 If no → Level 3
Question 5 — Self-Regulating Response When a critical PI breached its tolerance band last week, how did the response start? Was it triggered by a defined system mechanism (alert, protocol, automatic escalation) — or did it start when a human noticed and decided to act?
If system-triggered → at least Level 5 on that process If human-triggered → Level 4 maximum on that process
What the Result Means
If you answered "no" at Question 1, your plant is at Level 0 — and the priority is fundamental documentation work before any other improvement initiative will sustain.
If you reached Question 3 but failed it, you are where most well-managed plants in this region operate: Level 2 with Level 3 components installed. The components exist but do not integrate. The next priority is connection, not addition.
If you reached Question 4 but failed it, you are at Level 3. You operate a coordinated system. The next priority is visualization and statistical thinking — making the system legible and predictive, not just functional.
If you reached Question 5, you are operating at Level 4 in the processes you tested. Level 5 is a strategic decision about infrastructure investment, not just operational discipline.
Most plants will land between Level 1 and Level 3. That is not a failure — it is the starting point. The damaging mistake is misclassifying your level: a plant that believes it is at Level 4 while operating at Level 2 will invest in solutions for problems it does not yet have, while ignoring the foundations it lacks.
The single most valuable use of this assessment is the conversation it triggers internally. Bring it to your operations leadership team. Have each person answer independently. Compare results.
The disagreement is the diagnostic. If your Quality Manager and your Production Manager place the same plant at different levels, you have surfaced an alignment problem that was previously invisible — and that alignment problem is itself a Level 2 issue you can act on this week.
Where to Start
The five levels are not a ladder you climb in order. They are a diagnostic that tells you where the most valuable next intervention is.
If you are at Level 0 — write the process. Not for an audit. For the operator who needs to know what good looks like.
If you are at Level 1 — make the standards live at the gemba. Print them. Put them at the workstation. Audit them. Update them when reality changes.
If you are at Level 2 — connect what you have. Make the DMS feed the AIP. Make the gemba walk verify the PIs. Make the True North visible in every level of the cascade.
If you are at Level 3 — invest in visualization and statistical capability. Train your team leaders to think in patterns, not events. Build the boards that an outsider can read in five minutes.
If you are at Level 4 — design the infrastructure that allows your system to respond without you. This is where digital tools begin to matter — not as efficiency tools, but as the substrate for self-regulation.
The goal is not Level 5 for its own sake. The goal is to operate at the level where your plant can compete on the terms your customers and your market require. For most automotive Tier-1 plants in 2026, that is solid Level 3 with selective Level 4 capability in critical processes.
If you are not there yet, the next twelve months are about closing that gap deliberately. If you are there, the next twelve months are about deciding which Level 4 capabilities to invest in first.
At AdaptiveOps, we work with manufacturing plants in Central Europe to assess their actual maturity level, identify the highest-value interventions, and build the systems that move them from one level to the next. If you want a structured assessment of your plant's current state, book a free 30-minute diagnostic call at /contact.
Related: Why Having 7 Priorities Means Having None — the True North that anchors every maturity level.
Related: How to Build a Daily Management System That Actually Works — the foundational system for Level 3.
Related: Why Your Operators Should Never See a Percentage — the measurement cascade required for Level 3 integration.
Related: 5 Signs Your Daily Management System Is Dead — the diagnostic for whether your Level 3 system is real or installed.
Related: Why Most Gemba Walks Are Just Expensive Factory Tours — how to verify your maturity level at the gemba, not in a meeting room.