In the last article, we walked through the logic chain that takes a financial goal at the top of a plant and turns it into a short list of specific processes — the 20% that deserve Level 5 maturity, while the rest stay solid at Level 2-3.
The article ended with a tool: the Level 5 Targeting Self-Assessment, which runs that exact chain on your own numbers in fifteen minutes.
This article is what happens when you run it.
To make the example clear, I built a hypothetical plant — AdaptiveOps Production — and ran the full assessment with realistic but illustrative numbers. The point is not the plant; the plant is fictional. The point is what the assessment produces, what it means, and how every output connects to a specific process discipline you may already recognize.
If you have read the earlier articles in this series, you will see them come together here.
The Setup: AdaptiveOps Production
Imagine a manufacturing operation with significant headroom to improve. The leadership team has set a clear True North for the year — the single goal that, if achieved, makes everything else secondary:
Plant Cost Rate: reduce from €30 to €25 per unit.
A €5 reduction per unit, on a plant producing millions of units annually, is a meaningful number — large enough to change the plant's competitive position with its customers, large enough to require coordinated effort across departments, small enough to be plausible in a twelve-month horizon if the chain is built correctly.
This is the kind of target that makes operational excellence work matter. It is also exactly the kind of target that gets missed, year after year, when plants act on intuition instead of decomposition.
For the choice of True North as a single financial number — and why having more than one annual priority is the same as having none — see the True North article.
Step 1: The Maturity Reality Check
The first step of the assessment is honest about where the plant actually stands. AdaptiveOps Production rates its key processes on the 0-5 maturity scale, and the distribution that emerges is the most common pattern I see in real plants:
Most processes sit at Level 2-3. Almost nothing operates at Level 4-5.
This is the profile of a competent, well-managed plant. Documentation exists. Standards are followed. A Daily Management System runs. Improvements happen year over year. The foundation is real — and yet, when a financial gap of €5 per unit appears, the same foundation that delivered last year's results cannot reach this year's target.
That is not a failure. It is a signal. A plant operating at Level 2-3 across the board has reached the ceiling of what reactive management can deliver. To remove €5, some processes have to become predictable, statistically controlled, and eventually self-regulating — Level 4 and Level 5.
The question, as we established in the previous article, is which ones.
For the full maturity scale and what each level actually means in practice, see the Process Maturity 0-5 article.
Step 2: Decomposing the €5 Into KPI Movement
The True North is financial. The drivers are operational. The bridge between them is a set of Key Performance Indicators, each with a specific numerical target.
AdaptiveOps Production identifies six KPIs that, taken together, drive Plant Cost Rate. The assessment captures the current value, the target, and the required move:
This is the moment most plants skip. They will state that they want to "improve OEE" without ever calculating by how much OEE has to move to deliver the financial result they have committed to. Or they will set a target — "raise OEE to 65%" — without checking whether that target, even if achieved, contributes meaningfully to the cost gap.
The discipline at this step is twofold. First, every KPI gets a specific numerical move, not a directional intention. Second, the moves are sized so that, combined, they deliver the €5. Not approximately. Specifically.
Building the precise conversion model — how exactly each percentage point of OEE translates to a euro contribution at this plant's cost structure — is the part that requires real financial data, real product mix, and a calibration we do with clients directly. The assessment tool runs the logic and gives directional targets. The full model gives provable euro-by-euro contributions.
The language of these KPIs — percentages, rates, parts-per-million — is the language of the Area Manager. For why this language matters, and why operators should never see percentages, see the KRI/KPI/PI article.
Step 3: From KPIs to Six Named Processes
Each KPI is broken open through its process indicators, and the loss components are traced to the underlying process — and the department that owns it.
The assessment output for AdaptiveOps Production lists nine processes in total. Six of them are primary drivers — the principal route by which a specific KPI moves. These are the candidates for Level 5.
1. Changeover / setup on the bottleneck line — Engineering
Drives: OEE (primary)
Every minute lost on changeover at the bottleneck is a minute the plant cannot recover anywhere else. OEE is most sensitive to availability, and availability is most sensitive to setup time on the line that defines plant throughput.
To take this process to Level 5 means more than running a SMED workshop. It means standardized setup that produces the same time every time, deviation detection in real time, and automatic triggers when a changeover exceeds its target — without anyone having to decide to escalate.
This connects directly to the Daily Management System — see how to build a DMS that actually works — and to the gemba walks that verify it on the floor, covered in why most gemba walks are just expensive factory tours.
2. Operator cross-training & skill matrix — HR / Production
Drives: Labor Efficiency (primary)
Labor efficiency loses ground in two ways: when operators are absent, and when the operators who are present cannot cover the stations that need running. A cross-training process at Level 5 turns absenteeism from a crisis into a managed input.
This is one of the most underrated process disciplines in operational excellence. Most plants track absenteeism as a lagging indicator — number of absent employees per day. A more useful PI is the one I described in the gemba walk article: number of cross-trained operators available per line per shift. That PI measures the plant's capacity to absorb absence, not the absence itself.
This is also the prototypical example of a flexible PI — one that becomes critical seasonally, in autumn and spring when illness rates spike. A Level 5 cross-training process automatically elevates the cross-training availability PI during those windows. The system adjusts; the team does not have to remember.
For more on the cross-training example and how PIs become seasonally critical, see the gemba walk article.
3. Material flow & handling — SCM / Logistics
Drives: Scrap Rate (primary)
This one surprises Plant Managers when the assessment surfaces it. Scrap is intuitively a Quality problem — defective products, capability issues, operator error. But a significant share of scrap in most plants originates in how material moves: damage in transit, contamination during transfer, wrong material delivered to a station, expired material used because FIFO discipline failed.
A Level 5 material handling process detects flow deviations before they cause scrap: temperature excursions, FIFO violations, route deviations, container damage. The PI moves from "scrap parts at end of line" to "material handling events per shift" — a leading indicator that prevents the lagging one.
When this process is identified as critical, it usually becomes a funded project in the Annual Improvement Plan. For how the AIP turns critical processes into structured improvement work, see the AIP article.
4. Problem solving / root cause closure — Quality / Continuous Improvement
Drives: Internal PPM (primary)
Internal PPM is the canary in the coal mine. Defects caught inside the plant are cheaper than defects caught by the customer — but if internal PPM is high and not falling, the problem-solving discipline is broken.
A defect occurs. A 5-Why or 8D is opened. It gets closed with an action: "operator retrained." Two weeks later, the same defect reappears under a slightly different description. The cycle repeats indefinitely.
Level 5 problem-solving means root causes are actually closed — verified through repeated absence of the defect, not through the conclusion of a meeting. The system tracks reopened items as a primary metric, because reopens are the signal that closure was theatrical, not real.
This is the failure mode most directly connected to a dying Daily Management System — when the same red items reappear week after week, the problem-solving process is broken upstream. See 5 Signs Your DMS Is Dead for the diagnostic.
5. Customer complaint / containment — Quality
Drives: External PPM (primary)
External PPM is what the customer sees. It is the most expensive defect category — not because of the defect itself, but because of containment, sorting, penalty cost, and the relationship damage that compounds.
A customer complaint process at Level 5 is fundamentally about speed and structure. The complaint arrives. Containment activates within hours, not days. Root cause investigation runs in parallel to containment, not after it. Communication to the customer follows a structured cadence, with named owners and committed timelines.
The PI here is not "number of complaints." It is hours from complaint receipt to confirmed containment and days from complaint receipt to verified root cause closure. An unresolved complaint generates penalty cost that lands in the plant's financial result, and a damaged relationship loses future programs that would have made the next True North achievable.
6. Engineering change control — Engineering
Drives: Obsolete / Write-off (primary)
Every engineering change carries an inventory risk: the parts that become obsolete the moment the change takes effect, the work-in-progress that has to be reworked, the safety stock that no longer fits the new specification.
A change control process at Level 5 does not slow down engineering changes — it sequences them. It calculates the inventory exposure of each change before approval, schedules the change to coincide with low-inventory points, and triggers depletion runs on legacy parts before the change activates.
The PI is inventory write-off per engineering change — a number that, when monitored consistently, makes the cost of poorly sequenced changes visible to the people approving them.
What's NOT on the List
The assessment generated nine processes total. Six are above. The other three — standardized work adherence, preventive maintenance, production planning — are real and important, but their contribution to the €5 gap is secondary.
This is the discipline the Pareto cut enforces. Standardized work matters; it should be solid. Preventive maintenance matters; it should be reliable. Production planning matters; it should be sound. But none of these processes, by themselves, will be the difference between hitting €25 and explaining why the plant landed at €27.
They stay at Level 2-3. They get attention through the Daily Management System. They do not absorb the scarce resource of improvement capacity that the six primary processes require.
And the dozens of other processes the plant runs every day — receiving, audit response, training administration, internal communication, environmental compliance — do not appear on the list at all. They function. They should not be on a Level 5 transformation roadmap, because the investment would not return.
What Happens When Six Departments Share One Number
Read the candidate list again, slowly. Notice who owns each process:
Changeover — Engineering.
Cross-training — HR.
Material flow — SCM.
Problem solving — Quality / CI.
Customer complaint — Quality.
Engineering change — Engineering.
Six processes. Five departments. One number at the top: €30 → €25.
Something happens to a leadership team when this list appears on the wall — something that no team-building exercise produces and no methodology mandates directly. The HR Director does not work on "absenteeism" anymore. She works on the cross-training process that feeds labor efficiency that contributes to the €5. The SCM Director does not optimize "logistics" anymore. He optimizes the material flow that reduces scrap that contributes to the €5. The Quality Director does not chase "PPM in general." She closes the specific problem-solving and complaint processes that contribute to the €5.
Same work. Completely different alignment.
For the first time, every department head is accountable for a contribution to a single number that the Plant Manager owns. The improvement conversations stop being departmental — "HR is doing fine on absenteeism, but Maintenance is behind on PPM" — and start being unified: "we are at month six, we have removed €2.40 of the €5, and the gap is in the cross-training process specifically."
This is the result that justifies the entire methodology. The candidate list identifies which processes deserve Level 5. The shared number forces six department leaders to operate as one team — pulling in one direction because the mathematics of the chain leaves them no other coherent choice.
A leadership team that has built this chain together stops debating priorities at every meeting. They debated them once, when they set the True North. Everything after that is execution against an agreed map.
What the Tool Gives You — and What It Doesn't
The assessment produces the candidate list — which processes matter, who owns them, and why each one connects to the True North.
What the assessment cannot produce is the precise euro contribution of each process to the €5 gap. That requires a calibrated conversion model built on the plant's real cost structure: actual fixed cost allocation, actual contribution margin per product, actual labor and overhead breakdown.
It also cannot produce the next layer down — the maintenance metrics that calibrate equipment availability, the changeover-time targets that translate setup discipline into OEE gain, the inventory thresholds that translate engineering change sequencing into write-off avoidance. That layer is where the chain stops being directional and becomes prescriptive.
The tool tells you where to look. The conversion model tells you exactly how far each lever has to move.
What Comes Next
The candidate list and the shared number produce the structural conditions for alignment. But alignment is not automatic — even when the chain is built, leadership teams can still drift back into departmental optimization within weeks.
In the next article, I will go deeper into the mechanism this article only introduced: how a single annual goal, when set and communicated correctly, becomes the engine that produces sustained focus, real teamwork, and the kind of cross-functional ownership that no organizational chart can mandate. Why some leadership teams stay aligned for twelve months — and why others collapse back into silos by quarter two.
At AdaptiveOps, we work with manufacturing plants to build this chain end to end — from True North definition through the KPI conversion model to the named processes that deserve Level 5. If you want to map this for your plant, book a free 30-minute diagnostic call — or run the Level 5 Targeting Self-Assessment first to see your own candidate list.
Related: Is Your Plant at Level 1 or Level 5? — the maturity assessment this series builds on.
Related: Not Every Process Deserves Level 5 — the previous article in this series, with the full logic chain.