Standard Work in Lean: How to Create and Maintain It

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

Standard work sets the current best method, sequence and timing for each task. Learn how to create standard work with operators, keep it alive and improve it.

Standard work is the current best method for a task, written down with its sequence and timing, so that every operator on every shift does the job the same way. This article is for lean managers who want to create standard work that people actually use and keep it alive afterwards. It explains the three elements, a step-by-step method, the documents that support it, a worked example with numbers and the mistakes that turn standards into shelf paper.

Key points

• Standardized work rests on three elements: takt time, work sequence and standard inventory. Together they define how one operator does the job.
• Standard work is the baseline for kaizen. Without a standard, there is nothing to improve from and no way to see that a change worked.
• Write it with the operators who do the job. Observe the real work, time it and agree on the current best method.
• Do not confuse standardized work with work standards, or standardization with commonization.
• Maintain it by asking why the standard is not followed, not by chasing compliance. Update it after every proven improvement.

What is standard work in lean?

The Lean Enterprise Institute defines standardized work as establishing precise procedures for each operator's work in a production process. The terms "standard work" and "standardized work" are used for the same idea.

Many plants already have standard operating procedures (SOPs). Standard work differs because it adds timing against takt time and is meant to be improved, not just followed. It lives on the shop floor, next to the work. A value stream map shows which processes need a standard first.

Two points deserve emphasis. First, it describes the current best method, not a fixed law. Once it is established and posted at workstations, the institute says, standardized work becomes the baseline for continuous improvement and is the object of continuous improvement through kaizen. Kaizen is the Japanese word for improvement through small, repeated steps by the people who do the work.

Second, it is for the people who do the job. Engineers and front-line supervisors use the forms to design the process, and operators use them to improve their own jobs.

The benefits listed by the institute are practical: it documents the current process for all shifts, reduces variability, eases training of new operators, lowers injury and strain, and provides a baseline for improvement.

What are the three elements of standardized work?

The institute names three elements.

1. Takt time. The rate at which products must be made in a process to meet customer demand. It sets the time frame for the job.
2. Work sequence. The exact order in which an operator performs the tasks within takt time.
3. Standard inventory. The in-process stock, including units in machines, that is needed to keep the process running smoothly.

An article from the Lean Enterprise Institute describes the same content as timing, sequence and the standard amount of material required, "no more, no less". If one of the three is missing, the standard is incomplete. A sequence without a takt does not say whether the operator is fast enough. A takt without a sequence does not say how to reach it.

How do you create standard work step by step?

Create it with the operators, on the real job, one task at a time.

1. Choose a task. Pick a repeatable job with a clear pain, such as high variation between shifts, long training time or quality problems.
2. Clarify the work standards first. The Lean Enterprise Institute says: before you can begin with standardized work, you must clarify your work standards. Know the product specification and quality requirements.
3. Calculate takt. Divide the available production time by customer demand.
4. Observe the work. Watch several operators do the job on several occasions. Do not time one good cycle. Note each step, the walking, and the waiting.
5. Break the job into elements. Write down each step with its time: manual work, walking and machine time.
6. Agree on the current best method. Together with the operators, choose the best way to do each element. Take the safest and most reliable method, not just the fastest.
7. Check against takt. Add up the elements. The total cycle should be at or just under takt. If not, look for waste before you ask people to work faster.
8. Write it on one page. Use photos and numbers, not paragraphs. Show the sequence, the times, key points for quality and safety that prevent a defect, and the standard inventory.
9. Train and test. Have the operators run the new method for a few days. Collect their remarks and adjust.
10. Post it at the workstation. Put it where the work is done, and name the owner.

Which documents support standard work?

The institute describes several forms. You do not need all of them. Use what the task requires.

• Standardized work combination table. It maps manual work time, walk time and machine processing time for each operator in a sequence. It lets you recalculate operator work content when takt expands or contracts.
• Process capacity sheet. It calculates the capacity of each machine in a linked set of processes, often a cell, so that you find and remove bottlenecks.
• Standardized work chart. It shows operator movement and material location against the layout. It is often posted at workstations and updated as conditions change.
• Work standards sheet. It summarizes the documents that define how to build the product to engineering specifications, including quality requirements.
• Job instruction sheet. Also called a job breakdown sheet, it lists job steps and key points for training new operators.

Leader standard work uses the same logic for leaders. It is a short routine that says what a leader checks, where and when: the board, the line, the open actions. It is not a Lean Enterprise Institute term in the sources above, so treat it as a common practice that you adapt. It matters because the standard needs a leader who looks at it every day.

How do you maintain standard work?

Most standards fail after the launch, not during it. The Lean Enterprise Institute's article on missing pieces of standardized work offers three warnings that help.

• Do not confuse standardized work with work standards. The first describes how the operator does the job. The second defines how the product is built to specification.
• Do not confuse standardization with commonization. Standardization sets a baseline for improvement. Commonization means doing a job the same way everywhere, which is a different aim.
• Do not impose standardized work without a structured improvement process. The article says standardized work and kaizen depend on each other, and that standardized work without kaizen kills motivation and lets problems repeat.

Leaders have a particular role. The article says leaders cannot simply dictate standards from on high, and that chasing compliance is a trap. Instead, leaders should ask, in a spirit of pure inquiry, why the operator cannot follow the standard. The answer often exposes a missing tool, an unclear step or a real problem in the process.

A practical rhythm for continuous improvement:

1. Leaders check the standard at the gemba, the real place of work, and ask questions.
2. Operators propose a change. The team tests it on one shift.
3. If it works, the standard is updated, signed and posted. The old version is removed.
4. All shifts are trained on the new version.

Example: three ways to do one job

This is an illustration with made-up numbers.

A cell has a takt of 3.0 minutes per unit, from 420 minutes of available time and a demand of 140 units. Three operators on three shifts do the same job in different ways. Their measured average cycle times are 2.6, 3.4 and 3.9 minutes.

• Average: (2.6 + 3.4 + 3.9) ÷ 3 = 3.3 minutes.
• Range: 3.9 − 2.6 = 1.3 minutes.
• Output per operator per shift: 420 ÷ 3.3 = about 127 units, below the demand of 140.

The team watches all three and agrees on one method. The standard has these elements, in minutes: load part 0.4, start the cycle 0.1, walk 0.2, deburr 1.1, inspect 0.5, unload 0.3 and walk back 0.2. The total is 2.8 minutes, under takt.

After training, the three operators measure 2.8, 2.9 and 2.9 minutes.

• Average: (2.8 + 2.9 + 2.9) ÷ 3 = 2.87 minutes. The range is now 0.1.
• Output per operator per shift: 420 ÷ 2.87 = about 146 units, above the demand of 140.

Then an operator suggests moving a gauge closer, which saves 0.2 minutes of walking. The team tests it, and the new standard is 2.7 minutes. This is how a standard becomes the baseline for kaizen. The numbers are assumptions. Measure your own job.

Common mistakes

• Writing it in the office. A standard written without the operators does not match the real work and will be ignored.
• Documenting one person's habits. Observe several operators and choose the best method together.
• Too much detail. A thick manual is not read. One page with photos and key points works better.
• Treating it as fixed. If it never changes, kaizen has stopped. Update it after every proven improvement.
• Chasing compliance. Asking why people cannot follow the standard finds problems. Policing them hides problems.
• Skipping the leader's role. Without a leader who looks at the standard daily, it drifts.

How software can help

Standards for process steps and responsibilities often sit in documents that nobody can find. Software can keep one current version and show who is responsible for each step. iFAKT's Polaris BSM provides business swimlane modelling that documents business processes together with the responsibilities of the roles involved. Whatever you use, the test stays the same: the operator at the workstation must see the current version, and know who can change it.

Next step

Pick one repeatable task, observe three operators and write the current best method on one page together with them. Then post it at the workstation and set the date to review the standard work with the team.