Many production teams jump from problem to solution too quickly. Output is short, so overtime is added. Defects appear, so operators are reminded to be careful. 5S drops, so the area is cleaned again. These actions may feel fast, but they often do not teach the team why the problem keeps returning.
Small experiments give supervisors a better daily Kaizen habit. Instead of waiting for a big project, the supervisor helps the team test one simple change while the process is still running. The point is not to make every operator a project leader. The point is to learn faster, with less blame, and with clearer evidence from the line.
Why Small Experiments Matter for Supervisors
Supervisors work close to the actual condition. They see when material is staged wrongly, when tools are hard to reach, when a fixture causes repeated adjustment, when the board is not updated, and when operators are quietly working around a weak standard.
If every issue must wait for a monthly improvement meeting, the learning is too slow. By then, the exact condition has changed and the team is left with opinions. A small experiment keeps improvement near the real work.
- It reduces guessing. The team tests what may help instead of arguing from memory.
- It lowers risk. The change is temporary, visible, and checked before it becomes permanent.
- It builds ownership. Operators can see their input become a practical test, not just a suggestion form.
- It supports no-blame coaching. The focus moves from who caused the problem to what condition needs to change.
What Counts as a Good One-Shift Experiment?
A good experiment is small enough to run without disrupting production, but clear enough to produce learning. It should change one condition and measure one expected result.
| Problem seen on the line | Small experiment | What to check |
|---|---|---|
| Operator walks too far for shared tool | Place the tool at point of use for one shift | Walking reduced and no new safety or mix-up risk |
| Wrong material picked during changeover | Add temporary colour label and separate staging lane | Pick errors reduced and material flow stays clear |
| Minor stop repeats at one station | Change cleaning or inspection timing for one shift | Stop frequency and recovery time improve |
| 5S standard drifts after lunch break | Run a two-minute reset check before restart | Area returns to standard without supervisor chasing |
| Hourly board is updated late | Assign one owner and fixed update minute each hour | Gap is visible early enough for action |
| New operator waits for instruction | Post a simple first-job sequence at the workstation | Waiting time and repeated questions reduce |
The Supervisor's 6-Step Experiment Routine
The routine should be simple enough to use during a live shift. If the form is too heavy, supervisors will avoid it when the line is busy.
1. Name the exact condition
Do not start with a general statement like "operator not disciplined" or "machine unstable". Name what can be seen: the tool is kept three metres away, material label is not visible from the loading side, or the board is updated after the hour has already passed.
2. State the expected result
Before changing anything, define what should improve. Examples: reduce walking, reduce waiting, reduce minor stop frequency, make the hourly gap visible within five minutes, or keep the 5S standard after restart.
3. Test one change only
If the team changes tool location, manpower, material staging, and sequence at the same time, nobody knows which change helped. For daily Kaizen, one small test is more useful than a big mixed action.
4. Make the test visible
Mark the test on the line board or handover note. The team should know what is being tested, when it started, who is checking it, and when the result will be reviewed.
5. Check the result at the process
The supervisor should return to the actual point of work. Do not rely only on the end-of-shift total. Look at the process condition: movement, waiting, defect point, recovery time, operator feedback, and any new risk created by the change.
6. Decide: adopt, adjust, or stop
If the experiment works and creates no new problem, update the standard. If it partially works, adjust and test again. If it does not work, stop the change and keep the learning. A failed test is still useful if it prevents the team from locking in a weak solution.
Small Experiment Checklist for Production Supervisors
Use this before approving a trial on the line. It keeps daily Kaizen practical and protects safety, quality, and delivery.
- Is the problem visible at the workplace? If not, go and confirm the condition first.
- Is the experiment small enough to reverse? Avoid permanent changes until the result is proven.
- Does it change only one condition? Too many changes create confusion.
- Is safety protected? Do not test any shortcut that bypasses safety, quality hold, or customer requirement.
- Is the check timing clear? Decide whether to review after one hour, half shift, full shift, or before handover.
- Will the next shift understand it? If the test continues, include it in shift handover standard work.
- Will the standard be updated if it works? Without standardisation, the improvement stays as memory.
How to Run Experiments Without Blame
Small experiments fail when supervisors use them to prove that somebody was wrong. The better approach is to treat the experiment as a way to learn about the process.
When the first test does not work, avoid asking, "Who suggested this?" Ask better questions: What did we expect? What actually happened? What condition did we miss? Did the change create a new problem? What is the next smaller test?
This style is firm but fair. The production target still matters. The standard still matters. The difference is that the supervisor leads the team toward evidence instead of fear.
Where Small Experiments Fit in Daily Kaizen
Small experiments are the bridge between seeing a problem and improving the standard. They work best when connected to the supervisor routines already covered in this series:
- Line Visual Management for Supervisors
- Hourly Production Control for Production Supervisors
- Shift Handover Standard Work for Production Supervisors
- The Supervisor's 5 Questions for Daily Kaizen
- Why Problems Should Be Seen Earlier, Not Hidden Longer
When a Small Experiment Should Become a Standard
A change should not become standard just because people like it. It should become standard when it improves the target condition, does not create new risk, can be repeated across shifts, and can be explained simply to the people doing the work.
| Adoption question | Good signal | Risk signal |
|---|---|---|
| Did it improve the condition? | Output, quality, safety, 5S, or response time improved | Only opinion improved; no observable change |
| Can the next shift repeat it? | The method is simple and visible at the workplace | Only one person understands the new way |
| Did it avoid new problems? | No added safety, quality, material, or ergonomic risk | The fix helps output but creates another loss |
| Was the standard updated? | Work instruction, visual, board, or checklist reflects the change | The change depends on memory and reminders |
| Is there an owner? | One supervisor or line leader checks sustainment | Everyone agrees, but nobody follows up |
Bottom Line for Malaysian Manufacturing Leaders
Daily Kaizen does not need to start with large events. It can start with supervisors learning how to run small, disciplined experiments during normal production. That habit helps teams move from firefighting to controlled improvement.
If you want supervisors to build this routine across shifts and lines, the habit needs coaching, not only a briefing. Our Kaizen Champion development, HRDC claimable Kaizen training, Lean manufacturing workshops, 5S training, TPM capability building, and practical factory-floor consulting help teams turn small tests into stable standards. For a data baseline, connect experiments to the OEE calculator, current improvement case examples, and a focused manufacturing assessment.