Lean Six Sigma and Strategy Execution: Closing the Gap
There is a well-documented paradox at the heart of organisational performance: most organisations have strategies they cannot execute. The strategy is researched, workshopped, and beautifully presented. It describes where the organisation is going, what it will achieve, and why it matters. Then it sits in a deck, referenced at the annual all-hands and forgotten by the following quarter. The work that actually gets done — the projects, the process changes, the daily operational activity — proceeds without any clear line of sight to the strategic intent. Lean Six Sigma, used well, is the antidote to this disconnect.
Why Strategy Without Execution Infrastructure Fails
The failure of strategy execution is not primarily a strategy problem. It is an infrastructure problem. Organisations that cannot execute their strategies typically share two structural weaknesses. First, they run improvement projects that have no connection to strategic priorities. A team invests months improving a process that is operationally tidy but strategically irrelevant — it is better than it was, but the organisation is not closer to where it needs to go. Second, when improvement does happen, it optimises locally in ways that miss the strategic point. A manufacturing line becomes more efficient, but the strategic need was for faster product launches, not lower unit costs. The improvement is real; the impact on strategy is negligible.
These failures share a root cause: the organisation lacks a systematic mechanism for deploying strategic objectives downward into the work. Without such a mechanism, improvement energy is diffused across hundreds of local decisions that are each reasonable in isolation but collectively do not add up to strategic movement.
The Connection: Strategy, Hoshin Kanri, and DMAIC
The framework that connects Lean Six Sigma to strategy has three components. Strategy defines the destination — the vital few priorities that the organisation must move on to remain competitive and fulfil its mandate. It answers the questions: what must we improve, why does it matter, and how will we know we have succeeded? Without this clarity at the top, everything downstream is guesswork.
Hoshin Kanri — sometimes called policy deployment — is the mechanism that translates strategic intent into annual improvement priorities. Through a structured process of cascading objectives and negotiated targets (the "catchball" process), strategic goals are decomposed into departmental priorities and then into specific improvement projects. Every project in a well-run Hoshin system can be traced back to a strategic objective. The connection is explicit, documented, and reviewed.
DMAIC projects — the structured problem-solving engine of Six Sigma — then close the gaps. Once the Hoshin process has identified what needs to improve and by how much, DMAIC provides the rigorous analytical approach to understand the current state, identify root causes, develop and test solutions, and sustain the improvement. Critically, because each DMAIC project has been selected through the Hoshin deployment process, every completed project moves the organisation closer to its strategic destination.
The Vital Few vs. The Trivial Many
One of LSS's most important contributions to strategy execution is the discipline it imposes on prioritisation. The Pareto principle — that roughly 80 per cent of effects come from 20 per cent of causes — applies to improvement opportunities as readily as it applies to defects. Most organisations have more improvement ideas than they have capacity to pursue. Without a structured prioritisation process anchored to strategy, organisations default to the most visible problems, the most vocal advocates, or the easiest wins.
A strategy-connected LSS programme forces a different question: not "what problems do we have?" but "which problems, if solved, would most advance our strategic priorities?" That shift in framing — from operational firefighting to strategic problem selection — is often the single most valuable thing an LSS programme brings to an organisation.
Building the Execution Infrastructure
The practical steps for connecting LSS to strategy execution include establishing a project selection process tied to the strategic plan, building a project portfolio that is reviewed at the leadership level, creating standard measures of project impact in strategic terms (not just process metrics), and developing the internal capability to sustain the programme. None of these steps is technically complex. All of them require sustained leadership commitment — which is why the absence of that commitment is the most common reason LSS programmes produce activity without strategic movement.
Organisations that get this right build a compounding advantage. Each completed project contributes to strategic goals while also developing internal problem-solving capability. Over time, the organisation becomes faster at identifying what matters and more capable of acting on it. That combination — strategic clarity plus execution discipline — is what separates organisations that execute from those that plan.
XNM Consulting helps organisations build strategy execution capability grounded in operational excellence. Learn more on our Strategic Advisory page.