Continuous Improvement: Making Changes Stick Where Work Happens
The change you approved on Tuesday is running on Tuesday
Right now there is a gap between the moment an improvement is approved and the moment the person doing the job is actually doing it the new way. That gap is filled by printing, walking, swapping, and hoping the old copy in somebody's toolbox went in the trash.
Close that gap and continuous improvement stops being a program you run and starts being something that just happens. The team suggests a change, you approve it, the revision goes live, and the next person to start that job sees the new way. No walk. No stack of paper. No superseded copy sitting in a drawer waiting to cause a nonconformance.
That is the whole argument of this page. The rest explains why.
What continuous improvement actually means
Continuous improvement is the practice of making small, repeated changes to how work is done, rather than waiting for a big project to fix everything at once. The idea shows up under several names, and they overlap more than the training courses admit.
PDCA (Plan, Do, Check, Act). Plan a change, run it, measure what happened, then either adopt it or try something else. The cycle repeats forever, which is the point.
Kaizen. Small improvements suggested by the people doing the work, usually many of them, usually cheap. The strength of kaizen is volume. It falls apart when suggestions take three weeks to reach the floor.
Lean. Remove the steps that do not add value for the customer. Waiting, rework, over-processing, unnecessary movement.
Six Sigma and DMAIC. Reduce variation using data. Define, Measure, Analyze, Improve, Control. The Control step is the one people skip, and it is the one this page is about.
ISO 9001 clause 10.3 and AS9100. Both require you to continually improve the suitability and effectiveness of your quality system. An auditor will ask what you changed and how you know it took hold.
Every one of these ends in the same place: somebody has to work differently tomorrow than they worked yesterday. And the only durable record of how work should be done is the work instruction.
Standard work is the thing you improve
You cannot improve a process that is done three different ways on three different shifts. There is nothing to compare against and no way to tell whether your change helped or whether you just got a better operator that week.
So the first move in any continuous improvement effort is to write down the current best-known way to do the job. Not the ideal way. The way it is actually done by the person who does it well. That document is your baseline. Every improvement is a change to it.
This is why documentation and CI are the same problem. If your work instructions are stale, the baseline is fiction, and every measurement you take after a change is measuring against fiction.
If you are not sure what belongs in a work instruction versus a higher-level procedure, work instructions vs SOPs covers the split. If you are writing the instruction itself, how to write training documentation operators actually use is the practical version.
Building CI into your document process
1. Make the current revision the only one anybody can reach
If an old copy still exists somewhere reachable, some percentage of your work is being done to the old copy. That is not a discipline problem, it is a system problem. Anything you can pick up, you will pick up.
The fix is to have exactly one place to get the instruction, and to have that place always serve the current revision. What "available at the point of use" actually requires goes into what ISO 9001 clause 7.5.3 expects here.
2. Give people a way to suggest a change from where they stand
Most improvement ideas occur to somebody mid-job, with dirty hands, twenty feet from where the problem is. If capturing that idea requires walking to an office and filling out a form, you will capture maybe one in ten.
A simple revision request that can be raised at the machine, the bench, or the vehicle collects far more. A one-page revision request form would help most shops here. We do not have one to hand you yet, so build your own and keep it to five fields or fewer.
3. Time the loop, not just the outcome
Track how long it takes from a suggestion being raised to the new revision being live at the point of work. That number is the speed limit on your entire improvement program. Shortening it improves everything downstream, and it is one of the few CI metrics that is easy to measure honestly.
4. Close the loop with training records
A change nobody was told about is a change that did not happen. Every revision that affects how the job is done needs the people doing that job to acknowledge it. Keep the record. Your auditor will ask, and more importantly you will want to know who is running the old method.
5. Sort the pile before you automate it
If you have 200 documents and nobody knows which 60 are live, faster delivery just delivers the mess faster. Applying 5S to work instructions and training records walks through cleaning that up first.
This is not just a manufacturing problem
The same loop breaks in the same place in almost every industry.
A restaurant group changes an allergen procedure and it reaches the binder in the back office of eleven locations at eleven different times. A facilities team improves a lockout sequence and the laminated card at the panel still shows the old one. A fleet maintenance shop updates a pre-trip check and the drivers keep working from the version they memorized two years ago. A clinic revises a specimen handling step and the poster in the draw room stays up for months.
Different work, identical failure: the improvement lives in a document management system, and the work happens somewhere the document management system is not.
Where ScanToRun fits
A tag goes on the machine, the door, the bench, the vehicle, the shelf, the panel. Somebody scans it with the phone already in their pocket and the current revision opens, formatted to read on a phone. No app, no login.
For continuous improvement, that means the last step of every improvement cycle is one you do at a desk: publish the revision. Publishing is delivery. There is no walk between the two, and no window where half the floor is on the old method.
The training register handles the other half. When a revision goes out, you can see who has acknowledged it and who has not, which is the evidence an AS9100 or ISO 9001 auditor asks for when you claim an improvement was implemented.
If you run a machine shop, ScanToRun for machine shops is the version written for your floor. If phones are restricted where you work, read digital work instructions on a floor that doesn't allow phones first, because there are cases where this is the wrong tool and we say so.
See a sample instruction as it opens on a phone, or book a demo and bring one of your own documents. Pricing is in the section on the home page.