Author: Adam Payne

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.

Inside the Hidden Factory: Where Mid‑Sized Manufacturers Leak Margins Every Shift

Posted on by Adam Payne

Most manufacturers are actually running two factories at the same time.
One is the factory you plan. The other is the one you live in.

There is the visible factory. This is the one you show visitors when they walk the floor. It is the factory in your production schedules, your financial forecasts, and your quarterly targets. Materials arrive on time, machines run at speed, and products ship out the door when promised. In this world, everything makes sense.

Then there is the hidden factory.
This is the factory where you and your team actually spend most of your time. It is the day‑to‑day leakage of time, labour, and margin that happens quietly while everyone is busy looking at the big picture. It includes unplanned rework, searching for misplaced tools, minor machine faults, and manual workarounds your operators invent just to get through the shift.

I have spent enough time walking around manufacturing floors to know that these losses are often incredibly small individually. An operator waiting five minutes for a supervisor to authorise a material swap does not feel like a crisis. But when you repeat that five‑minute delay across dozens of operators, multiple shifts, and five days a week, it suddenly becomes very expensive.

The core message is simple: you can achieve significantly better profit margins without buying a single piece of new equipment. You just need to dismantle the hidden factory.

Understanding the invisible drain on your resources

The hidden factory is the gap between your planned production and what really happens on the shop floor. It is the collection of activities that consume your capacity without creating any real value for your customer.

This includes rework, waiting, scrap, searching for items, moving things unnecessarily, dealing with interruptions, and relying on manual workarounds. Every time an operator stops adding value to a product because they need to find a specific drawing, your hidden factory grows. Every time a part is sent back down the line because a burr was not removed properly, you are feeding the hidden factory. These activities use up electricity, wear down tooling, occupy floor space, and consume your wage bill—but they do not add a single penny to your revenue.

Mid‑sized manufacturers feel this pain more acutely than anyone else. If your turnover sits somewhere in the £5M to £25M bracket, you are likely experiencing a specific scaling crunch. Smaller firms can survive through sheer heroics. The owner knows everyone by name, the production manager carries the schedule in their head, and problems are solved by people working later or harder.

But growth adds complexity far faster than it adds systems, standards, or leadership routines. As you scale past £5M and head toward £25M, informal processes stop working. The heroics that built your business become a liability. You cannot rely any longer on Dave from assembly knowing exactly how to fix a recurring machine fault because Dave is now managing twenty people and does not have the time. Smaller firms can survive on adrenaline. Mid‑sized firms pay a heavy financial price for inefficiency.

The quiet culprits eroding your margins

The invisible losses draining your margin rarely announce themselves with flashing red lights. They are insidious.

Think about rework that was never built into the original quote. You priced the job assuming it would go through the line once. When it goes through twice, your margin vanishes. Or consider scrap that was not properly recorded. I have seen skips full of wasted material at the back of factories that mysteriously never appear on official waste reports.

Operators searching for tools, parts, drawings, or instructions is perhaps the most common waste I see. Watching a highly skilled, highly paid engineer wander around a facility for fifteen minutes looking for a specific drill bit is heartbreaking. That is not value‑added work. That is friction.

Waiting is another massive drain—waiting for material, for quality approval, for maintenance to reset a machine, or for a management decision. While they wait, the clock ticks and your labour costs accumulate, but the product is not moving.

Extra motion, backtracking, and moving work‑in‑progress around the floor also erode margins. If your layout forces people to walk fifty paces every time they need to move a part to the next station, you are paying people to walk instead of paying them to build.

Add to this the manual data entry and spreadsheet patching caused by legacy systems. How many supervisors spend Friday afternoons typing numbers from paper into Excel, only to copy those numbers into another system entirely? It is madness when you step back and look at it.

These losses stay hidden because they rarely appear as one big catastrophic problem. If a main conveyor snaps, everyone notices. The factory stops, management gets involved, and it is fixed immediately. But if an operator wastes ten minutes every hour because their workstation is poorly organised, nobody notices.

These losses are spread across different people, shifts, and departments. Over time, the business gets used to them. Managers walk the floor and see people moving around, carrying things, and looking busy. They see activity, but they do not necessarily see waste. Activity and productivity are very different things.

Local workarounds often hide root causes instead of fixing them. If a machine keeps jamming, an operator might figure out a clever way to unjam it with a screwdriver. They feel proud of this workaround. The problem is that the machine is still broken, and the underlying cause is never addressed. The workaround becomes the new, slower standard operating procedure.

Legacy systems and the daily reality

Old systems create immense friction in scheduling, reporting, stock control, and communication. Many mid‑sized manufacturers are stuck in a strange technological purgatory. You have outgrown basic accounting software but have not fully implemented a modern enterprise resource planning system.

The result is spreadsheets—hundreds of them. Spreadsheets and disconnected tools increase duplication and delay. When your process visibility is poor, your hidden margin loss is high. If you do not know exactly where every job is at any given moment, you are losing money.

But technology alone does not solve a broken process. I have seen companies spend hundreds of thousands of pounds on shiny new software, only to find they have just digitised their inefficiency. If your underlying process is a mess, putting it on an iPad just gives you a very expensive, portable mess.

Let us walk through what the hidden factory looks like on a random Tuesday morning on the shop floor:

  • A job has to be restarted because the specification sheet was unclear and the operator guessed wrong.
  • A CNC machine sits idle because the next batch of raw material is missing from the staging area.
  • In assembly, an operator spends ten minutes locating a torque wrench because the previous shift left it in the wrong cabinet.
  • Later in the day, scrap is discovered, but only after value has already been added. The part was machined, polished, and coated before someone realised the initial cut was out of tolerance.
  • A supervisor spends an hour rechecking a batch of work because quality standards are inconsistent and they do not fully trust the new hires yet.

These everyday occurrences quietly destroy your throughput. None of these events look dramatic on their own. Nobody is shouting. No alarms are sounding. It just looks like another day at work. But these are the exact moments where your profit is leaking away.

Empowering your people to see the waste

You might think about bringing in consultants or buying new machinery to fix this. But the fastest fix is usually standing right in front of you. Training your team is the most effective way to dismantle the hidden factory.

People need to learn how to see waste before they can remove it. Right now, your operators walk past inefficiency every day because it has become part of the furniture. It is invisible to them.

Improving shop‑floor awareness improves problem‑spotting. Capability building is always cheaper and faster than capital expenditure. You do not need a half‑million‑pound machine to stop people walking around looking for tools. You need better habits.

Training is the route to better decisions, habits, and standards. It is about teaching the language of waste. Once your team understands concepts like overproduction, excess inventory, and unnecessary motion, they will start pointing these things out to you.

Start by using Gemba walks to observe real work. Gemba means the real place where the work happens. You do not fix a factory from a boardroom. You go to the floor, stand in a circle, and watch the process. Look for the friction.

Run simple value stream mapping sessions. Map out how a product moves from raw material to finished good. Write down every step. You will be surprised by how many times a product is picked up, put down, moved, stored, and moved again before it gets worked on.

Involve your operators in identifying friction points. They know which machine is temperamental and which supplier always sends parts late. If you dictate solutions from the top down, you will get resistance. If you ask them what frustrates them and help them fix it, you will get buy‑in.

Build standard work and visual controls. A workspace should be so intuitive that anyone could walk up to it and know within thirty seconds if things are running normally or if there is a problem.

Encourage root‑cause thinking instead of blame. If an operator makes a mistake, do not tell them to be more careful. Ask why the process allowed the mistake. Was the lighting poor? Were the instructions confusing? Was the tool worn out? Fix the process, not the person.

Practical first steps and the business case

If all of this sounds overwhelming, start small. Choose one line, one manufacturing cell, or one specific product family. Do not try to boil the ocean.

Go to that area and ask a simple question: Where is time being lost every shift?

Start measuring rework, waiting, movement, scrap, and expediting. You do not need complex software for this. A clipboard and a stopwatch will do just fine.

Fix the obvious problems first.

  • If people are walking too much, move the materials closer.
  • If tools are getting lost, buy shadow boards and insist tools are returned after use.
  • If information is unclear, redraw the setup sheet until it cannot be misread.

Manufacturing excellence is really just the mastery of the basics.

Share your wins quickly to build momentum. When you save an operator twenty minutes a day by reorganising their workstation, make sure everyone knows about it. Make hidden waste visible in daily team meetings. Talk about it constantly.

The business case is clear. Recovered minutes become extra capacity. If you have fifty operators and save each twenty minutes a day, you gain nearly seventeen hours of extra production capacity daily—the equivalent of hiring two full‑time employees for free.

Reducing scrap and rework improves margins immediately. You stop buying raw materials twice to make one product. You stop paying for electricity and labour to machine a part that ends up in the bin.

Better flow improves delivery performance. Jobs move smoothly through the factory without bottlenecks or delays, shrinking lead times. Shorter lead times help you win more business.

Tie these gains back to cash, not just operational metrics. Every piece of scrap eliminated is cash. Every hour of overtime avoided because the shift ran smoothly is cash.

Many mid‑sized manufacturers already have enough capacity to hit growth targets. They do not need a bigger building or more machines. They are simply leaking their existing capacity into the hidden factory.

The real opportunity moving forward

You must view the hidden factory as a serious profit leak, not just a minor operational nuisance. Dismissing ten minutes here and five minutes there as the cost of doing business ignores the cumulative impact of these delays across your workforce over a year.

Mid‑sized manufacturers are at the point where hidden waste moves from slightly annoying to incredibly expensive. You cannot afford to scale inefficiency.

The fastest and most sustainable route to better margins is making waste visible and teaching your people how to remove it. You have a factory full of intelligent, capable people who want to do a good job. Give them the right tools and perspective, and they will transform your operations.

If you recognise your business in these scenarios, it might be time to take a different approach. Stop trying to outgrow your problems and start fixing the process instead. If you want to improve performance, increase throughput, and reclaim margins without major capital investment, we should talk.

Explore our Lean Training Programmes today. We can help you equip your team with the skills they need to spot the hidden factory, eliminate daily friction, and build a more profitable, less stressful manufacturing operation.

From Promising Delivery Dates to Consistently Hitting Them

Posted on by Adam Payne

How Lean tools reduce lead time variation and improve OTIF in technical businesses

Let us talk about the exact moment a delivery promise starts to wobble. You probably know the feeling well. The sales team wins a fantastic order from a key customer and confidently gives a delivery date. The customer is delighted. The sales director is pleased. But somewhere down the hall, your production manager is looking at the master schedule and quietly wondering how on earth that date is going to hold.

This is a classic dynamic. I have seen it many times in mid-sized UK manufacturing plants. You win an order, you look at the routing cards, you give a date, and then reality gets involved. The problem here is not just an operational headache. It is a trust problem. When delivery dates keep slipping, customers stop believing them. They start calling for updates constantly, which wastes time, or worse, they start looking for alternative suppliers who can actually do what they say they will do.

We often misdiagnose the core issue. We assume the problem is simply that our lead times are too long. But the real enemy is often lead time variation. It is the unpredictability that kills credibility. If you are consistently slow, customers can at least plan around you. But if you are unpredictable, you become a serious risk to their own production schedules.

Today we are going to look at how Lean methods help engineering and manufacturing factories become more predictable, reliable, and ultimately more customer-friendly.

Why delivery dates slip in technical businesses

If you run an established technical business with anywhere from twenty to two hundred employees, you probably already know how to make your product. Skill is rarely the issue. Your engineers are capable, and your machinists are experienced. The issue is usually flow.

Why do dates slip so consistently in engineering firms? Usually, it is a messy combination of systemic issues that have just become normal. Excess work in progress is often the biggest culprit. There is a deep psychological need in manufacturing to see everyone looking busy. If operators are standing still, middle managers get nervous. So what happens? Jobs get released to the shop floor too early just to keep the machines running. The system gets flooded. And suddenly your factory floor becomes a very expensive storage area for part-finished goods.

When you have too much work in progress, you create queues between process steps. A component might need only three hours of actual machining time, but it spends three weeks sitting on a pallet waiting for its turn on the milling machine.

Then you have to factor in changeover delays. If setting up a machine takes half a day, your team will naturally want to run larger batches to justify the setup time. Those bigger batches clog the system further. Add in the inevitable rework, a quality hold because someone missed a critical tolerance, or late engineering information from the design office, and the schedule starts to unravel.

And then there is the material shortage. You can have a complex assembly ninety-nine percent complete, but it cannot ship because one small fastening component is missing. All of these issues create variability on the shop floor. That variability makes planning difficult and turns delivery promises into guesses.

Why lead time variation matters more than average lead time

We need to talk about the difference between a process that is fast on average and one that is genuinely predictable. People often confuse the two.

Imagine you quote a four-week lead time to a customer. Sometimes you get lucky and deliver in three weeks. The customer is pleasantly surprised. But the next time they order, a machine goes down, a supplier is late, and the same product takes nine weeks to deliver. On average, your lead time might look acceptable. But averages are not much use to a customer who has their own assembly line waiting for your components. Predictability is far more valuable than intermittent speed.

When a manufacturing process is highly variable, planners are forced into a corner. They learn from being burned. They stop trusting the process and begin building buffers into everything. A routing that technically takes two weeks gets quoted as four weeks to be safe. Then sales adds another week just to manage expectations.

Suddenly you are quoting five weeks for two weeks of actual work. And the frustrating part is that you may still miss the date. Work expands to fill the time available for its completion, and buffers create more waiting, more work in progress, more confusion, and more firefighting.

We often end up celebrating firefighters. The expeditor who stays late to get a desperate order out of the door gets praised. The planner who quietly builds a boring, predictable schedule gets less attention. But consistency is what improves credibility with customers.

Lean tools that improve delivery reliability

Let us look at the Lean tools that actually fix these systemic issues. At its heart, Lean is about making work easier, smoother, and much more predictable.

Value Stream Mapping

You cannot fix a process you cannot see. Value stream mapping reveals exactly where time is lost across the full order-to-delivery flow. You map the journey from the moment the purchase order arrives to the moment the finished goods leave the loading bay.

It is usually quite eye-opening when leadership teams see this mapped out properly for the first time. It exposes waiting, clumsy handoffs between departments, hidden rework loops, and the real bottlenecks. You quickly realise that products spend far more time waiting than being worked on.

Pull systems and Kanban

This is about stopping the habit of pushing work onto the floor just because a machine happens to be empty. In a pull system, work only starts when the next step is ready to receive it.

Pull reduces overproduction and cuts excess work in progress. By controlling how much work is on the floor, you keep flow more stable, more visible, and far easier to manage.

SMED

Single Minute Exchange of Die is a methodology for faster changeovers. If your changeovers take hours, you are going to run bigger batches. If you can use SMED principles to bring setup time down sharply, you can afford to run smaller batches.

Smaller batches link directly to shorter queues and a more flexible production schedule. Jobs move through the factory rather than sitting in slow-moving clumps.

Heijunka

This is the practice of workload levelling. You do not want a massive spike of complex work hitting the floor on Monday morning followed by almost nothing on Thursday. Heijunka smooths the peaks and troughs of customer demand into a steadier, more manageable rhythm.

Smoother production means less stress on machines, less overtime for staff, and delivery dates that are much more dependable.

Standard work and visual management

If anyone can walk onto your shop floor and instantly see whether the plan is on track, you have good visual management. Standard work reduces the variation in how tasks are actually carried out by different operators.

Visual management helps teams spot problems before they become delivery problems. If a job is falling behind, a good visual board highlights it immediately.

How Lean improves OTIF

On time and in full, or OTIF, is the ultimate metric for customer satisfaction. Delivering ninety percent of an order on time is still a failure if the customer needs all of it. Delivering everything in full but three weeks late is equally unhelpful.

Lean directly attacks the root causes of poor OTIF. Better flow means components arrive at final assembly when they are actually needed. Fewer delays mean the schedule holds true. Fewer quality issues mean you are not scrambling to remake a part at the last minute.

When you improve both halves of the OTIF equation, you change how the market sees you. Customers talk. When you become the supplier who regularly delivers what was promised, when it was promised, you build genuine trust.

Example of a UK manufacturer reducing lead time

Imagine an established company in the Midlands making complex industrial valves. They have around a hundred and twenty employees, a turnover in the tens of millions, and a long engineering history.

Their promised delivery dates were too optimistic. The production floor was chaotic and unreliable. Work in progress was stacked everywhere. Supervisors were running around the factory trying to find the right subassemblies to finish urgent orders.

They started with value stream mapping and discovered their real bottleneck was testing and calibration. Everything piled up there because the upstream machines were producing more parts than testing could handle.

They reduced work in progress, removed excess pallets, implemented smaller batches, and tightened scheduling discipline. If a machine had no scheduled work, the operator was moved to support the bottleneck.

The result was significant. Lead times became shorter because jobs were not waiting in huge queues. OTIF improved because the factory was no longer promising what it could not reliably deliver.

How to start in your own business

Reading about Lean is easy. Implementing it is harder. So do not try to change your whole factory overnight.

Pick one product family or one value stream. Map that single flow from start to finish. Measure the actual lead time against the lead time you quote to customers. Identify exactly where the longest delays happen.

Start small with a pilot area. Introduce pull and visual management in that one flow. Prove it works. Then scale what works across the rest of the business.

Conclusion: from hoping to knowing

Customers do not value promises. They value dependable delivery. Lean helps technical businesses turn delivery from a stressful guessing game into a controlled system.

Consistency creates confidence. It gives your sales team confidence to quote accurately. It gives your production team confidence that the plan is realistic. And most importantly, it gives your customers confidence that you will do what you said you would do.

If your technical business is struggling with slipping dates, chaotic schedules, and frustrated customers, it is time to stop blaming the operators and start fixing the system. Step back, look at the flow objectively, and start building a factory that delivers what it promises, time after time. If you need support with this please do get in contact here.

Why Lean Initiatives Fail After 6 Months (and How to Stop It)

Posted on by Adam Payne

Picture the scene. You’ve just wrapped up a massive improvement push. Maybe it was a sorting and setting in order blitz across the shop floor or a value stream mapping project promising to slash lead times. For the first few months, everything looks fantastic. Communication boards are clean and used, tools are perfectly placed in shadow boards, productivity is up, and your team seems genuinely engaged with the new way of working.

Fast forward six months.

You walk the floor and notice the daily management boards haven’t been updated since last week. Audit schedules are collecting dust in a corner. Firefighting is back in full swing, and your key performance indicators are quietly drifting back to where they started before you spent all that time, money, and effort.

It’s incredibly frustrating, and I’ve seen it happen more times than I care to count. I know exactly how deflating it feels to watch hard-won gains slip away.

The core claim I want to make here is simple: the problem isn’t the tools. The problem is treating these changes as short-term projects instead of a completely new way of running your factory.

In this post, we’ll unpack why these gains are so fragile and, more importantly, provide a practical playbook to sustain them in a busy UK manufacturing environment. You don’t have the time or budget to keep rolling out the same initiatives year after year. Let’s stop the rollback and start building a system that lasts.

The Six-Month Lean Slump: A Pattern, Not a One-Off

The six-month slump is a very specific, highly predictable pattern. You get the initial enthusiasm, quick results, a brief plateau, and then the inevitable regression back to the mean.

If this sounds painfully familiar, take comfort in the fact that you’re not alone. Across global manufacturing, and particularly here in the UK, failure to sustain continuous improvement is the rule rather than the exception. High rollback rates are common. Consultant-led programmes often don’t outlive the consultant. Once the external energy leaves the building, old habits creep back almost instantly.

It’s easy to blame the team. You might think your people just don’t care enough or that they’re resistant to change. But that’s rarely the case.

There are deep structural reasons why these initiatives are so fragile after those first few months. It’s not about a lack of willpower. It’s about how your business is fundamentally wired. This isn’t just a case of lazy operators. To fix the drop-off, you need to understand what’s really going wrong beneath the surface.

Why Lean Gains Are So Fragile

Lean Is a System, Not a Toolkit
The biggest trap we fall into is confusing a collection of tools with a comprehensive operating system. Doing some tools is not the same as changing your culture.

You can roll out visual boards, single-minute exchange of die, and kanban systems until you’re blue in the face. But if those tools aren’t backed by fundamental changes in leadership behaviour, company culture, and daily management, they will always be fragile.

Processes improve on paper, but if the way decisions are made stays the same, the old system reasserts itself. The reward systems and incentives haven’t changed. The daily habits of supervisors haven’t shifted. The tools become expensive window dressing on an unchanged operation.

The Time Bomb: Enthusiasm Versus Habits
There’s a massive difference between event energy and the slow, boring grind of building new habits.

During an improvement event, everyone is buzzing. You’re off the line, drinking lots of coffee, and fixing things that have annoyed you for years. But that three- to six-month window after the event is critical. The novelty wears off. The consultant packs up their laptop and goes home. The day-to-day pressures of getting product out the door ramp up again.

Without rigid routines and accountability, people naturally revert to the path of least resistance. It’s just human nature. If following the new standard takes slightly more mental effort than doing it the old way, and nobody is checking anyway, the old way wins every single time.

Why SMEs Feel It More
UK small and medium enterprises feel this pain particularly sharply.

In a typical smaller manufacturer, leaders are stretched incredibly thin. You have fewer support roles, less middle management, and a constant undercurrent of firefighting just to meet customer demands. When things get tight, the new initiative suddenly feels like extra work. It stops being the way we survive and grow, and it quickly becomes that thing we do when we have spare time. Which, let’s be honest, is never.

So it’s the first thing dropped in a crunch. This brings us right back to the core idea. The new methods must be part of how you run the business. They cannot be an overlay on top of an already overloaded operation.

Seven Common Reasons Lean Initiatives Collapse After Six Months

Let’s break down exactly what goes wrong. I’ve noticed seven common culprits, and you can probably spot a few of these in your own facility right now.

1. Lack of Visible Leadership Commitment
People on the shop floor have an incredible radar for what’s a passing fad and what’s a genuine priority. They can spot a hollow corporate initiative from a mile away.

The signs are always obvious. Leaders stop visiting the gemba. They stop asking about the new standards. They don’t follow up on the actions they promised to clear. In fact, they only really talk about continuous improvement when the consultant or the big boss is in the building.

The effect is immediate and devastating. Teams conclude that this whole thing will blow over soon. Instead of investing their energy in learning new ways of working, they just wait it out. And really, who can blame them?

2. Short-Term Focus and Initiative Fatigue
Then there’s the classic flavour-of-the-month mentality.

It’s one methodology this year. Maybe it’s something completely different next year. When you chase quick wins or immediate cost savings without a longer strategic intent, you just breed deep disillusionment.

People become highly sceptical. They roll their eyes in the canteen and say they’ve seen it all before. And they’re right. If there’s no long-term vision attached to the changes, it just feels like management is throwing mud at the wall to see what sticks.

3. Tool-Only Implementation (No Culture Change)
Have you ever walked into a factory where visual boards and laminated standards appeared overnight? It’s a very strange vibe. There’s usually very little explanation and absolutely zero involvement from the people actually doing the work.

The methodology becomes something done to operators, rather than something they own and control.

The symptoms are quite funny in a tragic sort of way. You see perfectly tidy toolboxes, but only when the auditor is walking around. You see beautifully laminated standard operating procedures that absolutely nobody reads. The boards look fantastic for visitors, but they don’t drive a single actual decision on the floor.

4. Weak Daily Management and Follow-Up
Improvement needs a rhythm. It requires daily huddles, clear metrics, regular reviews, and relentless problem-solving cycles.

When those rhythms are missing, performance simply drifts. Issues that you thought were fixed months ago suddenly recur. Those beautiful visual boards just become expensive wallpaper.

This is exactly why the six-month point is so dangerous. Once the initial push stops, if there’s no daily routine to catch the slip, the gains quietly evaporate while everyone is looking the other way.

5. Insufficient Training and Frontline Engagement
A shocking number of operators and supervisors never actually get the concepts explained to them in practical terms. They might get a one-hour presentation filled with Japanese words, but that’s about it.

When you lack proper training in problem-solving and standard work, your teams remain completely dependent on external experts or the one continuous improvement manager you hired.

This leads straight to theatre. People go through the motions. They fill out the forms because they were told to. But they don’t really understand or own the changes they are making.

6. Poor Communication and Misaligned Goals
How you frame the initiative matters immensely. If it’s framed purely as a cost-cutting exercise, it feels incredibly threatening. People naturally assume it means losing their jobs.

Contrast that with framing the work around quality, delivery, safety, reducing stress, and growing the business securely. That’s a message people can actually get behind.

But even with good messaging, misalignment will kill your progress. If the production manager is targeted entirely on volume, and the quality manager is targeted on defect reduction, they will clash. Conflicting targets completely undermine the collaborative behaviours you are trying to build.

7. Leadership Turnover and Competing Priorities
This one is incredibly common in the UK market right now. A new managing director, operations manager, or private equity owner comes in and decides to completely change direction.

Efforts stall immediately when leadership changes, especially if the new regime has different priorities or very little experience with continuous improvement.

It highlights exactly why you need a system that outlives individual leaders. If your entire culture of improvement rests on the shoulders of one enthusiastic plant manager, you are building your house on sand.

What Sustainable Lean Looks Like in a UK Factory

In mature sites, improvement is not a side project. It is the actual engine used to hit strategic objectives. Whether that’s reducing lead time, hitting on-time-in-full delivery targets, improving quality, freeing up capacity, or reducing working capital.

Improvement projects are chosen and resourced specifically because they move those big needles. They are not chosen just because doing a cleaning event seems like a nice idea this month. Everything connects back to the business plan.

Leaders in these successful factories behave very differently. They regularly go out to the gemba where the work happens. They ask curious questions about the standards. Most importantly, they actually help their teams solve problems instead of just demanding answers and pointing fingers.

They also use a beautifully simple daily management system. It is not overly complex or bureaucratic. There are key performance indicators, daily huddles, visual boards, and a very clear escalation process.

In a truly sustainable environment, small improvements are constant. They are just expected as part of the normal working day.

Operators are actively encouraged to spot waste, test out new ideas, and contribute to updating the standards. It is not a top-down mandate where management dictates every tiny move. Instead, it is a collaborative effort where everyone feels empowered to contribute to the continuous improvement journey.

Five Disciplines to Stop Your Lean Gains Slipping Away

  1. Make Lean a Strategic Choice, Not a Side Project
    Align your metrics and improvement projects explicitly to overarching goals. Review progress with the same seriousness as financials. This alignment ensures that every effort contributes to the broader objectives of the organisation, making Lean an integral part of the business strategy rather than an isolated initiative.
  2. Build a Simple Daily Management System
    Choose a handful of meaningful metrics. Introduce short daily huddles and ensure visual boards are updated in real time. This system should be easy to understand and implement, allowing for quick adjustments and fostering a culture of transparency and accountability.
  3. Standardise Before You Optimise
    Good standard work is visual, simple, and co-created with operators. Regular checks ensure standards are followed and updated. By standardising processes first, you create a solid foundation upon which further improvements can be built, ensuring consistency and reliability in operations.
  4. Invest in People—Training, Involvement, Recognition
    Provide practical training in problem-solving. Involve people in designing new ways of working and recognise their contributions. Investing in your workforce not only enhances their skills but also boosts morale and engagement, leading to a more committed and innovative team.
  5. Fix Leadership Habits
    Leaders must schedule time for continuous improvement and hold themselves accountable for sustainment. Leadership commitment is crucial for maintaining momentum and ensuring that Lean principles are embedded in the organisational culture.

From Six-Month Project to Long-Term Advantage

Continuous improvement doesn’t fail because the tools are wrong. It fails when treated as a temporary campaign instead of a permanent operating system.

Run a self-check in one production area. Pick one discipline to strengthen over the next ninety days. If you’re tired of watching your hard work fade away, we can help. Reach out to discuss our on-site Lean Coaching and Mentoring Programme. Let’s stop the rollback together and start making real, lasting progress. By embedding Lean into the very fabric of your organisation, you can transform short-term gains into long-term advantages, ensuring sustained success and growth in an ever-competitive market.

Build a Culture of Continuous Improvement