Standard Work
A documented set of procedures that establishes the current best method for performing a task, serving as the baseline for continuous improvement in lean manufacturing and operations.
Read summarized version with
What is Standard Work?
Standard work is a documented set of procedures capturing the best known way to perform a specific task or process right now. In lean manufacturing and operations management, it represents how work should be done based on what we currently know. What makes standard work different from other documentation? It's meant to change. Teams use it as a living baseline, constantly questioning and improving it through kaizen activities.
Unlike static procedures that gather dust, standard work gets revised regularly. When someone on the floor finds a better approach, the documented standard gives everyone a reference point for testing whether the new method actually works better. A standard operating procedure might be more stable, while standard work embraces frequent updates. Without that baseline, how would you even know if a change is an improvement? You can't measure progress against nothing.
The concept started in lean manufacturing but has spread to healthcare, software development, customer service, and just about anywhere work happens repeatedly. There's something almost paradoxical about it: standard work creates consistency while also enabling change. By defining what "normal" looks like, you make it possible to spot when something's different, and potentially better.
Key Characteristics of Standard Work
- Three Core Elements: Standard work ties together takt time (how fast customers need things), work sequence (the exact order of steps), and standard inventory (the minimum materials you need on hand). All three matter for repeatable results.
- Living Document: This isn't a document you write once and forget. Standard work changes as people discover better methods. It represents what works best today, not some permanent answer.
- Baseline for Improvement: Kaizen needs a starting point. Standard work gives you that stable foundation so you can actually measure whether a proposed change makes things better or just feels different.
- Visual and Accessible: You'll typically see standard work posted right where the job happens, often with diagrams or photos. Many teams create work instructions for the more detailed steps. If people can't easily reference it while working, it's not doing its job.
- Operator-Informed: The people doing the work should help create the documentation. They know the shortcuts, the tricky parts, and the practical realities that managers might miss.
Standard Work Examples
Example 1: Manufacturing Assembly
Picture an automotive parts manufacturer with a circuit board assembly station. Their standard work sheet spells out a 47-second cycle time to keep up with demand, walks through all 12 steps in order, and notes that 3 boards should always be in process at the station. One day, an operator realizes that moving a tool closer cuts the cycle down to 44 seconds. The team tests it, confirms it works, and updates the standard work. Now everyone benefits from that three-second gain.
Example 2: Hospital Patient Admission
An emergency department puts together standard work for patient admissions. The documentation maps out everything from arrival to room assignment, sets time targets for each phase, and lists what supplies need to be stocked at intake. Staff notice that checking insurance eligibility earlier in the flow cuts down on delays later. They run a test, see the improvement hold up, and revise the standard work so the new sequence becomes the default.
Standard Work vs Standard Operating Procedure
People often mix these up, but standard work and SOPs serve different purposes.
| Aspect | Standard Work | Standard Operating Procedure |
|---|---|---|
| Purpose | Creates a baseline you can improve against | Keeps things consistent and compliant |
| Focus | Today's best method, expected to evolve | Stable process with formal change control |
| Detail Level | Very specific, down to exact timing and sequence | Often broader, covering the overall process |
| When to use | When you're optimizing repetitive tasks and driving kaizen | When regulatory compliance and consistency matter most |
How Glitter AI Helps with Standard Work
Creating and maintaining standard work can be tedious. Glitter AI makes it easier by letting experts and frontline workers capture current best practices through screen and process recording. No more writing everything from scratch or struggling to explain visual processes with text alone.
When teams find improvements through kaizen, Glitter makes updating the documentation quick. Record the new method, and everyone can see exactly how it's done. This approach to process documentation keeps the continuous improvement cycle moving. Your standard work stays stable enough to be useful but flexible enough to evolve as people find better ways to work.
Frequently Asked Questions
What does standard work mean?
Standard work is a documented set of procedures showing the current best way to perform a task. It acts as a baseline for continuous improvement, giving teams something concrete to measure potential changes against.
What is an example of standard work?
In manufacturing, standard work might document a 47-second sequence for assembling a product, covering the order of steps, timing, and materials needed. When someone finds a faster method, the team tests it against this standard and updates the documentation if it checks out.
Why is standard work important?
Standard work matters because it creates consistency while still allowing for improvement. Without a documented baseline, you can't really tell if changes are actually making things better, and good ideas tend to get lost instead of spreading.
How do you create standard work?
Start by watching how the work gets done now. Document the most efficient sequence of steps, and make sure you're getting input from the people actually doing the work. Identify takt time and standard inventory needs, then post the documentation where people can easily reference and update it.
What is the difference between standard work and SOP?
Standard work is designed as a living baseline with detailed timing and sequence, expecting regular updates as people find better methods. SOPs are broader procedure documentation focused on consistency and compliance, with more formal change control processes.
Turn any process into a step-by-step guide