Lean maturity is useful when it helps leaders see what capability is missing. It becomes dangerous when the score, stage, or assessment starts replacing the business result. An organization does not exist to move from level two to level three on a maturity model. It exists to create value for customers, develop people, and improve performance in a way that lasts.
This distinction is easy to lose in a transformation program. Teams can complete training, install visual boards, and report a higher score while delivery, quality, cash, safety, or customer experience barely changes. The activity may be genuine, but the sequence is backwards.
Illustrative photograph. Photo: PJ Wallace / Unsplash.
Lean maturity is a diagnostic, not a destination
A maturity model gives leaders a structured view of current practices. It can reveal sporadic problem solving, fragile standard work, dependence on escalation, or improvement disconnected from strategy. Used this way, Lean maturity creates a common language and highlights capability gaps.
The model cannot, however, decide what deserves attention first. Two operations with the same maturity score may need completely different interventions. One may be constrained by unreliable equipment. Another may have excellent equipment but weak production planning. A third may be losing customers because supplier quality is unstable. Moving all three through the same roadmap would be tidy, but not necessarily effective.
The better question is not, “What should we implement next on the Lean ladder?” It is, “What is preventing this business from achieving the result that matters now?” Only after that question is clear should leaders select the methods, systems, technology, or organizational changes that fit the cause.
How maturity programs drift away from performance
Drift occurs when the means become easier to manage than the ends. Training, audits, and improvement events are easy to count. Business outcomes are harder: they cross functions, involve trade-offs, and expose assumptions about how the system works.
Four patterns usually signal that the program has become score-led:
- Uniform sequencing: every site receives the same toolkit regardless of its constraint or customer problem.
- Activity as evidence: workshops, certifications, and boards are treated as proof of improvement rather than inputs to it.
- Local optimization: one department improves its metrics while lead time, inventory, or service worsens across the value stream.
- Audit behavior: teams prepare for assessments instead of using the model to expose weaknesses and learn.
None of these means the maturity model is wrong. They mean governance has disconnected it from the outcomes it was meant to support.
A business-first framework for choosing the next improvement
A practical alternative is to place business performance at the front of the improvement cycle. The following five-step framework keeps Lean maturity in its proper role.
1. Define the result and the boundary
Name one result, the affected process, the baseline, and a useful time horizon. “Improve delivery” is too broad. “Increase on-time, in-full delivery for this product family within two quarters” is testable. Add guardrails so delivery is not improved at the expense of safety, quality, inventory, or workload.
2. Find the system constraint
Go to the work, follow the end-to-end flow, and separate symptoms from causes. Is demand released erratically? Is the bottleneck starved or blocked? Is equipment unstable? Are suppliers driving schedule changes? The constraint may sit outside the area where the problem appears.
3. Diagnose the capability gap
Now use the Lean maturity model. Ask which missing capability allows the constraint to persist: daily management, standard work, problem solving, maintenance, leader behavior, strategy deployment, or cross-functional planning. The assessment becomes evidence—not a report card.
4. Select the smallest coherent response
Choose an intervention that matches the cause. The response could combine Lean methods with supplier development, maintenance, leadership routines, a digital tool, capital investment, or a policy change. Avoid a broad program when a focused experiment can test the logic faster.
5. Verify the result and sustain the capability
Track both the outcome and the process condition expected to produce it. If the change works, standardize it, develop the people who will maintain it, and confirm the result holds after attention moves elsewhere. Then reassess the system.
Match the intervention to the problem
The following table illustrates why a standard maturity roadmap should not automatically determine the next move.
| Visible business problem | Question to investigate | Possible response | Outcome measure |
|---|---|---|---|
| Chronic late delivery | Is the constraint capacity, scheduling, reliability, or material availability? | Flow analysis, planning redesign, focused maintenance, or supplier development | On-time delivery and end-to-end lead time |
| Rising conversion cost | Is cost driven by rework, changeovers, overtime, low utilization, or poor product mix decisions? | Root-cause problem solving, setup reduction, quality at source, or policy changes | Cost per good unit, first-pass yield, and overtime |
| Cash trapped in inventory | What creates the need for buffers and excess work in process? | Pull, batch reduction, planning parameters, supplier reliability, or portfolio simplification | Inventory turns, lead time, and service level |
| Improvement gains disappear | Are standards owned, checked, coached, and revised by the people doing the work? | Leader standard work, daily management, coaching, and process confirmation | Sustained result after 30, 60, and 90 days |
Use two scoreboards, not one
A mature operating system needs two connected scoreboards. One shows customer and business outcomes. The other shows enabling capabilities: how reliably teams follow standards, respond to abnormalities, solve problems, develop people, and align improvement with strategy.
Outcome measures alone can encourage short-term fixes. Capability measures alone can reward implementation theater. Together, they test cause and effect. If maturity improves but the outcome does not, revisit the diagnosis: implementation may be weak, the assumed cause may be wrong, or another constraint may govern the system.
Questions leaders should ask before launching another Lean initiative
- Which customer or business result must change, and by how much?
- What evidence shows where the current constraint sits?
- Which capability gap is causally connected to that constraint?
- What alternatives—including Lean, technology, capital, policy, and leadership changes—have been considered?
- What is the smallest safe experiment that can test our assumption?
- Which guardrail metrics will prevent local optimization?
- How will we know the gain is sustained after 90 days?
This discipline makes Lean more relevant: tools solve an important problem, people see why the work matters, and leaders connect capability building to value.
The destination is better business performance
Lean maturity remains valuable as a diagnostic. It shows what an organization can do reliably and what it still needs to learn, informing priorities without becoming the priority.
Start with the business problem. Understand the system that produces it. Build the capability that removes the constraint. Verify the result and sustain the gain. When the sequence is right, maturity grows as a consequence of solving meaningful problems—not as a substitute for doing so.
Frequently asked questions
Is a Lean maturity model still worth using?
Yes. It can expose capability gaps, create a shared vocabulary, and support comparisons over time. Use it as diagnostic evidence alongside business and customer results, not as a standalone measure of transformation success.
Should leaders report Lean maturity scores?
They can, provided each score is linked to the result it is expected to influence. Reporting should also show whether that result improved and whether the gain was sustained. A higher score without a relevant outcome is a reason to investigate, not declare victory.
How do we decide whether Lean, technology, or capital is the right answer?
Begin with evidence about the constraint and its causes. Compare feasible responses, test the smallest coherent option, and measure the effect. Many strong solutions combine management capability, process redesign, technology, and investment rather than treating them as competing camps.
Source and further reading
- Randy Kesterson, “Improving Business Results with Lean Maturity”, LinkedIn. This article develops the central idea from that public post into a practical business-first framework.
- Randy Kesterson, “One Minute Alignment Test”, Lean Community.
- Randy Kesterson, “Key Elements of Successful Transformation”, Lean Community.
8 years as a successful senior advisor and 18 years as an executive leader in the industry. Leadership roles: in Aerospace & Defense and Space,
Industrial (Doosan Bobcat, VP Global Ops & OpEx, John Deere, started career as a mfg engineer), and Corp Board of Director roles, 5 years.
