Lean teams use standard work as the baseline for improvement. Without a standard, you cannot tell whether a change helped or whether a problem is new. It also makes training faster and results more consistent across shifts.
Where it comes from
Standardized work is a foundation of the Toyota Production System, built on takt time, work sequence and standard in-process stock. Its training methods also draw on Training Within Industry job instruction.
At a glance
The three elements and a combination chart
Swipe sideways to see the whole diagram.
How to apply Standard Work
- 1
Observe the current method
Watch several operators perform the task over multiple cycles. Note the steps, variation between people and any waiting or rework.
- 2
Break the task into elements
List each work element in order and time it. Identify key points that affect safety, quality or ease of work.
- 3
Agree on the current method
With the operators, choose the method that is safest and most consistent. Remove obvious waste before you write it down.
- 4
Document it visually
Create a standard work sheet or instruction with photos, sequence, timing and key points. Keep it short and post it at the point of use.
- 5
Train to the standard
Teach the method step by step and confirm each person can perform it. Track who is qualified on which tasks.
- 6
Audit and improve
Check regularly that work follows the standard. When someone finds a better way, test it and update the standard so the gain sticks.
Worked example (illustrative)
A machine shop finds that the same fixture changeover takes anywhere from 14 to 31 minutes, depending on the shift. Operators from each shift agree on one sequence and record it with photos and key points. Over the next month, changeovers fall in a range of 15 to 18 minutes, and the next kaizen starts from that shared baseline.
Common mistakes
- Having engineers write standards alone, so operators do not trust or follow them.
- Treating the standard as permanent instead of the starting point for improvement.
- Writing long text documents that nobody reads at the workstation.
When Standard Work is not the right tool
Rigid step-by-step standards fit repetitive work. Highly varied knowledge work needs lighter standards, such as checklists, definitions of done and agreed policies.
A standard written without the people who do the work rarely holds.
Standard work procedures
A standard work procedure documents the current best way to do a task: the sequence of steps, the time each takes and the amount of work in progress needed. It is written with the people who do the work, not for them.
Unlike a long SOP, standard work is short and visual. Photos, key points and the reason for each key point fit on one page posted at the workstation. When someone finds a better way, the procedure is updated, so the standard is the base for kaizen.
The three standard work forms
Manufacturing teams often use three forms. A process capacity sheet shows what each machine can produce. A combination table shows manual, machine and walking time against takt.
A standard work chart shows the layout, the operator's path and where stock is held.
Training to the standard
Training Within Industry job instruction teaches a standard in four steps: prepare the learner, present the job, try out performance and follow up.
Leaders keep their own routine too. Gemba walks are part of leader standard work.
Standard work and staffing: an example
This example is illustrative. A line with a 60 second takt has 330 seconds of manual work per unit across its steps.
330 ÷ 60 = 5.5, so the line needs 6 operators as it stands. The standard work sheets show 30 seconds of walking to a shared parts rack. Moving the parts to the point of use brings the work to 300 seconds, exactly 5 operators at takt, and the sixth person moves to the next improvement.
Work standards and standard work
Two ideas are easy to mix up. A work standard defines the result that must be met: specifications, acceptance criteria and rules. Standard work describes the method used to get there: the steps, timing and working conditions. The Lean Enterprise Institute keeps the two apart for this reason.
In an illustrative order-entry process, the work standard is an accurate, approved order with all required customer data. The standard work shows how to check the request, find missing data, get approval and release the order. Keep both visible: following the method is not enough if the result fails its acceptance check.
For work that varies or needs expert judgment, standardize the frame rather than every choice: intake rules, review points, records and escalation limits. Say when a different method needs approval.
What standard work changes
The main benefit is a process that is visible and comparable. These are typical effects, not guaranteed savings:
Consistency across people and shifts
One agreed method makes expectations and handoffs clear. "Send the job to maintenance" becomes a set handoff: name the asset, describe the issue, note the conditions and send it to the right queue.
Checks where errors start
Name the item to inspect, the pass rule and the action if it fails, at the point where a mistake can still be caught, such as confirming the right part before installing it.
Training and cross-training
The standard becomes the shared guide for demonstration, practice and assessment. Record skill against observed criteria, not attendance.
A base for productivity work
Look for searching, waiting, copying data and poor handoffs before asking anyone to work faster.
Handover when roles change
A trained coworker can find the current version and know the next step without depending on one person.
SOPs, work instructions and standard work sheets
Teams use these labels differently, so agree the split inside your organization. One workable structure:
| Document | Main purpose | Typical content |
|---|---|---|
| Standard operating procedure | Guides a repeat process | Roles, approvals, key stages, records, exceptions |
| Work instruction | Shows how to do one task | Steps, images, settings, warnings, checks |
| Standard work sheet | Shows the agreed method against takt | Sequence, timing, layout, standard in-process stock |
| Checklist | Confirms key actions | Checks before release or handoff |
| Work standard | Defines good output | Specifications and acceptance criteria |
Standard operating procedure
Guides a repeat process
Typical content: Roles, approvals, key stages, records, exceptions
Work instruction
Shows how to do one task
Typical content: Steps, images, settings, warnings, checks
Standard work sheet
Shows the agreed method against takt
Typical content: Sequence, timing, layout, standard in-process stock
Checklist
Confirms key actions
Typical content: Checks before release or handoff
Work standard
Defines good output
Typical content: Specifications and acceptance criteria
Explain the reason behind key steps as well as the action. "Record the reading" is not enough if the worker does not know which reading, where to write it or when to escalate. The work instructions software category covers tools that hold these documents.
Observing before writing
Watch real cases, not just the ideal path, and ask experienced people to explain routine versus hard jobs. A simple observation record covers five points:
- Activity: What happened, and what triggered it?
- Input: What information, material, tool or approval was needed?
- Wait: What blocked the next step?
- Decision: What choice changed the path through the process?
- Verification: How was correctness checked before handoff?
Review the notes with the team before drawing conclusions. A workaround often points to a missing resource or a rule that does not fit the job, not poor discipline. Separate must-do controls from recommended steps, and never treat a standard work exercise as permission to skip established safety controls.
Writing for the point of work
Use short action lines, plain terms and images where the order is hard to describe. Keep warnings and checks next to the step they belong to. A practical layout has five blocks:
Identity
Name, owner, version, approval and effective date.
Preparation
Required skill, inputs, equipment and controls.
Execution
Ordered steps, roles and branch points.
Verification
Acceptance rules, records and release conditions.
Exceptions
Stop points, escalation contacts and how to handle deviations.
Test the draft on a trained coworker who did not write it: can they find what they need and explain the next step? Fix unclear wording before release. Then give the standard an owner, keep only the current version in use and set review triggers, such as a new tool, a repeated defect or a changed specification.
Workstation setup in the standard
Standard work should cover the physical setup the task needs. OSHA's guidance says a work surface should fit both the worker and the task, with height chosen to reduce awkward bending and reaching, and it treats close visual work differently from heavier manual work.
So there is no single correct bench height to copy into every standard. Document instead:
- Adjustable parts: Which surfaces, fixtures or supports can move, and how.
- Tool and material places: Where common tools and parts belong.
- Workpiece handling: How the piece is supported and turned.
- Review triggers: Which cases need an ergonomic review rather than a quick workaround.
- Reporting: Who hears about discomfort, long reaches or a poor working height.
Treat layout photos as aids, not proof the setup suits everyone, and check it again when the product, equipment or staffing changes.
Measuring whether standard work helps
Measure results, not whether documents exist. Set a baseline, compare similar work under similar conditions and use a mix of measures so faster work does not hide worse outcomes:
| Measure | Definition | Check |
|---|---|---|
| First-pass acceptance | Outputs accepted without correction ÷ outputs checked | Keep the acceptance rules the same |
| Lead time | Time from the start event to the finish event | Count waiting the same way each time |
| Rework | Time or cases needing correction | Record causes as well as totals |
| Training readiness | Observed skill against task criteria | Do not substitute attendance for skill |
| Output per labor hour | Accepted output ÷ defined labor hours | Compare similar work and difficulty |
| Exception frequency | Cases needing a path outside the normal flow | Ask whether exceptions show a weak standard |
First-pass acceptance
Outputs accepted without correction ÷ outputs checked
Check: Keep the acceptance rules the same
Lead time
Time from the start event to the finish event
Check: Count waiting the same way each time
Rework
Time or cases needing correction
Check: Record causes as well as totals
Training readiness
Observed skill against task criteria
Check: Do not substitute attendance for skill
Output per labor hour
Accepted output ÷ defined labor hours
Check: Compare similar work and difficulty
Exception frequency
Cases needing a path outside the normal flow
Check: Ask whether exceptions show a weak standard
Decide in advance what would justify adopting, revising or stopping a pilot. If the method made work faster but added errors, revise it rather than calling it a win.
Mistakes that turn standards into paperwork
- 1
Documenting an untested method. Observe and trial the sequence before calling it standard.
- 2
Writing without the people who do the work. Ask them to challenge missing inputs, odd sequences and unclear words before release.
- 3
Forcing every case into one path. Define valid variants and when each applies.
- 4
Too much detail at the workstation. Keep point-of-work steps short and link to background.
- 5
Checking compliance without checking conditions. Look at equipment, materials, training and time first.
- 6
Leaving repeat deviations open. Give them an owner and decide whether the process or the standard should change.
- 7
Publishing without maintenance. Give revisions an owner, remove old copies and brief people on changes.
Guides on this topic
- One-piece flow: how single-unit flow cuts waiting and WIPOne-piece flow explained: a worked comparison with batches, takt and cycle time, the benefits to check, production and transfer batches, flow and pull, where it fits, the conditions it needs, a pilot plan and how to measure it.Read the guide
- Line balancing: how to split work so a line meets taktLine balancing explained: takt and cycle time, balance efficiency, the data to collect, yamazumi charts and assignment rules, a worked four-station example, workstation checks, software questions and a pilot plan.Read the guide
- Kaikaku: when a process needs redesign, not another small fixKaikaku explained: what radical change means in lean, how it differs from kaizen, when it fits and when to pause, a six-step way to run it, examples from factories to purchasing, measures and how to protect the change.Read the guide
- Kamishibai board: how card-based audits keep standards visibleThe lean kamishibai board explained: how red and green audit cards work, how to build the board, writing a good card, running and rotating checks, follow-up, 5S and LPA uses, digital boards and common mistakes.Read the guide
Sources
Books and papers show their publication year. Web pages show the month we last checked them.
- 1.Jeffrey K. Liker, The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer (McGraw-Hill, 2004)
- 2.Donald A. Dinero, Training Within Industry: The Foundation of Lean (Productivity Press, 2005)
- 3.David Mann, Creating a Lean Culture: Tools to Sustain Lean Conversions (Productivity Press, 2005)
- 4.Chet Marchwinski (editor), Lean Lexicon: A Graphical Glossary for Lean Thinkers, 5th edition (Lean Enterprise Institute, 2014)