Standards aren't control — they are freedom

The objection that holds no one back

Tell an experienced employee that their work is to be standardised, and you will probably meet resistance. "It's more complicated than that." "My experience can't be written down." "It will take our flexibility away." The objections are real — and they are all a sign that the standardisation hasn't been explained properly.

Because a standard is not a description of how a capable manager thinks the work ought to be done. It is the documentation of the best known way of doing it — as defined by the people who actually do it. And with one decisive addition: standards are temporary. They apply until we find a better way.

Ohno and Toyota: the standard as the starting point for improvement

Taiichi Ohno — the man who, more than anyone, built the Toyota Production System — put the point directly: "Without standards, there can be no improvement." It is not an equivalent to "we must control what people do." It is a recognition that improvement requires a fixed point to improve from. If two employees solve the same task in two different ways, and the result varies, we don't know whether the variation is due to the method or the person. We can't improve something we can't repeat.

What standards actually free up

Think of a newly trained employee starting in a department without standards. The next months are spent asking colleagues, rediscovering what others already know, and avoiding mistakes that are never documented. An experienced colleague spends time answering questions, correcting variations and making sure things end up right.

Add a good standard. The new employee is productive faster. The experienced employee spends their capacity on improvement, not repetition. The organisation stops rediscovering the same thing — and begins to build on top of it. That is the freedom: freedom from the invisible routine that swallows energy and never puts its name to the task.

Kaizen requires a standard

Kaizen — continuous improvement — is one of Lean thinking's core concepts. But kaizen is only possible if there is a standard to improve from. Masaaki Imai, who popularised the term, was clear: standardisation and kaizen are two sides of the same coin. You standardise the best you know; you improve it; you standardise the new; you improve again. The PDCA cycle is the formalised version of that loop. Remove the standard, and you break the cycle at the first step.

The wrong standard is a problem — not standards as a principle

Yes, there are bad standards. Too bureaucratic, too detailed, written by people who don't understand the work. They create resistance, rightly. But the solution is not the absence of standards — it is better standards. Written by those who do the work. Focused on what actually varies and causes problems. And revised when we know better.

To see what a usable standard looks like in practice, a standard work template is a good starting point. It is built so it can be filled in by the team itself — not imposed from above.