Standard Work

A packing team has three different methods for the same order type, and some steps are skipped under pressure, causing rework. Standard work can define the current effective sequence and make problems visible.

The Lean Enterprise Institute describes standardised work through takt time, work sequence and standard in-process inventory in production contexts, and other tasks may use different details but share the idea of an agreed baseline. Lean guidance also frames standards as a starting point for improvement, not the final perfect method, so when conditions change the method should be reviewed with people doing the work.

Choose repeatable work, since a routine assembly step may benefit from exact sequence while a one-off strategic decision may need principles rather than a rigid script. Observe the real task, because a procedure written without watching workers can be impossible to follow, and ask why workarounds exist before declaring them failures.

Document critical steps by showing what to do, in what order, with which tools and quality checks, and avoid a long manual that hides the few points that matter. An illustrative cycle-time range is slowest observed task time minus fastest observed time in a sample, so if times run from four to seven minutes the range is three, and variation needs investigation, not automatic blame.

Link safety, because a faster method is not better if it bypasses guards or strains workers, and include safety requirements in the standard. Clarify timing: takt time reflects customer demand pace while actual cycle time is the time to perform work, and they should not be treated as the same number.

Set inventory or handoff limits where relevant, since too many items in progress can hide bottlenecks while too few can stop a line, and the correct level depends on the process. Make visual instructions where useful, as photos or diagrams can show orientation and sequence, but keep them current and accessible.

Train by practice, since reading a document does not prove someone can perform the task, so demonstrate, observe and give feedback. Give workers a way to suggest changes, because a standard should make deviations visible and testable, not silence improvement ideas, and control versions so that if two sites use conflicting instructions the current approved method is marked and differences are explained where justified.

Handle exceptions with an escalation path for unusual customer needs or equipment failures, because a standard that pretends exceptions never happen invites hidden workarounds, and check supplies, since workers cannot follow a method if the tool or component is missing. Measure quality and burden, because a new sequence may reduce defects but add excessive strain or waiting, avoid copying another site unchanged, since layout, equipment and demand can differ, and assign ownership so a process owner can approve changes, keep training aligned and be the contact when workers find a mismatch.

Review after changes, as new equipment, software or regulations can make a formerly good method wrong, and use audits carefully, because a check can show where the process differs from the standard and then ask whether the standard or practice needs to change, not just produce a compliance score. An SOP may describe a whole process or policy while standard work often focuses on detailed repeatable actions, although organisations use terms differently; for owners, standard work kept close to the workstation, with improvements recorded and everyone affected trained, makes reliable practice visible and helps people do good work consistently while learning from real conditions.