What We Learned: Lean Six Sigma's Most Important Lessons
Over the past two years, this series has covered Lean Six Sigma from first principles to advanced application: the DMAIC framework, the eight wastes, control charts, voice of the customer, and change management. As the campaign closes, it is worth identifying the lessons that matter most — not the methods and tools, but the insights that change how practitioners think about their work.
Everything Is a Process
The most fundamental shift that Lean Six Sigma produces is the habit of seeing work as a collection of connected processes. Once you develop this lens, you cannot stop seeing it. Customer service is a process. Hiring is a process. Procurement is a process. Budget approval is a process. Even the informal, undocumented, nobody-owns-it-but-somehow-it-works routines that every organisation has are processes — they just have not been mapped.
This matters because processes can be measured, analysed, and improved. A complaint that "things take too long" is unanswerable without a process view: too long where, for whom, and at which step? The process lens turns vague frustrations into specific, solvable problems.
The Process Causes Most Defects — Not the People
W. Edwards Deming estimated that approximately 94 per cent of problems are caused by the system, not the individuals working in it. That figure can be debated, but the direction is correct and the implication is profound. When something goes wrong repeatedly — when the same errors occur, the same delays appear, the same customer complaints come in — the first question should be what in the process is producing this outcome, not who made the mistake.
Organisations that blame individuals for systemic problems make two errors: they fail to fix the actual cause, so the problem recurs, and they demoralise people working inside a broken system. Root cause analysis — asking "why" until you reach the system-level cause — is a corrective to both.
Measure First, Then Improve
The "Measure" phase of DMAIC is not bureaucratic overhead. It is the discipline that separates improvement from opinion. Before a Lean Six Sigma project defines its target, it must understand what is actually happening. What is the current process capability? How much variation exists? What does the baseline data show? Without this, the improvement target is a guess, and the claim of improvement after the fact cannot be verified.
This discipline is harder to maintain than it sounds. Organisations are impatient for action; stakeholders who have already decided on a solution resist measuring first. But projects that skip measurement most often produce solutions to the wrong problem — impressive in a presentation, ineffective in the process.
The Customer Defines Value
Value-added activities in Lean are defined precisely: an activity adds value if the customer would pay for it, it transforms what they receive in a way they care about, and it is done right the first time. Everything else is waste — including many activities that feel essential inside an organisation, such as approvals, reviews, and sign-offs that add time without adding value. The discipline is that the customer is the final arbiter, not the operations team or senior leadership. Organisations that answer honestly what the customer values and design their processes accordingly are systematically harder to compete against.
Small and Fast Beats Large and Slow
The history of process improvement is littered with large-scale transformation programmes that consumed enormous resources, generated impressive presentations, and produced modest lasting results. The pattern is familiar: a broad scope that cannot be managed coherently, implementation timelines measured in years, stakeholder fatigue by the halfway point, and limited accountability for outcomes.
The Lean Six Sigma project discipline — scoped tightly, time-boxed rigorously, measured against a specific and verifiable target — produces better outcomes per dollar and per hour invested. Small, completed, measured projects that build on each other compound into genuine organisational change. The ambition does not have to be small; the projects do.
Leadership Behaviour Makes or Breaks Continuous Improvement
Continuous improvement programmes reflect the leaders who sponsor them. When senior leaders talk about improvement but behave in ways that contradict it — rewarding speed over quality, treating defects as acceptable, letting capacity constraints persist indefinitely — the programme stalls regardless of the quality of the tools or the training. The methods work. The discipline of applying them consistently under pressure is a leadership test, not a methodology test.
The leaders who build genuinely improving organisations ask different questions. They ask what the data shows, not what their instinct says. They ask why things happen, not who is to blame. They treat improvement projects as investments, not costs. They follow up on what was measured, not just on what was done. These behaviours, consistently modelled at the top, are what make the difference between a programme that lasts and one that fades.
How XNM Applies These Lessons
XNM Consulting brings these principles into every engagement. We start with the process view — mapping what is actually happening before recommending what should change. We measure before we improve and verify the results after. We scope improvement work to produce completed, measurable outcomes rather than open-ended transformation. And we work with leadership to build the behaviours that make improvement self-sustaining, not dependent on consultants.
To learn more about how XNM integrates Lean Six Sigma thinking into strategic and operational work, visit our Strategic Advisory page.