Why Your 5S Programme Died (And How to Make the Next One Stick)

You know the feeling. Somewhere on your shop floor there’s a strip of floor tape lifting at one corner, marking out a spot for a bin that hasn’t actually lived there since spring. Maybe there’s a shadow board with two or three tool outlines standing empty, and nobody’s quite sure whose job it is to chase them up. Perhaps there’s a laminated 5S checklist pinned near the tea point, slightly curled at the edges, last signed off sometime around Easter, if you’re being generous about the date.

If any of that sounds a bit too familiar, you’re not alone, and honestly, you’re not bad at this. Nearly every manufacturer I’ve come across, whether that’s a twelve-person fabrication shop or a two-hundred-person precision engineering site, has tried 5S at least once, got a genuinely good result in the first few weeks, and then watched it quietly slide back to roughly how things were before. It’s such a common pattern that it’s almost predictable. Which, oddly, is good news. Predictable problems can actually be planned for. Unpredictable ones can’t.

This isn’t going to be another explainer on what Sort, Set in Order, Shine, Standardise and Sustain mean. You already know that, or you wouldn’t have read this far down the page. What we’re going to do instead is be properly honest about why your last attempt died, whichever attempt that was, and then build something a good deal more specific than “just keep at it,” because that advice has never actually helped anyone stick with anything.

The predictable death of a 5S programme

Here’s the pattern. See if it matches your own experience. Someone, maybe you, maybe a keen new operations manager, decides 5S is happening. There’s a launch day, sometimes a whole launch week. Skips get filled. Areas get taped off, labelled, photographed for a proud before and after that ends up on a noticeboard or, these days, probably a LinkedIn post. Everyone feels genuinely pleased with what they’ve done, because a cleared out, organised workspace does feel better to work in. That part is never really the problem. That part almost always goes well.

Then week three happens. Production picks up because a big orders landed. Someone key is off sick. The daily check that was meant to happen gets skipped, just this once, for a genuinely good reason. Then it gets skipped again the following week, for a slightly less good reason. By week eight, the checklist’s gone from something people fill in to something people occasionally notice and feel a bit guilty about.

There’s decent evidence behind this pattern too, not just a hunch. Work looking at how workplaces sustain 5S over time has found that without regular audits, an area tends to drift back to roughly how it looked before the project started within three to six months. And once that happens properly, you’re not topping something up. You’re starting again, from scratch, usually with a slightly more cynical team than you had the first-time round.

That’s the bit that stings most, I think. It’s not that the programme failed exactly, in the way a project fails when something obviously goes wrong. It’s that it quietly, gradually reverted, and by the time anyone noticed properly, the cost of restarting felt too high to bother with. So it just didn’t happen. Everyone moved on, unofficially.

The first four S’s, Sort, Set in Order, Shine and Standardise, are honestly the easy part, relatively speaking. They’re visible, they’re satisfying, and a determined team can achieve something that looks properly impressive in a concentrated burst of a few days. Sustain asks for something completely different. It asks for a habit, held indefinitely, under normal production pressure, with none of the adrenaline of a launch day to carry it along. That’s not a lesser task. It’s a different kind of difficult altogether, and pretending it’s the same job as the first four just sets you up to be surprised when it doesn’t behave the same way.

The honest reasons yours probably died

Let’s actually name what usually goes wrong, because vague reassurance never fixed anything and you didn’t come here for a pep talk.

It started as a management edict, not a shared decision. A lot of 5S programmes begin with someone senior deciding the whole site needs sorting out, then rolling the same system out everywhere at once. The trouble is, when a system gets imposed from above rather than built with the people who’ll actually use it every day, the team can tell. If the shadow board doesn’t suit how a particular bench genuinely works, or the labelling makes sense to whoever designed it in an office but not to the operator using those tools fifty times a shift, people quietly stop bothering with it. Not out of laziness, to be clear. Just because a system that doesn’t fit the actual work gets worked around, every single time, until it’s simply ignored.

Sort and Set in Order got treated as the finish line, not the start. This might be the single most common failure I’ve seen, and I’d bet it’s the closest to home for a lot of people reading this. The visible transformation happens in the first two S’s. The clutter goes, the workspace looks completely different almost overnight, and it’s genuinely tempting to call that a win and move attention onto whatever’s next on the list. But Standardise and Sustain are where the actual value gets locked in for good. Without them, you’ve had a very thorough, temporary tidy up, and temporary tidy ups have a shelf life measured in weeks.

Nobody actually built in the time for it. 5S activities are meant to happen daily, but a daily habit needs a slot in the day that genuinely exists, not a vague hope that someone finds five minutes between everything else that’s actually urgent. If sustain has to compete directly with getting an order out of the door, it loses. Every single time. That’s not a character flaw in your team. It’s just how priorities behave under real pressure, and pretending otherwise is how these programmes get set up to fail before they’ve even properly started.

There was no consequence either way. If nothing changes whether the audit happens or doesn’t, if nobody asks about it, checks it, or even mentions it in passing, people reasonably conclude it doesn’t actually matter that much. And to be fair to them, if leadership never turns up to look, why would anyone on the shop floor assume leadership genuinely cares? Actions, or the lack of them, tend to speak a good deal louder than the launch day speech did.

None of these are unusual failures, or embarrassing ones. They’re the default outcome of launching something with genuine enthusiasm and no structure behind it for what happens in month four, once the enthusiasm’s worn off and the actual test of the thing begins.

Start small, on purpose

If your last attempt was a big bang, whole site launch, that’s probably worth naming honestly as part of why it struggled. The instinct behind it makes total sense. You can see mess in every corner of the building, so you want results everywhere, quickly. Doing one area at a time feels frustratingly slow when there’s this much to fix.

But a site wide rollout means asking everyone, across every department, to change their habits at the same time, with no working example anywhere on site to point to when someone inevitably asks, is this actually going to work here, or is it just another idea from a meeting room upstairs. Pick one area instead. Ideally somewhere with a supervisor or a couple of operators who are already a bit more engaged than most, the sort of people others on the floor genuinely listen to without being told to.

Let that area become your proof. Not a pilot in the sense of a trial that might quietly get abandoned if it doesn’t work out, but genuinely your first working example, the one you can point to later. Give it real time, and honestly, give it your attention. Turn up. Ask how it’s going, properly, not as a box ticking exercise. Let the team adapt the system to fit how they actually work, rather than handing them a template built for a completely different factory in someone else’s training manual. Shadow boards that make sense on a machining line might make no sense at all on an assembly bench, and that’s fine. Let it flex.

When the rest of the site sees one area that’s stayed genuinely tidy for three months without anyone chasing it constantly, that does more convincing than any launch presentation or all hands meeting ever could. People believe what they can see working just down the corridor a good deal more than they believe a slide deck.

This approach is slower. It’s meant to be. Slow and steady genuinely does better here than fast and site wide, mostly because it gives you a real answer, backed by your own factory’s own evidence, the next time someone quietly asks whether this is just going to end up like last time.

An audit cadence that survives the shop floor

Assuming you’ve got a working area, or you’re ready to build one, the next question is what actually keeps it alive once the novelty’s worn off and the launch photos have stopped getting looked at.

The answer is a proper audit rhythm, not a single checklist filled in once and then forgotten about on a clipboard somewhere. A cadence that tends to hold up in practice looks something like this. Weekly checks at area level, run by the team leader or supervisor who’s actually there every single day, covering the basics is everything where it should be, is the standard being followed, has anything started to drift since last week. Monthly checks that go a bit wider, run by someone a level up, maybe an operations manager or whoever’s leading continuous improvement across the site, looking across several areas at once rather than just the one. And then quarterly walks from senior leadership, reviewing the overall picture across the whole business, which matters more than it might sound like it should on paper, because it’s the clearest possible signal your team gets that this isn’t just a shop floor exercise nobody upstairs actually cares about.

The frequency matters more at the start than it does later on. Early in the process, once a month simply isn’t often enough, because the habit hasn’t properly formed yet and small drifts compound quickly if nobody’s checking in close to real time. Once an area’s been properly standardised and it’s genuinely holding steady on its own, you can stretch the interval out sensibly, moving from monthly towards something more like six monthly. But that’s something you earn through evidence, not something you assume from day one because you’re keen to reduce the admin.

One more thing worth saying plainly. An audit that only ever finds problems, and never once notices what’s gone right, will wear a team down faster than you’d expect. A quick, genuine word of recognition when an area’s holding its standard does more for sustaining a programme than most people give it credit for. People tend to keep doing the thing that gets noticed. That’s just how it works, in a factory or pretty much anywhere else you’d care to name.

It’s also worth saying that none of this needs to be complicated or expensive. A shared spreadsheet or a laminated sheet on a clipboard does the job just as well as any fancy digital system, provided someone’s actually using it. The tool was never the bit that mattered.

The five-minute check that actually keeps it alive

Here’s the properly practical bit, the thing you can put in place this week rather than filing this post away with good intentions, the way the last three articles you read on this probably ended up.

Pick a fixed time, ideally the same point in the shift every single day, maybe the first five minutes after the morning briefing, or just before the first break when everyone’s naturally already stopped. The team leader walks the area with whoever’s working it and looks at four things, nothing more, because the moment this turns into a twenty-minute exercise, it quietly stops happening within a fortnight.

Is everything in its place. Is the area clean enough that you’d actually spot a problem, a leak, a spill, a loose fitting, before it turns into a bigger one. Is anything missing from where it should be, a tool, a label, a bit of documentation that’s supposed to live on that board. Is there anything that needs sorting today, not filed away for next week when there’s more time, because there rarely is more time next week either.

That’s genuinely it. No spreadsheet, no scoring system for a daily check like this, just eyes on the area and a note of anything that needs fixing, written down somewhere visible so it doesn’t just live in someone’s head and quietly get forgotten by lunchtime. Save the fuller checklist, the properly scored version with all the detail, for the weekly and monthly audits further up the cadence. The daily check exists purely to catch small drift before it becomes the sort of drift that takes a full week to sort back out again.

Five minutes is a deliberately small number. It has to fit inside a normal working day without anyone ever needing to justify it against a production schedule, because if it needs justifying, it’ll lose that argument eventually, probably sooner than you’d think, and probably on exactly the day it mattered most. The whole point of keeping it this short is that there’s genuinely no good reason to skip it, even on a proper mad day. And on the days it does get missed, because it will, occasionally, the answer isn’t to quietly abandon it. It’s just to do it tomorrow, and maybe ask, honestly, why it slipped in the first place.

If you want it to really stick, rotate who leads it every so often. Not so often that ownership feels unclear or nobody quite takes it seriously, but enough that it doesn’t become one person’s personal project that quietly dies the day they’re off sick, on holiday, or move on to a different role entirely. That single person dependency is, funnily enough, its own kind of roadblock, and one that’s just as capable of quietly ending a genuinely good programme as any of the reasons further up this list.

Bringing it together

None of this is complicated, and that’s rather the point of writing it down properly. A 5S programme rarely dies because the idea was wrong. Sort, Set in Order and Shine are genuinely useful on their own, and most teams can pull off a transformation that looks properly impressive within the first couple of weeks. What actually kills it is what happens after that, once the launch energy’s gone and production’s back to normal and nobody’s built in the structure to keep the habit alive without needing enthusiasm to carry it single handedly.

So if your last attempt fizzled out somewhere around month three or four, that’s honestly not a verdict on your team, or on 5S as a method. It’s just what happens to any initiative that jumps straight from a strong launch to an assumption that it’ll maintain itself from there. It won’t. Very little does, if we’re honest about it.

Start with one area rather than the whole site. Build an audit rhythm that runs more often early on and eases off once the standard’s genuinely holding on its own. And put a proper five-minute check into the working day, small enough that skipping it never feels like the sensible option, even on the busiest morning of the month.

That floor tape peeling at the corner, the shadow board missing a few tools, the curled-up checklist from around Easter, none of that has to be where this ends up again. It just needs a plan for month four this time, decided now, while things are calm, rather than in the middle of the next busy period when there’s no headspace left to think about it properly at all.

If any of this has felt a bit too close to home, that’s genuinely what our Lean Awareness Training is built around. It’s not a theory session on what Sort, Set in Order and Shine mean, your teams probably heard that bit before. It’s a practical look at why 5S programmes stall in real UK factories, the audit habits and daily checks that actually survive a busy production run, and how to get a stalled programme back on its feet rather than starting from nothing all over again. Get in touch to find out when the next session’s running.

Sharing is caring!