Standard Work vs SOPs: what's actually different
A practitioner once said: 'An SOP tells you to check the torque. Standard Work tells you to check it at 10.5 ± 0.3 Nm with a calibrated driver, why it matters, and what to do if it's out of spec.' That's the distinction.
SOPs describe the job
Standard Operating Procedures document the task. They're usually written in paragraphs, organized by policy, and designed to pass a regulatory audit. They're necessary. They're also almost never used by the operator doing the task in real time.
Standard Work designs the job
Standard Work comes from Toyota's Job Instruction (TWI JI). Each step has four elements: (1) what to do, (2) the key point (what could go wrong), (3) the reason the key point matters, (4) a time or quality target.
- Step: 'Position vial under capper.'
- Key point: 'Align seal-pressure indicator to green zone.'
- Reason: 'Off-center pressure cracks the seal at crimp.'
- Time: 4 seconds. Quality check: green indicator confirmed.
Why the distinction matters
When takt, cycle time, and quality are linked in the document, the operator can see deviation in real time. When an SOP is a five-page narrative, the operator reads it once in training and never again. Standard Work is what actually shapes day-to-day behavior on the line.
Governance — the other half
Standard Work needs the same governance as an SOP: approver, effective date, revision history, training matrix, Layered Process Audits (LPAs). Missing any of those and you have a good training tool but not an audit-ready document. Taktly treats both halves as first-class.