Skip to content

Standard Work

Definition

Standard Work is the documented, best-known method for performing a process today. Rather than a rigid, unchangeable procedure, it is an intentionally simple, accessible baseline that enables consistency while explicitly inviting improvement. Standard Work specifies: Steps (what is being done), Sequence (in what order and how long it should take), Task Ownership (who is responsible), Methods (what instructions are needed), Materials (what equipment and supplies are required), and Outcomes (what clearly defined, measurable results are expected). The workbook emphasizes keeping Standard Work simple, easy to read, and accessible on the floor—not hidden in a binder. It is continuously improved as people discover better ways.

In the Book

Slides 93-98 define Standard Work and how to create it. Slide 94 states: "Standard Work: Mindful standardization of work. No ambiguity. The best known way to perform a process today." Slide 95 explains why Standard Work matters: it helps "develop the most reliable methods to consistently achieve the best outcomes for each process" by "defining the best known way to perform the process today."

The workbook identifies Standard Work Components (Slide 97): - Steps: What is being done? - Sequence: In what order? How long should it take? - Task Ownership: Who is responsible for each step? - Methods: What instructions are required? - Materials: What equipment and supplies are needed? - Outcomes: What clearly defined measurable results are expected?

Slide 98 provides a "Creating Standard Work" checklist contrasting what to DO and what NOT to do: - DO: Keep it simple, include all info on one easy-to-read document, include key points to optimize technique, make it accessible, always look for ways to improve. - DON'T: Make it overly complicated, put it away in a binder or desk drawer, allow one-off changes on a whim, make it too rigid or difficult to change.

Why It Matters

Standard Work creates a shared baseline. Without it, each person invents their own method, and variation in output is inevitable—quality, speed, and safety all suffer. With it, people know they are doing the same thing consistently, and any deviation becomes visible and discussable. Crucially, Standard Work is not the endpoint—it is explicitly presented as "the best known way today," inviting people to propose and test improvements. This prevents the calcification of bad habits into policy; it also enables reliable diagnosis (if output varies, check whether people are following Standard Work, or whether Standard Work itself needs improvement). This is exportable: any process where consistency matters—surgery protocols, software deployment, customer onboarding, customer service interactions—benefits from explicit, accessible, continuously improved documentation of "how we do this."