The 30 Days After Lean Training: A Plan So It Doesn’t Fade

Posted on by Adam Payne

You know the feeling. Two days of training, a room that smelled faintly of flipchart pens, and by the end of it everyone was genuinely up for it. Someone from the shop floor who barely speaks in meetings suddenly had three ideas about the goods in bay. The trainer was good. The examples landed. You drove home thinking, right, this time it’s actually going to happen.

Then Monday happened. A machine went down, a customer moved a delivery date forward by a fortnight, and somebody left. By week three the workbook was in a drawer. By week six, if you’re honest, the only visible evidence of the training was a line in the accounts.

That’s not a failure of your team. It’s not even really a failure of the training. It’s what happens by default when nothing changes about the thirty days that follow. And it’s fixable, but only if you decide what those thirty days look like before you book the course, not after the energy has already drained out of the room.

So here’s the whole thing. The actual framework. Three projects in week one, a fifteen-minute huddle every day, a board on the wall that anyone can see, and a review on day thirty that you run in front of the team rather than in your office with a spreadsheet. That’s it. Four moving parts.

I’ll be upfront about something. Most training providers keep this bit slightly vague, because the follow-on coaching is where the money sits. I think that’s a bit backwards. If you can run this yourself, run it yourself. You’ll get more out of the training you’ve already paid for, and you’ll know exactly what you’re buying if you do decide to bring someone in later.

Why lean training fades, and why it isn’t your team’s fault

Start with the uncomfortable bit. Research on the forgetting curve suggests that without reinforcement, people lose roughly half of what they learned within an hour, about 70% within a day, and up to 90% within a week. That’s not a slight on anyone. That’s just how memory works when information isn’t used.

It gets worse when you look at application rather than recall. The Association for Talent Development puts the proportion of retained knowledge that actually gets applied on the job at somewhere around 10 to 20%. Stack those two numbers together and you can see why a two-day course, on its own, changes almost nothing. Not because the content was weak. Because a course is an event, and what you’re trying to change is a routine.

You’ll have seen the statistic that seventy, or eighty, or ninety percent of lean transformations fail. Those figures do circulate widely, with claims that around 70% of continuous improvement implementations fail and that 66 to 90% fail to sustain their improvements. To be honest, when you chase those numbers back through the citations, they get a bit thin, and I’d be wary of anyone who quotes them at you with too much confidence. What’s much better evidenced is the reason things stall. Transformations tend to unravel not because the tools were wrong but because leadership attention didn’t persist past the initial rollout, with momentum commonly lost within six to twelve months.

Read that again, because it’s the whole point. The thing that kills it isn’t resistance. It’s drift. Nobody says, “we’re stopping this.” It just stops being mentioned, and then one day you realise it’s been four months.

And the cost of that drift has gone up. UK employer training spend has fallen to around £1,700 per employee, down from £1,960 two years earlier and nearly 30% lower than 2011 in real terms. The average employee now gets 5.7 days of training a year, the lowest figure on record. You’re getting fewer shots at this than manufacturers did a decade ago. Which makes wasting one feel considerably more expensive than it used to.

Week one: three projects, and nothing else

The single most common mistake is enthusiasm. Everyone comes out of the training with eleven ideas and tries to start nine of them. Within a fortnight none of them are finished, which teaches the team something quite damaging: that this stuff gets started and never lands.

So week one, you pick three. Three is deliberate. It’s enough that the improvement isn’t one person’s pet project, and few enough that you can hold all three in your head while you’re also, you know, running a factory.

Pick them against four rules.

One: it has to be finishable inside thirty days. Not “substantially progressed.” Finished. If it needs capital approval, a new supplier or another site’s cooperation, it’s a good project but it’s the wrong project for this month.

Two: it has to be visible from where people actually work. Changeover time on a specific machine. The layout of one bench. How parts get from inspection to dispatch. If nobody can see the change by walking past it, it won’t reinforce anything.

Three: it needs one named owner. Not a team, not a department, one person with a name. Shared ownership sounds collaborative and behaves like nobody owning it.

Four: it needs a number. Minutes, metres walked, scrap pieces, days of stock, whatever fits. Pick the number before you start and write down what it is today. You’d be amazed how many improvement projects can’t prove anything afterwards because nobody recorded the starting point.

Write all three on one sheet of paper. Project, owner, measure, the number today, the number you’re aiming at, the date. Then stop. Don’t add a fourth because someone had a good idea on Wednesday. Put it on the ideas list for next month.

I’ve watched this go wrong the same way more than once. A firm comes out of training genuinely fired up and decides the first project will be “reorganise the whole production layout.” Which is, to be fair, probably the right thing to do eventually. But it needs a shutdown weekend, a forklift and about eleven conversations with people who weren’t in the training. Six weeks later nothing has moved, and the quiet conclusion in the canteen is that lean is a thing managers talk about. Meanwhile the boring project nobody chose, the one where you move the consumables trolley four metres and save an operator a hundred and twenty steps a shift, would have been done by Thursday and would have convinced more people than the layout ever could.

Small and finished beats big and pending. Every time, in that first month.

The daily fifteen minute huddle

This is the engine. If you only do one thing from this post, do this one.

Same time every day. Same place, which is on the floor in front of the board, not in an office. Standing up. Fifteen minutes with a timer, and when the timer goes you stop, even mid-sentence, because the reliability is more valuable than the extra five minutes of discussion.

The pattern that’s used across lean daily management systems is a short huddle of roughly ten to fifteen minutes, led by staff rather than managers, held directly in front of the visual board so the numbers get discussed and updated in the moment. That last detail matters more than it sounds. A huddle away from the board becomes a meeting. A huddle at the board stays a conversation about the work.

Keep the agenda to four things. What happened yesterday against the number. What’s in the way today. One update on each of the three projects, even if the update is “nothing moved.” And who is doing what, by when.

That’s it. No round the room updates. No “while we’re all here.” The moment it becomes a general meeting it grows to forty minutes and then people start finding reasons to miss it, and then it’s dead. I’ve seen a good huddle killed inside three weeks by exactly that, and the odd thing is nobody notices it happening, because each individual extra topic seemed reasonable at the time.

A few things worth deciding up front. Who runs it when the usual person is off, because they will be off. Whether it happens if you’re not there, and the answer should be yes, emphatically yes, otherwise it’s your meeting rather than the team’s. And what happens when a problem comes up that the group can’t solve. You need a simple escalation route, even if that route is just “it goes on the board with my name on it and I’ll come back tomorrow.”

Come back tomorrow, by the way. Actually come back. The fastest way to teach a team that raising problems is pointless is to ask them to raise problems and then not close the loop.

The board on the wall

Physical. On the floor. Where the work happens, not in a meeting room and definitely not only in a spreadsheet on your laptop.

I know digital boards are neater. I know the reporting is better. But in the first thirty days you’re not trying to build a reporting system, you’re trying to build a habit, and a whiteboard that fifteen people walk past forty times a day does something a dashboard cannot. Established guidance on visual boards makes the same points: keep it simple at the start, site it somewhere a stand-up huddle can physically happen and get team members to update items rather than doing it all yourself.

Keep it to three to five measures. Not twelve. Tracking a dozen or more metrics dilutes attention, and three to five well-chosen indicators hold focus far better. Whatever you pick, it should be something the team can influence today. Group order intake is interesting but nobody on the floor can move it this morning.

On the board: the three projects with owner and status, the measures with today’s number written by hand, a column for problems raised and who’s on them, and a space for ideas that aren’t being worked on yet. That last column is quietly important. It gives you somewhere to put the fourth good idea without derailing the three you committed to, and it stops people feeling ignored.

Handwritten, always. There’s something about a number written up in marker pen by the person who owns it that a printed sheet never quite achieves. Also, printouts get out of date and stay on the wall for weeks, which trains everyone to ignore the board.

Two failure modes to watch. The first is the beautiful board, laminated and perfect, that nobody dares write on. The second is the board in the wrong place, round a corner, past a fire door, somewhere you have to make a deliberate trip to see. If it takes a decision to look at the board, people will stop making that decision by about week two.

Day thirty: the review you run in front of the team

Put the date in the diary on day one. Tell everyone the date on day one too. That’s not a formality, it’s most of the mechanism.

Thirty days in, you stand in front of the board with the team, for about half an hour, and you go through five things. What you said you’d do. What actually happened, with the numbers. What you learned, including from whatever didn’t work. What you’re keeping permanently. And what the next three projects are.

Run it publicly. In front of everyone, not as a management summary that gets emailed round afterwards. A commitment made in front of the people doing the work behaves completely differently to one made in a leadership meeting, and the recognition lands differently too. When the operator who owned the changeover project stands up and says the number went from fifty-two minutes to thirty-one, that’s worth more to the next thirty days than anything you could say on their behalf.

Talk about the one that failed. Properly, not defensively. Usually one of the three won’t have landed, and how you handle that is the real test. If a missed project produces a telling off, you’ve just taught everyone to pick easy projects forever. If it produces a genuine conversation about what got in the way, you’ve taught them that the system is about learning, which is the whole idea.

If your trainer offers a follow up session, this is the day to use it. Not week one, when everyone still remembers everything. Day thirty, when you’ve hit real obstacles and have actual questions.

Then, on day thirty-one, you pick the next three and carry on. The huddle doesn’t stop. The board doesn’t come down. That’s the bit people get wrong: they treat day thirty as the finish line, when it’s closer to halfway. The UCL research on habit formation found it takes an average of 66 days for a new behaviour to feel automatic, with a range running from 18 days to as much as 254 depending on the behaviour. Thirty days gets you to the point where it stops feeling like an imposition. It doesn’t get you to the point where it survives you going on holiday.

One more thing from that research, and it’s genuinely reassuring. Missing a single day had no measurable effect on habit formation. So if the huddle doesn’t happen on the Tuesday everything went wrong, that’s fine. You haven’t broken it. Just don’t miss twice.

Bringing it together

None of this is complicated, which is sort of the problem with it. Three projects, one board, fifteen minutes a day, a review on day thirty in front of the people who did the work. There’s no clever methodology hiding in there and no software to buy. It’s just a decision about what happens in the four weeks after the training, made while you still have the energy to make it.

The reason it works isn’t that it’s clever. It’s that it replaces attention, which fades, with structure, which doesn’t. Improvement efforts overwhelmingly stall because leadership focus moves on rather than because the tools were wrong, and a fifteen minute huddle is basically a mechanism for making focus happen without anyone having to remember to focus.

It also costs nothing, which matters at the moment. With manufacturing forecast to grow under 1% this year and energy and employment costs still squeezing margins, the improvement you can make with a whiteboard and a quarter of an hour a day is a very different proposition to the one that needs capital.

So don’t try to do everything in this post. Pick the date of your day thirty review and tell someone. That’s genuinely the first move. The three projects and the board can be sorted in an afternoon once there’s a date that makes them necessary.

And yes, this is the part that most providers would rather sell you than publish. I’d rather you had it. If you run it yourself and it works, brilliant, that’s the training doing its job. If you get three weeks in and the huddle has turned into a status meeting, or the projects have stalled because they were too big, that’s when a bit of outside help earns its money, and at least you’ll know precisely what you’re asking for.

If you’d like someone to sit in on your first week and your day thirty review and help you choose three projects that will actually finish, get in touch and we’ll talk it through.

Kanban on a Shoestring: Two Bin Replenishment Without Buying a New ERP

Posted on by Adam Payne

Somebody has sent you a quote for £60,000. Maybe it arrived on a Monday morning, about ten minutes after you found out that a line had been standing idle waiting for a box of M8 washers that cost less than the biscuits in the meeting room.

I’ve been in that room. Not the same one, obviously, but close enough. I’ve walked into more stores cages than I care to count where a perfectly capable team was losing hours every month to parts worth pennies, and where the proposed fix was a piece of software with a project plan, a data migration and a go live date that everybody quietly assumed would slip.

I want to be fair here. An ERP can be a very good thing. If you need proper bills of materials, job costing, traceability and one version of the truth across sales, purchasing and finance, it might be exactly what your business needs, and £60k isn’t a silly number for it. But that’s not the problem that landed on your desk this morning. The problem is that things run out. Cheap, boring, everyday things.

For that specific problem, there’s a method that’s older than most ERP vendors, needs no software and can be running on your shop floor by the end of next week. Two bins and a card.

This is a practical build guide. We’ll cover which items are worth putting on it, how to size the bins, where the card should live, and what to do in the first month when, and I’ll be honest with you, people will forget. They always do. It’s fine. It’s part of how you get there.

Why a £60k system might be answering a different question

Start with the money, because it matters. For a UK manufacturer with somewhere between ten and fifty people, one buyer’s guide puts a realistic first year budget at £20,000 to £100,000, depending on how complicated the operation is. So your quote isn’t outrageous. It’s just a lot of cash to spend on something that may not touch the actual problem. FactoryIQ

Then there’s the risk side. One 2026 analysis of discrete manufacturing projects (written by an ERP consultancy, so take it with a pinch of salt) reports that around 73 per cent fail to meet their objectives, with average cost overruns of 215 per cent. I wouldn’t tattoo those numbers on your arm. But I’ve seen enough go lives to know the direction of travel is about right.

Here’s what I’d want you to think about. Most stockouts on most shop floors don’t come from a shortage of software. They come from cheap consumables and small components that nobody has been asked to watch. Fasteners, gaskets, abrasives, sleeving, labels, cable ties, that sort of thing. And an ERP only knows what’s on the shelf if somebody books stock in and out. Picture how likely that is for a bag of washers at half past two on a Friday afternoon. Yes. Exactly.

That’s the quiet flaw in using a system to fix a discipline problem. The software’s reorder point is only as good as the stock count underneath it, and the stock count for low value parts is usually the least accurate number in the building. A two-bin system sidesteps the whole thing. There’s no transaction to forget, because the empty bin is the transaction.

None of this is new, either. Taiichi Ohno developed pull replenishment at Toyota, and the kanban card owes a good deal to the older two bin method, where emptying the first bin sends a card to purchasing. You may have heard the story about Ohno having a lightbulb moment in an American supermarket. Apparently, that’s a bit tidier than the truth. His 1956 trip was a business visit to study car plants and equipment suppliers, with the supermarket as a side trip. I quite like that, actually. The idea didn’t need a grand moment of inspiration. It just needed somebody to notice that an empty container is already a perfectly good message.

Which items qualify (and which really don’t)

You won’t put everything on this system, and you shouldn’t try. Not every part in your building deserves the same treatment.

The tidy way to think about it is ABC analysis. Rank your parts by annual spend, and you’ll usually find that the C items, the cheap ones, make up about half of your part numbers but only five to ten per cent of the value. Those are your candidates. They’re the parts that cause the most nuisance and tie up the least cash.

You don’t need a system to work this out. Export twelve months of purchase lines from Xero, Sage or whatever you use. Multiply unit price by quantity, sort from highest to lowest, and look at the bottom half. That’s an afternoon’s work at most, and I’d say it’s less if you’re comfortable with a spreadsheet.

But there’s a better filter than the spreadsheet, and it’s free. Ask your supervisors and your buyer one question: what did we run out of in the last six months? The list writes itself in about ten minutes. The best candidates are usually the parts people already swear about.

Then run each candidate through five quick tests.

Steady demand. It gets used most weeks, in roughly similar amounts. If it’s used in a burst once a quarter, it’s not a two-bin part.
Low value per unit. A spare bin of them shouldn’t make your finance director wince.
Short, dependable lead time. Your supplier delivers in days, not weeks. Catalogue items from a wholesaler are ideal.
Physically binnable. It fits in a tote, a box, a bag or a marked shelf space you can point at.
Used in a known place. One or two locations, not scattered across three buildings.

And what doesn’t qualify? Anything engineered to order. Anything with a long or unpredictable lead time. Expensive components where holding a second bin is a real cash decision. Project driven parts that spike with a big job. And anything where you need batch traceability, because two bins won’t give you that. Those parts need proper records, and that might be where a future ERP genuinely earns its money. I’m not being dogmatic about it. Kanban isn’t a religion.

Now the bit people always want to skip. Don’t start with all four hundred C items. Pick a handful. Most guides suggest piloting on a small number of parts before rolling it out across the warehouse, and I agree completely. I’d say fifteen to twenty-five items is about right. Include a few of the ones that hurt most, so people see the benefit quickly, and a few boring ones that will work first time and build a bit of confidence. Those early wins matter more than you’d think.

Sizing the bins without needing a degree in statistics

The maths is gentler than people expect. The logic goes like this: when the front bin runs out, the reserve bin has to keep you going until fresh stock arrives. So the reserve needs to cover your daily usage multiplied by the time it takes to get replacement stock, plus a bit extra for when things go wrong. Most guides boil it down to daily usage times lead time, plus safety stock.

I’d tweak that in one small way. Lead time isn’t only your supplier’s delivery time. It’s everything between the bin emptying and new stock being on the shelf, and that includes the time the card spends sitting in a tray waiting for someone to notice it. So here’s the version I’d actually use:

Bin quantity = daily usage × (your own delay + supplier lead time in working days) + safety stock

Let’s make it real. Say you use stainless M8 bolts at about 60 a day. Your supplier delivers three working days after you order. Your own delay, the time between the bin emptying and the buyer placing the order, is about a day. That’s 60 × 4, which is 240. Add 25 per cent for safety, which is another 60, and you get 300. The supplier sells in boxes of 100, so that’s exactly three boxes per bin. Lovely. Rare, but lovely.

If it doesn’t divide that neatly, and it usually won’t, round up to the nearest whole pack. A bin that’s slightly oversized costs you pennies. A stockout costs you an hour of a line.

Now, where does the daily usage number come from? There are two routes. The careful one is to track real usage for at least two to four weeks before you fix any quantities. Count what goes out, or count empties, or ask the operators to tally on a bit of paper stuck to the shelf. The lazy but surprisingly decent one is to take your annual purchased quantity from the purchase ledger and divide it by the working days you actually run. For most UK sites that’s somewhere around 225 once you take out weekends, bank holidays and leave. It won’t be perfect, but it’ll be closer than a guess, and a lot closer than what most people put in an ERP’s reorder field.

For the safety margin, I’d go 25 per cent for reliable suppliers and up to 50 per cent for patchy ones. And in month one, lean towards too big rather than too small. You can trim later once you’ve got real evidence.

Then run one last sanity check. The time it takes to get through a bin has to be longer than the time it takes to reorder and receive replacements, otherwise the second bin could run dry before new stock arrives. In our example, 300 bolts at 60 a day lasts five days against a four-day replenishment loop. That gives you one day of breathing space. Good.

Two practical points that catch people out. First, check the bin can physically hold the quantity. I’ve seen beautifully calculated numbers that needed a bin the size of a wheelie bin. If it doesn’t fit, use a bag, a marked shelf, or a bigger container, or reconsider whether it belongs on the system at all. Second, watch out for minimum order quantities. If your supplier only sells 1,000 at a time, your bin size might need to be 1,000, and now it’s a different conversation about cash and space.

Sanity check the cash too. Three boxes of bolts at around 9p each is £27 of stock per bin, so £54 across the pair. For genuinely cheap C class parts, the total stock you’re holding is usually a small number. Do the sum for your own list. It’s a useful moment, to be honest, because it shows just how little money is tied up in the things that stop your line.

Where the card goes, and why it’s the whole system

The bins get all the attention. But the card is the actual system. The card is the message. If it goes missing, you’ve just got two boxes on a shelf and a false sense of security.

On the card itself, keep it plain. You want the part number and a description in the words your team actually uses, not the catalogue’s. Add the supplier and their product code, the bin quantity and pack size, the lead time, where the part lives, who orders it, and the date the size was last reviewed. Colour code it by supplier or by buyer if you can. Laminate it or slip it in a clear pocket, because shop floors are grubby places and paper doesn’t last a week without help.

Here’s the loop, and I’d suggest pinning it up where everybody can see it:

The operator uses up the front bin.
They pull the card and drop it in the collection point, then slide the reserve bin forward.
The buyer collects cards at set times, orders one bin’s worth, and moves the card to an “on order” board with the date written on it.
When the delivery arrives, goods in refills the empty bin and puts the card back on it.
The refilled bin goes to the back of the shelf and becomes the reserve.

Now, where does the card physically sit? For small loose parts, my favourite is at the bottom of the front bin. It’s revealed the moment the last item is taken, so nobody has to remember anything. The empty bin practically announces itself. For bulkier items, where a card in the bottom would get buried, use a clear pocket on the shelf edge or the front face of the bin.

The collection point matters as much as the card. Put it somewhere people walk past anyway. A clear wall pocket at the end of the aisle, a small letter tray by the stores hatch, something like that. Not on the buyer’s desk in the office. Every step you add between the empty bin and the buyer is another place the card can quietly die.

The “on order” board is worth the ten minutes it takes to make. Two columns will do, “to order” and “on order”, with the date the order went in. When a card has sat under “on order” for longer than the lead time, it’s obvious. You’ll spot a late delivery before your operators do, which is a nice change.

Then think about your buyer’s rhythm. If cards get collected at nine and two every day, your own delay in the formula is roughly half a day to a day. If they get collected on Fridays, it’s a week, and every bin you sized needs to grow. This is the sort of detail that quietly wrecks a system that looked perfect on paper.

And here’s the honest weakness. A paper card can be dropped, borrowed or wiped, and an empty bin nobody actioned looks the same as a full one until the line starves. That’s true, and I’d rather you knew it now. The method is sound. The card carrying it is fragile. So build in one simple rule: a bin without a card is a red flag, and a card without a bin is a red flag. Then have the owner do a two-minute walk of the pilot area each day for the first few weeks, looking for exactly those two things.

The first month: what to do when people forget

People will forget. I say that with real affection. It isn’t laziness, it’s just that you’re asking a busy team to change a habit they’ve had for years, and habits are stubborn.

I remember helping a site where the cards kept vanishing. Somebody would find an empty bin, no card, and the buyer had no idea what to order. We spent a week suspecting sabotage, or at least a mild lack of enthusiasm. It turned out they were being taken home in overall pockets and going through the wash. We switched to cards fixed to the bin with a cable tie and the problem stopped inside a day. Nobody had done anything wrong. The system had just made it easy to walk off with the card.

That’s the mindset I’d encourage. When something goes wrong, don’t ask who forgot. Ask what the system made easy.

Before you start, give it an owner. A name, not a department. The advice from people who’ve done this is blunt: without a clear owner, the system collapses the first time somebody goes on holiday. Decide who checks the cards, who orders, and who covers when they’re away. Write it on the board.

Then here’s roughly how I’d shape the first four weeks.

Week one: sit with it. Walk the pilot area twice a day. Most problems show up on day two, and they’re usually small and slightly embarrassing. A bin in the wrong place. A card with a typo in the supplier code. A reserve bin that’s actually half empty because it was never filled properly at the start. Fix things on the spot and thank people for pointing them out.

Week two: resize. By now you’ll have a few real cycles of data. Some bins will be too small (you’ll know, because you nearly ran out) and some too big (because they haven’t moved in ten days). Adjust quantities and update the cards. This is the week that turns a guess into a system.

Week three: deal with the awkward bits. Holiday cover, night shift, agency staff who weren’t there for the briefing. This is also when the odd behaviours emerge, so watch for them. There are usually four.

Someone slides the reserve bin forward but leaves the card on it, so the buyer never sees it. Someone tops up the front bin from the reserve “to be helpful”, which quietly destroys the safety margin. Someone borrows a bin from another station and doesn’t bring it back. And the buyer, quite reasonably, batches cards until Friday because that’s when the orders go out anyway.

None of these is a disaster. Each one tells you where the design needs a small fix. Perhaps a sign on the shelf saying, “never top up from the reserve”, or a fixed collection time agreed with purchasing.

Week four: count and decide. Before you make any decision about expanding, gather three simple numbers. How many stockouts happened on the pilot items, compared with the month before? How many emergency or expedited orders did you place? And roughly how many minutes did your buyer spend chasing these parts? A tally sheet on the wall is plenty. You’re not building a dashboard. You’re just trying to have an honest conversation with some evidence in it.

If it’s worked, and in my experience, it usually does, add the next batch of items. If parts of it didn’t, you’ll know exactly which parts, and you’ll have spent a few hundred pounds finding out rather than sixty thousand.

Bringing it together

Two bins and a card won’t run your business. It won’t cost your jobs, schedule your machines or give you traceability on a critical component. It isn’t meant to.

What it will do is solve one specific, expensive, irritating problem, which is running out of cheap things. It works because the empty bin is the signal, so there’s no stock count to get wrong and no transaction to forget. You pick items that suit it, mainly steady, low value parts with short lead times. You size the bins using daily usage, a realistic lead time (including your own delay) and a sensible safety margin. You put the card where it can’t quietly disappear. And you give it a named owner and a month of patience while people find their feet.

If you still want an ERP after that, good. It’s a perfectly reasonable thing to want. But you’ll be buying it for the right reasons, to handle the complicated parts of the business, and you’ll have taken the daily nuisance of washers and cable ties off its plate. In fact, a well-run kanban loop for your C items can sit happily alongside a future system, doing the boring job it does best.

So here’s what I’d do this week. Ask your supervisors what you’ve run out of since March. Pick fifteen of the worst offenders. Do the sums on a single sheet of paper, buy a few dozen bins and a pack of card, and try it for a month. If it doesn’t work, you’ve lost very little. If it does, you might just find that the £60k conversation gets a lot shorter, and a lot more interesting.

Want a hand setting this up?

Reading a build guide is one thing. Putting it into practice on a busy shop floor, with real suppliers, real deadlines and a team who already have full-time jobs, is another. I know that.

If you’d like some support, we can do as much or as little as you need. We can walk your stores with you and choose the right pilot items, size the bins from your own purchase data, design the cards and the collection point, and stay involved through that awkward first month when people forget. There’s no software to buy and no six-month project plan to sign off. The aim is a working pilot on your shop floor within a couple of weeks.

If you’d like to talk it through, book a no obligation call with one of our team. Bring your list of things you keep running out of. That’s usually all we need to get started.

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

Posted on by Adam Payne

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.

The True Price of a Late Shipment: Why Lead Time Reduction Protects Your Biggest Clients

Posted on by Adam Payne

Nobody rings you up to tell you they’re leaving.

That’s the bit that catches most manufacturers off guard. You brace for the big goodbye, the awkward call from procurement, the meeting where someone finally admits things aren’t working. Honestly, it rarely goes that way. Most of the time a client just quietly starts sending you less. A purchase order that used to land every month slows to every other month. A quote you’d normally win goes to someone else and nobody bothers explaining why. The account manager who used to chase you for updates stops chasing altogether, because they’ve already found a supplier who doesn’t need chasing.

By the time you spot that pattern on a spreadsheet, the relationship has usually been eroding for a while.

I think manufacturers are generally good at measuring the wrong side of this problem. You’ll have a dashboard for on-time-in-full, a KPI for average lead time, maybe a red, amber, green rating for your own supplier performance if you’re the one being measured this time. What you rarely have is a clean line drawn between “we shipped that order four days late” and “and that’s part of why our biggest client now sources a third of that product line from someone else.” The two things sit in different departments, on different reports, reviewed by different people at different meetings. So the cost of a late shipment gets treated as an operations problem. It should be treated as a commercial one too.

That’s really what this piece is about. The maths on lead time reduction is well proven at this point. Cut it in half and you’re not just running a leaner shop floor. You’re removing one of the quiet, unglamorous reasons your best clients start looking elsewhere. Let’s get into why.

The cost you can see is never the real cost

When a shipment runs late, you can usually put a number on the obvious bit. Maybe there’s a penalty clause buried in the contract. Maybe you’re paying for a next day courier to bail yourself out, which on a heavy or awkward item can wipe out the margin on the whole order. Maybe someone in customer service loses half a day fielding calls and drafting apology emails. All of that is real, and all of it is annoying, but none of it is actually the expensive part.

The expensive part is what happens in the client’s head.

Research on delivery reliability keeps landing on a similar pattern, whichever industry you look at. One widely cited survey found that roughly two thirds of customers will stop buying from a supplier after two or three late deliveries, and about one in seven will walk after just a single one. Those particular numbers come from a retail context, so treat them as directional rather than gospel, but anyone who’s spent time in manufacturing account management will tell you the underlying behaviour rings true. Clients rarely announce a rule like “three strikes and you’re out.” They just start quietly hedging. A second supplier gets added to the approved list. An order that would once have been 100% with you becomes 70%. It isn’t dramatic. It’s just insurance, from their side of the table.

There’s a piece of research from B2B International on this that I think about a lot. It makes the point that a supplier who never has one dramatic failure, no huge blow up, no crisis call, can still be slowly losing an account through a string of small things. A delivery that lands a day or two late here. A pallet that turns up short there. An invoice query that never quite gets resolved. None of those on their own would prompt a call to the managing director. Stack a few years of them together, though, and you’ve built a relationship that’s fragile without ever having had a visible crack in it. To be fair, most buyers won’t switch the second something goes wrong, because switching suppliers is a genuine pain: new quality checks, new onboarding, new risk to manage. That inertia buys you time. It just doesn’t buy you forever, and it’s not something worth relying on as a strategy.

If you manufacture anything that feeds into a client’s own tightly scheduled production line, this matters even more. A late delivery into a schedule like that doesn’t just annoy someone. It can stop their line. And a client whose line has stopped because of your shipment remembers that far longer than they remember the previous twenty deliveries that went perfectly fine.

Your biggest client is also your biggest exposure

Here’s an uncomfortable one. Look properly at your own client list and there’s a decent chance a small number of accounts account for most of your turnover. It’s such a consistent pattern across industries that it’s earned a name, the Pareto principle, and in manufacturing it often shows up in a fairly extreme form. One advisory firm reviewing manufacturing clients found a business where a single customer made up 56% of total revenue. That’s not some rare outlier. Plenty of mid-sized manufacturers would find something similar if they were honest about the numbers on their own dashboard.

The thing about that kind of concentration is it cuts both ways. Those big clients are wonderful, obviously. They’re what pays for the new machinery, the wage bill, the Christmas do. But they’re also the accounts with the most leverage over you, the most sophisticated procurement teams, and the widest choice of alternative suppliers. A small client with a modest order probably doesn’t have the appetite to run a full tender process the moment you slip a date. A large client almost certainly does and probably runs one periodically anyway as a matter of policy.

So when you think about where an unreliable lead time actually bites hardest, it’s rarely your smallest, most forgiving accounts. It’s the big ones, the ones with a procurement director who has supply risk targets of their own, the ones who can dual source without much disruption to their own operation at all. There’s a real irony in this. The clients you can least afford to lose are often the ones with the least reason to stay loyal once your delivery performance starts to slip.

I worked with a fabricator a few years back whose largest client, a fairly well-known name in construction plant, quietly moved about a third of their order volume to a second supplier after two missed deadlines in the same quarter. There was no scene, no crisis meeting. The account manager on the client side just mentioned, almost in passing, that they’d started “spreading the risk a bit.” That phrase should worry any manufacturer who hears it, because its client speak for we don’t fully trust you to deliver anymore, and we’re quietly managing that ourselves rather than making it your problem to fix. The order never fully came back either, even once delivery performance recovered. Trust rebuilds a lot slower than it breaks. Worth remembering next time a delay feels like a one off.

The maths that should worry you more than the KPI dashboard

Put the emotional argument to one side for a second, because there’s a purely financial one that’s just as strong. Arguably stronger.

Across pretty much every study anyone’s done on this, the pattern holds up. Multiple pieces of research converge on the same range: winning a genuinely new customer typically costs somewhere between five and twenty-five times more than holding onto one you already have. The odds of selling to a customer who already buys from you sit around 60 to 70%, compared with something like 5 to 20% for someone brand new. And the profit effect of retention isn’t small either. Bain & Company, whose work on this is about as solid as it gets, found that a modest five-point improvement in customer retention can lift profits by somewhere between a quarter and almost double, depending on the business.

Sit with that range for a second. A quarter to nearly double, from a five-point shift in retention. Most manufacturers would move heaven and earth for a 5% improvement in scrap rate or a 5% improvement in overall equipment effectiveness. Retention deserves at least the same attention, probably more, and yet it rarely gets a line of its own on the operations review.

Now factor in something specific to manufacturing that makes this sharper than it would be for, say, a software business. Winning a new manufacturing client usually isn’t a quick transaction. There’s a tender, a sample run, quality audits, possibly tooling investment on your side before a single commercial part ever ships. That sales cycle can run months, sometimes well over a year for anything technical or regulated. So when you lose a chunk of business from an existing client, you’re not just losing this quarter’s revenue. You’re signing up for a replacement process that’s slow, expensive, and not guaranteed to work, while your fixed costs, the building, the machines, the people, carry on regardless of whether that gap ever gets filled.

To be honest, I think this is the argument that lands hardest once you get it in front of a finance director. Lead time reduction usually gets pitched internally as an efficiency project, something the operations team owns with a business case built around labour hours and inventory carrying cost. Fair enough, as far as it goes. But the bigger number, the one that should really be on the same slide, is what it costs you if the reliability problem that project fixes ends up quietly pushing volume out the door to a competitor instead.

What halving your lead time actually buys you

The good news, if there’s good news in an article about the many quiet ways you can lose a client, is that lead time reduction is one of the better documented improvement projects out there. It isn’t some vague cultural initiative. It’s mechanical. You map the current process using value stream mapping, you find the waiting, the batching, the unnecessary movement, and you take it out.

The results, across a genuinely wide range of manufacturing case studies, cluster in a similar place. One coatings manufacturer cut inventory by half and trimmed lead time by 60% through a lean project. A case study on trailer production found lead time cut by roughly 47%, with work in process time dropping by just over half. Another manufacturer, working through TPM and lean tools over several years, took order lead time from 10 days down to just 4, while lifting on time delivery from 85% up to 98% in the process. None of these are outliers or best-case marketing figures. A 50% reduction in lead time is a genuinely reasonable, achievable target for a lot of manufacturing operations that haven’t already done this work.

But here’s the part that actually matters for this article. A shorter lead time isn’t valuable just because it looks good on a dashboard. It’s valuable because of what it lets you do commercially.

It means you can say yes to an urgent order that a competitor has to turn down, which is exactly the kind of moment that either wins or loses a big client’s long-term trust. It means you’re carrying less finished goods stock as a buffer against your own unreliability, freeing up working capital that’s currently sitting on a shelf compensating for a slow process instead of doing something useful. It means when something genuinely does go wrong upstream, a raw material shortage, an energy price shock, a supplier failure of your own, you’ve got more slack in the system to absorb it before it ever reaches the client at all. And that matters more than usual right now. Something like three in four European shippers reported some kind of supply chain disruption during 2024, and UK manufacturers are currently juggling rising input costs against softer domestic demand on top of that. In an environment like this, being the supplier who’s boringly, reliably on time isn’t a nice to have. It’s a genuine point of difference, and one that’s getting harder for competitors to fake.

Maybe the simplest way to put it is this. Every day you shave off your lead time is a day of buffer between something going wrong inside your operation and your client actually noticing. Halve the lead time and, roughly speaking, you’ve halved how often your internal problems become their external problem.

Turning this into something you can actually act on

None of this means you need a two-year transformation programme before you see any benefit. Start narrow.

Pick the product lines or order types that flow to your two or three biggest clients and map those specifically, rather than averaging performance across your whole catalogue. A shop floor that’s brilliant on average but unreliable for its highest value client isn’t actually performing well. It’s just hiding the problem in the numbers. Value stream mapping is the standard tool here, and it doesn’t need to be complicated. Walk the actual process, time the actual waiting, and you’ll usually find the biggest chunk of your lead time isn’t the machining or the assembly at all. It’s queueing, batching, and things sitting around waiting for the next step. That’s the low hanging fruit, and it’s typically where most of a 50% reduction ends up coming from.

Alongside the process work, build a visibility layer that lets you catch a slip before the client does. A surprising amount of the trust damage from a late delivery has nothing to do with the lateness itself. It’s about the client finding out from their own goods in receipt team rather than from you. Good, proactive communication is repeatedly named by customers as one of the biggest factors keeping them loyal to a supplier, and a phone call about a likely delay lands completely differently to a client discovering it on their own. It’s a small thing operationally and a disproportionately valuable thing relationally.

Finally, and this is the bit that often gets missed, put your lead time and delivery performance data next to your account risk register, not tucked away in a separate report nobody outside operations ever opens. If your biggest client’s on time in full rate has been sliding for two quarters running, that shouldn’t just be a fact sitting in a spreadsheet the plant manager glances at. It should trigger the same kind of conversation you’d have if that client’s payment terms started slipping, because commercially, it’s the same category of warning sign. Maybe even a more urgent one.

The takeaway

There’s a version of this article that just tells you lead time reduction is good for efficiency and leaves it there. That’s true as far as it goes. It also undersells what’s actually at stake.

Every late shipment is a small data point your biggest clients are quietly collecting about whether they can rely on you. Most of them won’t tell you they’re worried. They’ll just start hedging, spreading a bit of volume elsewhere, treating you as one option among a few rather than the obvious first call. By the time that shows up as a lost tender or a shrinking order, the actual decision was probably made months earlier, in a series of small moments that never got escalated to you as a problem at all.

The financial case for fixing this isn’t subtle. Retaining a client costs a fraction of winning a new one, the profit upside from even modest retention gains is significant, and manufacturing sales cycles are long enough that losing an account is a genuinely painful thing to recover from. Meanwhile, a 50% cut in lead time is a realistic, well proven target that also happens to be one of the most direct ways to reduce how often your operation lets a big client down in the first place.

So maybe the honest way to think about lead time reduction isn’t as an efficiency project with a nice side benefit for client relationships. Maybe it’s closer to insurance for your biggest accounts, one that happens to pay for itself in inventory and labour savings while it’s at it. Either way, it deserves a seat at the commercial table, not just the operations one.

Have a proper look at your delivery performance against your top five clients specifically. Not the average across the whole business, the actual numbers for the accounts you’d genuinely struggle to replace. That’s usually where the real story is hiding.

If reading this has you thinking about your own lead times, and honestly, a bit uneasy about what your top clients might quietly be doing about it, that’s a useful feeling, not a bad one. Our Lean Coaching Programme walks manufacturers through exactly this kind of work: finding where your time is really going, cutting the waste nobody’s noticed yet, and building the reliability that keeps your biggest accounts from ever needing to look elsewhere. Worth a conversation?

Cost of Quality Failures: A Practical Guide for UK Manufacturers

Posted on by Adam Payne

Picture the scene. You walk past the scrap bin on a Friday afternoon, more out of habit than curiosity, and you clock what’s sitting in it. Maybe you weigh it. Maybe you just eyeball it and do the maths in your head based on last month’s average cost per kilo. Either way you land on a number. Let’s say it comes to £5,000 for the month. Not brilliant, but not a crisis either. You mention it in the ops meeting, someone nods, and everyone moves on to the next item on the agenda.

Here’s the bit that catches most manufacturers out, and to be honest it caught me out too the first time someone walked me through it properly. That £5,000 isn’t your cost of quality failure. It’s not even close. It’s the bit you can see, weighed and priced at raw material cost, sitting in a skip by the loading bay. Everything that actually caused that scrap to exist in the first place, the machine time burned re running the job, the hours your best people spent sorting good parts from bad, the courier you paid extra to get a replacement batch to a customer by Thursday morning, none of that is in the bin. It’s scattered across half a dozen different cost codes, buried in overtime sheets, filed under “administrative time” on a job card, or in a lot of cases just never recorded anywhere at all.

Add it all up properly, and most plants find their real monthly figure sits three to five times higher than what they originally thought it was. Not because anyone’s hiding it on purpose. Just because nobody’s actually adding it up.

This matters more than it used to. Whether you’re running a job shop in the Midlands, a fabrication plant in the North West, or a small assembly operation anywhere else in the UK, margins are tighter than they’ve been for a while, and a hidden cost running at three or four times what you assumed is not a small thing to have sitting undiscovered in your numbers.

So that’s what this piece is for. We’re going to look at why the gap between the visible number and the real one exists, what’s actually hiding inside it, and then walk through a simple way to build a proper monthly figure for your own plant using numbers you probably already have sitting somewhere in your systems. By the end of this you should be able to sit down for twenty minutes with a spreadsheet and come out with a number that’s a lot closer to the truth than whatever’s written on the scrap sheet.

Why the scrap bin only tells you half the story

There’s a reason quality people keep reaching for the iceberg analogy. The bit above the water, the scrap, the obvious rework, the returned batch, is the bit everyone can see and everyone feels comfortable reporting. It’s tidy. You can weigh it, price it against your bill of materials, and put a clean number on a slide.

The trouble is the iceberg analogy actually undersells it a bit, because most icebergs sit roughly seven eighths underwater, and in plenty of the plants I’ve looked at over the years the hidden portion of quality cost runs even bigger than that relative to what makes it onto a report. Industry research puts the total cost of poor quality somewhere between five and thirty five per cent of sales revenue for manufacturers, with a lot of studies settling around fifteen to twenty per cent as a rough working average. Now compare that to scrap and rework on their own, which tend to sit somewhere under three per cent of revenue even at weaker performing sites. The gap between those two figures is where all the genuinely interesting stuff is hiding.

Why does it stay hidden for so long? Mostly it comes down to where the money actually gets spent, and how disconnected those places are from each other. Scrap sits neatly inside a manufacturing cost centre. Rework labour often gets coded as ordinary production time if nobody’s bothered to track it separately, because from the operator’s perspective they’re just doing their job. Expedited freight lands inside the logistics budget under something generic like “delivery costs,” with no note attached explaining it was a rush job caused by a batch that failed inspection three days earlier. The quality engineer’s Tuesday spent writing up a corrective action report doesn’t show up as a cost anywhere at all, it’s just treated as part of what a quality engineer does. None of it gets flagged as quality cost, because none of it is labelled that way anywhere in your finance system. They’re just costs, spread thin enough that nobody ever connects the dots between them.

I’ve sat in more than a few production meetings where this plays out almost exactly the same way. Someone flags that the scrap number’s up again this month, there’s a short discussion about the supplier, or the operator, or a machine that’s drifting out of tolerance, and then everyone moves on. What almost never happens is someone standing up and saying, right, but what did that actually cost us once you factor in the four hours we lost re running the job and the taxi fare we paid to get parts to the customer on time. That conversation just doesn’t happen, mostly because the information needed to have it properly isn’t sitting in one place for anyone to look at.

And to be fair, that’s not really anyone’s fault. Finance systems are built to track cost centres, not causes. It takes a deliberate effort to pull the threads back together into one figure, and most plants simply haven’t built that habit yet.

The six numbers hiding behind your scrap figure

Let’s break down what’s actually going on when a batch fails, because once you see it laid out properly it’s genuinely hard to unsee.

Material cost. This is the one you already know, and it’s the easy part. Raw material, purchased components, whatever went into the parts that ended up in the bin, priced at what you paid for it. It’s probably already sitting in your ERP system somewhere, tagged to a scrap transaction, assuming your system is set up reasonably well.
Machine time. Every hour a machine spends running a job that ends up scrapped, or re running a job because the first attempt failed, is an hour that machine wasn’t available for anything else. Price that time at your fully loaded machine rate, the figure that covers depreciation, power, maintenance and everything else, not just the labour standing next to it. If a job normally takes four hours and you end up running it twice, that’s four extra hours gone, and on a line that’s already busy that’s not a trivial number to lose.
Labour. Rework hours are the obvious one here, someone physically fixing or sorting parts, priced at a proper loaded rate that includes national insurance and other overheads, not just the basic wage. But don’t stop there. Think about the time spent writing the non conformance report, sitting in the root cause meeting, making the supplier call, chasing the corrective action afterwards. That’s all real, paid labour time, and it’s rarely coded anywhere as quality failure cost.
Re inspection. When something fails, you almost always end up inspecting more afterwards, either the reworked batch itself or the next few batches while everyone’s understandably nervous. That extra checking has a real cost, in hours and often in equipment time too if you’re tying up measurement kit that could be doing something else. It’s a cost that only exists because the process let you down once already and nobody quite trusts it yet.
Expedited freight. This one’s a personal favourite of mine because it’s so easy to miss and genuinely painful once you total it up properly. A batch fails, the customer still needs their parts on time, so you pay for next day courier instead of your usual pallet network, or you fly something in rather than shipping it by sea. That premium, the difference between what you’d normally have paid and what you actually paid, is a direct consequence of the quality failure. I’ve seen individual incidents where the expedited freight bill on its own was bigger than the material cost of the scrap that caused it in the first place.
Lost capacity. This is the big one, and it’s the category most plants leave out entirely. Every hour spent on rework or re running a failed job is an hour you didn’t spend making something you could actually sell. Value that lost time not at your machine rate, but at what that capacity would have earned you in contribution margin had it gone towards good saleable output instead. On a line that’s already running close to full capacity, this figure can dwarf everything else on the list, because you’re not just paying for the mistake, you’re also losing the profit you would otherwise have made in that same window of time.

A quick word of caution before you go filling in your own numbers. Machine time and lost capacity can overlap if you’re not careful, since they’re both really about the same lost hours, just viewed through two different lenses, one as a direct cost, one as an opportunity cost. Pick one lens for those specific hours and stick with it, or you’ll end up counting the same time twice and your final figure will look inflated rather than genuinely honest. Better to be conservative and defensible here than impressive and wrong.

Building your own number, step by step

Right, let’s actually do this. Grab a notebook, or better still, open a spreadsheet, because this is something worth keeping and repeating every month rather than doing once and filing away.

Step one. Total material scrapped this month, priced at cost. This should already exist somewhere as scrap transactions in your system. If it doesn’t for whatever reason, your finance team can usually pull it from stock write offs without too much trouble.

Step two. Machine hours lost to failed runs and re runs this month, multiplied by your fully loaded machine rate. If you don’t know that rate off the top of your head, ask finance. Most plants already have it calculated somewhere for costing purposes, even if nobody’s shown it to you directly before.

Step three. Labour hours spent on rework, re inspection, and quality admin, meaning non conformance reports, root cause work, and corrective actions, multiplied by your loaded labour rate. Be honest with yourself here. If your quality technician spent six hours on paperwork because of one bad batch, that’s genuinely six hours, even if it doesn’t feel like it at the time.

Step four. Extra freight cost this month, meaning the difference between what you’d normally pay to ship something and what you actually paid because it needed rushing. Your logistics team or your finance system should have this if you ask the right question, which is usually something like “what did we pay above standard rates this month, and why.”

Step five. Lost capacity hours, valued at contribution margin per hour rather than machine rate, remembering the double counting warning from the last section. If you’re not sure of your contribution margin per hour, it’s roughly your average selling price per unit minus your variable cost per unit, multiplied by units produced per hour on that particular line.

Add all five together and you’ve got your real monthly cost of quality failure.

Let’s run through it using the numbers from the start of this piece, just to make it properly concrete rather than abstract. Say your scrap bin comes to £5,000 for the month, material cost only, exactly like the example we opened with. Rework and re inspection between them come to ninety hours this month, and at a loaded labour rate of around £26 an hour that’s £2,340. Machine time lost to re running failed jobs comes to thirty five hours at a fully loaded machine rate of £38 an hour, adding another £1,330. You had three shipments that needed rushing this month to cover replacement batches, adding £650 above what you’d normally have paid for standard delivery. And your lost capacity, the hours that could have gone towards saleable output instead, comes to around £9,000, based on sixty hours of lost production time valued at roughly £150 an hour in contribution margin.

Add it up. £5,000 plus £2,340 plus £1,330 plus £650 plus £9,000 comes to £18,320 for the month.

That’s not £5,000. That’s a little over three and a half times higher, and honestly this is a fairly conservative example. Plenty of plants, especially ones with tighter margins per unit or more complex, longer running products, land at four or even five times their scrap figure once everything’s counted properly. If your own number comes out lower than that once you’ve done the exercise, it’s worth going back and double checking you’ve genuinely captured all five categories rather than quietly assuming your plant is somehow the exception to a pattern that shows up almost everywhere else.

What you do with the number once you’ve got it

Getting to a proper figure is only useful if it actually changes something afterwards. So what do you do with it once it’s sitting in front of you.

First, use it to build the business case you’ve probably struggled to make before now. Telling your finance director you want another inspection point, or a bit of preventive maintenance budget, or time for the team to do proper root cause work instead of constantly firefighting, lands very differently when you can say “our quality failures are costing us eighteen thousand pounds a month, and here’s exactly where it’s going” rather than “scrap’s felt a bit high lately, to be honest.” Numbers with a clear breakdown behind them get taken seriously in a way vague concerns just don’t.

Second, track it monthly rather than treating this as a one off exercise you do once and forget about. The real value isn’t in the single number, it’s in the trend underneath it. Is it going up or down. Which of the five categories is moving and which is staying flat. If your material scrap stays roughly the same but your expedited freight bill keeps climbing month on month, that tells you something quite specific about where your process control is actually breaking down, probably somewhere in scheduling or capacity planning rather than on the shop floor itself.

Third, and this feels particularly relevant if you’re running a plant anywhere in the UK right now, this kind of visibility matters more when margins are already under pressure. And they are under pressure. Manufacturers across the country have been dealing with rising energy costs, climbing employment costs, and now increases to business rates landing on top of everything else, adding close to a billion pounds a year in extra cost across the sector according to Make UK’s own analysis. A fair number of firms are reportedly sitting on less than twelve months of cash, with some genuinely worried about what happens if costs keep outpacing what they’re able to charge their customers. In that kind of environment, a hidden monthly cost running three to five times bigger than anyone realised isn’t just an interesting bit of analysis to file away. It’s real money that could be going towards keeping the lights on, investing in the tools that actually prevent the failures happening in the first place, or simply protecting your margin long enough to get through a genuinely difficult trading year.

Fourth, resist the urge to try and fix everything at once. Once you’ve broken your number down into its five parts, you’ll usually find one category is doing most of the damage on its own. Maybe it’s lost capacity because you’re running close to full and every failure costs you real sales you can’t easily recover. Maybe it’s expedited freight because your scheduling buffer’s grown too thin over time. Fix the biggest lever first, remeasure the following month, and let the number itself tell you honestly whether it worked.

The bin was never the real number

I think the honest takeaway here is a fairly simple one, even if getting to it properly takes a bit of graft. The scrap bin was never lying to you exactly. It’s just been telling you a small, tidy fraction of the truth and quietly letting you assume that was the whole picture all along.

Once you pull material cost, machine time, labour, re inspection, expedited freight and lost capacity into one place, you’ll almost certainly land on a number that’s uncomfortable in a genuinely useful way. Not uncomfortable because it’s wrong, but because it’s finally accurate, and accurate numbers tend to demand action in a way vague, half formed ones never quite manage to.

You don’t need a new system to start doing this properly. You need an hour with a spreadsheet, the willingness to ask your finance and logistics teams a few pointed questions they might not have been asked before, and the discipline to repeat the exercise every month rather than treating it as a one off audit you tick off and forget. Do that consistently for a few months and you’ll have something a lot of your competitors probably still don’t, a real, defensible number for what quality failure is genuinely costing you, and a clear map of exactly where to spend your next pound of improvement budget for the biggest possible return.

The scrap bin will still be sitting there on Friday afternoon, same as always. But now you’ll know it was only ever the tip of what you’re actually paying for.

Ready to close the gap

Working out the real number is one thing. Actually closing the gap between £5,000 and £18,000 is another, and that’s usually where plants get stuck. Not because the will isn’t there, but because nobody’s got the spare time to build a proper improvement system on top of an already busy shop floor.

That’s what TCMUK’s Lean Coaching Programme is built for. It’s not another consultant turning up with a clipboard, it’s hands on coaching from Adam Payne and the team, working alongside your people to turn scrap, rework and firefighting into a genuine culture of continuous improvement. One client using the programme cut waste by 93 per cent and lifted efficiency by 52 per cent. Clients typically see scrap and rework fall by around a quarter within the first year.

If you’d like a straightforward, no pressure conversation about what that could look like for your plant, you can find out more about the Lean Coaching Programme.

The Hidden Costs of a Disconnected Team: How to Calculate the ROI of Better Collaboration

Posted on by Adam Payne

There’s a particular kind of silence that falls over a production meeting when someone asks a simple question and nobody in the room can answer it.

You know the one. Somebody from sales wants to know why the order that was promised for Thursday is now going out the following Wednesday. And the room goes quiet. Not because people are being difficult, but because the answer lives in about four different heads, none of which have spoken to each other since last Tuesday. Maintenance knew the machine was struggling. The night shift supervisor mentioned it to somebody. Quality flagged a dimensional drift a fortnight ago and it went into an email that got buried. Planning never heard any of it.

Nobody did anything wrong, exactly. And that’s the problem.

Here’s the thing about a disconnected team. It never appears on your profit and loss statement. There’s no line item that reads “cost of people not talking to each other.” You’ll find energy costs, materials, labour, depreciation, insurance. You won’t find the £300,000 that quietly walked out of the building last year because your shift handovers are a scrap of paper and a shrug.

That invisibility is exactly why it survives. Anything you can’t measure, you can’t defend a budget against. So when you go to your board or your MD and ask for money to develop your supervisors, or to fix how your teams work together, you’re competing against a new CNC machine with a quoted payback of eighteen months and a supplier brochure full of confident numbers. You’ve got a feeling. They’ve got a spreadsheet.

To be honest, I think that’s the real reason so much of this gets kicked down the road. Not because manufacturing leaders don’t believe in it. Most of the ones I’ve met believe in it deeply. It’s because they’ve never been handed the arithmetic.

So let’s build the arithmetic. By the end of this you’ll have a number. Your number, from your plant, using your data, that you can put in front of a finance director and defend.

Disconnection doesn’t announce itself

Before you can cost it, you need to recognise it. And it rarely looks like conflict.

I spent a morning a while back at a precision engineering firm in the West Midlands. Roughly 140 people, decent order book, third generation family ownership, the sort of business that’s genuinely good at what it makes. Walking the floor, everything looked healthy. Clean, organised, people busy and reasonably cheerful.

Then I sat in on the eight o’clock meeting.

The production manager ran through the day. Maintenance sat at the far end of the table and said almost nothing. When I asked afterwards why that was, the maintenance lead gave me an answer I’ve thought about ever since. He said he’d stopped raising things in that meeting about two years ago, because whenever he did, it turned into a conversation about why he hadn’t fixed it yet. So now he just gets on with it, and tells production when it’s done.

That’s disconnection. Not shouting. Not sabotage. A capable, conscientious person quietly deciding that sharing information isn’t worth the aggravation.

Once you start looking for it, you see the pattern everywhere:

Information that only travels through one person, so when they’re on holiday the whole thing wobbles. The WhatsApp group that’s become the real production system, running parallel to whatever software you’ve paid for. Sales agreeing to lead times without asking operations, and operations assuming sales will always overpromise, so they pad every estimate as a defence. Quality being treated like the police rather than a resource. Two shifts running the same cell with genuinely different methods, and neither of them knowing the other exists.

And the classic. Somebody spots a problem early, mentions it once, gets no response, and never mentions it again. That one costs more than all the others combined, and you’ll never know it happened.

Gallup has been running the largest ongoing study of workplace performance for decades now, covering well over 180,000 business units. One of their most consistent findings is that roughly 70% of the variance in team engagement is explained by the quality of the manager. Not pay. Not perks. The person your people report to. Which means disconnection is usually not a workforce problem at all. It’s a capability gap sitting in your supervisor layer, and supervisors in manufacturing are very often brilliant technicians who got promoted and never received a day of training in how to lead.

That’s not a criticism of them. It’s a description of how our industry has recruited for about fifty years.

The four places the money actually leaks

Right. Numbers.

I’d suggest four buckets, because four is enough to be credible and few enough that you’ll actually complete the exercise. Missed deadlines. Preventable mistakes. Morale and absence. Turnover and lost knowledge.

Missed deadlines and disruption. Not all downtime is a coordination failure. A bearing fails, a bearing fails. But a surprising slice of it is. The changeover that took ninety minutes instead of thirty because the tooling wasn’t staged. The line that ran the wrong drawing revision for half a shift. The stoppage that maintenance could have prevented if anybody had told them about the noise.

Research from Censuswide for Fluke in 2025 found that around 68% of UK manufacturers had experienced unplanned downtime in the previous twelve months, with nearly half reporting six to ten incidents a week. Separate work from IDS-INData suggests a typical UK company loses something in the region of 49 hours of production a year to it. I’d treat the eye watering per hour figures that circulate with these studies carefully, since they’re drawn largely from very large plants and commissioned by suppliers who sell the fix. But the frequency data holds up. Six to ten stoppages a week is a lot of small fires, and a decent proportion of small fires are lit by somebody not knowing something somebody else knew.

Preventable mistakes. The American Society for Quality has long put the cost of poor quality at somewhere between 15% and 20% of sales revenue for many manufacturers. Scrap and rework on their own run from around 0.6% of revenue for strong performers to about 2.2% for weaker ones. And the honest analyses tend to land at three to five times the visible scrap figure once you count the machine time consumed, the capacity lost, the engineering hours spent investigating and the expedited freight to cover the gap.

Look at the root cause lists for scrap and rework and you’ll find the same culprits every time. Human error. Unclear or outdated work instructions. Inconsistent processes between shifts. None of those are equipment problems. All of them are communication problems wearing an engineering costume.

Morale and absence. The CIPD’s 2025 Health and Wellbeing at Work report found UK employees taking an average of 9.4 sick days a year. That’s up from 7.8 in 2023 and 5.8 before the pandemic, and it’s the highest they’ve recorded in over fifteen years. Mental ill health was the leading cause of both short- and long-term absence, and 64% of organisations reported stress related absence with workload as the top factor.

Here’s the part that ought to sting. Only 29% of organisations train their line managers to support staff with mental ill health. So the person with the single biggest influence over whether someone comes to work on Monday has usually been given no help at all in doing it.

Gallup’s numbers make the same point from a different direction. Compare business units in the top quartile for engagement against the bottom quartile and you get 81% lower absenteeism, 64% fewer safety incidents, 41% fewer quality defects, 18% higher productivity and 23% higher profitability. Those are median differences across a vast sample. In a sector where safety incidents and defects carry real financial weight, that’s not a wellbeing statistic. That’s an operations statistic.

Turnover and lost knowledge. Make UK’s labour turnover research showed sector turnover falling to 10.85% in 2024, down from 20.75% in 2022, with voluntary turnover at just over 6% and retirement now the most common reason for leaving. On the face of it, good news.

I’d be cautious about celebrating, though. A cooling labour market keeps people in place whether they’re happy or not. And an ageing workforce means the departures you’re seeing are the ones carrying thirty years of undocumented knowledge out of the door with them. Make UK’s Skills Commission identified 55,000 long term unfilled vacancies in the sector, costing an estimated £6 billion in lost output a year, with 42% of manufacturing vacancies now classed as skills shortage vacancies, up from 29% in 2017. Around 36% of the workforce is over 50.

Replacement isn’t cheap either. CIPD research puts it at 75% to 200% of annual salary depending on the role. Oxford Economics landed on an average of £30,614 per employee. And an unfilled CNC machinist post on a three-shift operation has been estimated at £8,000 to £15,000 a month in lost output and overtime.

A formula you can do on the back of a delivery note

Here’s the calculation. It’s deliberately crude, because a crude number you actually finish beats an elegant model you abandon.

Annual cost of disconnection = A + B + C + D

A. Missed deadlines and disruption. Take the hours of stoppage or delay per month that you’d honestly attribute to coordination failures rather than genuine equipment failure. Multiply by twelve. Multiply that by your contribution per productive hour. Then add expedited freight, recovery overtime and any customer credits from the last year.

B. Preventable mistakes. Take your annual scrap and rework value. Estimate the share caused by unclear instructions, handover gaps or shift variation rather than material or machine faults. A third is a common, conservative starting point.

C. Morale and absence. Take your absence days per employee, subtract a realistic benchmark, multiply the excess by headcount, then by the fully loaded daily cost of covering that absence.

D. Turnover and lost knowledge. Take last year’s leavers, strip out retirements and genuine life events, and multiply what’s left by a conservative replacement cost.

Let me run it for that West Midlands firm. Roughly 140 people, £18 million turnover, precision engineering.

A. They reckoned about six hours a month of stoppage or delay came down to coordination. Wrong tooling staged, wrong revision, maintenance not informed. That’s 72 hours a year. Their contribution per productive hour worked out at roughly £1,285. So £92,520. Add £25,000 for expedited freight and recovery overtime across the year. Call it £117,000.

B. Scrap and rework at 1.5% of £18 million is £270,000. Attribute a third to communication and handover issues. £90,000.

C. Absence running at 10 days against a realistic target of 6. Four excess days across 140 people is 560 days. At £180 a day fully loaded, including agency premium and lost output. £100,800.

D. Around 15 leavers. Seven were retirements or genuine moves. Eight were avoidable. At £15,000 each, which is half the Oxford Economics average and deliberately cautious. £120,000.

Total: £427,800 a year. About 2.4% of turnover.

Now the return. You will not fix all of that, and you shouldn’t claim you will. Assume you recover 20%, which is modest against Gallup’s quartile differences. That’s £85,560 a year.

Say the investment is £40,000. Supervisor development for your team leaders, a proper structured handover process, and some facilitated cross functional problem solving.

ROI = (£85,560 minus £40,000) divided by £40,000 = 114%. Payback in roughly five and a half months.

And here’s the bit I’d hold in reserve. Halve every single one of those assumptions. Recover only 10%. The thing still pays for itself inside the year.

Taking the number upstairs

You’ll get three objections. I’d have them ready.

“Those numbers are made up.” They’re estimates, and you should say so first, before anyone else does. Then point out that the capital expenditure case for the machine you approved last year was also built on estimated utilisation and estimated yield improvement. Everyone was comfortable with that. The difference here isn’t rigour, it’s familiarity. Offer to show the calculation with the assumptions halved. If it still works, and it will, the argument is basically over.

“We can’t attribute that to communication.” Fair challenge, and the honest answer is you can’t attribute all of it. So don’t try. Pick the incidents where the root cause analysis already says what you need it to say. Most manufacturers have months of nonconformance reports with root causes like “operator not informed of revision change” or “handover not completed.” That’s your evidence, and you didn’t have to generate it. It’s been sitting in your quality system all along.

“This is a soft skills thing.” This is where the Gallup data earns its keep, because those are hard operational outcomes. Fewer defects. Fewer safety incidents. Lower absence. Higher productivity. Nobody in a manufacturing business thinks safety incidents are soft.

One more piece of advice, and it’s the one I’d actually lead with. Don’t ask for the whole thing. Ask for one line, one shift pattern, one supervisor group, for one quarter, with agreed measures taken before and after. A pilot is much easier to say yes to than a programme, and a pilot that works builds a business case nobody can argue with, because it’s built from your own plant rather than somebody else’s research.

What actually shifts the number

Briefly, because this could be its own article.

Start with your supervisors. It’s the highest leverage thing available to you, and it’s usually the most neglected. The people running your shifts were promoted because they were excellent at the job and then handed responsibility for fourteen humans with no preparation. Give them the basics. How to run a decent conversation. How to give feedback that doesn’t land as an attack. How to escalate a concern without it becoming a row.

Fix your handovers properly. Not a form. A short, structured conversation with a consistent shape, at a consistent time, with a consistent set of things covered. It sounds almost too simple to be worth the effort. It’s usually the single cheapest improvement available in a manufacturing business.

Put the functions that blame each other in the same room on a regular basis, working on something concrete. Maintenance and production. Quality and operations. Not a workshop with flip charts. An actual recurring problem with an actual owner and an actual deadline.

And measure it. Absence, scrap by root cause, delivery performance, near misses, exit reasons. Take a baseline before you start, because the most common way these initiatives die is that they work and nobody can prove it.

The cost is already being paid

I’d finish on this.

The money in your four buckets isn’t hypothetical, and it isn’t a future risk you might one day face. You paid it last year. You’re paying it this month. It’s leaving the business right now in six-hour chunks of coordination failure, in scrap that traces back to a conversation that didn’t happen, in the four extra sick days that were really about a supervisor who never learned how to have a difficult conversation, and in the retiring toolmaker whose knowledge nobody wrote down.

The only genuine question is whether you’re counting it.

Because once you count it, the conversation changes completely. You stop asking permission to invest in your people and start explaining why the business is choosing to absorb a six-figure annual loss it could reduce for a fraction of the cost. That’s not a training request. That’s an operational improvement proposal, and it belongs in the same queue as the capital expenditure it’s currently losing out to.

Do the sum. Use your own numbers, be deliberately conservative, write down every assumption so nobody can accuse you of hiding one. It’ll take you an afternoon and a couple of conversations with your finance and quality people.

I’d be surprised if the number comes back small. It very rarely does.

Ready to put a number against the fix?

Here’s the slightly awkward bit about the sum you’ve just done. The moment you’ve got the figure, doing nothing becomes a decision rather than an oversight.

So if the number came back bigger than you were expecting, these are the two levers I’d pull first, and they map almost exactly onto the two problems in this article.

Helping Managers to Succeed and Lead is for that supervisor layer. The people who got promoted because they were brilliant at the job and then had fourteen humans handed to them with no preparation. It pairs each manager with a dedicated mentor, starts with the Igniting The Leader In You training, and then follows a 90-day milestone structure with reviews at 10, 30, 60 and 90 days. That last part matters more than it sounds. Most training fails not because the content was wrong but because nobody came back three weeks later to ask how it was going.

High Performing Teams in the Workplace is for the other half. The maintenance lead who stopped speaking up. The two shifts running the same cell differently. It’s a full day workshop, on site at your facility, for up to twelve people, built around five pillars including a working rhythm for solving problems and the trust to challenge each other without it turning into a row. It’s £1,400 per group, excluding VAT and travel, which is under £120 a head for a team of twelve.

Put that against the number you calculated earlier. I’d guess the arithmetic makes itself.

If you’d rather just talk it through first, that’s genuinely fine. Call 0330 311 2820 or start with a fifteen-minute conversation about where your teams are now and where you need them to be. No pitch. Just a look at your figures and an honest view on what’s worth fixing first.

The Five Step Meeting Cadence That Stops Your Team Going in Circles

Posted on by Adam Payne

You know the meeting. It happens every Monday at nine, or maybe it’s Friday afternoon when everyone’s just watching the clock until they can get to the car park. Someone opens with “right, where are we with the delivery issue on line two” and forty minutes later you’re still talking about the same delivery issue. Same names come up. Same excuses get an airing. Someone says they’ll “look into it” and everyone nods like that means something. Then next week, you open with almost the exact same sentence.

If that sounds familiar, you’re not alone. And to be honest, it’s not really your team’s fault. Most weekly meetings in manufacturing weren’t built with any real structure to begin with. They grew out of habit. Someone, years ago, decided Monday morning was a sensible time to get everyone in a room, and the agenda has more or less stayed the same ever since, drifting between updates, gripes and the odd bit of finger pointing.

Here’s the thing though. You already know a method that would sort this out. You probably use it on the shop floor most days without giving it a second thought. Plan, Do, Check, Act. PDCA is stitched into how most UK manufacturers run their quality checks, their changeovers, their continuous improvement work. Nobody ever thought to apply that same discipline to the one meeting that’s supposed to hold the whole week together.

This post walks you through a five step meeting cadence built on that PDCA rhythm. It isn’t theory dressed up as advice. It’s a structure you can lift and use this week, with a sample agenda, the questions worth asking at each stage, and some fairly blunt thoughts on getting actions to actually happen, rather than just getting written down and quietly forgotten.

Stick with me on this one. It sounds almost too obvious to need writing down, and maybe that’s exactly why so few teams actually do it properly.

Why your weekly meeting keeps going nowhere

Worth diagnosing this properly first, because if you jump straight to a new agenda template without understanding why meetings drift in the first place, you’ll be back here in six months wondering why nothing’s changed.

Most circular meetings share a few habits, and I’d guess at least two of these sound familiar.

There’s no shared starting point. Everyone walks in with their own version of how the week went. Production thinks it went fine. Quality has a different story. Nobody’s looked at the same numbers before the meeting starts, so the first fifteen minutes gets eaten up just agreeing on what actually happened, before anyone’s even touched what to do about it.

Then there’s the tendency to ask “who” instead of “why”. A machine goes down twice in a fortnight and the conversation turns into who was on shift rather than what actually failed and why it keeps failing. That’s a completely natural instinct, by the way. Nobody enjoys sitting with an uncomfortable root cause. Blame is quicker and it feels like progress even when it changes nothing at all.

Actions get assigned to “the team” rather than a person. You’ve heard it. “We need to look at that.” Who’s we? By the time next week rolls around, everyone quietly assumed someone else picked it up.

And maybe the biggest one. Nobody actually checks last week’s actions before diving into this week’s problems. So the list just grows. It never gets reviewed, never gets properly closed off, and the same issues resurface because the loop never actually closes. That’s the circle, really. It isn’t that your team lacks ideas or effort. It’s that the meeting has no mechanism for finishing what it starts.

There’s a quieter version of this too, one that doesn’t get talked about much. Meetings that run long because they’ve become the only place certain people feel heard. Someone on the floor has been raising the same tooling problem for months and this is their one chance a week to say it out loud, so naturally they take it, even if it isn’t really on the agenda. That’s not a discipline problem exactly, it’s more a sign that other channels for raising issues aren’t working, and the weekly meeting has ended up carrying weight it was never designed for. Worth keeping in mind, because tightening the meeting won’t fix that on its own. You may need a separate, quicker way for people to flag things day to day so the weekly session doesn’t have to absorb everything.

Add in the pressure most UK manufacturers are under right now, energy costs that remain among the highest of any developed economy, wage costs climbing faster than most would like, margins getting squeezed from every direction, and you can see why a meeting that eats an hour and produces nothing concrete is such an expensive habit. Time on the shop floor and in the office is tight. A meeting cadence that actually works isn’t a nice to have anymore. It’s one of the cheaper productivity levers you have, and it costs nothing except discipline.

The five step cadence that actually closes the loop

PDCA isn’t a new idea, and you don’t need me explaining it to you like you’ve never seen a fishbone diagram. But most teams only apply it to the physical process, the actual making of things, and never think to turn it inward on how they run meetings. That’s a shame, I think, because the same logic that stops a defect recurring on the line works just as well at stopping the same conversation recurring in the meeting room.

Here’s how it breaks down into five practical steps, each one mapping back to that plan, do, check, act rhythm.

Step one: start with the scoreboard, not the chat

Before anyone speaks, put the numbers up. Whatever your version of a scoreboard is, safety incidents, quality rejects, delivery performance, output against target, get it on the wall or the screen before the meeting even opens. This is the check part of the cycle, and it needs to happen first, not as an afterthought halfway through when someone remembers to mention it.

The point here isn’t to read the numbers aloud like a weather report. It’s to give everyone the same starting picture so the conversation is about what the data means, not what the data even is. Ask something simple. What moved since last week, and what didn’t?

Step two: ask why, not who

Once you know what happened, dig into the misses. Not every miss deserves deep analysis, to be fair, some things really are just a one off. But the recurring ones, the second and third time something’s gone wrong, deserve five minutes of proper root cause thinking rather than a shrug.

Try asking why something happened three times before you accept the first answer. The first answer is nearly always a symptom. “The machine jammed” isn’t a root cause. Why did it jam? What changed? Has it happened before? This is where you separate a genuine one off from a pattern that’s quietly costing you every single week.

Take something as ordinary as a late delivery. First answer is usually “the supplier was late.” Fair enough, but why? Maybe the order went in later than it should have. Why was that? Maybe nobody flagged the stock level until it was already tight. Why not? Maybe the reorder point on that part hasn’t been reviewed since demand picked up. Suddenly you’re not looking at a supplier problem anymore, you’re looking at a stock threshold that needs updating, and that’s an action you can actually fix this week rather than a supplier you can’t control.

Step three: pick one or two priorities, not ten

This is the plan part, and it’s where a lot of meetings quietly fall apart. There’s a temptation, especially when the scoreboard’s had a rough week, to try to fix everything at once. Don’t. Pick the one or two issues that matter most this week and commit to them properly. Everything else either waits its turn or gets handled outside the meeting entirely.

I’ve sat in on meetings where the team left with eleven actions and, unsurprisingly, completed about two of them. Compare that with a team that commits to two focused actions and actually finishes both. Which week made more real progress? It isn’t close, if I’m honest.

Step four: assign actions like you mean it

This is where the do part starts to take shape, even though the actual doing happens after the meeting ends. An action needs three things to survive the week. A single named owner, not a department or a team. A clear definition of what done looks like. And an actual date, not “soon” or “when I get a chance.”

Write it down somewhere everyone can see it, whether that’s a physical board by the meeting room or a shared spreadsheet everyone actually opens. If it only lives in someone’s notebook, it doesn’t really exist.

Step five: close the loop before you close the meeting

Before anyone leaves the room, read the actions back out loud. Every single one, owner and date included. It sounds almost too simple to matter, but this thirty second habit catches more misunderstandings than you’d expect. Someone will occasionally say “wait, I thought Dave was doing that one” right there in the room, which is a far better place to catch that mistake than a week later when nothing’s happened.

Then confirm the next meeting time. That’s what turns this into a cadence rather than a one off event. Next week’s check phase depends entirely on this week’s plan being clear enough to actually check against.

A sample agenda you can steal for Monday morning

You don’t need anything fancy for this. A thirty to forty minute slot, the same time and place every week, and a bit of discipline about actually sticking to it. Here’s a version you could run more or less as is.

Zero to five minutes: scoreboard review. Numbers go up before anyone talks. A quick read on what moved.
Five to fifteen minutes: last week’s actions. Go through each one. Done, not done, or in progress. For anything not done, ask why, briefly, and decide whether it carries forward or gets dropped for a good reason.
Fifteen to twenty five minutes: root cause the recurring issues. Pick the pattern that’s cost you the most this week and spend real time on why it keeps happening.
Twenty five to thirty five minutes: agree this week’s one or two priorities and assign them properly, owner, definition of done, date.
Thirty five to forty minutes: read the actions back, confirm everyone’s clear, and lock in next week’s meeting.

Notice what’s missing from that list. There’s no slot for general updates or a round the table where everyone shares what they’ve been up to lately. That’s on purpose. If people need to share updates that aren’t tied to an action or a metric, that’s what a quick message or a shorter, separate forum is for. This meeting has one job, which is closing the loop on what happened and opening a clear plan for what happens next.

Adjust the timings to suit your own team, obviously. A small tool room with four people might get through the whole thing in twenty minutes. A larger site with department heads from quality, production and logistics might genuinely need the full forty. What matters far more than the exact minutes is that every step happens, in order, every single week, without anyone skipping straight to problem solving before the scoreboard’s even gone up.

Getting actions to actually stick

Even with a decent cadence, actions still slip through the cracks if you’re not careful about how you write them. A few things worth getting right.

Write the action as an outcome, not a task. “Look into the packing line delay” is vague enough that almost anything counts as having done it. “Identify why pallets are queuing at the packing line and report back with one fix” gives you something you can actually check against next week.

One owner only. This one trips up more teams than you’d think, mostly because it feels a bit awkward to put someone on the spot in front of the group. But a shared action is nobody’s action. If a task genuinely needs two people, name a lead anyway. Someone has to be accountable for chasing it, even if others are helping along the way.

Keep actions small enough to finish in a week. If something’s clearly bigger than that, break it down. “Reduce scrap rate on line three” isn’t a week’s action, it’s a project. “Trial the revised setting on line three for two days and report the scrap rate” is.

Resist the urge to let actions roll over silently. If something didn’t get done, that’s information, not a failure to sweep under the rug. Maybe the priority genuinely shifted. Maybe the owner got pulled onto something urgent. Either way, say so out loud rather than letting it quietly vanish off the list. A meeting where actions can disappear without anyone noticing teaches everyone that deadlines are optional, and that lesson spreads fast, far faster than you’d like.

One more thing, and this comes from watching a fair few of these meetings over the years. The first few weeks will feel a bit stilted. People aren’t used to being asked “why” three times in a row, and they’re definitely not used to having their name next to a date on a board where everyone can see it. Stick with it anyway. I remember a small fabrication shop going from a Monday meeting that regularly ran past an hour with nothing much to show for it, to a twenty five minute session that actually cleared its action list most weeks. It took about six weeks of sticking to the format before people stopped treating it as a novelty and just started treating it as how things are done there.

Bringing it all together

None of this is complicated, and that’s rather the point. You don’t need new software, a consultant, or a training course to run a tighter weekly meeting. You need a scoreboard everyone looks at before they talk, a habit of asking why rather than who, a short list of priorities instead of a long wish list, actions with a name and a date attached to them, and thirty seconds at the end to read it all back.

Given what UK manufacturing is up against at the moment, tight margins, energy costs that show no sign of easing, a skills gap that means you genuinely can’t just throw more people at a problem, the time you waste in unproductive meetings is time you can’t really afford to lose. A tighter cadence is one of the few improvements that costs you nothing but the discipline to run it properly, and it tends to pay for itself within a month.

Give it five or six weeks before you judge it. The first meeting or two might feel a little awkward, and that’s fine, that’s normal, honestly. But once the habit sets in, you’ll notice the same conversation stops coming back week after week. Problems actually get closed instead of just discussed. And that Monday morning meeting stops being something people quietly dread and starts being the moment your week actually gets sorted out.

Start small if that feels safer. Pick just one team, one line, one meeting, and run the five steps properly for a month before you roll it out anywhere else. You’ll learn far more from getting it right in one room than from launching it everywhere at once and watching it fizzle out in three of the four. And if it does wobble in week two, which it might, that’s not proof it doesn’t work. That’s just the check phase doing exactly what it’s meant to do.

Want help making it stick

Reading about a better meeting cadence is one thing. Actually running it with a team that’s fallen into old habits, under real deadlines, with a hundred other things pulling at their attention, is another thing entirely. That’s exactly what our High Performing Teams Workshop was built for.

We work directly with your leadership team to build a cadence like the one above, tailored to your own scoreboard, your own priorities and your own people, so it survives well past that first slightly awkward week. You’ll leave with a cadence that’s already running on your shop floor, not just a good idea you meant to try someday.

If you’re ready to stop going in circles and start closing the loop for good, get in touch to find out more about the workshop and book your place.

The Accountability Framework: How to Empower Your Team to Own Their Results (Without Micromanaging)

Posted on by Adam Payne

Picture a Tuesday afternoon on the shop floor. A shift supervisor is walking the line, stopping at every station, checking every reading twice, signing off on jobs that honestly did not need signing off at all. The operators know the drill by now. They wait. They do not fix small problems themselves because that is not really their job, is it. It is his.

If that scene feels familiar, you are not alone. Most manufacturing leaders did not deliberately set out to micromanage their teams, it crept in gradually, one safety scare or one scrapped batch at a time, until checking everything started to feel like the only responsible option available to them. The trouble is that constant checking quietly erodes the very thing you need most, which is people who think for themselves under pressure. In a sector already stretched thin by skills shortages and an ageing workforce, that erosion is a cost you genuinely cannot afford right now.

This post is about building a different kind of control. Not looser standards. Not stepping back and hoping for the best. A framework built on two things that sound almost too simple: clear expectations and honest after-action reviews, done without blame. Get those right and something interesting happens. Your team starts owning the result, not just the task in front of them. You will still walk the floor. You just will not need to sign off on everything you see there.

Why manufacturers reach for control first, and what it actually costs you

Let me be fair to the instinct, because it is not an unreasonable one. Manufacturing runs on precision, and a missed torque spec, a contaminated batch, or a guard left off a machine can carry consequences that are genuinely serious rather than merely inconvenient. When the cost of a single error is that high, checking everything starts to feel like due diligence rather than distrust, and I understand why supervisors default to it. I did the same thing myself, earlier in my career, well before I properly understood what that habit was quietly costing me.

Here is the thing nobody quite says out loud, though. UK manufacturing is genuinely short on hands at the moment, with tens of thousands of unfilled vacancies across the sector at any given time, and roughly a fifth of the current workforce aged 55 or over and heading towards retirement within the next decade. Add rising costs into that mix, with a substantial share of manufacturers reporting increases of up to twenty percent over the past year, and you begin to understand why margins for error feel considerably thinner than they used to. When you are already short of experienced people, and every mistake now costs more than it did two years ago, the temptation to hover over the people you do have becomes stronger still. You cannot afford a mistake, so you check, and then you check again, which is a fairly rational response to a genuinely difficult set of conditions. It simply does not achieve what it feels like it should achieve.

The problem is that constant checking does not actually protect you from mistakes long term. It just moves the risk somewhere else. People stop flagging small issues because they assume someone above them will catch it anyway. Decisions queue up waiting for a signature that adds nothing except a delay. New starters, already hard to find and expensive to train, learn quickly that initiative gets corrected rather than praised, so they quietly stop offering it. Then they leave, and you are back to square one, recruiting into a market where good candidates already have other options and know it. It is probably no coincidence that recent industry research found fewer than half of manufacturers now describe themselves as genuinely agile, the lowest figure in five years. Rigid, closely supervised teams do not adapt quickly. They wait for permission.

I remember spending a morning on the floor of a components plant in the West Midlands a few years back, watching a line leader physically walk over and approve a changeover that the operator had done a hundred times before without a hitch. Competent bloke, clearly capable, just waiting for a nod that added nothing except a few minutes of dead time and a quiet message that his judgement was not quite trusted yet. Multiply that across a shift, a week, a year, and you start to see where the fatigue comes from. Not from the work itself. From being managed like you cannot be relied on.

None of this means loosening your standards. It means moving the control from your physical presence at someone’s shoulder to something more reliable: clear expectations up front, and a proper look back afterwards. That is the shift the rest of this post is about.

Start with expectations so clear nobody has to guess

Most accountability problems do not actually start at the point of failure. They start much earlier, at the point where somebody was told to keep on top of quality or make sure output stays up and left to work out what that actually means in practice.

Vague instructions are the enemy here, I think, more consistently than laziness or carelessness ever are. If a target is not observable, meaning it is not something you could point at and confirm definitively happened or did not happen, then you have not actually set an expectation. You have set a hope instead, and hopes are notoriously difficult to hold anyone accountable to fairly.

So get specific. Instead of keep quality high, try something like scrap rate stays under two percent per shift, and any reject gets logged with a reason code before the next changeover. Instead of watch the schedule, try every delay over fifteen minutes gets flagged to the team leader within the hour, not at the end of the shift when it is too late to do anything useful about it. These are not complicated asks. They are just precise enough that everyone knows what good looks like and, just as importantly, what falls short of it.

It also helps to be explicit about where the boundaries of someone’s own decision making actually sit. What can an operator decide alone, without asking anyone first. What needs a quick check with the team leader. What genuinely has to go up the chain before anything moves. You do not need a fancy framework for this, though plenty of businesses use something like a simple breakdown of who is responsible for a task, who needs to be consulted, and who just needs to be kept informed. What matters is writing it down somewhere everyone can see it, not keeping it in your head as an unspoken rule that people only discover after they have already broken it.

This matters even more in manufacturing because of shift patterns and handovers. A message that lives only in one supervisor’s head is not much use to the night shift, or to the agency worker filling in on a Friday who has never worked your line before. I have seen sites transform their handover quality just by moving from a quick verbal chat at the door to a short-written log with three or four fixed questions. What ran well. What did not. What needs watching next shift. It takes two minutes to fill in and it means expectations travel with the work itself, not just with whoever happened to be standing there when something was decided.

One more thing worth saying honestly. Clear expectations are not a document you write once and forget about. Targets shift, lines change, new kit gets installed, people move roles. Revisit them properly every few months, out loud, with the team present, not just as a memo nobody actually reads.

Swap the blame game for after action reviews

This is probably the part of the framework that feels most uncomfortable at first, and also the part that does the most work once it beds in.

An after-action review is a short, structured conversation that takes place immediately after a job, a shift, or an incident, organised around four honest questions. What was supposed to happen. What actually happened. Why did a gap emerge between the two. What will we do differently next time as a result. It is a method that originated in military training and was subsequently adopted extensively within lean manufacturing, Toyota included, because it converts everyday experience into genuine learning instead of allowing it to simply evaporate at the end of a shift.

Compare that with how most root cause meetings actually go in practice. Someone made an error, so everyone gathers in a small room, and even with the best intentions in the world, the conversation tends to circle around who did it rather than what allowed it to happen in the first place. People get defensive. Honest explanations start turning into excuses. And the next time something goes slightly wrong, the person involved is that little bit more likely to quietly fix it themselves and say nothing, rather than risk sitting through another one of those meetings.

That is genuinely dangerous in a manufacturing environment, maybe more than in most workplaces. Near misses, small quality slips, odd noises from a machine that probably mean nothing, these are exactly the things you want reported early, while they are still cheap and safe to deal with. A culture that punishes honesty does not stop mistakes from happening. It just stops you hearing about them until they get too big to hide.

The fix is not removing accountability. It is separating accountability from blame, which are not actually the same thing even though we tend to treat them like they are. Accountability means owning what happened and what you will do about it next. Blame is about assigning fault to a person and leaving it there. You can have deep accountability with almost no blame at all, and honestly, that combination tends to produce far better results than the blame heavy version ever does, because people keep telling you the truth.

Practically, this can be as simple as a ten-minute huddle at the end of a shift or a job run. Three or four questions, everyone allowed to speak, no names attached to problems, just facts and fixes. I worked alongside a food production site where this felt awkward for about the first fortnight. People were clearly waiting for someone to get told off. Nobody did. By week three, operators were flagging their own near misses before a supervisor even noticed there was anything to flag, because they had learned the review was about the process, not about catching them out personally. That shift, from hiding problems to surfacing them voluntarily, is honestly the clearest sign the framework is starting to work.

Keep these reviews short, keep them regular, and resist the urge to turn them into a lecture with extra steps. The moment they start feeling like a telling off in disguise, people stop being honest in them, and you lose the entire point of running them at all.

Give people room to move inside clear guardrails

Once expectations are clear and the review habit is properly bedded in, you have actually earned the right to loosen your grip a bit. This is the step a lot of manufacturers skip, because it feels like the riskiest one.

Autonomy on a factory floor does not mean anything goes. It means defining the guardrails properly so people can move freely inside them. Your SOPs already do some of this work, they fix the how for safety critical steps, and that is right, some things genuinely should not be left to individual judgement on any given day. But most SOPs stop there. They rarely say when to escalate, when a small deviation is fine to handle locally, or what decisions comfortably sit within someone’s own role without asking. Fill in that gap and you give people a proper map, not just a fence around them.

Start small if trust has been thin on the ground until now. Let a team leader decide on minor changeover sequencing without asking first. Let an operator adjust a process parameter within an agreed range rather than calling someone over every single time a reading drifts slightly off centre. Watch what happens through your after-action reviews rather than through standing over their shoulder all shift. If it goes well, which it usually does, widen the scope a little further next time round. Trust built this way is earned in both directions, and it tends to actually stick.

There is a psychological safety piece underneath all of this that is easy to skip past but really is not optional. People will only use the freedom you give them if they genuinely believe raising a problem early will not backfire on them personally. This links straight back to the review culture from the last section. If someone brings a near miss to an after-action review and gets thanked for the honesty, that behaviour repeats itself. If they get quietly punished for it, even subtly, even just a slight change in tone, that behaviour stops overnight, and you are right back to people hiding things until they cannot be hidden any longer.

I think the leaders who get this right tend to share one habit in particular. When something goes wrong and gets flagged early, their first question is never who did this. It is always something closer to what did we miss, or what would have made this easier to catch sooner. That single change in the first question you ask, more than any policy document you could write, sets the tone for whether your team owns problems openly or buries them quietly instead.

None of this happens overnight, to be honest. You are not flipping a switch from controlled to autonomous in one meeting. You are widening the guardrails gradually, checking the reviews stay honest, and learning to trust the process you have built rather than your own instinct to check everything yourself, one small step at a time.

Where to start this week

Here is the shape of the whole thing, stripped right back. Set expectations specific enough that nobody on your team has to guess what good looks like. Review the work honestly and regularly, separating accountability from blame so people keep telling you the truth even when it is inconvenient. Then, and only then, widen the space people have to make their own calls, watching through those reviews rather than through constant supervision.

None of this is about loosening your standards, whatever it might look like from the outside. If anything, it raises them, because a team that genuinely owns its results tends to catch more, fix more, and hide less than one that is simply waiting to be told what to do next. It does feel slower to build than just doing it yourself or hovering until a job is done right in front of you. I will not pretend otherwise, because it is. But the payoff, fewer surprises, fewer good people walking out the door towards a competitor twenty miles up the road, less of your week spent firefighting things that should never have reached your desk, is worth the slower start.

If you want to take one thing away from this and actually try it this week, make it the after-action review. Pick one shift, one job, one changeover. Run the four questions honestly, no names, no blame, just facts and fixes on the table. See what your team tells you once they believe it is genuinely safe to be honest with you. It usually says more about where your accountability gaps really are than any formal audit ever will.

This is exactly the kind of practical, day to day skill we build out properly in the High Performing Teams workshop, if you want a fuller toolkit rather than just a starting point. But even without that, the four questions above will get you moving in the right direction. Your team already knows more about where things go wrong than you probably give them credit for. Give them a framework that lets them actually tell you and watch what they do with the responsibility once they know it will not be used against them.

The Leader’s Guide to Diagnosing a “Stuck” Team: 7 Warning Signs and What to Do About Them

Posted on by Adam Payne

Most teams do not fail suddenly. They drift.

At first, the signs are small: a decision takes a little longer than it should, a handover needs another chase, or a meeting ends with a lot of discussion and very little action. Over time, though, those small signs add up. You end up with a group of capable, highly paid professionals working hard but making frustratingly slow progress.

In established manufacturing and engineering businesses, that drift usually shows up in very specific ways. You see the same issues come back month after month. Departments struggle to hand work over cleanly. People spend too much time waiting for approval. And there is often that familiar tension between the shop floor, engineering, operations, and the rest of the business.

It is tempting to call this a morale problem. Sometimes leaders assume people are disengaged, lazy, or unhappy. But in most cases, a stuck team is a diagnostic issue, not a morale issue. The real problem is often unclear goals, fuzzy roles, or confused decision rights. People want to do good work, but the structure around them has started to slow everything down.

This guide is designed to help directors and senior leaders spot the warning signs early. It is a practical checklist for diagnosing what is really going wrong beneath the surface, and what to do first to get momentum back.

What a stuck team looks like

When we talk about a stuck team in technical businesses, we are rarely talking about a lazy team. In fact, it is usually the opposite. The business still has plenty of activity. The phones are ringing, the factory is busy, emails are flying, and everyone seems to be working flat out.

But activity is not the same as progress.

In manufacturing and engineering firms, being stuck often means there is a lot of movement but not enough ownership, clarity, or improvement. Management meetings keep raising the same points. Decisions sit waiting for sign-off. One department assumes another is dealing with the issue. And everyone feels as though they are working hard without actually moving the business forward.

You might see production delays linked to unclear priorities. You might see quality issues that keep reappearing because nobody has owned the root cause. Or you may see engineering changes slow down because responsibility is split between too many people. These are not random frustrations. They are symptoms of a system that has lost alignment.

The important point is this: the problem is often structural, not personal. Your people are probably reacting to the environment they are working in. If you fix the environment, you usually improve the performance.

1. No shared priorities

One of the clearest signs of a stuck team is a lack of shared priorities. People may be working exceptionally hard, but they are pulling in different directions. In technical businesses, that is easy to do because each function naturally sees the world differently.

Production wants throughput. Quality wants consistency. Sales wants promises kept. Engineering wants the right technical solution. Procurement wants cost control. All of those views make sense on their own. The trouble starts when there is no shared agreement on what matters most right now.

Without clear priorities, teams chase different goals and create confusion on the shop floor. Decisions get made locally without a wider commercial view. People begin to question why certain tasks matter, or why they are being asked to do something that seems to conflict with another department’s objective.

You can often hear the tension in the language people use:

“That’s not our priority.”
“We were told something different.”
“No one agreed that was the focus.”
“Why are we doing this now?”

Initial action: run a short leadership reset. Get the key people in a room and agree the top three priorities for the next ninety days. Just three. Then communicate them clearly and repeatedly so everyone knows what matters most right now.

2. Unclear roles and responsibilities

Unclear ownership is a silent killer of momentum. It creates hesitation, duplication, and frustration. In manufacturing and engineering businesses, this often shows up when work crosses between departments or when responsibilities have grown informally over time.

You know this is happening when you hear phrases like:

“I thought someone else was doing that.”
“Nobody told me I needed to sign that off.”
“That should have been picked up by operations.”
“I assumed engineering had checked it.”

Tasks require repeated follow-ups. People step into each other’s areas. Decisions are delayed because nobody feels fully authorised to make the call. The result is unnecessary friction, and that friction becomes normal.

This is especially common in established businesses that have grown steadily without fully resetting the structure. Key people leave. New people arrive. Processes evolve. But the business never quite stops to define who owns what, where decisions sit, and what each person is actually accountable for.

Initial action: choose one workflow that is causing pain and map it out on a whiteboard. Then assign a single named owner to each critical step or outcome. Do not assign tasks to a department. Assign responsibility to a specific person accountable for the result.

3. Meetings produce discussion, not action

We have all sat in these meetings. They go on for far too long. Everyone has something to say. The discussion is lively, and the people in the room clearly know their stuff. But when the meeting ends, nothing meaningful changes.

That is usually a sign that the team is missing clarity, accountability, or discipline around decision-making.

If your management meetings end with vague takeaways, the team will keep circling the same issues. The symptoms are easy to spot: long agendas, no review of previous actions, no firm deadlines, and no clear owner for each task. The same topics keep returning because nobody has closed the loop.

This is exhausting for capable people. High performers want to execute. They do not want to spend half their week in conversations that lead nowhere. Over time, this sort of meeting culture teaches the team that talking matters more than doing.

Initial action: change the rules of engagement for your meetings. End every meeting with three things: who owns what, by when, and how progress will be reviewed. If a topic does not have those three things attached to it, it was just a chat.

4. Problems keep bouncing between functions

In technical environments, problems rarely sit neatly inside one department. They move between sales, production, quality, engineering, operations, and sometimes purchasing too. In a stuck team, those problems bounce back and forth without being resolved.

This often turns into blame-shifting. Engineering says production did not follow the drawing. Production says the drawing was not buildable. Quality says the issue should have been picked up earlier. Sales says the customer was promised something the business could not realistically deliver. Everyone has a reason. Nobody has ownership.

Poor handovers make this worse. Information gets lost between departments. Assumptions are made and never checked. People spend more time arguing about where the issue belongs than fixing the issue itself. Over time, that friction damages trust and creates the kind of culture where departments start to see each other as obstacles rather than partners.

Initial action: create a simple escalation route. If an issue bounces between departments more than once, it must go to one named decision-maker or a specific forum for immediate resolution. Stop letting problems sit in the middle ground.

5. Leaders only hear good news

If you are a director and everything you hear from your team is positive, you should be concerned.

Filtered communication is dangerous. When people are reluctant to raise bad news, leaders lose visibility. Problems stay hidden until they become expensive, embarrassing, or difficult to fix. By then, the issue is no longer a small operational problem. It is now a business problem.

The warning signs are easy to recognise. Meetings go quiet when you ask for updates. Issues appear late in the project lifecycle. Leaders are surprised by problems that everyone else already knew about. People avoid difficult conversations because they hope the problem will go away on its own.

This is one of the clearest signs that trust or psychological safety has weakened. People are not being open enough about what is actually happening, and that means leadership decisions are being made with incomplete information.

Initial action: change how you ask for information. In your next team meeting, ask one direct question: “What is stuck, blocked, or at risk right now?” Then thank people when they bring you bad news. If the messenger is punished, the truth disappears again.

6. The team is always firefighting

Some stuck teams do not look stuck at all. They look busy. Very busy. The problem is that they are trapped in a cycle of short-term urgency.

When every day is reactive, there is no time to improve systems, solve root causes, or strengthen capability. The business keeps dealing with the next urgent thing, then the next, then the next. Leaders feel as though they are constantly catching up rather than steering the business.

The symptoms are obvious once you look for them. Planned work gets interrupted. People never seem to have time for improvement. The same issues consume the same energy again and again. Your best people start to look tired because they are always solving emergencies instead of building better systems.

Firefighting can feel productive in the moment, but it prevents the business from maturing. It keeps the team in survival mode. And survival mode is not where you build consistent performance.

Initial action: force a break in the cycle. Block a regular improvement slot each week, even if it is just one hour. Protect that time and use it to fix one recurring problem properly so it does not keep catching fire.

7. The same problems keep coming back

If the same issues keep resurfacing, the team is probably fixing symptoms rather than root causes.

You will see this in repeated quality issues, recurring customer complaints, and the same operational bottlenecks showing up again and again. People raise the problem, there is a bit of activity, and then the team moves on. For a while, it looks like progress. Then the issue returns.

This is what happens when a team loses its capacity for deep problem-solving. Under pressure, people reach for quick patches because they are trying to keep the business moving. The trouble is that quick patches do not create learning. They just buy time.

Over time, this becomes one of the most frustrating patterns in the business. Everyone knows the issue exists. Everyone is tired of discussing it. But nothing permanent changes because nobody has slowed down long enough to deal with the actual cause.

Initial action: pick one recurring issue that drives everyone crazy. Run a simple root cause review with the people closest to the work. Agree one permanent corrective action and set a strict follow-up date to check whether the fix worked.

A simple diagnostic checklist

If you want a quick sense of where your team is stuck, ask yourself these questions:

Do we have clear top priorities that everyone understands?
Does everyone know exactly who owns what?
Do our meetings end with clear actions and deadlines?
Are handovers between departments working smoothly?
Do people raise problems early, or do they hide bad news?
Are we spending enough time on improvement, or just firefighting?
Are recurring issues being permanently resolved, or just discussed?

Score each one honestly. The area where you feel the most hesitation is usually where you need to start. You do not need to fix everything at once. You need to find the point of friction that is holding the rest of the system back.

What good looks like

In a high-performing team, priorities are clear and shared. You can ask someone on the shop floor about the main goal for the month, and they will give the same answer as the engineering director. That kind of alignment is a strong sign that leadership is working.

People know their roles and own their outcomes. Decisions move quickly because authority is pushed to the right level. Issues are surfaced early without fear of blame. Meetings are tight, focused, and end with clear actions. Recurring problems reduce over time because the team is learning rather than simply reacting.

This is not a fantasy. It is what happens when leadership discipline is applied consistently. When you remove friction, good people usually want to do good work. They do not need to be forced. They need an environment that helps them perform.

Diagnose before you fix

A stuck team usually needs careful diagnosis before intervention. Leaders who identify the real structural causes of stagnation can act faster and with more confidence. That is the difference between treating symptoms and improving performance.

Clarity, ownership, and alignment are the foundations of team momentum. When those elements are missing, everything feels harder than it should. When they are in place, the business becomes easier to run, easier to manage, and far more capable of improving.

Your job as a leader is not to force your team to do more. It is to remove the blockers that stop good people from delivering their best work. Build an environment where doing the right thing is the easiest option, and performance starts to move in the right direction again.

If these warning signs feel familiar, the next step is not a bigger initiative. It is a clearer diagnosis. That is exactly the thinking behind our High Performing Teams workshop for manufacturers, where we help leadership teams identify bottlenecks, align priorities, and build stronger accountability.

How to Get Employees to Embrace Change: Overcoming Shop-Floor Resistance to Lean Methods

Posted on by Adam Payne

Introducing lean operational methods should make a business more efficient, more competitive, and more resilient. But if you work in manufacturing or engineering, you will know that the real challenge is rarely the process itself. It is getting people to accept it.

Too many change programmes fail because they are announced from the top, translated into jargon, and handed down to the shop floor as if buy-in can be demanded. It cannot. Employees embrace change when they understand why it is happening, when they feel involved in shaping it, and when they can see a clear benefit in their daily working lives.

That is especially true in technical businesses where experienced operators, machinists, welders, assembly teams, and supervisors already know what is broken in the process. They do not need to be told that improvement is necessary. They need to be convinced that this particular improvement will help, rather than simply make life harder.

This article looks at how to overcome shop-floor resistance to lean change in a way that is practical, credible, and commercially useful.

Why Shop-Floor Resistance Happens in Manufacturing

Resistance to change is often misunderstood. Leaders may see it as stubbornness, laziness, or a refusal to move with the times. In reality, it is usually a rational response to uncertainty.

On the shop floor, people are not reacting to a spreadsheet. They are reacting to the possibility that their workload will increase, their experience will be ignored, or their job security may be affected. When a new lean initiative is introduced, some employees hear, “We want you to do more with less.” Others hear, “We think the way you work now is wrong.” Neither interpretation helps build trust.

There is also the issue of history. Many manufacturing businesses have launched improvement initiatives that promised a lot and delivered very little. Employees remember those moments. If the last big programme ended with more paperwork, more meetings, and no real operational benefit, they will be sceptical the next time management announces something new.

That is why resistance should not be treated as a discipline problem. It is a message. It tells you that your people need more context, more reassurance, and more involvement before they will commit.

Why Lean Can Feel Threatening

Lean is one of the most misunderstood terms in manufacturing. Done well, it removes waste, improves flow, reduces frustration, and makes the business stronger. Done badly, it can feel like a polite label for cost-cutting.

That distinction matters. If your team believes lean is just a way of squeezing more output from fewer people, you will struggle to win support. If they believe it is about improving the way work gets done so that everyone has a better operation to work in, you have a chance.

For many employees, the word “lean” can trigger worry because it sounds abstract. Operators do not spend their day thinking about value streams or continuous improvement frameworks. They think about broken tooling, late materials, awkward changeovers, excessive walking, repeated rework, and the frustration of having to firefight avoidable problems. If a new initiative does not connect with those realities, it will feel detached from the world they actually work in.

The first task, then, is to make lean feel practical. Not theoretical. Not managerial. Practical.

Communicate the Change Early and Clearly

If you want employees to embrace change, you have to communicate before the rumour mill does it for you.

One of the biggest mistakes businesses make is waiting until everything is finalised before speaking to the workforce. By that stage, people have already filled the silence with assumptions. They may have overheard half a conversation, spotted a consultant on site, or sensed that something is being kept from them. Once that happens, trust begins to erode.

The best communication is early, honest, and repeated often. Say what the business is trying to achieve. Explain why the change is necessary. Be clear about what is changing, what is not changing, and what support people will receive along the way.

Avoid jargon wherever possible. Terms like “operational transformation”, “value-stream optimisation”, or “efficiency realignment” may sound impressive in a boardroom, but they do little to help a machine operator understand what is happening on the shop floor. Plain language works better. Tell people what problem you are trying to solve and why it matters.

It also helps to be honest about the difficult parts. If a change will take time to get used to, say so. If the business is facing competitive pressure, explain that too. People respect directness. They are much less forgiving of vague optimism.

Reframe Lean Around the Employee Experience

If lean is going to land well, it needs to be framed in terms of the employee experience, not just the business case.

That means answering the question every employee asks, whether aloud or not: “What is in it for me?”

For a production operator, the answer may be fewer interruptions, clearer instructions, better tooling locations, and less frustration caused by missing materials. For a supervisor, it may mean spending less time chasing problems and more time leading the team. For a maintenance engineer, it may mean fewer avoidable breakdowns caused by poor housekeeping or inconsistent standards.

This is where many change programmes fail. They talk about productivity, profitability, and competitiveness, but they never translate those ideas into daily working benefits. If you want people to buy into lean, make the connection visible.

Lean should be explained as a way to reduce waste, not people. It should be about making work smoother, safer, and more reliable. It should help staff do a better job with less frustration. Once employees see that, they are far more likely to engage.

Involve the Shop Floor Before You Implement

One of the most effective ways to reduce resistance is to involve employees early in the process.

Too many improvement efforts are designed in offices and then rolled out to the people expected to use them. That approach almost guarantees resistance. It sends the message that management already has the answer and only wants the workforce to comply.

A much better approach is to ask the people doing the work where the problems really are. They know where waste sits in the system. They know which tasks slow everything down. They know which shortcuts have become necessary because the original process no longer works properly.

That knowledge is invaluable.

Use workshops, Gemba walks, team discussions, and practical problem-solving sessions to gather their input. Ask them what frustrates them most, where time is lost, and which issues create the most stress. Then use that insight to shape the improvement plan.

When people help build the change, they are less likely to resist it. It becomes their solution, not a management imposition. That shift in ownership is one of the most powerful things you can create in a lean rollout.

Make Supervisors Your Change Champions

Supervisors and team leaders are often the most important people in a lean change programme. They are the link between senior management and the shop floor. If they do not believe in the change, the workforce will sense it immediately.

Employees do not just listen to what supervisors say. They watch what they do. A rolled eye, a dismissive comment, or a shrug of indifference can undermine weeks of careful communication. On the other hand, a calm and supportive supervisor can make a new process feel manageable and credible.

That is why supervisors need to be brought in early, briefed properly, and supported throughout the rollout. Do not just hand them a process document and expect them to carry the load. Give them time to ask questions, express concerns, and understand the logic behind the change.

It also helps to position them as coaches rather than enforcers. Their role is not simply to police compliance. It is to help people adapt, solve problems, and build confidence. If supervisors are left confused or unsupported, they cannot do that job well.

Consistent leadership matters too. If one shift follows the new standard and another quietly ignores it, the entire initiative begins to unravel. Alignment across shifts is essential if the change is going to stick.

Train People in a Practical, Hands-On Way

Training is often treated as a box-ticking exercise. That is a mistake.

If you want a new lean process to work, people need to understand it, practise it, and feel confident using it. That means training must be practical, specific, and tied to the actual workplace.

Long classroom sessions are rarely effective on their own. Most manufacturing employees learn best by doing, not by sitting through a slide deck. Demonstrations, visual prompts, side-by-side coaching, and repeated practice are much more effective than theory-heavy presentations.

The aim is not to overwhelm people with lean terminology. It is to make the new method feel achievable. If a process looks too complicated, too rushed, or too abstract, people will naturally fall back into old habits the moment pressure rises.

A good rule is to focus on competence before speed. Make sure people know what they are doing, why they are doing it, and how to do it safely and correctly. Once confidence builds, performance will follow.

Show Quick Wins Early

One of the most important lessons in change management is that people need to see results.

If a lean initiative takes six months to show any visible benefit, enthusiasm will fade. People need early evidence that the change is worthwhile. That is why quick wins matter so much.

Start with improvements that are visible, practical, and easy to appreciate. Reduce unnecessary walking. Improve a workstation layout. Introduce visual management to make materials easier to find. Cut a painful changeover time. Tidy a work area so it becomes easier and safer to use.

The improvement does not need to be dramatic. It just needs to be real.

When employees can see a better way of working and feel the difference in their own shift, scepticism starts to soften. Quick wins build credibility. They show that management is serious, that the process is working, and that the effort is leading somewhere useful.

They also help create momentum. Once one team sees a benefit, other teams become more open to trying the same thing.

Keep the Feedback Loop Open

Many businesses make the mistake of treating implementation as the finish line. They launch the new process, hold a meeting, perhaps make some celebratory noise, and then move on. But in reality, this is the point where the real work begins.

No process works perfectly on day one. There will always be friction, misunderstandings, and opportunities for refinement. If you do not create a feedback loop, problems will build quietly until people revert to the old way of doing things.

Regular feedback sessions help prevent that. Short daily reviews, improvement boards, team check-ins, and supervisor-led conversations all give people a chance to speak up. Just as importantly, they show that leadership is still listening.

This is where psychological safety matters. If employees believe they will be dismissed or criticised for raising issues, they will stop speaking. If they believe their feedback leads to genuine improvements, they will keep contributing.

Change should never feel like a one-off event. It should feel like an ongoing process of learning, refining, and improving together.

Common Mistakes That Increase Resistance

There are a few recurring mistakes that make it much harder to get employees to embrace change.

The first is launching without explanation. If people do not understand why the change is happening, they will invent their own explanation.

The second is using too much jargon. Manufacturing teams do not need management theatre. They need clarity.

The third is involving only senior managers and leaving frontline teams out of the conversation. That almost always produces resistance.

The fourth is trying to change too much at once. If every process is changing simultaneously, people can quickly feel overloaded.

The fifth is failing to follow through. If leadership says this change matters, but then disappears after launch, employees notice.

The final mistake is treating lean as a short-term project rather than a long-term culture shift. If the business wants continuous improvement, the commitment must be continuous too.

How to Build a Culture of Acceptance

If you want change to stick, you need to build more than compliance. You need to build trust.

That starts with the tone of the conversation. Employees are far more likely to support change when they feel respected, informed, and involved. It continues with visible leadership. People want to see that the people asking for change are also willing to listen, adapt, and support the rollout properly.

Over time, the goal is to shift the culture from “this is being done to us” to “we are doing this together.” That is when lean begins to work properly. Not because the tools are clever, but because the people using them believe in the purpose behind them.

For manufacturing and engineering businesses, that belief matters enormously. Technical change can only succeed when operational change is matched by human buy-in.

Final Thoughts

Employees do not embrace change because management says they should. They embrace change when they understand it, trust it, and can see the benefit in their own working lives.

If you want to overcome shop-floor resistance to lean methods, focus on the fundamentals. Communicate clearly. Involve people early. Support your supervisors. Train practically. Show quick wins. Keep listening. And make sure the change improves the work, rather than just renaming it.

Lean is most powerful when it is done with people, not to them.

Ready to Build Buy-In for Lean Change?

If your business is planning a lean rollout, but you want stronger shop-floor engagement and less resistance, we can help. At TCMUK Limited, we work with manufacturing, engineering, and technical businesses to turn operational improvement into real employee buy-in.

If you want to build a stronger culture of continuous improvement, get in touch to discuss how we can support your next stage of growth.

Why lean training fades, and why it isn’t your team’s fault

Week one: three projects, and nothing else

The daily fifteen minute huddle

The board on the wall

Day thirty: the review you run in front of the team

Bringing it together

Why a £60k system might be answering a different question

Which items qualify (and which really don’t)

Sizing the bins without needing a degree in statistics

Where the card goes, and why it’s the whole system

The first month: what to do when people forget

Bringing it together

Want a hand setting this up?

The predictable death of a 5S programme

The honest reasons yours probably died

Start small, on purpose

An audit cadence that survives the shop floor

The five-minute check that actually keeps it alive

Bringing it together

The cost you can see is never the real cost

Your biggest client is also your biggest exposure

The maths that should worry you more than the KPI dashboard

What halving your lead time actually buys you

Turning this into something you can actually act on

The takeaway

Why the scrap bin only tells you half the story

The six numbers hiding behind your scrap figure

Building your own number, step by step

What you do with the number once you’ve got it

The bin was never the real number

Ready to close the gap

Disconnection doesn’t announce itself

The four places the money actually leaks

A formula you can do on the back of a delivery note

Taking the number upstairs

What actually shifts the number

The cost is already being paid

Ready to put a number against the fix?

Why your weekly meeting keeps going nowhere

The five step cadence that actually closes the loop

Step five: close the loop before you close the meeting

A sample agenda you can steal for Monday morning

Getting actions to actually stick

Bringing it all together

Want help making it stick

Why manufacturers reach for control first, and what it actually costs you

Start with expectations so clear nobody has to guess

Swap the blame game for after action reviews

Give people room to move inside clear guardrails

Where to start this week

What a stuck team looks like

A simple diagnostic checklist

What good looks like

Diagnose before you fix

Why Shop-Floor Resistance Happens in Manufacturing

Why Lean Can Feel Threatening

Communicate the Change Early and Clearly

Reframe Lean Around the Employee Experience

Involve the Shop Floor Before You Implement

Make Supervisors Your Change Champions

Train People in a Practical, Hands-On Way

Show Quick Wins Early

Keep the Feedback Loop Open

Common Mistakes That Increase Resistance

How to Build a Culture of Acceptance

Final Thoughts

Navigation