In my experience, many plants know how to write standard work. Far fewer know how to update standard work once their best operator finds a better way, and that is where variation quietly comes back.

Wen Cut 2 Minutes 40 Seconds on a Tuesday

Wen ran the housing job on first shift. On a Tuesday she found that seating the housing against the rear stop before closing the clamp took out a re-seat. Her cycle dropped from 14 minutes 20 seconds to 11 minutes 40 seconds.

Her supervisor saw it and was pleased. Nobody changed the document, because the plant had no habit of how to update standard work between reviews.

By Friday, second shift was still running the written method at 14 minutes 20 seconds, and first shift was running Wen’s. Same part number. Two methods. Neither shift did anything wrong.

Why Does Standard Work Go Stale After an Improvement?

Standard work goes stale when the improvement travels by word of mouth and the document waits for a review.

There are two reasons. First, reviews run on a calendar, while improvements arrive on a Tuesday. We covered the calendar side in how often manufacturing SOPs should be reviewed. Second, nobody owns the change. The operator assumes the supervisor will handle it. The supervisor assumes engineering will. Engineering never heard about it.

So the cost is not zero. Take an illustration: at 30 cycles a shift, 2 minutes 40 seconds is 80 minutes of capacity that second shift keeps spending. And the written standard now describes a method that the best person on the floor has already abandoned.

Do Better Management Practices Actually Pay Off?

The best evidence I know of comes with a caveat about what it measured.

Nicholas Bloom and four co-authors ran a randomized field experiment at textile plants in Maharashtra, India, published in The Quarterly Journal of Economics (figures here are from the NBER working paper version). Treatment plants received free consulting on modern management practices, including standard operating procedures and recorded quality defects. The bundle, not SOPs alone, raised productivity 11%, and the authors report that quality defects fell by about a third. The study also found that many firms simply weren’t aware that practices like standard operating procedures existed.

That is one industry in one country, so treat it as a signal, not a promise for your plant. The authors also note that their estimates would run high if firms slide back once the consultants leave. In my view, that is the risk to watch. A standard that cannot absorb an improvement is one that people stop treating as the standard.

How to Update Standard Work in Five Moves

Here is the sequence, in five moves. It sits inside your change control, not around it.

1. Catch it the day it happens. Make it safe to say “I changed a step.” If the first reaction is a reprimand, you will hear about the next change from the audit.
2. Time both methods on the same job. Run at least three cycles of each, on the same shift, with the same material. A single good cycle proves nothing.
3. Check quality, safety and spec. A faster method that drops a check isn’t an improvement. If the step is safety-critical or regulated, your formal change control decides, and the moves below follow it.
4. Name one owner and a deadline. One person decides within two working days. “We’ll look at it at the next review” is how Wen’s method stayed on one shift.
5. Change the document and pull the old copy the same day. Tell every shift at the next huddle, then walk to the station and confirm the old sheet is gone.

This is the same discipline behind how to standardize work across shifts. Standardizing once isn’t enough, because the standard has to keep moving to stay the standard.

Why Is the Better Method Often Missing From the Standard?

In my experience, the person who finds it is rarely the person who edits the document. Operators discover improvements with their hands. Documents are edited by someone at a desk, days later, from a summary.

We saw the same pattern when operator-to-operator variation showed up on one job: the best method lived in one person, and everyone else ran what was written. The fix isn’t telling operators to be more careful. It is shortening the distance between the hands that find the improvement and the page that records it.

It also connects to defects caused by inconsistent processes. Two methods for one part is an inconsistency you created yourself.

What the Market Sells Instead

Mostly approval routing. Document-control software that moves a revision through signatures once somebody has already written it. An annual review calendar. An AI assistant that summarizes the binder as it stands.

Each of these handles the paper after the change exists. Most of them start after the change exists and don’t notice it happened on the floor. That is the gap, and a routing workflow won’t update standard work for you, because the first step is missing.

How Smart Living SOPs Update Standard Work

At SenseiLab, we built Smart Living SOPs around that first step. When an operator finds a better method, they describe it to our AI agent in their own words. The supervisor reviews it, and the SOP updates at the station where the work happens. The old revision leaves the station at the same time, so the two shifts are less likely to drift apart.

You can start the manual version this week, without us.

Run the Two-Shift Comparison to Update Standard Work This Week

It takes about half a shift and one job.

1. Pick one job that runs on more than one shift.
2. Ask each shift: “Which step do you do differently from the written method?”
3. Watch both versions and time three cycles of each.
4. Check the faster one against quality, safety and spec.
5. Decide who owns the change, and update the document the same day.

If both shifts say “no differences,” ask again with the supervisor out of the room. You will probably find at least one. Each difference is usually either an improvement waiting for a document or a risk waiting for an audit.

Frequently Asked Questions About Standard Work

How do you update standard work in manufacturing?

Catch the improvement on the day it happens, time both methods on the same job, check quality, safety and spec, and name one owner to approve the change. Then change the document and pull the old copy the same day.

How often should standard work be updated?

When a better method is proven, not when the calendar says so. A scheduled review is still useful as a backstop. Our piece on how often manufacturing SOPs should be reviewed covers that.

Who should approve a change to standard work?

One named person, usually the supervisor or process owner, within a short fixed window such as two working days. Safety-critical and regulated steps also go through your formal change control.

How can we standardize work across shifts?

Start by finding where shifts already differ, then choose one method and write it down. Our guide to how to standardize work across shifts walks through it.

Forward this to one supervisor whose shifts run the same job two different ways.

— Diego Echenique, SenseiLab.

About the author: Diego Echenique, MBA, is CEO & co-founder of SenseiLab, with 20+ years in manufacturing operations.