Every 5S rollout I've ever watched fail died the same way. Not in a dramatic collapse — in a slow fade. Posters go up. Everyone gets a laminated card with the five words on it: Sort, Set in Order, Shine, Standardize, Sustain. There's a kickoff meeting. Maybe donuts. Six months later the red tag bin is full of dust and nobody remembers whose job it was to empty it.
The consultants who sell this stuff will tell you 5S failed because the shop "didn't buy in" or "lacked leadership commitment." That's a diagnosis that costs nothing and explains nothing. The real reason is simpler and less flattering to the people who write the training decks: they built a poster campaign and called it a system.
What Gets Sold vs. What Gets Built
The first three S's are easy to sell because they're easy to see. Sort is a purge — pull everything off the shelf, decide what's trash, throw it out. Set in Order is satisfying — shadow boards, labeled bins, everything with a home. Shine is a good photo op. You can walk a VP through a floor after a 5S blitz and it looks transformed, because it is transformed, for about as long as it takes everyone to go back to doing their actual jobs.
Standardize is where it starts to get harder, because now you need a document that says what "in order" means and who checks it. Most programs still survive this step. They write the SOP. They laminate it.
Sustain is where 5S actually dies, and it dies because Sustain isn't a poster. Sustain is a system with an owner, a cadence, and a cost. Nobody wants to say that part out loud in the kickoff meeting, because it's the part that requires headcount instead of enthusiasm.
What 30,000 Assets Does to a 5S Program
I run a pattern shop across four warehouses. We're not stocking shelves of identical bolts — we're holding over 30,000 unique physical assets: wood patterns, match plates, core boxes, in iron, bronze, aluminum, and steel tooling variants, some of which haven't been pulled in years and some of which get pulled twice a week. Every one of those assets has a location, a condition, a revision history, and a customer it belongs to. That's not a shelf you can 5S with a Saturday blitz and a stack of red tags.
Here's what the consultants don't model: at that scale, Sustain isn't a phase you graduate into. It's a full-time job, every day, forever. Someone has to know that pattern 4471-B moved from Costa Mesa to South Gate for a repair and hasn't come back. Someone has to notice that a core box hasn't been used in three years and flag it for disposition instead of letting it eat rack space until the next audit finds it by accident. Someone has to catch the transfer that got logged wrong before it turns into a two-week hunt during a rush order.
That someone, in my shop, is a Pattern Inventory Clerk. Not a poster. Not a laminated card. A person whose job is to be the truth about where things are and what condition they're in, every single day, because the alternative is a foundry floor stalling out on a pour while three people search a warehouse for a match plate that's actually sitting exactly where the log says it isn't.
The Incentive Problem Nobody Names
Here's the structural piece the consultants skip, because naming it means admitting their product doesn't fix it: 5S fails in a lot of shops because the people who fund the rollout and the people who pay the daily cost of Sustain are never the same people. Leadership signs off on the blitz because a clean floor is visible, cheap, and looks good in a plant tour. Sustain is invisible when it's working and only visible when it's failed — when the pattern's missing, when the pour gets delayed, when the audit finds the shadow board empty and nobody knows why. You don't get credit for the disaster that didn't happen.
So the incentive, quietly, is to fund the parts of 5S that generate a good before-and-after photo and starve the part that generates no photo at all. That's not a shop floor problem. That's a budget problem wearing a lean manufacturing costume.
A clerk-driven system fixes the incentive by making Sustain someone's actual job description instead of everyone's shared afterthought. It's not romantic. It doesn't photograph well. It's a person doing cycle counts, updating a database, flagging discrepancies, and doing it again tomorrow. But it's the only version of Sustain I've seen survive past year one, because it has an owner who gets asked about it directly instead of a poster that gets walked past.
What Root Cause Actually Says
If you run a root cause analysis on a failed 5S program, you rarely find the failure in Sort, Set in Order, or Shine. Those phases have a clear task and a clear finish line. The failure sits in Sustain almost every time, and the root cause is almost never "the floor didn't care." The root cause is: nobody was paid, scheduled, or held accountable to keep it true.
That's an unglamorous root cause. It doesn't need a poster. It needs a line item.
Where This Leaves You
If you're a plant manager who's watched a 5S rollout fade the way I described, don't run it again with a better poster. Ask who owns Sustain on day 200, not day 2. If the honest answer is "everyone," you don't have a system — you have a photo op with a shelf life. Build the role, staff the role, and measure the role the same way you'd measure any other function that keeps your floor running: on whether the thing it's responsible for is actually true when someone checks it.
The red tag was never the point. The point was whether the floor is still telling the truth six months after the consultants left.
Send this to whoever owns your 5S board.