3 Lean Six Sigma tools that work outside the factory
The 5 whys, a map of your own time and the PDCA cycle. Three shop-floor tools that work just as well on an ordinary week.
Lean Six Sigma puts two methodologies together: lean removes what adds no value, and Six Sigma reduces the variation of what does.
Enter your email and you will get an alert when something new is published. Unsubscribe anytime.
Three of its tools work just as well outside a factory. And you don't need any training for any of them.
1 · The 5 whys
Faced with a problem, you ask "why?" five times running until you get from the symptom to the cause.
I'm late in the mornings. Why? I leave with no time to spare. Why? I get up late. Why? I turn the alarm off half asleep. Why? It's on the bedside table. Why? Because at night I use it as a phone too.
Notice where that ends up. The cause wasn't your lack of discipline. It was where the phone is.
Real causes are almost always structural. And the solutions that come out are far smaller than you expected.
2 · Map your own value stream
Value stream mapping applied to your time. You note down for a week where each half-hour block goes, without judging yourself, and then sort each activity into three piles: adds value, doesn't add value but is needed today, and doesn't add value and could go now.
It surprises you the same way it does in a plant. The proportion of genuinely productive time is rather less than you think. And the main thief is hardly ever the one you suspected.
3 · The PDCA cycle
Plan, Do, Check, Act. Applied to a personal change, it saves you from the classic mistake: trying ten things at once and not knowing which one worked.
| Phase | In practice |
|---|---|
| Plan | decide ONE change and how you'll know it works |
| Do | try it for a fixed period |
| Check | compare it against the starting point |
| Act | if it works, make it routine; if not, change it |
The key is in the P: one change at a time. With three simultaneous changes there's no way of knowing which produced the effect.
The catch?
That all three share a condition that makes them genuinely difficult: they demand data nobody collects.
The five whys stay an opinion if nobody knows how often the problem happens. Mapping the stream demands recording times. And PDCA without measurement turns into "it feels like it's improved".
The bridge to 2026
That's the reason I go on so much about the line recording its own behaviour.
Not to pile up data — there's plenty of that everywhere. It's that these tools, which have been good for decades, only work properly when the measuring doesn't depend on somebody finding a moment to do it.
And that moment never turns up. Not in your plant and not in your week.