Standard Work
The current best-known way to do the work. Until you find a better one.
What is Standard Work?
Standard work is the current best-known method for performing a task, documented clearly enough that any qualified person could follow it and produce the same result. It is not a fixed rule. It is a baseline, captured in writing so improvement has something to start from. When someone finds a better way, the standard work is updated and the new method becomes the next baseline.
Standard work is the most misunderstood concept in lean. The phrase sounds rigid and bureaucratic, like a SOP enforced by managers, and that misunderstanding kills the practice in most shops that try it. Standard work is actually the opposite. It is the current best-known way of doing a task, written down precisely so the team has something concrete to improve. Without standard work, every operator has their own method, drift goes unnoticed, and improvement has no baseline to push against. Standard work is the substrate of kaizen, not the enemy of it.
"Standard work is the floor of improvement, not the ceiling of behavior. Without it, the team has nothing to push against."
How standard work works
Standard work is documented in a form the operator can use at the workstation. Most lean shops use one or more of three standard formats:
- A standard work chart that shows the workstation layout, the sequence of steps, and the movement pattern, with the operator's path drawn on a small floor plan.
- A job element sheet that lists the steps in order, with key points and reasons for each. The key points are the details that matter for quality or safety; the reasons explain why.
- A standard work combination table that sequences manual time, walk time, and machine time across the cycle, used when the work is time-sensitive against a takt target.
The document is built with the operators who do the work, never imposed on them. The most common failure pattern in lean implementations is engineers writing standard work in a conference room and rolling it out to the floor. That kind of standard work is fiction, and the team treats it as such. The standard work that lives is built at the workstation with the people who do the work.
When an operator finds a better way, the standard work is updated. The update is fast, often the same shift, with the team confirming the change. The new method becomes the standard from that day forward. This is the rhythm that distinguishes lean shops from procedure-driven ones. Procedure shops freeze the standard and audit compliance. Lean shops change the standard whenever someone learns something.
Where standard work fits on the shop floor of a small manufacturer
Imagine a 22-person precision parts machine shop where one part requires a particular touch-off sequence to hit a tight tolerance on a feature. The senior machinist has run this part for three years and gets it right every time. Then she goes on medical leave for two months. The shop discovers that the other two machinists who try to run the same part both produce out-of-spec parts on the first attempt.
The shift lead spends two hours with the senior machinist the day before her leave starts, sitting at the machine and writing a one-page job element sheet. Eleven steps. Each step has a key point and a reason. The sheet gets posted at the machine. The second machinist runs the part the next morning and hits tolerance on the second attempt instead of the fifth. The third machinist follows on the next shift, same result.
When the senior machinist returns, she reviews the sheet, suggests one small refinement, and the standard is updated. The shop has not just preserved the knowledge during her absence. It has captured it in a form that improves over time and that anyone can read. That is standard work at small scale. One page, written with the operator, updated when someone finds a better way.
Common mistakes with standard work
- Writing it from a desk. Standard work built without the operator is fiction. The team will follow it for a week, then quietly revert.
- Treating it as a rule. Standard work is a baseline, not a regulation. The point is improvement, not compliance.
- Updating too rarely. A standard that has not changed in two years is out of sync with how the work actually happens. Update when someone finds a better way.
- Hiding it in a binder. Standard work belongs at the workstation, visible during the work. If the operator has to walk to a binder, the standard is too far away to be used.
- Confusing it with a SOP. A SOP is a formal procedure document, often for compliance. Standard work is a living, operator-built improvement baseline. The two look superficially similar and are deeply different in purpose.
Standard work and related Lean tools
Standard work and standardized work are used interchangeably by most lean writers; Toyota specialists draw a small distinction that rarely matters in small-shop practice. Standard work is the data foundation for a standard work combination table when work needs to be sequenced against takt. The discipline of leaders verifying and improving standard work is captured in leader standard work. The visual partner to standard work is the visual work instruction, posted at the station for at-a-glance reference.
Related terms
Root Cause Analysis
Find the cause underneath the cause. Stop fixing the same problem twice.
Read termProcess Mapping
Draw the steps. See the handoffs. Find the gaps.
Read termPlan-Do-Check-Act
Lean's basic improvement loop. Small, fast, and built to repeat.
Read termYamazumi Chart
Stacked bars of work, one per operator. See line imbalance fast.
Read term