Key takeaways
Short answer: An SOP defines how to perform a task correctly, safely, and compliantly — it is a stable reference. Standard work captures the current best way to run a repeating cycle: the sequence, the takt time, and the standard WIP. SOPs are for compliance and change rarely; standard work is the baseline for improvement and is expected to change. See also oee for manufacturing.
If you treat standard work like an SOP — heavyweight, change-controlled, rarely touched — you freeze it, and continuous improvement stops. Standard work is meant to be re-set every time the team finds a better way.
The SOP guarantees the task is done correctly; standard work optimises how the cycle flows. Both reference each other but serve different masters: compliance vs improvement.
Standard work stabilises cycle time, which directly supports the Performance term of OEE. Unstable, undocumented cycles show up as speed loss and micro-stops.
See how Fabrico captures this automatically on your lines — explore OEE for manufacturing or book a demo.
No — it captures timing and WIP and is meant to change often.
The team doing the work, with team-leader support.
Every time a better method is proven.
No — they serve compliance and improvement respectively.
Login
Blog
