Understanding Lean Six Sigma - Stefani's Briefs

Lean Six Sigma often attracts mixed reactions, which is usually a sign that it has been widely used, but not always thoughtfully applied. Many of the common critiques are valid, but they tend to reflect how the approach is used in practice rather than a fundamental flaw in the approach itself.

One frequent criticism is that Lean Six Sigma is overly bureaucratic, weighed down by phases, tollgates, and templates which slow teams down. DMAIC was never meant to replace judgement; it exists to prevent us from jumping to solutions before we understand what is actually happening. The documentation package aids the understanding of the problem, but using it mechanically would only create drag.

Another concern is the strong focus on efficiency and metrics, sometimes at the expense of people and customer experience. This usually reflects environments where success is defined through dashboards and savings targets. In reality, Lean Six Sigma is about stability, predictability, and quality. When processes are clearer and more reliable, work becomes less stressful, interruptions decrease, and better outcomes follow.

There is also the argument that LSS does not work well in knowledge-based or complex environments, where work is less repetitive and outcomes are harder to standardise. This critique has merit when the methodology is applied dogmatically, but not all variation is bad, and not all work should be standardised. The real opportunity is rarely in how people think, but in everything around that thinking - unclear inputs, inconsistent handovers, and hidden assumptions that create noise. When LSS is used to stabilise those elements rather than constrain judgement, complexity becomes manageable instead of amplified.

Finally, many point out that Lean Six Sigma initiatives often fail to sustain, however in my opinion this rarely is a tooling problem. Sustainable improvement depends on ownership, leadership, and how deeply improvement is embedded into culture. Without that, even well-designed projects fade once attention or key change agents move elsewhere.

In my experience, Lean Six Sigma is most useful when it leads to real understanding of the work and the issues behind it. When I take the time to look at how the process actually runs, where people struggle, and what assumptions are being made along the way, the solutions I design tend to be much simpler and much more effective, because they fit the reality of the work, instead of fighting it.

That understanding also changes what I focus on when improving a process. Rather than fixing symptoms or adding controls, I can address the conditions that create the problem in the first place. As a result, the changes are easier for people to adopt, they make sense in day-to-day work, and they are far less likely to quietly revert once the initial attention fades. The methodology helps not by forcing solutions, but by guiding me to see clearly enough to design changes that actually work and last.

Ready? Let's talk.