“Without standards, there can be no improvement.”
Taiichi Ohno’s statement captures a foundation of the Toyota Production System. Improvement requires a visible current method against which a change can be tested. If every operator performs a task differently and the sequence is undocumented, a better result may be accidental and impossible to repeat. A standard makes the present condition explicit: the safest known sequence, expected time, quality checks, and points where abnormality should become visible. It is a baseline for learning, not a declaration that the work is finished.
That last distinction separates useful standardization from rigid bureaucracy. In lean practice, the standard should reflect the best method known now and should change when workers discover a safer, faster, or more reliable approach. The people doing the work are essential authors because they see friction that distant designers miss. A standard imposed without observation or feedback may create compliance theater. A standard developed with the work can preserve gains and give teams a common language for the next experiment.
Not everything valuable can be reduced to a script. Judgment, empathy, research, and creative exploration often need ranges rather than one prescribed sequence. Even repetitive work contains variation that requires discretion. Poorly chosen standards can hide risk, transfer burden, or make a metric look stable while quality deteriorates. The principle therefore demands clarity about what should be consistent—especially safety and handoffs—and where professional judgment must remain free.
The idea applies far beyond manufacturing. Software teams need reproducible deployment and incident routines; hospitals need reliable checks; service organizations need clear escalation paths. In each case, the standard makes deviation observable and learning shareable. Leaders can ask whether a process has a known baseline, whether the people using it can challenge it, and whether improvements are incorporated after testing. Ohno’s lesson is that progress becomes cumulative only when today’s best knowledge is captured well enough for tomorrow’s team to improve. A healthy standard also records why each important step exists. When people understand the risk or customer need behind a sequence, they can respond intelligently when conditions differ. Documentation that lists actions without purpose encourages blind compliance and makes revision harder. Teams can pair the standard with visible measures, examples of abnormal conditions, and a clear method for proposing change. The resulting discipline is neither improvisation nor rigidity. It is a shared hypothesis about the best current way to work, maintained by the people who test it every day. Visible purpose lets disciplined practice and informed adaptation strengthen each other.
Ohno’s maxim summarizes the role of standardized work in the Toyota Production System and continuous improvement.
A defined current method lets teams observe variation, compare experiments, and preserve gains.
A standard is the best known method for now, not an untouchable rule.
Workers closest to the process need authority to expose flaws and help revise the standard when evidence supports change.
Reliable baselines support learning in software, healthcare, logistics, and other high-consequence services.
The principle helps organizations make improvement cumulative without eliminating necessary professional judgment.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.