Why 5S Fails: It’s Not Your Team’s Discipline, It’s the Missing System

Six months after a $14m custom print shop rolled out 5S, I walked their floor. The shadow boards were still hanging. The bins were still on the workstations. But there wasn’t a single active piece of the program left running.

Prefer listening? Check out this week’s Solo Session where I go even deeper on the topic.

When I asked the team about it, they didn’t hold back. It never made sense to them why they were doing it in the first place. Worse, once their tools were organized and out on display, people from other areas kept walking off with them. It took more time to find things than it did before the program started.

Read that again. The program didn’t just quietly die. It made the floor worse. The operators who actually complied got punished for it, because their beautifully organized workstation became the shop’s free supply cabinet.

That shop is not an outlier. Walk almost any plant floor in the country and you’ll find the ghost of a 5S program. Faded tape outlines. A shadow board missing half its tools. A laminated audit sheet dated three years ago. Today I want to unpack why that happens to almost every program, and why it has almost nothing to do with your team’s discipline.

Prefer listening? Check out this week’s Solo Session where I go even deeper on the topic.

Nobody Ever Calls About a Failed Cleanup

In nearly 30 years of doing this work, I have never once had someone call me because the cleanup part of 5S failed.

The kickoff always works. It’s exciting. People are learning something new, the scope feels approachable, and there’s usually a pizza lunch and a banner involved. The area gets sorted, straightened, and shined, and for the first handful of weeks everything looks great.

The calls come later. A couple of tools go missing. Setup material isn’t where it’s supposed to be. The audit sheet gets walked through twice, then the clipboard goes in a drawer, and within a few months everyone quietly agrees that 5S “doesn’t work here.”

The cleanup worked. The sustain didn’t. If that pattern is this universal, the problem isn’t the people executing it. Something upstream is broken.

Your Program Was Sold to You as a Project

Here’s the uncomfortable part, and I’m going to say it plainly because I’m part of the industry that does this.

Consultants sell 5S as a project because the project is what’s easy to sell. The blitz has a tight scope, a beginning, a middle, and an end. “Let’s 5S one work cell” is an easy yes. The training, the kickoff, the cleanup event, all of that is billable work with a deliverable at the end.

The sustain part? There’s no revenue in it. So the consultant teaches you the framework, runs the blitz, and leaves you to your own devices on the part that determines whether any of it survives.

Think about what a project is: a kickoff, a deliverable, an end date. Now think about what that means for the fifth S. Inside project thinking, Sustain is literally out of scope. The project’s “done” is the cleanup. Your floor doesn’t have a “done.” Nobody at that print shop ever actually decided to stop doing 5S. The project just ended the way projects do.

The leadership team at that shop told me their reasoning for starting where they did: it was easy, and they could use it to get everyone on board. That’s the project mindset in one sentence. 5S as a change-management gimmick instead of an operating decision. The team smelled it immediately, which is why the first thing they told me was that it never made sense why they were doing it.

The Software Crowd Sells the Same Mistake in a Different Box

The 5S software vendors run the other version of this play. Their pitch: paper audits fail because there’s no visibility, so digitize the checklist and the program will finally stick.

I want to be careful here, because I built a 6S audit tool myself. It lives inside our Operations Workbench, and I’ll talk about it honestly at the end of this article. So take this as an admission, not a competitor swipe: the tool will not save your program. Mine included.

Automating the audit makes tracking easier and communication faster. That’s real, and it matters. But if your program is dying, the audit checklist was never the failure point. A digital audit that nobody schedules, nobody reviews, and nobody acts on dies the exact same death as the clipboard. It just dies with better graphs.

If you’re struggling to keep 5S alive, that’s a symptom of something deeper. Buying software to treat a symptom is how companies end up with a subscription and the same problem at the end of the month.

The Messy Floor Is the Symptom

So what’s the something deeper?

When a 5S area decays, the visible problem is the mess. Tools missing, material stacked where it doesn’t belong, the standard slipping a little more each week. The blitz mentality says: clean it up again. Which treats the symptom, which is why the symptom comes back, which is why the third blitz dies exactly like the first one did.

The root cause is a missing rhythm. No schedule for the audits, or a schedule that collapses at the first exception. No memory, because nobody compares this month to last month. No owner, because the findings on the audit sheet aren’t anyone’s job to fix. The area isn’t decaying because people stopped caring. It’s decaying because nothing in the operation is built to hold the gains.

This is the framework I teach showing up in physical form. Sort, Straighten, and Shine create clarity: anyone can look at the work center and know what belongs, where it lives, and what’s missing. Standardize creates consistency: the organized state becomes the documented normal instead of one operator’s personal system. Sustain is the accountability step. Without the clarity, consistency is impossible. Without consistency, accountability flies out the window. Programs that skip to the cleanup without building the rhythm underneath are trying to have accountability without the two things that make it possible.

The Moment That Kills It

Every dead program I’ve examined traces back to the same moment, and it doesn’t happen on the floor like so many think.

A hot job lands. The audit is on the calendar. Leadership has to pick one, and they pick the hot job, and the audit gets pushed to “later.” Later never comes.

If you run 6S the way I teach it, leadership participates in the audits personally. So when senior leaders struggle to choose between the hot job and the audit, I ask them: what chance does the rest of the team have? You just showed the entire floor exactly where 5S sits in the priority list. They will act on what they saw, not on the banner in the break room.

The same erosion happens with findings. An audit surfaces a gap that needs resources the floor can’t authorize. It goes up the chain and dies there, usually because someone genuinely forgot, not because anyone decided no. Nobody tells the operator who flagged it. Next audit, same gap. That operator surfaces one more finding, watches it disappear too, and stops raising their hand.

That’s the chain: gap surfaced, gap ignored, frustration builds, trust erodes. Run that loop long enough and you get what everyone loves to complain about, a culture problem. Notice that at no point in that chain did the floor fail. Every link that broke belonged to leadership.

The Second Rollout at the Print Shop

Back to that custom print shop, because what happened next is the whole lesson.

We restarted the program, and we started with the trust problem, since stolen tools had turned the first rollout into a cautionary tale. Before anyone touched a workstation, we talked about why the company was using lean tools at all, and how continuous improvement was going to make things better for customers and for the people doing the work. We laid out the full vision: every workstation would eventually be in the program, here’s the order, here’s how we plan to audit and sustain it. Nobody had to wonder if this was another flavor-of-the-month event, because the sustain plan was announced before the first sort.

Then we did something that surprised the team. We brought people from outside the department into the sorting process. When an outsider asks why a tool lives where it lives, “that’s the way we’ve always done it” doesn’t survive the conversation. The team had to rebuild the reasoning for their own workstation layout from scratch, and the outsiders learned what the work actually required.

The results were the kind you can see from across the floor. Setup times dropped, easily 30 percent by my estimate. But the more impressive win was harder to measure: people were talking to each other. Teams from different areas were learning from each other, and for the first time, people understood why their coworkers did what they did. The same program that had eroded trust six months earlier was now building it.

Same shop. Same tool. The difference was everything the first rollout skipped.

What a Real Sustain System Looks Like

If you take one section of this article to the floor with you, make it this one. A sustain system that holds has four working parts.

A cadence that survives contact with reality. Weekly audits are the standard I teach. Bi-weekly can work if the area is large or the constraints are real. The specific number matters less than this: pick a cadence you will defend, because the first skipped audit is the beginning of the end.

A rotation, not an owner. The best method I’ve found rotates the auditor between three perspectives: an individual contributor who works in the area, an individual contributor from outside the area, and leadership at different levels. The insider knows the work. The outsider questions what the insider takes for granted. Leadership presence signals that this matters, and leadership should be in the rotation at least once a month, personally walking an audit.

Results posted where everyone can see them. In the area and outside it. Score, trend, and the open gaps. One number from one audit tells you nothing. The direction across audits tells you everything, and posting it publicly is what makes the whole operation aware that the program is alive.

A loop that closes, every time. Every finding gets a disposition, and the disposition travels back to the person who surfaced it. Fix it, schedule it, or say “not now, and here’s why.” Any of those answers builds trust. The only answer that destroys the program is silence. This is the part that dies going up the chain in almost every system I’ve seen, so build the path deliberately: findings become tasks, tasks have owners, and the next audit checks whether the fix held.

Culture Is the Output of a Running System

Everybody wants the 5S culture. Leaders tell me, with a straight face, that they’re going to change the culture with a cleanup program because it’ll get everyone on board.

I love the enthusiasm, but you can’t install culture, and you can’t buy it either. Culture is the scorecard. It’s the output of running a system where surfaced problems actually get addressed, audits actually happen, and leadership actually shows up. People start believing the moment a problem they flagged gets fixed and someone tells them about it. Each turn of that loop builds a little more trust, and the accumulated trust is the thing you were calling culture.

That’s what happened at the print shop. Nobody ran a culture initiative. They ran an audit loop that closed, and the culture showed up as a byproduct. The business got the setup-time reduction and the throughput. The people got a floor where raising your hand means something. Those aren’t two separate wins. They’re the same system, seen from two angles.

About That Tool I Built

Now the admission I owe you, since I spent a section taking a swing at software vendors.

The Operations Workbench has a 6S Audit module. It went live last week. It does the things paper can’t: guided audits from your phone on the floor, automatic scoring, section-by-section trends, and findings that become tasks with owners so the loop I just described actually closes instead of dying in someone’s inbox.

Here’s the difference I’d ask you to weigh, and you can decide if it’s self-serving. The free tier isn’t a trial. Two work areas, full guided audits, your recent history, no credit card, no sales call. I’m not trying to monetize the audit checklist, because the checklist was never the product. The module exists to close the loop between the floor and leadership, inside a bigger commitment to running your business by design instead of by default. Someone selling you a standalone 5S audit app is selling you the checklist. I’m telling you the checklist is the least important part.

Use mine, use paper and a spreadsheet, use whatever you want. The system I described in this article works on any of them, and none of them work without it.

What to Do Monday Morning

Two paths, depending on where you are.

If you already have a program, skip the guilt and run an honest review of your sustain efforts. When was the last audit, actually? Who walked it? Where are the results posted, and can anyone on the floor name an open finding that got fixed? My bet is the gaps you find live in consistency and accountability, and most of them trace up to leadership, not down to the floor. Then pick one work center and restart the loop there. One area, audited on a cadence you’ll defend, with findings that close.

If you’re new to this, resist the blitz. Before anyone sorts anything, spend the extra weeks, and yes I mean weeks, sharing why the business is doing this at all. What’s driving it, what the end state looks like, how you plan to sustain it, and what’s in it for the team doing the work. Then start with one work center, bring outsiders into the sort, and build the audit rhythm before you expand anywhere.

This isn’t a project, an initiative, or an event. It’s the beginning of a different way of operating your business. Treat it with that level of intentionality and the results compound. Treat it as a project and you’ll be reading an article like this one again in six months.

Final Thoughts

The systems running your business right now are there either by design or by default. A dead 5S program is what by-default looks like: good intentions, a strong kickoff, and nothing underneath to hold the gains.

The fix was never more discipline, and it was never a better checklist. It’s a rhythm somebody defends, results everybody sees, and a loop that closes every single time someone raises their hand. Build that, and the clean floor takes care of itself. The culture does too.

That’s it for today.

See you all again next week!

Dave