Engineering · Manufacturing · Manufacturing Cost and Productivity

The Five-Step Shop-Floor Improvement Method

A practical improvement workflow combining time study, jig design, standard work, ERP/routing updates and re-measurement.

Handbook edition · ~7 min read

This expanded edition combines the original source-derived article with practical implementation guidance, evidence expectations, common failure modes and a close-out checklist.

shopfloor improvement
time study
jig design
standard work
ERP
benefit verification

Executive summary

The uploaded process flow condenses a practical manufacturing change into five connected steps. It is deliberately implementation-oriented: measure first, engineer the change, standardise it, embed it in the operating system and then prove the result.

01The five steps

Time study — measure baselineRecord current cycle time, labour exposure, rework and the work sequence.
Jig design — SolidWorks + prototypeConvert the observed constraint into a physical aid or fixture and test it before full release.
Standard work — pictorial instructionsDefine the new method clearly enough that another trained operator can reproduce it.
ERP update — lock into systemUpdate routing, BOM/operation notes, resource or other controlled master data where the change affects planning or execution.
Re-measure and track — verify savingsCompare with the frozen baseline and continue tracking long enough to confirm the change is sustained.

02Why the sequence matters

Skipping the baseline makes savings unverifiable. Skipping standard work makes performance person-dependent. Skipping the system update allows planning data to drift from reality. Skipping re-measurement leaves only an estimate.

H1Handbook application

The Five-Step Shop-Floor Improvement Method should be used as a working manufacturing reference rather than as a definition-only article. The practical question is not simply whether a team understands the terminology; it is whether the method can be connected to a real product, process, decision and controlled result. For this chapter, the operating focus is shopfloor improvement, time study, jig design, standard work, ERP, benefit verification. The original article develops the subject through 01 The five steps, 02 Why the sequence matters. The handbook layer below turns those concepts into an implementation routine that can be used during process review, improvement planning, design review or production problem-solving.

The most reliable way to use the chapter is to begin with a real current-state problem and to state the boundary clearly. Record what product or process is being considered, which requirement or business outcome matters, what evidence is available and who owns the decision. Avoid selecting a tool first and then searching for somewhere to apply it. Instead, use the method only where it helps explain, prevent, measure or improve the actual condition described in the article.

Practical guidance versus source content

The technical concepts and any numerical source examples remain in the original sections above. The handbook sections below add KEVOS implementation guidance so the page can be used on the shop floor or in an engineering review. These additions do not convert illustrative values into mandatory standards.

H2Working method

Define the decision.State what must improve or be decided and why the five-step shop-floor improvement method is relevant. Connect the question to a product requirement, process loss, risk, cost, quality or delivery outcome.
Establish the baseline.Collect representative evidence before changing the process. Use the same measurement definition before and after so improvement is not created by changing the denominator, scope or time period.
Map the mechanism.Use the chapter's concepts to explain how the current condition produces the observed result. Separate a visible symptom from the underlying design, process, measurement or management mechanism.
Select the smallest defensible intervention.Prefer a controlled trial that directly addresses the mechanism. Define success, safety/quality boundaries and what would cause the trial to stop.
Verify the result.Measure the after-state with the same method used for the baseline and check for unintended effects on quality, ergonomics, throughput, maintenance or downstream operations.
Standardise and hand over.If the result is acceptable, update controlled drawings, instructions, routing, control plans, maintenance or training records as applicable. Assign an operating owner and a follow-up check.

H3Evidence and records

A handbook method becomes repeatable when the evidence can be reviewed by someone who was not present during the improvement. For this topic, retain enough information to show the original condition, the reasoning used, the trial or analysis performed and the final controlled state.

Baseline work content and cost assumptions
Observed cycle time, labour or rework data
Transparent annualisation assumptions
Countermeasure investment and implementation cost
Before/after performance using the same scope
Benefit classification: capacity, cost avoidance or cash saving
Finance/process-owner sign-off for realised benefit where required

Evidence does not need to become unnecessary bureaucracy. A short time-study sheet, controlled drawing revision, annotated process map, trial log and before/after chart can be stronger than a long report if they capture the correct facts and are traceable to the actual product and process.

H4Cross-functional review

The subject should be reviewed with the people who understand both the technical intent and day-to-day work. A practical core team can include the manufacturing/operations engineer, process owner, operator/team leader, finance or cost owner, tooling/maintenance support. The exact team depends on the topic, but the review should cover four questions: does the proposed method preserve product/customer requirements; does it work under normal production conditions; can operators and support functions sustain it; and does the evidence justify the claimed benefit or conclusion?

Where the method changes product geometry, a drawing requirement, validated process parameter, tooling, gaging, inspection, work instruction or controlled master data, use the organisation's formal change process. A successful trial is evidence for change; it is not by itself authority to bypass engineering, safety, quality or customer controls.

H5Common implementation failures

Annualising a one-off observation
Counting released capacity as cash saving without a defined use
Ignoring quality or safety side effects
Excluding implementation/maintenance cost from the business case
Claiming benefit before the new method is stable and adopted

A useful review technique is to ask what evidence would prove the opposite conclusion. For example, if the team believes a countermeasure reduces variation, look for data showing the process behaviour over time rather than accepting a small set of favourable parts. If the team believes a design is easier to assemble, observe real operators and actual assembly conditions rather than relying only on CAD or bench evaluation.

H6Close-out checklist

The business or engineering question is explicitly stated.
The current-state baseline uses a defined and reproducible measurement method.
The mechanism connecting the proposed change to the expected result is understood.
Any numerical source example has been replaced with actual local data before a production decision is made.
The trial or analysis covers realistic production conditions and relevant variation.
Quality, safety, delivery, maintenance and downstream effects have been checked.
The after-state is measured using the same scope and definition as the baseline.
Controlled documents and system data are updated where the change affects them.
An operating owner and follow-up review are assigned.

H7Handbook questions

Scope

When should this method be used?

Use it when the issue described by The Five-Step Shop-Floor Improvement Method is materially connected to the observed product, process, quality or cost problem. Do not deploy it merely because the tool is available.

Evidence

How much data is enough?

Enough to represent normal process conditions and support the decision being made. The required depth depends on risk, variation, frequency and the consequence of being wrong; one convenient observation is rarely a robust baseline.

Change

When does a trial become the new standard?

Only after the result has been verified and the affected controlled documents, training, process settings and ownership have been updated through the required change process.

Sustain

How is the gain protected?

Define the normal condition, the monitoring or audit method and the reaction to drift. A change that depends on one person's memory is not yet a stable manufacturing system.

SSource basis and use

This article was developed from the uploaded KEVOS manufacturing reference set. Source items used for this page: files/chart-improvement-process-flow.png; files/chart-before-after-comparison.png.

Illustrative values from source graphics are identified as examples rather than universal benchmarks. Apply current drawings, customer-specific requirements, approved procedures, standards and validated process data before using numerical examples for production decisions.