plan do check act

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.

Continuous Improvement: The Simple Philosophy That Can Help Your Business Thrive

Posted on by Adam Payne

Continuous Improvement, The 1% rule, or Marginal Gains, whatever terminology you want to call it, they are all similar in philosophy and application. It is the idea of focusing on small incremental improvements to grow your business easily. The most successful businesses are always striving to improve to stay ahead of their competition.

In this blog I’ll explain how the philosophy of small incremental improvements can improve your business. This is a technique that many successful companies use in addition to Lean Thinking – a company’s philosophy of eliminating waste. It has been used for decades and can be found in micro businesses right through to corporate business models across industry and service sectors.

I’ve been a lean Sensei for 25+ years and implemented these small incremental changes in Hairdressers to Big Corporate Manufacturers. By implementing these marginal gains, it’s possible to make a huge impact on the performance of your company in a relatively short period of time. It’s Simple! and the data has proven time and time again that this method works!

You CAN NOT ignore the role of Continuous Improvement in business – and here’s why.

What is Continuous Improvement?

“Be Better Today Than You Were Yesterday, Plan To Be Better Tomorrow Than You Are Today” is a quote I have lived by for 25+ years of my working career.

The 1% Rule is a relatively new contender but has now become a business management philosophy that states that you should focus on improving your product or service by at least 1% every day. It was developed by Sir Dave Brailsford, former performance director of British Cycling, and used as a means to achieve micro improvement in the British Cycling Team. The concept behind the 1% rule is simple: if you focus on small improvements, you can achieve significant results over time.

The concept of the 1% rule in my opinion is based on Kaizen, which is Japanese for “continuous improvement.” Kaizen was first introduced to the Western World in the 1970s by Toyota, who taught that companies should embrace a culture of continuous improvement rather than trying to maximise efficiency one big hit at a time. Kaizen aims to reduce inefficiency in its 3 major forms. These are muda (waste), muri (overburdening work), and mura (inconsistency of work).

When we look at these strategies, we can see how the power of tiny gains really makes a difference.

1% Improvement Every Day 1.01365 = 37.78%

1% Decline Every Day 0.99365 = 0.03%

How does the Continuous Improvement work in business?

The PDCA Cycle, also known as the Plan-Do-Check-Act Cycle, is a model for continuous improvement that uses four phases to drive process changes through the organisation. This linked to the 3 forms of in-efficiency, muda (waste), muri (overburdening work), and mura (inconsistency of work) gives a superb structure and focus for all employees.

The PDCA Cycle Explained:

Plan: In this phase, you identify a problem or opportunity for improvement. You also create a plan for how to solve the problem or capitalise on the opportunity.

Do: In this phase, you carry out your plan and implement your solution.

Check: In this phase, you review your work to see if it was successful in achieving its objectives and if there are any unintended consequences of your actions.

Act: In this phase, you make adjustments based on what you learned in the check phase and continue with another iteration of the cycle to drive continuous improvement.

By continuously improving your processes, your organisation can achieve higher levels of performance at lower cost. This not only improves customer satisfaction but also helps an organisation achieve its goals faster.

The key to this and building on the marginal gains is to empower everyone to make these short, sharp improvement cycles small enough to be managed at a local level. This will enable them to use their creativity and judgment to find the most effective solution for their teams and customers.

The second aspect of this is that the improvements have to be visible and celebrated. This is not just about being proud of what you have achieved, but also about helping others see what you have done. This creates an environment where people are constantly looking for new ways to improve, which in turn leads to innovation.

The third aspect is that it has to be built into every process in a business. You cannot expect people just to do it because you asked them to – they need processes that encourage continuous improvement across everything they do from how they order stock through the distribution system all the way through customer support.

Why use the Continuous Improvement?

Continuous improvement is a process that can be used in every business setting of all sizes and all sectors, from small businesses to large corporations.

It’s Good for Business

The benefits of continuous improvement can be seen throughout the business world. By using this approach, companies are able to stay competitive while providing better quality products and services at lower prices. This helps them grow their customer base while increasing their profit margin through increased sales volume.

It’s Good for Employees

Continuous improvement is also good for employees because it provides them with job security. If you have implemented a continuous improvement program in your company, then you have created an environment where everyone is constantly making improvements which makes your company more competitive in the marketplace and less likely to be outsourced in favour of cheaper labour costs elsewhere.

  • People feel empowered because they have more opportunities for growth and development.
  • Employees feel more engaged because they feel like their work matters and makes a difference.
  • The company attracts better talent because employees want to work for companies that are doing great things for their customers.

Does Continuous Improvement really work?

Yes! Continuous Improvement absolutely works!

I’ve implemented and completed Lean Thinking and Continuous Improvement Projects in 100+ businesses over my career and have no doubt on the impact it can make.

On my very first project back in the 1990’s we took a machine change over from 480 mins to sub 20 mins, saving a £250K capital expenditure. As Senior Exec I’ve saved £10m+ year on year through the implementation of Continuous Improvement. I’ve seen every employee within a business take pride in completing numerous small incremental changes that compound in delivering a huge result.

In order to achieve these results, you need to be prepared to put in the work. It’s not an overnight process—it takes patience as well as an unwavering commitment to creating positive change at every level of your organisation. But once you’ve seen the first results, you’ll find it’s worth every minute invested!

You’ve only got to read some of our Case Studies to realise the potential.

Takeaway: Challenging yourself and your employees to make small improvements every day can have a dramatic effect on your overall business growth.

Why Standardised Work Isn’t Boring (And Why It’s The Secret Weapon You’re Ignoring)

Posted on by Adam Payne

Right, let’s talk about something that, on the surface, sounds about as exciting as watching paint dry. Standardised work. I know, I know. The phrase itself probably conjures up images of old black and white factory footage, rows of identical workers doing identical tasks with robotic precision. It feels rigid, a bit soul crushing, and completely at odds with the dynamic, creative, and, let’s be honest, slightly chaotic way most of our businesses actually run.

And that’s the problem right there. It’s one of the most powerful, transformative tools in the entire lean manufacturing playbook, yet it remains one of the least understood and least used. Why? Because we’ve completely misunderstood what it’s for.

From my own experience working with countless teams, I can tell you this with absolute certainty: without standards, you do not have continuous improvement. What you have is chaos. You have firefighting. You have good days and bad days that you can’t quite explain. You have a constant, draining variability that makes progress feel like guesswork.

I’ve heard all the rebuttals, and I’m sure you have too. They usually come from very smart, passionate people who genuinely believe their work is different.

“We don’t make cars, you know.”

“You see, our process is creative. It can’t be standardised.”

“We’re unique… this isn’t an assembly line!”

And I get it, I really do. The objection comes from a good place, a desire to protect the craft, the human element, the spark of ingenuity that makes their work special. But here’s the thing I always say in response. Everyone, and I mean everyone, works a process. That process, whether you’re designing a marketing campaign, admitting a patient to a hospital, writing code, or yes, building a car, can only be doing one of two things. It’s either creating value for your customer, or it’s destroying it. Which would you rather it be?

It doesn’t matter if you’re delivering lifesaving patient care or assembling a gearbox. The end result relies on a sequence of highly coordinated tasks and processes. When you find a way to standardise the best-known method for that sequence, you’re not killing creativity. You’re clearing the path for it. You are beginning the journey of fundamentally improving your work and eliminating the significant, often hidden, sources of waste that frustrate your team and disappoint your customers.

The Great Misunderstanding: “But Our Work is Special”

Let’s dig into that pushback a little more, because it’s the single biggest barrier to getting started. The idea that standardisation is only for the factory floor is a myth, but it’s a persistent one.

Imagine the head of a busy A&E department. Their environment is the definition of unpredictable. Every case is different, every patient unique. The idea of a “standard” way of working seems almost insulting to the skill and judgement of the doctors and nurses. But think about the process of triage. Is there a standard set of questions to ask to assess urgency? Is there a standard procedure for checking vital signs? A standard location for the crash cart? Of course there is. These standards don’t restrict a doctor’s ability to make a complex diagnosis. They do the opposite. They handle the repeatable, critical basics flawlessly every single time, freeing up the doctor’s mental energy to focus on the difficult, unique aspects of the patient’s condition. Without those standards, you get chaos, missed steps, and potentially tragic errors.

Or what about a team of software developers? They’re the epitome of modern knowledge work. Their job is to solve complex problems with elegant code. You can’t standardise creativity, right? Well, no, you can’t standardise the moment of inspiration. But you can absolutely standardise the process around it. How does the team handle bug reports? Is there a standard way to test new code before it’s deployed? A standard checklist for releasing an update to prevent servers from crashing at 2 a.m.? These standards don’t tell a developer how to write a brilliant algorithm. They create a stable, predictable framework so that their brilliant algorithm can be delivered to users reliably and without causing new problems. They prevent the team from constantly reinventing the wheel on routine tasks.

The truth is, every job has elements that are repeatable. Standardised work isn’t about the whole job; it’s about those repeatable parts. It’s about agreeing, as a team, on the best way we currently know how to do a specific task. By doing this, we create a baseline. A stable foundation. And you cannot improve something that isn’t stable. Trying to improve a chaotic process is like trying to measure a moving object with a ruler made of elastic. The data you get is meaningless.

So, the next time you hear “we’re different,” the answer isn’t to argue. It’s to ask a different question. “What parts of our work are repeatable? And for those parts, have we agreed on the best way to do them?” The conversation that follows is often the first real step toward meaningful improvement.

So, What Is It, Really?

At its heart, standardised work is incredibly simple. It’s the documented, current, best practice for completing a task. It’s a living document that captures the most efficient and effective way we know right now to get a job done to the highest quality. The goal is to ensure that the same results are achieved, in roughly the same amount of time, with the same level of safety and quality, regardless of who on the team completes the task.

The key word in that definition is current. This is not about carving a process into stone tablets to be handed down from on high. It’s not a rigid, top-down procedure manual that gets written once and then gathers dust in a forgotten folder on the company server. To be honest, that kind of documentation is worse than useless; it breeds cynicism.

Standardised work is the opposite of that. It’s a tool for the people actually doing the work. It’s a dynamic agreement, a hypothesis that says, “Based on everything we know today, this is the best way to do this.” And tomorrow, we might find a better way. When we do, we test it, prove it, and then we update the standard. It’s the engine of kaizen, or continuous improvement.

Think of it like a professional chef’s recipe. A Michelin starred chef has a precise, documented recipe for their signature dish. Every ingredient is measured, every step timed, every technique specified. This doesn’t stifle their creativity. It ensures that every customer who orders that dish gets the same brilliant experience. The standard recipe is the foundation. It’s what allows the kitchen brigade to perform flawlessly under pressure. The creativity happened when the chef was developing the recipe, experimenting with ingredients and techniques. And if they discover a better way to sear the scallops or a new spice for the sauce, they don’t just do it randomly. They test it, perfect it, and then they update the master recipe. They change the standard.

That is what we’re aiming for. A clear, agreed upon method that removes ambiguity and inconsistency from our routine tasks, freeing up our minds to focus on the real problems and the next improvement.

The Building Blocks of a Good Standard H2

While the specific document might look different in an office versus on a factory floor, the core principles and key elements remain remarkably consistent. To build effective standardised work, you generally need to understand three key components.

Standard Work Elements

1. Takt Time

This is a concept that often gets confused with cycle time, but they are very different things. “Takt” is a German word, and it means beat, or rhythm, like the baton of a conductor keeping an orchestra in time. In a business context, Takt time is the rhythm of your customer demand. It’s the rate at which you need to complete a product or a service to keep up with what your customers are asking for.

The calculation is simple:
Takt Time = Your Available Production Time per Day / Your Customer Demand per Day

Let’s use a non-manufacturing example. Imagine a mortgage processing team that has 420 minutes of available work time in a day (after breaks and meetings). The company receives, on average, 70 mortgage applications per day that need to be processed.

Takt Time = 420 minutes / 70 applications = 6 minutes per application.

This number is profound. It’s the heartbeat of the operation. It tells the team that to meet customer demand, one completed application needs to roll off their production line, so to speak, every six minutes. It’s not about how long it actually takes to do the work (that’s cycle time). It’s about the pace required to satisfy the market. Understanding Takt time helps you design your processes. If the team’s current process takes 10 minutes, you immediately know you have a problem. You can see the gap between your capability and your customer’s expectation, and that’s where your improvement efforts should focus. It prevents overproduction (working faster than needed, which builds up inventory and waste) and underproduction (working too slow, which leads to backlogs and unhappy customers).

2. Work Sequence

This is the most straightforward part. As the great Taiichi Ohno of Toyota put it, it is “The time for an employee to do a prescribed task and return to his original stance.” It is the actual step by step sequence of actions that a person performs to complete one cycle of their work within the Takt time.

A good work sequence is clear, logical, and focuses on the most efficient path of action. It’s not a dense paragraph of text. It’s usually a numbered list, often accompanied by pictures or diagrams, that breaks the task down into its core elements. What is the first thing you do? What is the second? Where do you get your materials from? What tool do you use? It captures the how of the job in a way that is easy for anyone to follow. This ensures that everyone is following the same best practice, which is the key to reducing variation and defects.

3. Standard Inventory

This third element is often overlooked, especially in service or office environments. In manufacturing, it’s easy to understand. It refers to the minimum number of parts or materials needed at a workstation to complete the work smoothly without interruption. You need enough to keep working, but not so much that you’re creating clutter and excess inventory.

In other sectors, the “inventory” might be different, but the principle is the same. For a software developer, it could be the number of open tasks in their “to do” column. Too few and they risk being idle; too many and they suffer from context switching and an overwhelming workload. For a call centre agent, it might be the number of reference documents they need open on their screen to answer customer queries effectively. For a doctor, it could be the standard number of patient files to have ready for their next appointments.

Standard inventory is about defining the minimum resources necessary to perform the job according to the standard work sequence and within the Takt time. It’s about ensuring the process flows without hiccups or delays caused by searching for information, tools, or materials.

Putting It All Into Practice: A Few Ground Rules

Knowing the theory is one thing, but actually creating and sustaining a culture of standardised work is another. It requires a thoughtful, human centred approach. Here are a few things to bear in mind.

First, and most importantly, involve the employees. The people who do the work every day are the experts. A manager sitting in an office trying to write a standard for a task they haven’t performed in years is a recipe for disaster. The standard will be wrong, and the team will resent it and ignore it. The best standards are created when a leader facilitates a conversation with the team, at the place where the work is done. You observe the process together, you time the different steps, and you collectively agree on what the current best practice is. This builds ownership and engagement. When the team creates the standard, they are far more likely to adhere to it and, even better, to improve it.

Focus on the gritty details. A standard that is too high level is useless. Its purpose is to reduce variation, and variation lives in the details. You need to capture the little nuances, the “tricks of the trade.” I remember working with one process where an associate had to physically lean on one part to get another part to fit correctly. A slight tolerance stack up in the components meant it was the only way. This “knack” had to be written into the standard work. Now, was that the long-term solution? Of course not. But documenting it made the problem visible to everyone, including the engineers. It quantified the issue. Imagine the lost time and production if a new person started, wasn’t told about the trick, and spent hours struggling. By documenting the knack, we created a temporary standard while a permanent engineering solution was developed to fix the root cause. Without that detail, the problem remains hidden in tribal knowledge.

Use visuals whenever you can. Our brains are wired to process images far more quickly and effectively than text. A single photograph with a few key annotations can convey more than a full page of written instructions. Use diagrams, photos, examples, and even colour coding to bring your standard work to life. A picture really is worth a thousand words, and it helps overcome language barriers and differences in reading comprehension. The goal is instant clarity.

Make it accessible. This seems obvious, but it’s a common failure point. The documentation is no good if it’s locked in a filing cabinet or buried in a complex server directory. The standard work needs to be available at the point and time that the work is actually being performed. Laminated sheets at the workstation, a monitor displaying the steps, a tablet with the instructions readily available. If a team member has to walk away from their work area to find out how to do their job, the system has failed.

Finally, build a system to innovate. This is the crucial point that prevents standardisation from becoming stagnation. While you don’t want employees deviating from the standard work on a whim, you absolutely must have a clear and simple process for them to suggest improvements. When someone has a new idea, a better way, there needs to be a method to consider it. This is often handled through a governance process or a kaizen suggestion system. It allows the new idea to be tested, analysed, and, if it proves to be better, for it to be approved and rolled out as the new standard for everyone. This creates a positive feedback loop. It tells the team, “We value your expertise, and we want your ideas.” The standard isn’t a cage; it’s simply the starting line for the next improvement.

Standardised work isn’t the most glamorous tool. It doesn’t have the futuristic appeal of AI or automation. But it is, without a doubt, the bedrock of operational excellence. It’s about creating stability in a chaotic world. It’s about respecting the people who do the work by capturing their collective knowledge. And most of all, it’s about building a solid foundation, a floor from which your entire team can rise, together, to new levels of performance. It’s time we stopped dismissing it and started seeing it for what it truly is: the starting point of all meaningful improvement.

Ready to Go Beyond the Basics?
Body: Standard Work is a cornerstone of Lean, but it’s just one tool in the toolbox. Our Lean Green Belt training gives you the complete framework to lead impactful improvement projects from start to finish.
Learn More About Green Belt Certification


>

0330 311 2820

Book a Return Call at a time that Best Suits You “HERE”