Joseph M. Juran, 1964

“Without a standard there is no logical basis for making a decision or taking action.”

Joseph M. Juran wrote this principle in Managerial Breakthrough, his 1964 account of how organizations move from control to significant improvement. A standard gives people a declared reference point against which actual performance can be compared and a meaningful difference can be discussed. Without a reference, “better,” “late,” “acceptable,” or “safe” can mean something different to every person. A useful standard makes expectations visible, supports measurement, and helps a team distinguish ordinary variation from a condition that deserves investigation and action. Behind the concise wording is a claim about how organizations create results. It encourages leaders to look beyond individual effort and examine design, incentives, information, relationships, and the customer context that determine whether a good intention becomes reliable performance.

Managers can define a small set of customer-relevant measures with an owner, method, frequency, and response threshold. When performance departs from the agreed level, the team should investigate causes and decide whether the process or the standard itself needs revision. Managers can translate the claim into a small experiment with a baseline, an owner, a defined customer or employee outcome, and a review date. Specificity protects the work from drifting into broad language that nobody can challenge or verify.

A standard can preserve mediocrity when it is treated as permanent or designed only for internal convenience. It should reflect evidence, customer need, safety, and current capability, and people closest to the work should be able to challenge an outdated rule. Responsible use also requires naming the tradeoff. Speed, cost, autonomy, safety, equity, and learning may not all improve at once. People closest to the consequences should have a meaningful voice, and uncertainty should be reported instead of hidden behind confidence.

AI systems make standards especially important because “looks plausible” is not an operating requirement. Teams need explicit criteria for accuracy, bias, privacy, security, escalation, and acceptable uncertainty before automated output can support a consequential decision. A standards review can ask which recurring debate lacks a shared definition, establish the reference, and schedule a date to test whether that reference still produces the intended customer outcome. Evidence from the experiment can guide scaling, revision, or stopping. The durable lesson is to join purpose with measurement and human judgment, so the organization becomes better at seeing reality and responding before a local success or failure hardens into mythology. Recording the decision and its limits gives colleagues a foundation they can inspect, challenge, and improve instead of asking them to rely on memory, authority, or an unexplained result.