lean manufacturing

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.

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

The Push vs Pull Debate: Why Volume and Variability Make the Call

Posted on by Adam Payne

Let’s start with a tale of two factories. Imagine two metal fabricators, each turning over about £5m a year. The first, “Big Batch Ltd,” runs massive batches months in advance, guided by a Master Production Schedule resembling a 1950s railway timetable. Their warehouse is packed to the rafters. The second, “Just-in-Time Bros,” operates strictly to order, running small batches and often facing stockouts while machines sit idle waiting for signals.

Here’s the irony: both think the other is mad. Big Batch says, “How can you run a business with idle machines? You’re losing money.” Just-in-Time counters, “You’ve got half a million quid tied up in stock that might go obsolete next month. You’re insane.”

The truth? They’re both right—and wrong. The issue isn’t that one system is inherently better. It’s that “Push” and “Pull” are often treated as moral choices rather than operational ones. We get caught up in Lean jargon or MRP rigidity and forget the two factors that matter most: volume and variability.

Every factory operates on a spectrum between these two. Problems arise when your system doesn’t match your reality. You might be busy yet never deliver on time, or drown in stock but still fail customers because you have plenty of Product A when everyone wants Product B. If you’re constantly changing production plans and paying for expedited shipping, you have a mismatch.

By the end of this post, I want to help you step back from the “Lean vs Traditional” debate and view this through the lens of volume and demand patterns. We’ll explore what Push and Pull mean in practice, not theory, and determine where your factory should sit on the spectrum.

The Basics: Push vs Pull Defined

Before diving into nuance, let’s agree on definitions. Miscommunication often stems from using the same words to mean different things.

The Push System

In Push systems, production is triggered by a plan, typically based on a forecast. Whether it’s an MRP system, Master Production Schedule, or a simple spreadsheet, work and inventory are “pushed” into the next process regardless of whether the customer has ordered it yet.

For example, a plastic bottle plant might schedule production weeks in advance based on forecasted orders. They run full shifts to minimise changeovers, producing millions of bottles that are palletised and pushed into the warehouse. Push thrives in contexts with long lead times, stable demand, and commodity products where availability is key.

Push systems are often associated with traditional manufacturing environments where predictability is high. They allow for long production runs, which maximise machine utilisation and reduce per-unit costs. However, they also come with risks, particularly when forecasts are inaccurate or demand suddenly shifts. The reliance on predictions means that any deviation from the plan can lead to inefficiencies, excess inventory, or stockouts.

Push systems also offer a sense of control, which can be comforting for managers who prefer predictability. For example, in industries where downtime is costly, having a robust Push system ensures that production schedules are adhered to, minimising disruptions. However, this control can sometimes be an illusion, as unforeseen changes in demand can quickly unravel even the most carefully planned schedules.

The Pull System

In Pull systems, production is triggered by consumption. Nothing is made until someone—either the final customer or downstream process—asks for it. Mechanisms include Kanban cards, empty bin signals, or digital triggers. It’s the “supermarket” concept: you don’t bake more bread until the shelf looks empty.

Imagine a machine shop supplying an assembly line. In a Pull system, the shop waits for the assembly line to use a bin of brackets and send the empty bin back as authorisation to make more. Pull suits high variability, lower volume, or custom demand where overproduction is risky.

Pull systems are often associated with Lean manufacturing principles, emphasising flexibility and responsiveness. They reduce inventory levels and improve flow by aligning production with actual demand. However, Pull systems require stability and discipline. If processes are unreliable or poorly managed, Pull can lead to chaos, with frequent stockouts and missed deliveries.

The key difference? Push relies on future predictions; Pull relies on present reality. And predictions are rarely perfect. This distinction is critical because it highlights the inherent risks of relying too heavily on forecasts. While forecasts can provide a useful starting point, they are ultimately educated guesses, and the further out they extend, the less reliable they become.

Volume and Variability: The Game Changers

Most people stop at definitions, deciding to implement Pull everywhere to “be Lean” or Push everything because they love their MRP. But the real world is messy. You need to analyse your portfolio through two axes: Volume and Variability.

High Volume, Low Variability
Think commodity components or standard packaging. Demand is stable, and you’re likely to sell a predictable amount annually. Push works well here at the finished goods level. Large batches maximise efficiency and economies of scale. The risk lies in overstocking if demand drops or hiding quality issues in excess inventory.

For example, consider a factory producing washers. The demand for washers is consistent, and the production process is straightforward. In this scenario, a Push system allows the factory to optimise machine utilisation and reduce costs. However, the factory must carefully monitor inventory levels to avoid overproduction and ensure quality standards are maintained.

High Volume, High Variability
This is the danger zone—think retail promotional items or seasonal products. Demand is high but unpredictable. A pure Push system leads to inventory swings: stockpiling for a promo that flops or scrambling to expedite when demand spikes. A hybrid approach often works best, pushing base volume but pulling variable top-ups.

Retail environments often face this challenge. For example, a company producing holiday-themed packaging might experience a surge in demand during the festive season. A hybrid system allows the company to Push production for the base volume while using Pull mechanisms to respond to unexpected spikes in demand.

Low Volume, High Mix, High Variability
This is typical of jobbing shops or custom assembly environments. Forecasting by SKU is nearly impossible. Push at the finished goods level is wasteful. Instead, Push raw materials and common sub-components, but Pull final assembly based on firm orders.

For instance, a custom furniture manufacturer might Push raw materials like wood and screws into stock but Pull the final assembly based on customer orders. This approach minimises waste and ensures the factory can respond to unique customer requirements.

Low Volume, Engineer-to-Order
Here, almost everything is Pull. You can’t make it until it’s designed. However, you might Push standard bolts or steel sheets into stock to avoid delays.

Engineer-to-Order environments often involve complex projects with long lead times. For example, a company building custom machinery might Push generic components into stock to ensure availability while Pulling the final assembly based on project specifications.

The takeaway? You don’t choose “Push vs Pull” for the whole factory. You decide where the “decoupling point” sits for different product families. This nuanced approach allows manufacturers to tailor their systems to the specific needs of their operations, ensuring that resources are allocated efficiently and customer demands are met.

Push Systems: Pros and Cons

Push systems often get a bad rap in Lean circles, but they have their merits.

The Good
Push excels in high-volume, stable environments. For items like toilet rolls, you don’t wait for someone to flush before starting production. Push enables economies of scale and ensures instant availability for critical spare parts. It simplifies planning, offering a sense of control.

Push systems also provide a buffer against variability. For example, a factory producing spare parts for critical infrastructure might use a Push system to ensure stock availability. This approach minimises the risk of stockouts and ensures customers receive their orders on time.

The Bad
The downside is inventory risk and cash flow. Push systems spend money based on forecasts, which can be wrong, leading to obsolete stock. They also create longer lead times as WIP queues grow. Stock buffers can hide problems like machine breakdowns or quality defects.

Push systems can also lead to inefficiencies. For example, a factory producing promotional items might overproduce based on optimistic forecasts, resulting in excess inventory and wasted resources. These inefficiencies can impact profitability and customer satisfaction.

Pull Systems: Pros and Cons

Pull is the darling of modern manufacturing theory, but it has challenges.

The Good
Pull reduces inventory and shortens lead times. It improves visibility, exposing problems like machine downtime immediately. It’s flexible, allowing quick responses to actual customer demand.

Pull systems also promote continuous improvement. For example, a factory using Kanban cards to manage production might identify bottlenecks and implement changes to improve flow. This approach enhances efficiency and ensures the factory can respond to customer needs.

The Challenges
Pull requires stability. If uptime is poor or changeovers take hours, a pure Pull system will break. It also demands discipline—Kanban levels, lot sizes, and replenishment rules must be strictly maintained. Factories that slash inventory without improving stability often face chaos and stockouts.

Pull systems can also be challenging to implement. For example, a factory transitioning from Push to Pull might struggle to establish clear rules and processes. Without proper planning and training, the transition can lead to confusion and inefficiencies.

Push vs Pull by Volume: A Decision Framework

How do you decide? Stop viewing the factory as a single unit and start segmenting your products.

Step 1: Segment Your Products
Split SKUs into three buckets:

  • Runners: High volume, predictable demand.
  • Repeaters: Medium volume, some variability.
  • Strangers: Low volume, erratic or custom work.

Step 2: Apply the Strategy
For Runners, Push works well at the finished goods level. Use Pull internally between processes to control WIP. For Repeaters, a hybrid approach is best: Push raw materials and sub-assemblies, Pull final assembly. For Strangers, rely on Pull, pushing only generic raw materials.

Step 3: Locate Your Decoupling Point
The decoupling point is where flow switches from forecast-driven (Push) to order-driven (Pull). For high-volume items, it might be at the warehouse door. For custom items, it could be at the raw material stage.

Step 4: Check Your Constraints
Identify your bottleneck. If you have a critical machine, buffer work in front of it to ensure it never stops. For example, Push raw sheets into a supermarket but Pull cutting and welding based on Kanban signals.

Real-World Hybrid Examples

Few factories are purely Push or Pull. Most use hybrids.

Injection Moulding Plant
An automotive supplier used Push for OEM parts with predictable schedules and Pull for erratic aftermarket demand. They also Pushed raw resin due to long lead times.

Electronics Assembly
An industrial controls company Pushed PCBs and chips based on forecasts but Pulled final assembly triggered by customer orders. Kanban managed shared sub-assemblies.

Bespoke Machinery Builder
A conveyor system builder Pushed stock for steel and motors but Pulled cutting and assembly based on project numbers. For standard options, they maintained a supermarket of pre-welded frames.

The pattern is clear: Push for predictable, generic items; Pull closer to the customer for variety.

Implementation Tips and Pitfalls

Changing your factory’s system is risky. Start small.

Start with One Family
Don’t overhaul everything at once. Pick one product family—perhaps a “Repeater”—and design the system for that loop first.

Map the Flow
Draw a value stream map to identify where schedules are created, WIP piles up, and firefighting occurs. Mark forecast-driven and order-driven points.

Size Buffers Deliberately
Calculate Kanban quantities based on demand, lead time, and variability. Guessing leads to stockouts or excess inventory.

Avoid “Fake Pull”
Don’t undermine Pull with weekly schedules or ignored Kanban limits. Pull requires discipline and system design.

Conclusion

Push vs Pull isn’t a moral choice; it’s a design choice driven by volume, variability, lead times, and customer expectations. Most factories need a hybrid system. The key is deciding where to place the decoupling point.

Segment your products into Runners, Repeaters, and Strangers. Map one value stream and ask, “Why are we pushing here? Could we pull instead?” Get the balance right, and you’ll stop drowning in stock you don’t need while delivering what customers actually want. That’s a better way to run a factory.

In conclusion, understanding the nuances of Push and Pull systems is crucial for optimising manufacturing operations. By carefully analysing volume and variability, and by strategically placing the decoupling point, manufacturers can create a system that not only meets customer demands but also enhances efficiency and profitability. The journey to finding the right balance may involve trial and error, but the rewards of a well-designed system are worth the effort. The ability to adapt and refine these systems over time is what sets successful manufacturers apart, ensuring they remain competitive in an ever-changing market landscape. Success lies in the ability to balance flexibility with predictability, ensuring that operations are both efficient and responsive to customer needs.

The Anatomy of a Value Stream Map: How to Identify Non‑Value‑Added Time

Posted on by Adam Payne

Picture the scene. It’s a Tuesday morning in a mid-sized factory somewhere in the Midlands. The shop floor is humming. CNC machines are whirring, forklifts are beeping as they reverse out of narrow aisles, and there’s a general sense of frantic, purposeful energy. Everyone looks busy. To the untrained eye, this is the picture of productivity.

But walk up to the production manager’s office, and the mood is different. The phone is ringing off the hook with customers chasing late orders. The warehouse is bursting at the seams with stock that isn’t moving, while the assembly team is standing around waiting for a single bracket that’s stuck in the paint shop.

It’s a paradox I’ve seen a hundred times. How can everyone be working so hard, yet the product takes weeks to get out the door?

The answer usually isn’t that your people are lazy or your machines are too slow. It’s that you’re looking at the individual processes, not the flow. You’re watching the runner, not the baton.

This is where Value Stream Mapping (VSM) comes in. Now, I know what you’re thinking. “Not another lean tool. We tried 5S in 2015 and it fizzled out.” I get it. But VSM isn’t just about drawing boxes on a whiteboard. It’s about seeing the truth of your operation—the end-to-end path from a customer placing an order to that order leaving on a lorry.

For UK manufacturers, especially SMEs who can’t compete on cheap labour against the giants in the East, this is critical. We compete on lead time, reliability, and technical flexibility. If your lead time is four weeks but the actual touch time on the metal is only four hours (and believe me, that’s a common ratio), you have a massive opportunity hiding in plain sight.

Let’s dig into the anatomy of a value stream map and figure out where all that time is going.

1. Why Value Stream Mapping Matters for UK Manufacturers

If you walk into most UK factories and ask, “What’s our lead time?”, someone will confidently say, “Standard is 20 days.” If you then ask, “How long does it actually take to make one?”, the answer might be, “Oh, about six hours of machining and two hours of assembly.”

The gap between those six hours and those 20 days is where the money is.

A value stream is simply the sequence of activities required to design, produce, and deliver a good or service to a customer. It includes two flows: the flow of material (the product moving) and the flow of information (the schedule telling it to move).

The problem is that traditional management focuses on the “value-added” bits—making the machine run 10% faster. But if the part sits in a queue for three days before it gets to that machine, making the machine faster doesn’t help the customer get their order sooner. It just makes the part join the next queue faster.

VSM allows you to see both the work and the waiting in a single picture. It exposes the mess.

For a UK SME, this perspective is vital. You likely don’t have the cash reserves to hold millions in inventory, and you can’t afford to air-freight parts to Germany because you missed a deadline. You need flow. By mapping the stream, you stop optimising islands of work and start optimising the journey of the product. It shifts the conversation from “work harder” to “stop waiting.”

2. The Anatomy of a Value Stream Map

So, what does this map actually look like? If you’ve only ever used flowcharts, a VSM might look a bit messy at first. It’s not a neat logic diagram; it’s a representation of reality, warts and all.

Here are the main organs of the anatomy:

Process Boxes
These are the squares across the bottom of the map representing operations—cutting, welding, assembly, testing. Crucially, these boxes don’t just say “Welding.” They contain data. We’re talking cycle time (how often a part comes off), changeover time (the killer of flow), uptime, and the number of operators. If you don’t have the data, you can’t do the map. No guessing allowed.

Material Flow
These are the arrows connecting the boxes. A thick striped arrow usually means “push” (making it because the schedule said so, regardless of whether the next person is ready). You’ll see symbols for “supermarkets” (controlled inventory) or FIFO lanes (first-in, first-out). If your map is covered in “push” arrows, you’ve already found a problem.

Information Flow
This is the part most people forget. It’s drawn at the top of the map. How does the shop floor know what to make? Is it an MRP schedule printed weekly? A daily kanban? A frantic supervisor running down with a post-it note? The information flow triggers the material flow. If the signal is bad, the flow is bad.

Inventory Symbols
These are usually triangles with an “I” inside, sitting between processes. This is where your cash is tied up. On a VSM, we don’t just count the parts; we convert that inventory into time. If you make 100 widgets a day and there are 500 widgets in the pile, that triangle represents 5 days of lead time. Seeing “5 days” written on a map hits harder than seeing “500 parts.”

The Timeline
This is the bottom line—literally. It looks like a castle battlement. The lower line represents processing time (value-added), and the upper line represents waiting time (non-value-added). At the end, you sum them up. This gives you your total lead time versus your processing time.

The anatomy matters because the insight comes from the relationship between these elements. A pile of inventory (triangle) caused by a long changeover (data box) driven by a weekly batch schedule (information flow) tells a story that a spreadsheet never could.

3. Value‑Added vs Non‑Value‑Added: Getting Clear on Definitions

Before you start sticking post-it notes on a wall, you need to agree on what “value” actually means. If you don’t, your mapping workshop will descend into an argument with the Quality Manager about why his three-hour inspection protocol is the most valuable thing since sliced bread.

I find the best way to cut through the noise is the Customer Test. Ask these three questions:

  1. Does it change the product? (Physically or chemically transforming it).
  2. Is it done right the first time? (Rework is never value).
  3. Would the customer willingly pay for it?

If you itemised your invoice and added a line saying, “Moving parts from Warehouse A to Warehouse B: £50,” would the customer pay it? No. They’d tell you to sort your logistics out. That’s non-value-added.

To be fair, we can’t just slash everything that fails this test. We need to categorise time into three buckets:

Value-Added Time (VA):
The seconds or minutes where the drill touches the metal, the welder strikes the arc, or the assembler tightens the bolt. This is usually a tiny fraction of the total time.

Necessary Non-Value-Added Time (NNVA):
These are things that add no value to the customer but are currently unavoidable due to your technology, regulations, or business setup. Payroll processing, regulatory compliance checks, or cleaning the machine. You want to minimise these, but you can’t just stop doing them tomorrow without breaking the law or the business.

Pure Non-Value-Added Time (Waste):
This is the enemy. Waiting for materials, looking for tools, moving parts three times because there’s no space, re-reading unclear instructions. This can be eliminated immediately without harming the product.

Getting these definitions clear prevents the “everything is waste” depression. It allows you to tell your team: “Look, we know the safety check is necessary. We aren’t calling it useless. We’re just calling it non-value-added so we can try to make it faster.”

4. Where Non‑Value‑Added Time Hides in a Value Stream

Once you have your eyes tuned to see waste, walking the factory floor becomes a very different experience. It’s like putting on X-ray specs. You stop seeing “busy” and start seeing “waste.” Let’s take a tour of where the time hides.

4.1 Waiting and Queues

This is usually the heavyweight champion of waste. If you track a single part through your factory, I’d bet a pint that it spends 95% of its life sitting still.

On your map, this shows up as those inventory triangles with huge time numbers inside. It also shows up on the timeline as long flat lines between the value-added blips. It happens because processes are unbalanced. If Process A takes 1 minute and Process B takes 2 minutes, Process A will just pile up stock in front of B. That pile is waiting time.

4.2 Transportation and Motion

There is a difference between moving things and moving people. Both are waste.

Transportation is moving the product. If your map has long, zig-zagging arrows, or if you’re using a lorry to move goods between units on the same industrial estate, that’s time (and risk of damage) adding zero value.

Motion is people. Watch your operators. Are they walking ten feet to get a wrench? Are they bending, stretching, or walking around pallets? That’s not working; that’s dancing. It’s tiring, and the customer doesn’t pay for the dance.

4.3 Overproduction and Excess Inventory

Overproduction is the worst waste because it creates all the others. It’s making things before they are needed, usually because we’re terrified of the machine stopping.

On the map, this screams at you through large batch sizes in the data boxes. If you have a batch size of 1,000 but the customer orders 50 at a time, you are guaranteeing inventory. That inventory takes up space, requires heating and lighting, needs counting, and often goes obsolete before it’s sold. It’s where cash goes to die.

4.4 Over‑Processing, Inspection and Rework

This is doing more than the customer asked for. Polishing the underside of a table. Painting a part that gets hidden inside a casing.

It also includes inspection. I know, quality is important. But inspection doesn’t add quality; it just catches the lack of it. If your map has a “Quality Gate” where parts sit for 24 hours waiting for a sign-off, that’s a massive delay. The goal is to build quality in, not inspect it in later.

4.5 Unused Creativity

This one doesn’t always show up as a symbol, but you see it in the notes. When you talk to the operators during mapping, they’ll say things like, “I know this paperwork is silly, I just fill it in because I have to,” or “I made a jig to fix this, but the manager took it away.”

That is the sound of unused brainpower. The people doing the work know where the waste is. If your map doesn’t reflect their frustrations, it’s not accurate.

5. Turning the Map into Numbers: Quantifying Non‑Value‑Added Time

You can draw boxes all day, but until you put numbers on it, it’s just art. You need to quantify the pain to get leadership to pay attention.

5.1 Building the Value Stream Timeline

At the bottom of your map, you draw the timeline. It looks like a square wave. The peaks are the processing times (seconds or minutes). The valleys are the lead times (hours or days).

You sum up the peaks. Let’s say it comes to 3 hours of value-added work.
Then you sum up the valleys (the inventory time). Let’s say it comes to 15 days.

The ratio is shocking. (3 hours / 360 hours) = 0.8%.
That means 99.2% of the time, your product is doing nothing. Presenting this number to a Board of Directors is usually a “pin drop” moment. It’s uncomfortable, but it’s the catalyst for change.

5.2 Using a Time Value Map

If the timeline is too abstract, use a Time Value Map. It’s a simple chart. The X-axis is the total lead time. Anything above the line is value-added; anything below is waste.

When you plot it, you’ll see tiny slivers of green above the line and massive blocks of red below it. This becomes your baseline. You don’t just say “we want to get better.” You say, “We want to remove 4 days of the red block by Q3.”

5.3 Connecting to Takt Time and Bottlenecks

Takt time is the heartbeat of the customer. It’s the available work time divided by customer demand. If the customer buys 480 widgets a day and you have 480 minutes, you need to finish one every minute.

Your VSM data lets you compare every process cycle time to this heartbeat. If a process takes 70 seconds but Takt is 60 seconds, you have a bottleneck. You will always have queues there. You cannot solve the non-value-added waiting time without addressing that bottleneck.

6. A Practical VSM Exercise for a UK SME

Ready to try it? Don’t try to map the whole factory at once. You’ll drown. Here is a practical approach.

6.1 Choosing the Right Product Family and Scope

Pick a product family that matters. Not the weird bespoke job you do once a year. Pick the bread and butter—the product that pays the bills but causes the headaches. Maybe it’s the one with the most complaints or the one that always requires overtime to ship.

Define the scope: “Door to door.” From the moment the raw material arrives to the moment the finished goods truck leaves.

6.2 Walking the Gemba and Collecting Data

Do not—and I repeat, do not—do this in a conference room. You cannot map a process from memory because your memory is filled with how the process should work, not how it does work.

Go to the “Gemba” (the place where work is done). Walk the flow backward, from shipping to receiving. Why backward? It stops you from just following the material and helps you see the customer pull (or lack of it).

Take a stopwatch. Be polite. Tell the operators, “I’m timing the process, not you.” Ask them what annoys them. Ask them, “What stops you from working?” That’s where the gold is.

6.3 Drawing the Current‑State Map and Highlighting Waste

Get a big roll of butcher paper and some post-its. Draw the map by hand. Don’t use software yet; it makes things look too tidy. You want the mess.

Use codes. “VA” for the good stuff. “NVA” for the waste. Colour code the waiting times in red. Circle the rework loops. If a part goes back to the start for re-painting, draw that loop. It looks ugly on paper, which is exactly the point.

6.4 Designing a Future‑State Map That Cuts Non‑Value‑Added Time

Now for the fun part. What could this look like?

If you removed the batching, could you cut the inventory by half?
If you moved the welding station next to the cutting station, could you eliminate the forklift trip?
If you introduced a “pull” system (don’t make it until the next guy asks for it), could you stop overproduction?

Design a future state that flows. Aim for a lead time reduction of 50%. It sounds ambitious, but given how much waste you’ve likely found, it’s usually achievable.

7. A Short Example: From 10 Days to 4

Let me tell you about a precision engineering firm I visited in Yorkshire. They made specialised gearboxes.

The Situation: Their lead time was quoted at 10 days, but they rarely hit it. The place was full of racks. The Managing Director was convinced they needed a bigger warehouse.

The Map: We mapped it. The total touch time to make a gearbox was 4.5 hours.
Where was the other 9 days and 19.5 hours?

  • 2 days waiting for raw material check-in (paperwork bottleneck).
  • 3 days in a queue before the milling machines because they ran big batches of 50 to “save setup time.”
  • 2 days waiting for a specialised heat treatment that was outsourced.
  • 1 day in Final Inspection because the inspector was also the packing guy.

The Future State:
We didn’t buy new machines. We didn’t hire more people.

  1. We created a “fast lane” for raw material check-in.
  2. We reduced the milling batch size from 50 to 10. Yes, that meant more changeovers, so we practiced SMED (Single Minute Exchange of Die) to cut changeover time down.
  3. We brought a small heat-treatment process in-house for the most common parts.
  4. We moved inspection to happen during assembly, not at the end.

The Result:
Lead time dropped to 4 days. The warehouse they wanted to build? Didn’t need it. They actually rented out space in their existing unit because the inventory shrank so much.

Conclusion

Value Stream Mapping isn’t magic, and it isn’t just for Toyota. It’s a mirror. It forces you to look at your manufacturing process through the unblinking eye of the customer.

It reveals the uncomfortable truth: that we spend most of our time waiting, moving, and fixing, rather than making.

But here is the good news. Because so much of your lead time is non-value-added, you don’t need expensive technology to fix it. You don’t need AI or robots to stop a pallet sitting in a corridor for three days. You just need the discipline to see it and the courage to change the flow.

So, here is my challenge to you. Pick one product family. Grab a stopwatch and a pencil. Go for a walk. Ask yourself: “Is this adding value, or is it just waiting?”

You might be surprised by how much time—and money—you find lying on the floor.

And don’t forget, if you need support in training your talent in this approach, it’s part of our Lean Green Belt training.

From Firefighter to Coach: 5 Traits That Define True Lean Leadership

Posted on by Adam Payne

You know the feeling. That tightening in your chest when you step onto the factory floor and something feels off. Maybe the presses sound wrong, or there’s a cluster of high-vis vests around the main conveyor. You walk over. You’re the production manager or operations director—it’s your job to fix things. You dive in, ask what’s wrong, bark a few orders because time is money, and the truck is due at 2 p.m. You move people around, maybe grab a spanner yourself because it’s quicker that way.

By 11 a.m., the line is running again. You feel relief, maybe even pride. You saved the day. You were the hero.

But here’s the uncomfortable truth: that hero complex is holding your factory back.

It’s a hard pill to swallow. I know because I’ve been there—running around, thinking I was being effective. But that command-and-control style, where the boss holds all the answers and everyone else just follows orders? It’s the antithesis of lean. It stifles problem-solving, creates dependency, and exhausts you.

If you want a manufacturing business that improves daily and runs smoothly even when you’re on holiday, you need to change how you lead. You need to stop being the boss and start being the coach.

It’s not just a buzzword. It’s a fundamental shift in behaviour. Let’s explore five practical traits that define this shift—from firefighting to fire prevention.

Trait 1: Coaching at the Gemba, Not Commanding from the Office

Where you spend your time matters. In lean manufacturing, there’s a term called gemba, meaning “the real place.” For us, that’s the shop floor—where value is created, where metal is cut, components are assembled, and packaging is sealed.

Traditional bosses manage from a distance, sitting in offices, looking at spreadsheets, or answering emails. If they visit the floor, it’s usually because something’s wrong or for a VIP tour. Operators look busy when they walk by—it’s a performance.

A lean leader operates differently. They know you can’t understand the process from a spreadsheet. You have to go see. But it’s not just about being there—it’s about how you’re there.

If you walk the floor to point out mistakes or check up on people, you’re a policeman, not a coach. That builds anxiety, not trust. A lean coach goes to the gemba to observe and support.

I remember a plant manager in the Midlands who had a brilliant routine. Every morning at 9 a.m., he walked the line. No clipboard, no phone—just walked. One day, he stopped at a cell where an operator was struggling with a fixture. The old-school boss would’ve said, “Why are you behind target?” or “You need to speed up.” This manager asked, “What’s making this hard for you today?”

That simple shift in language aligned him with the operator against the problem. The operator relaxed and showed him a burr on the part causing the issue. They fixed it together.

That’s what good looks like: structured gemba walks, attending daily huddles to listen, using visual boards to see work status at a glance. It’s about being present to remove obstacles, not create pressure. At first, it might feel aimless, but once the team realises you’re there to help, the dynamic changes completely.

It’s also important to note that being present at the gemba doesn’t mean micromanaging. It’s not about hovering over people or constantly checking their work. Instead, it’s about creating an environment where operators feel comfortable sharing their challenges. When you’re consistently present in a supportive way, you’ll start to notice patterns and recurring issues that might not show up in reports. This deeper understanding of the day-to-day realities on the floor is invaluable for driving meaningful improvements.

Trait 2: Developing Problem Solvers, Not Followers

If you’re always the one with the answers, you’re the bottleneck. I see this often in SMEs. A brilliant production manager knows the machines inside out, can hear a bearing failing from the car park. But because they’re so good at fixing things, nobody else learns how.

When a machine stops, everyone looks at the manager. They fix it, and everyone goes back to work. That’s not leadership—it’s being a highly paid mechanic.

A lean leader’s primary job is developing people, specifically their ability to see and solve problems. Frameworks like PDCA (Plan-Do-Check-Act) or A3 problem-solving teach teams to think scientifically.

Imagine the same scenario where a machine stops. Instead of pushing the operator aside and hitting reset, a coaching leader asks, “What do you think just happened?” The operator might say, “I don’t know, it just stopped.” The leader asks, “What was the last thing you did before it stopped?” They encourage the operator to find the root cause.

This takes patience. It’s excruciating at times—you know exactly which sensor is dirty and could fix it in five seconds. But if you fix it, the operator learns nothing. If you coach them through it, they learn about the machine and gain confidence. Next time, they might check the sensor themselves.

Eventually, you want a factory full of people who treat problems as opportunities to learn. They’ll run experiments: “If we move this bin here, it might be faster. Let’s try it.” That’s the holy grail, but you only get there if you stop being the hero and start being the teacher.

It’s also worth noting that developing problem solvers doesn’t happen overnight. It requires consistent effort and reinforcement. You might need to introduce structured problem-solving training or create opportunities for team members to practice these skills in a safe environment. Over time, as they gain confidence and experience, you’ll see a shift in how they approach challenges. They’ll start taking ownership of problems and proactively seeking solutions, which is exactly what you want in a lean culture.

Trait 3: Modelling Commitment and Authenticity

Trust is essential. You can’t coach people if they don’t trust you. And in manufacturing, people have a radar for insincerity. They know when a manager is faking it.

Nothing kills lean culture faster than a leader who pushes lean tools onto the workforce but doesn’t use them themselves. They demand 5S standards on the shop floor, but their own desk is a mess. They insist on standard work for operators but ignore escalation protocols when it suits them.

If you want to move from boss to coach, you have to walk the talk. Follow the standards. If safety glasses are required in the green zone, wear them every time—even if you’re just passing through for ten seconds.

It’s also about authenticity. One of the most powerful things a leader can do is admit when they’re wrong. In a traditional command-and-control environment, admitting a mistake is seen as weakness. In a lean environment, it’s a learning opportunity.

I worked with a director who made a bad call on a supplier change, causing quality issues. In a town hall meeting, he admitted, “I made a decision to switch suppliers to save cost. I didn’t properly evaluate the quality impact. That was my mistake, and I’m sorry for the extra work it caused. Here’s what I’ve learned and how we’ll prevent it happening again.”

The respect in that room skyrocketed. By showing vulnerability, he made it safe for others to admit mistakes. If you hide failures, your team will too—and hidden failures in a factory lead to scrap, delays, or accidents. Model the behaviour that says it’s okay to be wrong as long as we learn from it.

Authenticity also means being consistent in your actions and words. If you say that continuous improvement is a priority, your behaviour should reflect that. Attend improvement meetings, participate in problem-solving sessions, and celebrate small wins. When your team sees that you’re genuinely committed, they’ll be more likely to follow your lead.

Trait 4: Being an Active Coach and Problem-Solving Partner

Lean leadership is active, not passive. You’re not just a cheerleader shouting, “Go team!” You’re a problem-solving partner.

There’s a balance. While you should ask questions instead of giving answers, some situations require decisiveness. If the building’s on fire, you don’t ask, “How do you feel about the smoke?” You tell people to get out. But most daily issues require coaching.

A good lean leader has a routine. Maybe you use the Toyota Kata approach, with regular coaching cycles and daily visual board meetings. Your role is to look at the gap between the target and current condition, then ask, “What’s the next step?”

You help the team break big problems into manageable chunks. Many leaders set KPIs and shout when they’re not met. “We need OEE at 85%!” Great. How? The coach helps the team figure out the how and removes barriers. If they need tools to improve changeover time, your job is to get them the tools. You work for them.

Think of it as clearing the path. Your team is climbing a hill; your job is to chop down brambles and fill potholes so they can keep moving. It’s hands-on, reviewing data, asking, “What did we expect? What happened? What did we learn?”

It’s relentless and mentally demanding. It’s easier to sit in your office and look at the P&L, but the P&L is a history book. Active coaching changes what happens next month.

Trait 5: Creating a Learning and Improvement Culture

Culture in a factory is simply “the way we do things around here.” In traditional factories, continuous improvement is often a “project” or “initiative.” You might have a “Kaizen Week” once a year, then go back to the old way of working.

A lean leader understands improvement is the day job. It’s not something you do in addition to work—it is the work.

Change what you celebrate. Many factories reward firefighting—the person who stays late to fix the machine gets a pat on the back. But what about the person who did preventive maintenance so the machine didn’t break? They’re often ignored.

Celebrate small improvements and learning. For example, if there’s a near-miss safety incident, don’t just blame the driver or put up a “Safety First” poster. Investigate: Why didn’t the driver see the pedestrian? Was the lighting bad? Was there a blind spot? Treat it as a system failure, not a person failure.

This approach signals you’re interested in truth, not scapegoats. Psychological safety is essential. If people fear blame, they’ll hide problems, and you can’t fix what you can’t see.

You want a culture where breakdowns are opportunities to make processes more robust. It’s a massive mindset shift, but it’s the only way to sustain lean long-term.

Putting It into Practice: First Steps for Manufacturing Leaders

Where do you start? This might feel overwhelming, especially if your current reality is far from this ideal. You might think, “This sounds great, but I have orders to get out, and my team is stretched thin.”

You can’t change everything overnight. Start small. Authenticity matters more than perfection.

Here’s a quick self-check. Be honest with yourself:

  1. How much time did I spend on the shop floor this week? More than 10%?
  2. When I was on the floor, did I ask more questions or give more orders?
  3. Do I know the top three problems for my operators right now?
  4. When was the last time I admitted a mistake to my team?
  5. If I went on holiday for two weeks, would improvement activity stop or continue?
  6. Do my team hide bad news from me or bring it immediately?
  7. Am I modelling the standards I expect from others?
  8. Do I fix problems or fix the people who fix problems?

If these questions made you wince, that’s okay—it’s a starting point.

Pick one trait to focus on for 30 days. Maybe commit to a daily gemba walk. Just 20 minutes, same time every day. Ask, “What’s getting in your way today?” and listen. Or focus on Trait 2: next time a problem arises, stop yourself from giving the answer. Ask, “What do you think we should do?”

It will feel awkward, but stick with it. Changing ingrained habits isn’t easy, but the payoff is worth it. You’ll move from being the stressed-out boss holding everything together to the coach leading a team of problem solvers. Your factory will run better, and you might even enjoy your job again. If this resonates with you and you are looking for some support in making this shift, we can help. Sometimes it is hard to see the wood for the trees when you are in the thick of it. Our lean coaching and mentoring program is designed specifically for manufacturers who want to make this transition. We work with you on the shop floor dealing with real problems, not just theory in a classroom. Why not take a look? It might be the first step towards a calmer, more productive future for you and your factory. But for now, just try to ask one more question tomorrow than you did today. That is a good start.

Takt Time vs. Cycle Time: Understanding the Heartbeat of Your Factory

Posted on by Adam Payne

Every factory has a rhythm. Sometimes it’s a frantic, chaotic scramble. Other times, it’s a smooth, predictable pulse. If you’ve ever walked onto your shop floor and felt that sense of barely controlled chaos, the constant hum of expediting and last-minute changes, then you know what I’m talking about. The problem often isn’t that your people aren’t working hard enough. The problem is that the work has no heartbeat.

This is where Takt Time comes in. Think of it as the metronome for your entire operation, set perfectly to the rhythm of your customer’s demand. It’s the beat you need to hit. Cycle Time, on the other hand, is the actual rhythm your team is playing. It’s the time it takes to complete one piece at any given station. When those two rhythms are out of sync, you get noise instead of music. You get late orders, bulging inventory, and stressed-out team leaders.

For us here in the UK, this isn’t just a nice to have manufacturing theory. We’re dealing with volatile demand that can swing wildly from one month to the next. We’re facing skills shortages that make throwing more people at a problem a nonstarter. And the pressure from customers on lead times? It never lets up. In this environment, understanding and aligning your factory’s heartbeat isn’t an academic exercise. It’s a fundamental tool for survival and growth.

So, let’s cut through the jargon. In this post, I want to give you some practical, no-nonsense definitions, a few simple formulas you can use tomorrow, and some real examples from the kind of shop floors I walk through every week. We’ll look at how to use these two simple metrics to bring a sense of calm, predictable flow to your production.

The Core Concepts: Getting the Language Right

Before we start timing things with a stopwatch, we need to be crystal clear on what we’re actually talking about. Takt, Cycle, and Lead Time are often used interchangeably, and that’s where the confusion starts. To be honest, I’ve seen entire improvement projects go off the rails because the team wasn’t speaking the same language. Let’s fix that right now.

Takt Time: The Customer’s Rhythm

Takt is a German word, from Taktzeit, which translates to ‘cycle time’ or ‘beat’. It’s the rate at which you need to complete a product to meet customer demand. It is not a target set by a manager. It is not an engineering standard. It is a direct calculation based on two things and two things only: how much time you have available to work, and how many units the customer wants in that time.

The basic formula is beautifully simple:

Takt Time = Available Production Time ÷ Customer Demand

This is the heartbeat. If a customer wants 100 widgets per day, and you have 500 minutes of production time available, your Takt Time is 5 minutes per widget. This means a finished widget needs to roll off the end of your production line every 5 minutes to keep the customer happy. It’s a powerful concept because it links your shop floor directly to the marketplace. It’s the ultimate expression of customer pull.

Cycle Time: Your Process’s Rhythm

If Takt Time is what you need to do, Cycle Time is what you’re actually doing. It’s the total time it takes for a process to complete one unit from start to finish. You might measure the cycle time of a single operator at a workbench, a CNC machine, or an entire assembly cell. It’s the “click to click” time of the stopwatch.

Crucially, Cycle Time includes all the work that goes into one unit: the value adding time (drilling, welding, assembling) and the non-value adding time that’s part of the process (walking, picking up tools, waiting for a machine). What it doesn’t include are things like waiting for parts to arrive from a previous process or sitting in a queue. It’s the time that process is actively engaged on a single part.

Lead Time: The Whole Journey

Just to complete the picture, let’s briefly touch on Lead Time. This is the big one. It’s the total time a customer waits, from placing an order to receiving the goods. It includes all the process cycle times, but also all the waiting time in between. The piles of work in progress (WIP) sitting between stations? That’s all Lead Time. You can have super-fast cycle times at every station, but if products wait for days between each step, your lead time will be enormous. Aligning your cycle times to the Takt Time is one of the most powerful ways to slash that waiting time and dramatically reduce your overall lead time.

Calculating and Measuring: From Your Desk to the Shop Floor

Okay, theory is one thing. Let’s make this real. How do you actually figure these numbers out in a typical British factory?

How to Calculate Your Takt Time

Let’s imagine you run a single day shift at your facility in the Midlands. Your team is contracted for an 8-hour day.

First, you need your Available Production Time. This is not just the total shift time. You must be realistic.

  • Total Shift Time: 8 hours = 480 minutes
  • Less Morning Break: 15 minutes
  • Less Lunch Break: 30 minutes
  • Less Afternoon Break: 15 minutes
  • Less Team Briefing / Start up Checks: 15 minutes

So, your Net Available Production Time = 480 – 15 – 30 – 15 – 15 = 405 minutes.

This is the time you actually have available to make things. Now, you need Customer Demand. Let’s say your sales orders for the week show a consistent demand for a particular product family of 90 units per day.

Now you can do the calculation:

Takt Time = 405 minutes ÷ 90 units = 4.5 minutes per unit

Or, to make it easier to track on the shop floor, that’s 270 seconds per unit. This number is your North Star. Every 270 seconds, a finished product needs to be completed.

How often should you recalculate this? It depends on your demand stability. If your demand is pretty steady, a monthly calculation might be fine. But for many high mix UK manufacturers, demand can change weekly. In that case, you should probably recalculate it every Monday morning based on the new order book. It keeps the whole team focused on what the customer needs this week, not last month.

How to Measure Cycle Time on the Floor

This part requires leaving your desk and heading out to the gemba, the shop floor. The best tool for the job is often the simplest: a stopwatch and a clipboard.

Pick a process, say, a final assembly and test station. Your goal is to find out its true cycle time. Don’t just time it once. The first time you stand there with a stopwatch, I guarantee the operator will move like lightning. You need to get a representative sample. I’d suggest timing the full process for at least 10 to 20 consecutive units if you can.

Be transparent. Explain to the operator what you’re doing. “Hi Dave, we’re just trying to understand the process rhythm. Just work at your normal, safe pace. We’re timing the process, not you.”

Record the time for each unit. You’ll see variation. Maybe one unit needs a little rework. On another, the operator fumbles a part. A battery needs changing in a power tool. This is all part of the real cycle time. Don’t edit it out. After you have your samples, calculate the average.

Let’s say you timed 10 units at that assembly station and got these times in seconds: 280, 295, 270, 310 (a tricky one), 285, 275, 290, 280, 320 (a tool jam), 275.

The average cycle time for this station is the total of those times (2880 seconds) divided by 10 units, which equals 288 seconds.

Now we have our two critical numbers:

  • Takt Time (The Need): 270 seconds
  • Cycle Time (The Reality): 288 seconds

And right there, you’ve found a problem. A very important problem.

Spotting the Gap: Where the Music Goes Wrong

The ideal relationship is simple: every process in your value stream should have a cycle time that is equal to or, ideally, slightly less than the Takt Time. Never, ever greater.

When you compare the Takt Time to the cycle times of each station, you create a picture of your factory’s capacity and flow. I love doing this on a big whiteboard where everyone can see it. Draw a horizontal red line across the board representing your Takt Time of 270 seconds. Then, for each process step—cutting, machining, assembly, test, pack—you draw a vertical bar representing its average cycle time.

What you’ve just created is a line balance chart. And it tells you everything.

When Cycle Time is Greater Than Takt Time

In our example, the assembly and test station has a cycle time of 288 seconds, but the Takt Time is 270 seconds. This station is a bottleneck. It physically cannot keep up with the pace of customer demand. Every 270 seconds, the line needs a product, but this station takes 288 seconds. It falls behind by 18 seconds on every single unit.

The consequences? They’re probably all too familiar. A mountain of work in progress builds up before this station. The operators on the bottleneck station are constantly under pressure, probably skipping breaks or working unpaid overtime to catch up. Downstream processes are starved of work, waiting for parts. And ultimately, you miss your delivery promises. Your whole operation is dictated by the speed of its slowest point.

When Cycle Time is Far Less Than Takt Time

What about the other stations? You might find your cutting process has a cycle time of only 150 seconds. Great, right? Well, maybe not.

If a station is working much faster than the Takt Time, it leads to one of the deadliest wastes in manufacturing: overproduction. That cutting operator can produce a part every 150 seconds, but the next process only needs one every 270 seconds. So what happens? They keep working at their own pace and build up a huge pile of WIP.

This isn’t just inefficient; it’s dangerous. That excess inventory hides defects, costs a fortune in tied up cash, takes up valuable floor space, and creates a false sense of security. The business looks busy, but it’s busy creating waste.

By visualising the cycle times against the Takt Time, you can see instantly where your problems are. The bars that poke up above the red Takt line are your bottlenecks, and they are where you must focus all your improvement energy. The bars that are significantly below the line are opportunities for rebalancing work or multi skilling operators.

A Quick Story: Stabilising a Factory’s Heartbeat

I remember working with a medium sized engineering firm in the Northwest. Their on-time delivery was hovering around 75%, which was causing some serious friction with their key customers. The place felt manic. The production manager was a master firefighter, constantly juggling jobs and expediting orders. WIP was everywhere, stacked on pallets, clogging up the gangways.

The team felt they were at maximum capacity. “We can’t possibly make any more,” the manager told me.

Our first step was simple. We took their biggest product family and calculated the Takt Time. It came out at around 8 minutes per unit. Then we went out and measured the cycle times for the five main stages of production.

The results were a revelation for the whole team. We drew it up on a whiteboard. Three of the processes had cycle times of around 4 to 6 minutes, well below the 8-minute Takt. But one process, a complex manual assembly stage, had an average cycle time of over 11 minutes.

There it was. The bottleneck, clear as day. The entire factory, with all its expensive machines and skilled people, could only produce at the speed of that one overloaded assembly station. The other stations were overproducing like crazy to “keep busy,” which just buried the real problem in piles of inventory.

We didn’t need a massive investment. We focused all our attention on that one station. We did some simple 5S to organise the workspace. We created better component kits so the operator wasn’t searching for parts. We moved one small sub assembly task, which took about 2 minutes, to one of the under loaded upstream stations.

Within two weeks, the cycle time at the bottleneck station was down to 7.5 minutes, just under the Takt Time. And the effect was transformative. The flow of work smoothed out almost overnight. The piles of WIP started to shrink. The production manager went from firefighting to managing the flow. Three months later, their on-time delivery was at 98%, and they had freed up so much cash from the reduction in WIP that it paid for the next stage of their improvement journey. They had found their heartbeat.

Getting Started: Your First Steps

This all might sound great, but where do you begin? The key is not to try and boil the ocean. Start small, get a win, and build momentum.

Here are three quick wins you can try next week:

  1. Calculate Takt for One Key Product Family: Don’t try to do the whole factory. Pick one important value stream. Get the sales data, calculate your available time, and find your Takt Time. Write it on a whiteboard for everyone to see.
  2. Map the Cycle Times for a Single Line: Grab a stopwatch and walk that one value stream. Time each major process step. Don’t aim for perfection; aim for a good enough picture. Plot the cycle time bars against your Takt-Time line.
  3. Trial an Hour by Hour Board: At your newly identified bottleneck station, put up a simple board. Mark it out with the hours of the day. The target for each hour is simply 60 minutes divided by your Takt Time in minutes. At the end of each hour, the operator marks down the actual quantity produced. It makes the Takt visible and creates a simple feedback loop for the team.

Once you’re comfortable with these basics, you can move on to more advanced tools like full Value Stream Mapping to identify waste between processes, or more detailed bottleneck analysis. But the foundation is always the same: know the beat you need to hit and know the beat you’re actually hitting.

Listening to your factory’s heartbeat is the first step to controlling it. Takt Time and Cycle Time are not just numbers for engineers; they are the fundamental tools for creating a calm, predictable, and profitable manufacturing environment. They give you a shared language and a clear focus for improvement. So go on, find your rhythm.

And if you feel you need a guide to help you read the music and get your whole team playing in time, our lean coaching and mentoring programme is designed for exactly this journey. We can help you take these concepts from the page and make them a powerful reality on your shop floor.

The £50,000 Question Kevin Didn’t Ask: Why Your Lean Program is Failing in Silence

Posted on by Adam Payne

The CNC machine whirs, spitting out another finished component. Kevin, the operator, picks it up and runs the callipers over it, just like he has a hundred times today. He frowns. It’s close. It’s probably fine. But it’s not right. It’s at the very edge of tolerance, and he knows that by the time this batch gets to assembly, a few of them are going to cause a headache.

He looks over at his supervisor, Dave, who’s hunched over a spreadsheet, looking stressed. The board on the wall shows they’re slightly behind schedule. Stopping the line now would mean a difficult conversation, a lot of paperwork, and a definite earful about hitting their numbers. Everyone saw this coming. The tooling has felt off for a week, but the last time someone mentioned it, they were told to just keep an eye on it. So, Kevin puts the component in the ‘pass’ bin, takes a deep breath, and lets the machine run. He keeps his mouth shut.

This tiny, silent moment is where Lean methodologies go to die. It’s where safety risks are born, where quality defects multiply, and where your continuous improvement culture grinds to a halt. The missing ingredient isn’t a better tool or a more colourful board. It’s something a lot more human. It’s called psychological safety.

In the simplest terms, psychological safety is the shared belief that it’s safe to speak up. It means people feel they can flag a problem, question a process, admit a mistake, or even float a half-baked idea without fear of humiliation, embarrassment, or being labeled a troublemaker. It’s not about being soft. It’s about being smart. It’s about creating an environment where people feel empowered to contribute their full potential without fear of negative consequences.

What Psychological Safety Is (and Isn’t)

Psychological safety isn’t about lowering standards or creating a fluffy, everyone-gets-a-trophy environment. It’s the opposite. It’s the foundation of high performance. It’s the team climate that allows people to meet high standards. How can you expect perfect quality if people are afraid to point out defects? How can you improve processes if workers don’t feel safe suggesting better ways? You can’t. You just get silence. And silence, in manufacturing, is expensive and dangerous.

This isn’t just opinion. Amy Edmondson at Harvard Business School has studied this for decades, proving its link to learning and performance. Google’s ‘Project Aristotle’ famously found that the number one predictor of a high-performing team wasn’t who was on it, but how they interacted. The most important factor? Psychological safety. More than free lunches or fancy perks, it was the shared feeling that “I can take a risk and speak my mind without being humiliated.”

Psychological safety isn’t about being nice. It’s about fostering respectful, candid, and fearless interaction. It’s the difference between a team that just follows instructions and one that actively solves problems. One is compliance. The other is commitment. As a manufacturer, you know which one you’d rather have.

Psychological safety also doesn’t mean avoiding accountability. In fact, it’s the opposite. It creates an environment where accountability thrives because people feel safe enough to take ownership of their work, admit mistakes, and learn from them. It’s about creating a culture where people are encouraged to bring their best ideas forward, even if those ideas challenge the status quo. It’s about fostering a sense of shared responsibility for outcomes, where everyone feels invested in the success of the team.

When psychological safety is present, teams are more likely to innovate, adapt, and perform at their best. It’s not just about avoiding mistakes; it’s about creating an environment where people feel empowered to take risks, try new approaches, and learn from failures. This is especially critical in manufacturing, where the ability to adapt to changing conditions and continuously improve processes can mean the difference between success and stagnation.

Why Your Lean Programme is Stalling Without It

You’ve invested in Lean. You’ve done the 5S audits, put up visual management boards, and trained people on A3 problem solving. But is it really working? Or has it become a performance? A kind of compliance theatre?

The boards are updated just before the manager’s Gemba walk. Team huddles are one-word updates with everyone staring at their shoes. The suggestion box is full of cobwebs. Performance improved for a while, but now it’s plateaued.

This happens when you implement the tools of Lean without building the underlying culture. Lean isn’t a set of tools; it’s a set of behaviours.

  • Surfacing problems: Visual systems like Andon cords or SQDCP boards make problems impossible to ignore. But someone has to pull the cord or put a red magnet on the board. That’s an act of vulnerability, saying, “Something is wrong, and I need help.”
  • Running experiments: Continuous improvement involves trying new things, many of which will fail. If failure is met with blame, no one will volunteer to try something new. People will stick to the old, inefficient ways because they’re predictable.
  • Suggesting improvements (Kaizen): The best ideas for improving processes come from the people doing the work. But suggesting an improvement is implicitly a critique of the current process, which might be one their manager designed. It takes courage to say, “I think there’s a better way.”
  • Learning from failure: A Lean culture asks, “Why did the process allow this to happen?” A blame culture asks, “Who did this?” One leads to learning and improvement. The other leads to hiding mistakes.

Without psychological safety, your Lean tools are just wallpaper. People will go through the motions, fill out forms, and update boards, but they won’t engage their brains. They’ll do the bare minimum to stay out of trouble. Your Lean initiative, meant to unlock potential, becomes another box-ticking exercise.

Lean is fundamentally about people. It’s about empowering the people closest to the work to identify problems, suggest improvements, and take ownership of solutions. But without psychological safety, this empowerment is impossible. People won’t speak up if they fear being blamed, ridiculed, or ignored. They won’t take risks if they believe failure will be punished. And they won’t engage in continuous improvement if they feel their ideas won’t be valued.

The Warning Signs and Costs of Silence

How do you know if you have a psychological safety problem? It’s rarely dramatic. It’s a collection of small, subtle signals. It’s the silence where there should be a question. It’s the workaround where there should be a root cause analysis.

Common warning signs include:

  • Quiet Meetings: You ask, “Any problems?” and are met with silence. You know there are issues, but no one voices them.
  • Blame Finds a Person, Not a Process: A defect gets through, and the first question is, “Who signed this off?” instead of, “What part of the system failed?”
  • Shooting the Messenger: Someone raises a concern and is met with defensiveness or told, “We don’t have time for this.” They learn not to bother next time.
  • The Hero and the Workaround: An operator is celebrated for keeping an unreliable machine running with workarounds. No one asks, “Why don’t we fix the machine?”

These aren’t just ‘people problems.’ They directly impact Safety, Quality, Delivery, Cost and People (SQDCP):

  • Safety: Near misses go unreported. That wobbly pallet rack or small oil leak everyone steps over? People see them but don’t report them until they cause an accident.
  • Quality: Kevin’s silence about the CNC machine translates into rework, customer complaints, and damage to your reputation.
  • Delivery: Small issues grow into big ones that stop the line, causing unplanned downtime and missed deadlines.
  • Cost: Rework, accidents, and downtime add up. So does employee stress, burnout, and turnover.
  • People: People who don’t feel heard will leave, taking their skills with them.

The costs of silence are not just financial. They’re also cultural. A culture of silence breeds disengagement, mistrust, and apathy. It erodes morale and undermines teamwork. It creates an environment where people feel like cogs in a machine, rather than valued contributors to a shared mission. And over time, it drives away your best people—the ones who care enough to want to make things better.

How to Build Psychological Safety: Practical Steps for Leaders

This isn’t something you can fix with a memo or a poster. It’s built, conversation by conversation, by leaders on the shop floor. It’s about behaviours.

  1. Frame the Work as a Learning Problem: Acknowledge complexity. Say, “We’ve never done this exact run before, so we’ll need everyone’s eyes on it,” or “This is tricky; we’ll likely run into issues, and that’s okay.” This gives people permission to speak up.
  2. Respond to Bad News with Curiosity, Not Anger: If an operator says, “I think I’ve scrapped a pallet of parts,” fight the urge to react with frustration. Instead, say, “Thank you for telling me. Let’s look at it together.” This signals that bad news is valued.
  3. Model Fallibility: Admit when you don’t know something or make a mistake. Saying, “I messed that up, my apologies,” shows it’s okay to be vulnerable.

Embed these behaviours into existing Lean routines:

  • On Gemba Walks: Use them to listen and learn. Ask, “What’s getting in your way?” instead of, “Why is this a mess?”
  • In Daily Huddles: Ask, “What did we learn yesterday?” or “What’s one small thing we could fix today?”
  • During Problem Solving: Focus on the process, not the person. Use the 5 Whys to find systemic causes.

Simple Starting Moves for Your Factory

This can feel like a big cultural shift, but you can start small:

  1. Weekly ‘No Blame’ Improvement Huddle: Pick one team. Spend 15 minutes discussing what went wrong that week, with a strict no-blame policy. The leader’s job is to listen, say thank you, and ask, “What’s one small thing we could try next week?”
  2. Visible ‘Bugs & Ideas’ Board: Create a board with two columns: “Things That Bug Us” and “Ideas to Try.” Leadership must review it daily and act on what’s there.
  3. Instil the ‘Thank You’ Habit: Train supervisors to say, “Thank you for speaking up,” whenever someone raises a problem or idea.

Start in one area. Measure the number of issues raised and improvements implemented. As safety increases, so will contributions. Use this data to spread these practices across the facility.

The Foundation You Can’t Ignore

Psychological safety isn’t a ‘soft skill.’ It’s the hidden infrastructure of operational excellence. You can have the best tools and processes, but if people are afraid to speak up, you’re operating with one hand tied behind your back.

Your people see problems and opportunities before you do. Unlocking that intelligence is your biggest competitive advantage. It starts with making it safe for them to speak.

Take a walk around your factory floor tomorrow. Look at the conversations happening—and the ones that aren’t. Ask yourself:

Where are people staying silent, and what is that silence costing us?

If you’re not sure of the answer, or don’t like the one that comes to mind, we can help. Our Lean Coaching and Mentoring Programme helps leaders foster a culture where problems are surfaced early, ideas are shared freely, and continuous improvement becomes a reality—not just a slogan.