Why does a 5S program decay six months after the launch event?

A kaizen event is the most visible three days a floor will ever have. The red tags come off, the point of use marks go down, and by Friday the area looks like a different room. Six months later, in a lot of programs, it is not. The tools have drifted back toward wherever is convenient, the labels are peeling, and nobody can produce a second score to compare against the first. The area did not fail the method. It never had the part of the method that was supposed to catch the drift before it became the new normal.

The launch event is a photograph, not a program

Sort, Straighten and Shine all produce something you can see the moment the event ends: a cleared floor, a labelled shelf, a shadow board with every tool traced onto it. That visible result is real, and it is also the exact reason a program can look finished the day it is actually only half built. A photograph taken on the best day an area will ever have is not evidence the area holds that state, it is evidence the event happened.

Why a posted standard is not enough on its own

Standardize writes down what "right" looks like: a photograph of the correct state, what belongs where, the named owner, the trigger that starts a reset. That is real progress over no standard at all, but a standard nobody is checking is a document, not a control. Unless a specific person is named and scheduled to look at it on a specific cadence, checking it becomes optional the first week that person is short on time, and it is always someone's first short week eventually.

The missing sixth S

Classic 5S, Sort, Straighten, Shine, Standardize, and the fifth term, usually translated as discipline or sustaining the habit, has always had a sustain concept somewhere in it. What it has rarely had is an owned, scheduled instrument for actually running that discipline, which is the gap this method treats as its own separate, sixth step rather than an attitude everyone is supposed to hold onto. In practice, sustain means a layered audit: the team leader checks daily or per shift, the supervisor checks weekly, the manager checks monthly, every one of them scoring against the exact same sheet the original baseline used, so a score taken in month four is actually comparable to the score taken on day one instead of being a fresh, disconnected opinion.

Each layer catches a different speed of drift. A team leader checking daily catches a tool back in the wrong spot before the end of the shift. A supervisor checking weekly catches a slower slide the team leader's own habits might miss. A manager walking the area monthly is what tells the floor the standard still matters to someone above the shift level, and if leadership never walks it, the floor learns fast what the program is actually worth to the people who asked for it.

Why programs stop at five S's instead of six

Every one of Sort, Straighten, Shine and Standardize produces something you can point a camera at on day one. Sustain produces nothing visible that quickly. It is a checking habit that only proves itself over months, which makes it the easiest part of the program to skip when the event budget or the event week runs out, and the easiest to defer once everyone in the room is already pleased with how good the area looks by Friday afternoon. That is not a character flaw in the teams who skip it. It is what happens when the only two things a program measures are how the area looks the day the consultant leaves and how much time is left in the schedule.

The signs decay has already started

• The event was treated as the finish line, and no audit calendar exists past the week it ended.
• No individual is named as the owner of a given standard, only "the team."
• Nobody can hand you two scores, taken months apart, against the same sheet.
• An audit ran once, immediately after the event, and never again.
• Leadership has not walked the area since the day they accepted the finished standard.

Any one of these on its own is a warning. Two or more together mean the program already decayed and the area simply has not visibly slid back yet. It will.

What actually holds the gain

Four things, all of them plain rather than clever. The audit uses the exact same scoring sheet as the baseline, so a later score means something against the first one instead of being a new, unanchored opinion. The people who run the daily and weekly checks are your own team, trained and observed running it at least twice before the consultant leaves, so the discipline survives past the engagement rather than leaving with the person who built it. Every standard has one named owner, not a team, because a standard nobody in particular is responsible for is a standard everybody assumes somebody else is watching. And leadership walks the area occasionally, on a real cadence, because that is the signal that tells everyone else on the floor the standard still matters to someone who was not required to be there.

Common questions

What is Sustain, the sixth S, actually?

A layered audit: the team leader checks the area daily or per shift, the supervisor checks weekly, and the manager checks monthly, all three scoring against the identical sheet the original baseline used. The point is not the checking itself, it is that a score taken months later is comparable to the score taken on day one, so drift is visible as a trend rather than felt as a surprise.

Is a layered audit the same thing as an ISO or compliance audit?

No. A compliance audit checks against an external standard on its own schedule, usually run by someone from outside the area. A layered 5S or 6S audit is internal, frequent, and run by the people who work in and lead the area itself, specifically so the checking does not depend on an outside visit to happen.

Who should actually run the daily, weekly and monthly checks?

The team leader for the daily or per shift check, the supervisor for the weekly check, and the manager for the monthly one, each against the same scoring sheet. Training your own people to run every layer before the engagement ends is what lets the audit survive without the consultant.

Can Sustain be added to an existing 5S program without redoing everything?

Usually yes, if a real baseline score still exists or can be reconstructed close to the original state. What cannot be added after the fact is the baseline itself: without a score taken close to the original event, a later audit has nothing comparable to measure against, and the trend line has to start over from wherever the area actually is today.

How long does it usually take for an unaudited program to decay?

Long enough that it feels sudden rather than gradual, which is part of what makes it easy to miss. Six months is a common point for the gap to become visible to someone who was not watching closely, because that is roughly how long a posted standard with no scheduled check tends to survive against ordinary daily pressure before it stops being anyone's actual habit.

Keep reading

• What does a 5S engagement cost, and why won't anyone quote you one?, the nine real factors behind the number nobody publishes
• Corporate Lean 6S, the full four part engagement, including the layered audit this article describes
• The free zone scoring sheet and layered audit template, the same sheet a baseline and a later audit both score against
• The Method, the six S's in the order that works, and why Safety is the fourth one rather than an afterthought