Standardised Work is a system with a solid architecture in the depths of the document itself.
And its impact, used effectively, is the secret sauce to continuous improvement, productivity (with a solid quality focus) and a dream for digital twinning.
In the previous article we explored. Wait, stop. I explored and some of you read to the end of the blog and may have picked up a few pointers, I hope. Anyway, we explored something that is often overlooked: standardised work is not the document itself, but the system required to create, maintain, teach and confirm it.
The sheets in the workplace are the visible artefact of a much deeper structure. If the lifecycle behind the standard keeps it alive, the document itself must still perform an important task. And oh boy, does it!
For your continuous improvement and customer satisfaction, your standards must make work understandable. Not only to the person performing it today, but to the person who will perform it tomorrow, next month, or years from now. That requires something more than a list of instructions.It requires an architecture.
Why Instructions Alone Are Not Enough
Many organisations believe they have standardised work because they have written procedures.
They list steps. They define sequence… well, sometimes. Most times even that becomes too much of an ask. They sometimes include images or diagrams. But instructions alone do not preserve understanding.
If a step changes slightly, people are unsure why it matters. If something goes wrong, they cannot diagnose the cause. If an improvement is discovered, it remains local because the reasoning behind the work was never visible. If a newcomer arrives and needs training, the tacit knowledge is not available or sturctured. The problem is not that the steps are wrong. The problem is that the thinking behind the steps is invisible. Standardised work must capture both.
The Hidden Power of 1:1:1
This is where the structure often referred to as 1:1:1 becomes essential. It is deceptively simple.
Step
Key Point
Reason Why
Three small elements. Yet together they transform instructions into knowledge. Portable, trainable, improvable knowledge.
The step defines what is done.
The key point highlights what must not be missed.
The reason why explains the consequence of not following the key point.
Without the reason why, the standard only describes behaviour. With it, the standard describes causality, and causality is what allows people to think.
If you are still with me at this point, I’d like to thank you for geeking out on this. Stay with me on the journey, because so many, including colleagues in the business improvement world, will be swishing over to some other page and are going to miss the magic sauce. Persistence is a virtue.
Step: The Visible Sequence
The step describes the order of work. It defines the sequence required to maintain safety, quality and flow. This matters because sequence stabilises the process. It ensures that every operator begins from the same baseline. Without a defined sequence, variation is one step away from wreaking havoc with your value stream. Small differences accumulate overtime, and eventually the system, without standards and a chosen sequence, becomes unpredictable. The step therefore creates consistency. But consistency alone is not enough.
Key Point: The Critical Moment
The key point identifies the element of the step where something important could go wrong. It’s the ‘watch out’ for safety, quality, knack or dependency. Think of it as mum’s index finger pointing at the sky, raising a flag indicating an imminent consequence is to follow. You’ve had the warning, you’re mind is focussed.
In complex work, most steps are routine. But within those steps are moments where precision matters. The key point highlights these moments so that experience is not required to recognise them. This is where the knowledge transfer happens, and yet, we are still missing the crucial element.
Reason Why: The Transfer of Understanding
The reason why answers the question that every learner eventually asks: Why does this matter? It connects the action to the consequence. And like my mum’s index finger, I knew there were consequences for not following the ‘watch out’ – key point.
Tighten this bolt to this torque. Because the seal will fail if it is not.
Insert the component in this orientation. Because airflow depends on it.
Try that one more time, Mark. Because the flip-flop will follow. No soft parenting in 70s Africa, I’m afraid.
Here’s a good example of a 1:1:1, and if you haven’t read my blog on the history of Standardised Work, click here
When people understand the reason, they gain the ability to recognise problems and suggest improvements. The standard no longer restricts thinking. It invites curiosity and improvement.
From Compliance to Capability
This is the transformation that 1:1:1 enables. Without it, standardised work produces compliance, whereas with it, standardised work produces capability and endless improvement. Operators are not simply repeating behaviour, they are learning how the system behaves, detecting abnormal conditions earlier as they adhere to the one best way built with their input.
They can reflect more effectively, and contribute improvements that make sense within the process. This is why standardised work sits at the centre of continuous improvement. It does not freeze work or straitjacket improvement, rather it stabilises it long enough for learning to accumulate.
Why the Architecture Matters
The structure of the document determines whether knowledge can survive turnover. People will always move roles. Teams will always change. Leaders will eventually leave. If the knowledge behind the work remains in people’s heads, it disappears with them. But when the thinking behind the work is embedded in the standard, capability becomes structural. The organisation remembers, and not because people stay forever but because the knowledge has been captured in a form others can understand.
Standardised Work Is Not Just a Document
By now the picture becomes clearer.
My last blog showed that standardised work requires a lifecycle: creation, governance, training and confirmation.
This blog reveals that the document itself must also be designed carefully. It must not simply record what people do. It must explain why they do it. This is the difference between documenting work and preserving knowledge.
Looking Ahead
In the final article of this series I will return to the improvement flag. What, I hear you say? Has he not banged on enough about that. Is there really something else to be said. Well, yes. If standardisation occupies half the flag, it raises a difficult question:
Is standardisation also half the gap in our understanding of Lean?
Because without it, improvement does not accumulate, it resets. And the organisation forgets what it once knew.
Thanks for geeking with me.
