Root Cause Analysis in Food Manufacturing

The Food Industry Hub Blog

Food Industry Hub blog

The Food Industry Hub blog includes practical discussion for food manufacturing professionals across technical, cultural, management and professional themes.

This post is part of the category:

Introduction

Imagine you’re a food manufacturer facing recurring product defects. You’re firefighting the symptoms, but what if you could tackle the root of the problem instead? That’s where Root Cause Analysis (RCA) comes into play. It’s a proactive method to identify, address and, importantly, prevent issues from reoccurring. It’s not just about fixing problems, it’s about creating a seamless, efficient operation. Intrigued about how RCA can revolutionise your manufacturing process? Stay with us as we unpack this crucial tool further.

As we dive into the topic, you’ll be interested to know that Food Industry Hub offers integrated management systems for food manufacturers, which you can use to strengthen your assurance processes.

Table of Contents

Key Takeaways

  • Root Cause Analysis (RCA) in food manufacturing involves identifying underlying problems causing symptoms like product defects or inefficiencies.
  • The RCA process comprises defining the problem, gathering data, identifying possible causes, analysing the root cause, and developing corrective actions.
  • Tools used in RCA include the 5 Whys, Fishbone Diagram, Pareto Analysis, Failure Mode and Effects Analysis, and Fault Tree Analysis.
  • RCA benefits include improved problem-solving, increased efficiency, risk reduction, enhanced decision-making, and continuous improvement in food manufacturing processes.
  • Accurate data collection and analysis, despite potential challenges, is crucial for effective RCA and successful problem resolution in food manufacturing.
Concepts in Root Cause Analysis

Key Concepts in Root Cause Analysis

You’re about to explore key concepts in root cause analysis.

You’ll understand the difference between a symptom and a root cause, learn about causal relationships, and discover why prevention is more beneficial than just correction.

It’s all about pinpointing problems at their origin to ensure they don’t recur.

Symptom vs. Root Cause

In food manufacturing, understanding the difference between a symptom and the root cause is very significant. These two terms, while often used interchangeably, hold very different meanings in root cause analysis.

A symptom is merely a sign, an indication of something that’s gone wrong. It’s what you see on the surface. For instance, if a batch of cookies comes out of the oven burnt, the burnt cookies are a symptom. It’s easy to spot, but it doesn’t tell you why the problem occurred.

On the other hand, the root cause is the underlying reason that led to the symptom. It’s what’s lurking beneath the surface. If we take the burnt cookies example, the root cause could be a faulty oven sensor, an error in the baking time, or perhaps a mistake in the recipe itself.

When you’re dealing with a problem, don’t just focus on the symptoms. Dig deeper. It’s crucial to identify and address the root cause. By doing so, you’re not just fixing the current issue, but you’re also preventing future ones.

Causal Relationships

Ever wondered how one minor oversight in the food manufacturing process can trigger a chain of events leading to a significant issue? That’s where understanding causal relationships comes in.

Understanding causal relationships can help you comprehend how different elements in the manufacturing process interlink and influence each other. It’s like piecing together a complex puzzle, where each component, no matter how small, has a role to play.

One error, like a temperature fluctuation in a cooking process, can have a knock-on effect, leading to non-conforming product, waste, and potentially even recalls.

But it’s not just about identifying these relationships. It’s also crucial to understand the depth and breadth of these connections. How strong is the link? How many steps are there in the chain of events? Are there multiple, interconnected causes?

Prevention, Not Just Correction

Understanding and identifying causal relationships in food manufacturing is only the first step. The ultimate objective is prevention, not just correction. In other words, it’s about stopping problems before they even start.

You see, root cause analysis isn’t just about finding out what went wrong. It’s also about figuring out how to prevent the same thing from happening again. That’s why it’s so important to focus on prevention, not just correction.

When you’re carrying out root cause analysis, you shouldn’t just be looking for the cause of a problem. You should also be looking for ways to prevent it. By doing this, you’re not only solving the current problem but also preventing future problems.

The ultimate objective is prevention, not just correction.

RCA Process Steps

Now, let’s walk through the RCA process steps.

First, you’ll need to define the problem, then gather the necessary data.

Afterwards, you’ll identify possible causes, analyse the root cause and finally, develop corrective actions.

Define the Problem

Identifying the problem is your initial step in the RCA process. As a food manufacturer, you’re likely to encounter a myriad of issues, ranging from quality defects to operational inefficiencies. The way you approach these will depend heavily on how the original problem is framed or presented. So, ‘defining the problem’ extends beyond acknowledging the occurrence of a fault and significantly influences the rest of the process.

To illustrate, think about the following problem statements and how they might shape the subsequent root cause analysis:

• A piece of equipment malfunctioned.
• The conveyor belt at the in feed of oven 3 stopped running so product could not be loaded into the oven.
• The conveyor belt at the in feed of oven 3 stopped running for the sixth time in two weeks.
• When there are mechanical issues on line 3, there is often a delay of up to two hours before an engineer becomes available to fix the equipment.

In each of the above cases, the definition of the problem is slightly different – even though the circumstances and presentation of fault may be identical.

When beginning a root cause analysis, defining the problem correctly might require some critical thinking as to whether a reported fault represents an underlying issue, is symptomatic of a problem, or forms part of a trend which is itself indicative of a problem.

Gather Data

Once you’ve clearly identified and articulated the problem, the next step is to gather data. This step is crucial in the Root Cause Analysis (RCA) process, particularly in the food manufacturing industry.

It’s not just about collecting information randomly—you need to gather relevant, accurate, and comprehensive data to understand the depth and breadth of the issue.

You might be wondering where to start. Well, data can come from various sources such as quality control records, equipment logbooks, production schedules, customer complaint records, internal nonconformance trending, and simply by talking to operators and managers for the relevant processes.

Remember, you’re not just looking for data that directly relates to the problem. You’re also interested in information that gives the context of the problem like environmental conditions, operational changes, or new personnel.

While gathering data, it’s important to keep an open mind. Don’t jump to conclusions or make assumptions. You’re laying the groundwork for discovering the root cause, so ensure the data you collect is unbiased and factual.

Data gathering should be exploratory rather than confirmational. In other words, you should try to gather data in an open-minded way That enables information about the problem and possible causes to emerge, rather than making assumptions and gathering data that supports those initial leanings.

Stick to the facts, and don’t let personal opinions or hunches steer your data collection. You’ll need a solid foundation of information to correctly identify possible causes in the next step.

Identify Possible Causes

With your data at hand, it’s time to dive into the possible causes of the problem. This step in the root cause analysis (RCA) process is all about brainstorming and being thorough.

Don’t rush it; every possible cause should be considered, no matter how small it might seem.

Start by looking at your data. What patterns emerge? Are there inconsistencies in the production process, equipment failure, or human error? Once you’ve identified these patterns, you can start making a list of potential contributing factors that resulted in the manifestation of the problem.

Remember, you’re not looking for the definitive cause just yet. You’re compiling a list of possibilities.

Don’t discount anything at this stage. Even the most unlikely cause could turn out to be significant.

Analyse the Root Cause

Now, you have a comprehensive list of potential causes/contributing factors. Your next step? Dive deeper and analyse these to identify the root cause. It’s not about pointing fingers or laying blame; it’s about understanding what’s really going on beneath the surface.

Remember, you’re looking for the cause that, if eliminated, would prevent the problem from occurring. It’s not enough to find a cause that merely contributes to the problem.
Whatever problem is identified at the onset of the root cause analysis May have had one or more immediate/proximal causes. Often, those proximal causes are merely symptomatic of deeper systematic issues – which could be expressed in a variety of ways. This is why it’s important to correctly identify the nature of the problem, the immediate circumstances (causes/contributing factors) that led to the problem, and any weaknesses in the quality management system that made it possible for the problem to emerge.

It’s helpful to hold in mind the question ‘what assurance system or control measure should have prevented this problem from occurring, and how is it possible for that system to have failed?’.

Alternatively, you can think about an identified problem as falling within the remit of one or more control systems – So ask questions like…

• Should this problem have been prevented by a prerequisite programme? If so, does the root causes lie in the adequacy of the prerequisite programme?

• Should this problem have been prevented by a management process? If so, does the root cause lie in the adequacy of a procedure, compliance with instructions, or training?

This type of inquiry into the root cause steers the investigation from immediate approximal contributing factors toward the root cause.

Develop Corrective/Preventative Actions

After identifying the root cause, it’s your job to develop effective remedial actions that will prevent the issue from reoccurring. Corrective actions are solutions formulated to directly address the problem, while preventative actions are intended to work on the root cause to prevent the same problem from happening again.

First, brainstorm a list of potential corrective actions. Consider the resources available, the practicality of the solution, and the impact it can have on the problem. Be sure this list is comprehensive, considering all possible solutions.

Next, evaluate and rank these solutions. You’ll want to select the most effective.

Think about the corrective and preventative actions available to you, and whether it would be feasible for the root cause of the problem to exist after the implementation of these actions. Highly effective preventative actions would make it inconceivable for the same loss of control to emerge after their implementation.

Once you’ve chosen the most promising corrective actions, it’s time to create a detailed action plan. Identify the steps necessary to implement the solution, who’ll be responsible for each step, and when each step should be completed.

Implement and Monitor

Have it’s helpful to think about corrective and preventative action plans as falling into the Deming cycle (plan do check act).

If the root cause analysis as add identified a range of distinct contributing factors pointing to a root cause for the emergent problem, the corrective and preventative action plan should ideally include remedial actions to address all of the contributing factors as well as the root cause.

It’s a sector wide convention to refer to ‘the root cause’ as a singular – Which is helpful in that it places a focus on root cause over proximal causes… but potentially misleading in that it implies that there will be only one root cause. In fact, the outcome of the root cause analysis will often be layered – with numerous proximal contributing factors and one or more root causes that enabled those contributors.

The corrective and preventative action plan should include remedial actions to resolve the problem as it originally presented, correct for any proximal causes and associated risks, and eliminate the underlying root cause(s) so as to prevent the problem from recurring.

Distinct actions may be undertaken by different individuals within your team. This might be a reflection of department, function, or area of ownership. There may be different time scales for implementation depending on importance/severity, resource requirements, and practical constraints The limit the speed of implementation.


Following the plan do check act protocol, the effectiveness of any remedial actions should be verified After their implementation – with appropriate course correction where necessary.

Every possible cause should be considered, no matter how small it might seem

Common Tools Used in RCA

Now, let’s turn our attention to the common tools you’ll use in RCA.

These includes the 5 Whys, the Fishbone Diagram (also known as the Ishikawa Diagram), the Pareto Analysis, the Failure Mode and Effects Analysis (FMEA), and the Fault Tree Analysis (FTA).

You’ll find each of these tools invaluable in identifying, understanding, and addressing the root causes of problems in food manufacturing.

5 Whys

The ‘5 Whys’ is a common RCA tool you can use. You start with the end problem and ask ‘why’ five times, or until you reach the root cause. It’s simple, but it’s also powerful. It forces you to look past symptoms and uncover the underlying issues.

The ‘Whys’ are the series of questions you ask to drill down into the root cause of a problem. They’re the key to unlocking what went wrong and how to prevent it from happening again.

• Start out with the statement of the problem, and ask why did the problem occur? Whatever the answer to that question (the first ‘why’) is can be taken as approximal cause or contributing factor that resulted in the manifestation of the problem.
• Next, ask why that contributing factor was allowed to take effect – So why did the contributing factor that allowed for the emergence of the problem exist?
• Continue to ask ‘why’ for every proximal cause yielded by the investigation Until it is impossible to go back any further and the ultimate root cause is identified.

For instance, if a food product is spoiling prematurely, you don’t stop at ‘the refrigeration unit failed’. You ask, ‘why did the unit fail?’ and ‘why wasn’t it noticed?’ until you’ve identified the root cause.

Don’t be afraid to ask ‘why’ more or fewer times as needed. The number isn’t set in stone. What’s important is that you’re thorough, and you don’t stop until you’ve found the root cause.

That’s how you’ll prevent the issue from recurring, saving time, money, and potential damage to your reputation.

Fishbone Diagram (Ishikawa Diagram)

Your toolkit for Root Cause Analysis isn’t complete without the Fishbone Diagram, also known as the Ishikawa Diagram. This powerful tool helps you identify, explore, and graphically display all potential causes related to a problem or condition.

Imagine a fishbone’s structure. At the head, you’ve got your problem or condition. The spine represents the ‘root cause,’ and the ribs are potential contributing factors. You’ll sort these contributing factors into categories, often based on the 6Ms: Man (People), Method (Processes), Machine (Equipment), Materials, Measurements, and Mother Nature (Environment). This helps organise your thoughts and stimulate brainstorming.

In a food manufacturing context, let’s say you’re experiencing a drop in product quality. You’d place this at the head of your fishbone. Then, explore each category for potential causes. Perhaps manpower is an issue due to insufficient training. Maybe the machines are obsolete, or the materials could be subpar.

The Fishbone Diagram doesn’t just list potential causes; it also shows their relationships, which allows you to identify areas of focus. Remember, the aim isn’t to assign blame, but to uncover the root cause and improve your processes.

Pareto Analysis

Eighty percent of your problems could be stemming from just twenty percent of the causes, according to the Pareto Principle. This principle is the backbone of Pareto Analysis, a tool you’ll find invaluable in Root Cause Analysis (RCA).

Pareto Analysis helps you identify, prioritise, and tackle the causes that have the most significant impact on your problem. It’s a simple yet powerful technique. You start by listing the causes of a problem, then assign a score to each based on its severity or frequency.

Next, you’ll create a Pareto chart, a type of bar graph where causes are plotted in descending order of their scores. The leftmost bars represent the most critical causes – your ‘vital few’.

Focusing on these ‘vital few’ can lead to significant improvements. They’re what you need to tackle to see the biggest reduction in the problem.

But remember, Pareto Analysis isn’t a standalone tool. It’s most effective when used with other RCA tools, as each provides unique insights. So, don’t stop here. Keep exploring and combining tools to get to the root of your problems.

Failure Mode and Effects Analysis (FMEA)

Failure Mode and Effects Analysis (FMEA) is another powerful tool you can’t afford to overlook. This systematic approach helps you identify potential failures in your processes before they happen.

It’s all about being proactive, not reactive, which is key to ensuring the safety and quality of your products.

Imagine you’re making a batch of cookies. FMEA would have you list all the things that could possibly go wrong – from ingredients being mixed incorrectly to the oven temperature being too high.

You’d then rate each potential failure based on three factors: severity, occurrence, and detection. The end result? A risk priority number that tells you what needs your attention first.

But it doesn’t stop there. Once you’ve identified and prioritised your potential failures, you then develop actions to prevent them or reduce their impact.

You’re not just finding problems – you’re solving them.

Fault Tree Analysis (FTA)

Moving on from FMEA, let’s explore another instrumental tool in Root Cause Analysis – Fault Tree Analysis (FTA). FTA is a top-down, deductive approach used in identifying potential problems and their causes.

It’s a visual tool that helps you understand the interrelationships among failures in a system. You start with a top event – the failure you’re trying to prevent. Then, you work your way down, identifying all the possible causes of that failure.

Imagine it as a tree, with the top event as the trunk, and the potential causes as branches. Each branch can further divide into smaller branches, representing more specific causes.

FTA is particularly useful in the food manufacturing industry. You can use it to identify potential areas of failure in your processes, from ingredient sourcing to final product delivery.

It can help you pinpoint where a contamination might occur, or where a process might break down, leading to product spoilage.

It’s a proactive tool, enabling you to identify and address potential failures before they occur. Remember, it’s always better to prevent a problem than to fix it after it’s happened.

Failure Mode and Effects Analysis

Sign up for the Food Industry Hub Mail Service

Receive Food Industry Hub updates, resources, articles, tools and service developments direct to your inbox.

Each update helps you stay connected with new and relevant Food Industry Hub content, with links back to resources you may want to read, use or revisit.

Benefits of Root Cause Analysis

You might be wondering, “What’s in it for me?” when it comes to Root Cause Analysis (RCA).

Well, RCA can significantly improve your problem-solving skills, increase efficiency in your operations, and reduce risks associated with food production.

Plus, it can greatly enhance your decision-making process and promote continuous improvement in your business.

Improved Problem-Solving

With the implementation of root cause analysis in food manufacturing, your problem-solving skills are likely to see a significant improvement.

It’s not just about finding quick fixes but resolving issues at their source. This method encourages you to dig deeper, to uncover the ‘why’ behind the problem. You’ll move beyond treating symptoms and start tackling the disease.

Root cause analysis prompts you to investigate. Was it an issue with materials? Equipment? Human error? You’ll probe until you find the root cause.

This approach to problem-solving does more than rectify immediate issues. It stimulates a culture of curiosity and continuous improvement.

You’ll start asking the right questions, identifying patterns, and preventing future mishaps. It’s about transforming reactive measures into proactive strategies.

Increased Efficiency

Embracing root cause analysis can lead to a substantial increase in efficiency within your food manufacturing processes.

Efficiency isn’t just about speed; it’s about making the most of your resources. By identifying and addressing the root cause of a problem, you’re not just putting a band-aid on a symptom, you’re eliminating the source. This means less time spent troubleshooting, and more time dedicated to profitable operations.

Consider the resources spent on recurring issues. Manpower, materials, time – these costs add up. But when you solve a problem at its root, you cut these unnecessary expenses. Efficiency soars as waste plummets.

It’s not just about cost savings, though. Root cause analysis also improves the quality of your output. By fixing core issues, you reduce the chance of defects and ensure a more consistent product. This in turn boosts your reputation for reliability, leading to increased customer satisfaction and potentially higher sales.

In short, root cause analysis streamlines your operations. It’s a proactive approach that promotes efficiency, reduces waste, and enhances product quality.

And in the competitive world of food manufacturing, that advantage can make all the difference.

Risk Reduction

Root cause analysis serves as a powerful tool for risk reduction. By identifying the underlying causes of problems, you’re able to proactively address them, thereby reducing the likelihood of their recurrence. You’re not just putting a band-aid on a problem; you’re solving it at its source.

Imagine a scenario where a batch of product has been recalled due to a contamination issue. Without root cause analysis, you’d likely just clean up, make another batch, and hope for the best. But with it, you’d dig deeper. You’d investigate where the contamination originated, why it wasn’t detected earlier, and how your processes can be improved to prevent it from happening again.

In this way, root cause analysis helps you to minimise risks and foster a safer, more reliable production environment. It’s not just about fixing problems as they arise; it’s about preventing them from happening in the first place.

And in an industry where safety and quality are paramount, that’s a benefit you can’t afford to ignore. So, embrace root cause analysis, and take a proactive step towards risk reduction.

Enhanced Decision-Making

Your company’s decision-making processes can be dramatically improved through the use of root cause analysis. By identifying and understanding the underlying causes of problems, you gain valuable insights that enhance your decision-making capabilities.

It’s not just about fixing issues as they surface, it’s about digging deeper to understand why they arose in the first place.

Imagine you’re dealing with recurring equipment malfunctions in your food processing line. Instead of merely addressing the immediate issues, conducting a root cause analysis allows you to pinpoint the actual source of the problem. This might be poor maintenance practices, outdated equipment, or even inadequate staff training.

With this information, you’re better equipped to make informed decisions, whether it’s investing in new machinery or enhancing employee training programs.

Root cause analysis helps you anticipate potential challenges. As you delve into issues, you’ll likely identify patterns or trends that could lead to future problems.

Armed with this foresight, you can make proactive decisions that prevent such issues from surfacing, saving your company valuable time, resources, and potentially, your reputation.

Ultimately, root cause analysis is a powerful tool that can transform your decision-making process, making your business more efficient and effective.

Continuous Improvement

Root cause analysis paves the way for continuous improvement in your food manufacturing business. It’s like a compass, guiding you towards the pinpointed issues that need your attention. By identifying the root causes of problems, you’re able to make targeted changes that can significantly improve your processes and product quality.

Imagine not having to deal with the same issue repeatedly because you’ve resolved it from its core. That’s what root cause analysis offers. It eliminates the guesswork and provides clear, actionable insights.

This methodology encourages a proactive mindset. You’re not just waiting for problems to surface, you’re actively seeking potential issues and addressing them before they escalate. This can save you time, money, and resources in the long run.

Moreover, continuous improvement fuels innovation. As you refine your processes and solve root causes, you’re also opening doors for new ideas and strategies. This can lead to increased productivity, better product quality, and a competitive edge in the market.

In the end, root cause analysis isn’t just about solving problems. It’s about fostering a culture of constant improvement and innovation.

Increased Efficiency

Challenges in Root Cause Analysis

While root cause analysis can significantly enhance your food manufacturing processes, it’s not without its challenges.

You might grapple with incomplete data, a process that’s time and resource intensive, and even resistance to change within your organisation.

There’s also a risk of focusing too much on symptoms rather than the actual root causes.

Incomplete Data

One major stumbling block you’ll often encounter is incomplete data. This hitch can significantly impede your ability to pinpoint the exact cause of a problem. Without all the necessary data, you’re essentially attempting to solve a puzzle with missing pieces.

Not having full access to data might stem from various reasons. It could be due to insufficient data collection practices, miscommunication between departments, or employees’ lack of training in data recording.

To combat this, it’s prudent to regularly review and update your data collection and management practices. It’s imperative that everyone involved understands the importance of accurate, complete data.

Training programs can help familiarise your team with best practices and the potential consequences of incomplete data.

Time and Resource Intensive

Another significant challenge you might face in root cause analysis is its time-consuming and resource-intensive nature. This isn’t a process that can be rushed or skimped on. It demands a considerable investment of both time and resources to be effective.

You might need to dedicate hours, if not days, to thoroughly investigating and determining the root cause. It’s not as simple as finding a quick fix. Instead, it’s about delving deep into the problem, peeling back layers to reveal the true cause. This takes time and requires a meticulous approach.

In terms of resources, you’ll need personnel who are trained in root cause analysis techniques. It’s not something that can be handled by just anyone. You’ll also need to allocate funds for any necessary equipment or tools. This could range from diagnostic software to testing materials.

The process doesn’t end once you’ve found the root cause. You’ll then need to develop and implement a solution, which is another time and resource commitment.

Despite these challenges, it’s important to remember that root cause analysis is a crucial step in improving your food manufacturing processes. It may be difficult, but it’s a necessary investment for long-term success.

Resistance to Change

Often, one of the biggest challenges you’ll face in root cause analysis is resistance to change. It’s human nature to resist what we don’t understand or find uncomfortable, and changes in processes or procedures can certainly fall into this category.

You’re not alone if you’ve faced a workforce that’s reluctant to embrace new ways of doing things.

Resistance to change can manifest in many ways. It can be as subtle as a lack of engagement or as blatant as outright refusal to follow new procedures. Whatever form it takes, it’s a hurdle that needs to be overcome for successful root cause analysis.

You can tackle this issue head-on by ensuring clear communication about the reasons for change and the benefits it brings. Training, reassurance, and patience are key. Remember, change is a process, not an event.

Involving your team in the root cause analysis can also help. When people feel part of the solution, they’re more likely to embrace the necessary changes.

Despite the challenges, overcoming resistance to change is critical to achieving the full benefits of root cause analysis in food manufacturing.

Focusing on Symptoms

While it’s essential to address immediate problems, you should be careful not to focus solely on the symptoms during your root cause analysis.

It’s a common pitfall in food manufacturing, where pressure to maintain production levels can overshadow the need for thorough investigation. It’s like treating a fever without identifying the infection causing it.

In your quest for quick solutions, you may overlook the deeper, systemic issues that lead to recurring problems. This doesn’t mean you shouldn’t fix the immediate issues. Instead, it’s a call to take a step back, look beyond the surface, and dig deeper.

Consider a scenario in which a machine frequently breaks down. You could continuously repair it, but the breakdowns might still persist. The root cause could be anything from improper maintenance schedules to operator errors.

The challenge here is to balance immediate problem-solving with long-term, sustainable solutions. This requires an open mind, careful observation, and the patience to uncover the real root cause.

Ultimately, focusing on symptoms rather than root causes is a short-term fix that can lead to long-term headaches. So, don’t just treat the symptoms, cure the disease.

Incomplete Data

In Summary

So, you see, RCA is a game-changer in food manufacturing. By identifying and addressing the root causes, not just the symptoms, you can drastically improve your operations. Using tools like the 5 Whys and Fishbone Diagrams, you’ll streamline processes, enhance product quality, and reduce food safety risks. Sure, there may be challenges, but the benefits of fostering a culture of continuous improvement are worth it. Take the leap, implement RCA, and see the difference it makes.

Implement RCA, and see the difference it makes.

Further Resources

Food Industry Hub serves the food industry with a range of digital resources for the benefit of both commercial food manufacturers and food industry professionals.

For food manufacturers, we offer integrated management systems that give every user a direct interface with your QMS.

For food industry professionals, we provide an extensive signposting service in addition to informational content we hope you’ll find useful as you face new professional challenges. We have very ambitious plans to expand the range of services offered, and currently present informational content on management, safety and quality, food safety and quality culture, and professional success.

Responding to Serious Adverse Evidence Before the Cause Is Known

Responding to Serious Adverse Evidence Before the Cause Is Known

A concerning result arrives during production. The technical team is checking whether it reflects a local problem, a wider issue or an error in the evidence. Meanwhile, work and product may continue to move. Managers cannot wait for a complete explanation before...

Turning Strategic Priorities into Work Managers Can Deliver

Turning Strategic Priorities into Work Managers Can Deliver

A strategic priority can be understood throughout a food-manufacturing business and still leave daily work largely untouched. People may know the goal but continue with the same projects, staffing assumptions, approval routes and review measures. To make a priority...

How Senior Leaders Can Govern Without Rechecking Every Control

How Senior Leaders Can Govern Without Rechecking Every Control

Senior leaders are accountable for whether a management system has the people, resources and direction to work. They cannot personally inspect every receiving decision, maintenance task or verification record. Trying to do so would displace the specialists who own...

Making Management Review a Decision and Learning Process

Making Management Review a Decision and Learning Process

Management review brings senior leaders into contact with information that individual teams cannot resolve in isolation. A complaint trend, an overdue corrective action and a request for additional capability may each appear in a different report. Their relationship,...

How to Transfer Operational Learning Across Shifts and Sites

How to Transfer Operational Learning Across Shifts and Sites

A finding at one site can reveal a weakness that exists elsewhere. It can also describe a local arrangement that has no equivalent in another shift, function or facility. Managers need a way to distinguish those cases before turning one team's corrective action...

Preserving the Reasoning Behind Management Decisions

Preserving the Reasoning Behind Management Decisions

A current procedure can tell a team what to do without explaining why that method was chosen. That may be enough for routine execution. It becomes less helpful when a supplier changes, equipment is replaced, a recurring problem appears or the person who made the...

How Organisations Turn Findings into Verified Change

How Organisations Turn Findings into Verified Change

An investigation can be completed, its actions closed and its report filed while the conditions that produced the original problem remain largely intact. The records show that people responded. They do not yet show whether the organisation will make a better decision...

When Short-Term Savings Erode Management Capability

When Short-Term Savings Erode Management Capability

Reducing labour or support costs can be a sound management decision. The difficult case is a saving that leaves today's output intact because people absorb the missing work. Extra hours cover an absence, an experienced technician takes on a second area, or a...

How to Make a Credible Case for Preventive Investment

How to Make a Credible Case for Preventive Investment

Preventive work often competes for money with projects that promise an obvious increase in output. A new line can be described in units per hour. Better maintenance, stronger monitoring or more capable technical support may chiefly prevent interruptions that have not...

Commercial Judgement Begins With the Outcome That Must Be Protected

Commercial Judgement Begins With the Outcome That Must Be Protected

A lower unit price can look attractive until a material change slows approval, interrupts production or creates more waste. A tighter process setting can improve yield while making acceptable product harder to assure. In each case, the commercial result depends on...

When the Result Arrives Later Than the Management Response

When the Result Arrives Later Than the Management Response

A maintenance change is completed on Monday, and the following day's defect count is much the same. It is tempting to call the change ineffective. Yet the equipment may need to run across different products and operating conditions before the outcome it was...

Make Systems Thinking Useful to a Management Decision

Make Systems Thinking Useful to a Management Decision

A department can complete its work on time while the next team still receives something it cannot use. The local measure looks healthy; the wider process is delayed. Managers often meet this kind of problem as a missed target in one area, although the conditions...

A Process Improvement Must Survive Normal Production

A Process Improvement Must Survive Normal Production

A trial can produce an encouraging chart: fewer defects, less spread and a process that appears easier to control. Those results are worth examining, but they do not settle whether the change is ready for routine production. The trial may have used a narrow product...

Use Variation Data to Strengthen Cause Investigation

Use Variation Data to Strengthen Cause Investigation

Two defects may look similar in a daily report while pointing to different kinds of work. One may follow an unusual breakdown or a specific wrong-material selection. Another may be part of a recurring spread in results from a process that otherwise runs as designed....

Trust the Measurement Before the Variation Analysis

Trust the Measurement Before the Variation Analysis

A chart of process readings can make a production problem look well understood. The points may form a pattern, and a large number of observations can make the conclusion feel secure. Yet every point depends on a device, a method of taking the reading, a choice of...

When Six Sigma Is Worth the Analytical Effort

When Six Sigma Is Worth the Analytical Effort

A recurring defect can make a formal improvement project look like the obvious next step. The method has a name, a sequence of stages and the promise of more disciplined analysis. Yet the decision to use it should begin with the nature of the problem. A production...

Make TPM a Shared Reliability Practice With Clear Work Boundaries

Make TPM a Shared Reliability Practice With Clear Work Boundaries

An operator may notice a change in a machine long before its next planned maintenance visit. Engineering may know that the same component has needed adjustment several times. Each view can improve equipment reliability, but only if the observations reach a person who...

Before Reducing Inventory, Test What It Protects

Before Reducing Inventory, Test What It Protects

Reducing inventory can release cash, free warehouse space and make material flow easier to manage. A lower stock figure can also expose a factory to interruptions that its previous buffer quietly absorbed. The management decision is therefore more specific than...

When Higher OEE Hides a Worse Operating Result

When Higher OEE Hides a Worse Operating Result

A production line runs faster, loses less recorded time and reports a higher Overall Equipment Effectiveness score. That is useful news. It may also be an incomplete account of what changed. If Engineering now spends more time on reactive repairs, Hygiene has less...

Find the Real Bottleneck by Mapping Evidence and Decisions

Find the Real Bottleneck by Mapping Evidence and Decisions

A production line can finish its work on time while the product remains unavailable for its next step. The physical process may be complete, yet a result still needs interpretation, a record is missing, or someone with the right authority has not made a status...

Make Lean Improvements Without Removing Necessary Food Controls

Make Lean Improvements Without Removing Necessary Food Controls

A step that takes time may be waste, necessary protection or a mixture of both. In food manufacturing, the distinction matters when an improvement team sees a long changeover, an inspection before release or a route that appears unnecessarily indirect. Removing time...

Judge 5S by How Food-Factory Work and Controls Improve

Judge 5S by How Food-Factory Work and Controls Improve

A workplace can look orderly in an inspection photograph while the people using it still search for the right item, move around an obstruction or struggle to see a developing defect. It can also look busy and be well organised for the work being done. The purpose of...

When Small Improvements Keep Moving the Problem

When Small Improvements Keep Moving the Problem

A team makes a task quicker, closes its action and reports a better measure. Suppose the people who receive its work must then spend longer chasing missing information, correcting it or waiting for a decision. The first improvement may be real for that team, but the...

Find Improvement Opportunities in the Work People Actually Do

Find Improvement Opportunities in the Work People Actually Do

A process map can make a difficult task look effortless. It shows the approved sequence, the intended handovers and perhaps the time allotted to each activity. It may not show the search for a missing tool, the repeated re-entry of information or the pause while...

Make Continuous Improvement a Controlled Learning Cycle

Make Continuous Improvement a Controlled Learning Cycle

Continuous improvement often begins with a small irritation: a repeated wait, an awkward handover or a record that seems to duplicate another. People doing the work can usually describe the friction more clearly than a distant project team. Yet the benefit of removing...

Keep Open Issues Visible Until the Decision Is Closed

Keep Open Issues Visible Until the Decision Is Closed

A management meeting can finish while the issue it discussed remains open. The minutes may show that an investigation was assigned and a date agreed. By the next meeting, the original report may no longer be on the agenda. If the underlying condition persists, the...

Report While There Is Still Time to Decide

Report While There Is Still Time to Decide

A report can be accurate, complete and too late. If a supplier concern reaches the manager responsible for a purchasing commitment after that commitment has been made, the information can still inform later review. It cannot influence the choice that has already...

How Management Reports Lose Meaning on the Way Up

How Management Reports Lose Meaning on the Way Up

A senior manager cannot work through every operational record behind a site report. The information has to become shorter as it moves from the people doing the work to those who decide on priorities and resources. That change in detail is useful. Trouble begins when a...

A Balanced Scorecard Needs a Wider View, Not an Average of Risks

A Balanced Scorecard Needs a Wider View, Not an Average of Risks

A food manufacturer can meet its service target, improve yield and still have a serious unresolved control issue. Those results do not contradict one another. They describe different parts of the business, and managers need to see all of them before deciding what to...

When a KPI Improves but Control Gets Worse

When a KPI Improves but Control Gets Worse

A rising completion rate looks like progress. If a site closes more corrective actions within its target time, managers have a reasonable reason to look more closely at what changed. Yet the rate describes a defined event: cases recorded as closed within a period. It...

Interpreting KPI Movement Before Calling It Improvement

Interpreting KPI Movement Before Calling It Improvement

A falling complaint count looks encouraging. It may reflect fewer problems reaching customers, but the number alone cannot establish that conclusion. The site may have sold less product, changed its mix, altered its classification rules or made it harder for feedback...

Designing KPIs That Support Decisions and Still Deserve to Exist

Designing KPIs That Support Decisions and Still Deserve to Exist

A dashboard can display a precise number without helping anyone decide what to do. The number may be easy to collect, familiar to senior managers and stable enough to plot every month. Those qualities do not establish that it describes the condition the organisation...

Managing External Providers While Retaining Site Accountability

Managing External Providers While Retaining Site Accountability

An external laboratory can produce a result, a contractor can repair a machine, and a supplier can provide information about a material. The food-manufacturing site still has to decide what those outputs mean for its own work. That distinction becomes difficult in...

Using Theory of Constraints Without Losing Control of the Work

Using Theory of Constraints Without Losing Control of the Work

A production line may be able to make more product than the laboratory can test, or a technical team may complete its review faster than the authorised decision maker can consider it. Adding effort to the fast part of either process will make more work wait. The...

Following Change Impacts Beyond the Initiating Department

Following Change Impacts Beyond the Initiating Department

A change can look small from the place where it begins. A different packaging material may seem to require a supplier approval and a line trial. Yet the material could alter how equipment is set, how an allergen or hygiene control is applied, what the specification...

Keeping Controlled Information Aligned With Changed Work

Keeping Controlled Information Aligned With Changed Work

A revised instruction can be approved while the people expected to use it are still working with the old equipment or record. The reverse can happen too: a team develops a practical local method, yet the controlled instruction still describes the earlier one. Both...

Managing Temporary Controls During Operational Change

Managing Temporary Controls During Operational Change

Some changes cannot be introduced everywhere at once. A revised method may begin on one line while another continues with the old version. Equipment may become unavailable before a permanent repair is complete. In either case, people have to work in a period when the...

Managing Change Fatigue Through Better Sequencing and Mobilisation

Managing Change Fatigue Through Better Sequencing and Mobilisation

A site can have good reasons for changing a procedure, introducing new software and revising a handover arrangement. Each proposal may be sound on its own. If all three reach the same supervisors and teams at once, those people must learn, explain, practise and check...

Managing Resistance to Change Without Misdiagnosing the Problem

Managing Resistance to Change Without Misdiagnosing the Problem

A person who challenges a proposed change may be protecting a familiar routine. They may also have noticed that the new routine cannot be carried out as designed. Calling both responses “resistance” obscures the difference that a manager needs to understand before...

Managing Change From Approval to Stable Practice

Managing Change From Approval to Stable Practice

An approved change can still leave everyday work much as it was. The proposed method may have been assessed, the revised procedure issued and the training recorded, yet people can find that the new decision depends on an unavailable colleague or that the old form is...

Close Projects by Transferring Ownership Into Stable Operations

Close Projects by Transferring Ownership Into Stable Operations

A project can reach its final milestone while the new way of working is still settling. People may be using a temporary check, an improvement may be waiting for evidence, or one shift may be working differently from the process that was approved. Closing the project...

Manage Supplier Transitions Around Readiness, Not Delivery Dates

Manage Supplier Transitions Around Readiness, Not Delivery Dates

A replacement supplier may be able to deliver material on the date Procurement requested while the site is not ready to use it. The specification may still need agreement, approval evidence may be incomplete, or a trial may not yet have established whether the...

Close Physical Change Projects Only When Operation Is Ready

Close Physical Change Projects Only When Operation Is Ready

A new machine can be installed, commissioned and handed over as an asset while the production team is still unable to use it as part of a controlled routine. A new wall or barrier can be complete while people, materials and cleaning activities still follow the old...

Revisit the Project Promise When Scope or Assumptions Change

Revisit the Project Promise When Scope or Assumptions Change

A project can keep its original completion date on a report long after it has ceased to be the project that date described. An extra requirement may have been accepted without changing the resources available. A supplier may no longer be able to meet the lead time on...

Build Project Schedules Around the Work That Enables Operation

Build Project Schedules Around the Work That Enables Operation

The installation date is often the most visible point in a food-manufacturing project plan. Yet equipment can be in place while the work needed to use it responsibly is still unfinished. A specification may await approval, a relevant check may not be complete, or the...

Give Project Decisions an Owner Beyond the RACI Chart

Give Project Decisions an Owner Beyond the RACI Chart

A project can have a clear list of task owners and still stall when two departments need the same specialist, an approval exceeds the project lead's authority or a transition carries a risk no single function can accept. The problem is not necessarily poor task...

Govern Projects by the Operating Change They Must Deliver

Govern Projects by the Operating Change They Must Deliver

A project plan can be completed on time while the change it was meant to deliver remains difficult to use. New equipment may be installed, for example, while the people who will operate, maintain and assess it still lack an agreed way of working. The schedule records...

Plan Management Capacity for Events as Well as Routine Work

Plan Management Capacity for Events as Well as Routine Work

A team can have enough people for every task on its weekly schedule and still run out of capacity when an adverse result, equipment failure or significant supplier problem arrives. The new work does not politely wait for a meeting slot. People must establish what...

When Manager Overload Is a Problem With the Role

When Manager Overload Is a Problem With the Role

A manager can have a carefully organised diary and still be unable to keep up with the work the organisation expects. Planned reviews, staff support and routine decisions share the week with urgent exceptions. Some tasks can move; others return because the manager...

When One Person Carries Several Critical Roles

When One Person Carries Several Critical Roles

On a smaller food manufacturing site, one capable person may hold responsibilities that a larger organisation distributes across several posts. That arrangement can be efficient: the person understands the site, can connect related decisions and avoids unnecessary...

Manage Attention Where Decisions and Work Are Stuck

Manage Attention Where Decisions and Work Are Stuck

A manager can spend a full day responding to legitimate requests and still leave important work waiting. A complaint needs an answer, a meeting needs a decision, and a colleague needs an approval before proceeding. The difficulty is not simply the number of demands....

Laboratory Turnaround Is Only Part of the Decision Time

Laboratory Turnaround Is Only Part of the Decision Time

A laboratory can report a result within its agreed turnaround and an operational decision can still be late. The sample may have waited before dispatch, arrived without enough context to interpret it, or reached a reviewer who was unavailable at the point the result...

Shared Specialists Need One View of the Work

Shared Specialists Need One View of the Work

Two departments can each have a workable plan and still be unable to carry out both. Their schedules may depend on the same technical specialist, the same authorised reviewer or the same opportunity to access a production line. Because each plan looks only at its own...

Before Adding Resource, Find the Constraint in the Work

Before Adding Resource, Find the Constraint in the Work

When a queue grows, asking for more people feels practical. It may be the right response, but the queue alone does not show whether the shortage is labour, equipment, access, information or a decision. Additional staff can spend their time waiting for the same missing...

Start Resource Decisions With the Outcome at Stake

Start Resource Decisions With the Outcome at Stake

A request for another person, more laboratory hours or a larger maintenance budget can be easy to challenge and difficult to decide. The quantity is visible; the result it is meant to protect may be less so. A sound allocation decision starts by naming that result,...

Management Reports Should Make the Decision Visible

Management Reports Should Make the Decision Visible

A report can be full of completed actions and still leave a manager unsure what needs to happen next. Pages of activity show that work took place, but a single unresolved control weakness or resource constraint may matter more to the next decision. The opposite...

When the Budget Holder Does Not Own the Risk

When the Budget Holder Does Not Own the Risk

A department can be responsible for paying for work without being the one that bears the consequences if the work is delayed. Engineering may hold the maintenance budget, while Production needs the equipment and Technical needs assurance about its condition. A...

When a KPI Improves but the System Gets Worse

When a KPI Improves but the System Gets Worse

A department reports better performance. Its target has been met, the trend is moving in the desired direction, and the people responsible can explain how they achieved it. Yet work is accumulating elsewhere, decisions take longer, or a control activity is being...

When Departmental Objectives Collide, Make the Trade-off Visible

When Departmental Objectives Collide, Make the Trade-off Visible

A Production Manager may be asked to protect today's output while a Technical Manager needs time to establish whether a control has worked. Both are carrying legitimate responsibilities. The difficulty begins when the schedule assumes the line will run and the...

Respond Quickly Without Deciding Before the Evidence

Respond Quickly Without Deciding Before the Evidence

A customer wants an explanation today. An auditor has challenged a control. A supplier has information that may affect a production decision. Each situation calls for attention, and delay can carry a real cost. Yet a quick reply and a sound conclusion depend on...

Involve Stakeholders When Their Input Can Change the Work

Involve Stakeholders When Their Input Can Change the Work

A stakeholder list can be complete as a list of names and still be poor guidance for a decision. A senior person may have little direct part in a particular change, while an operator, supplier or specialist with no approval right may hold information that determines...

Coordinate Shared Work Without Losing Ownership

Coordinate Shared Work Without Losing Ownership

Cross-functional work often has many legitimate contributors. Production may control access to a line, Engineering may complete a modification, and Technical may assess whether the change meets its intended requirements. Each team can own its part while the overall...

Make the Next Team Able to Proceed

Make the Next Team Able to Proceed

A department can finish its assigned work while the wider job remains stuck. Engineering has completed a repair, but Production does not know whether the equipment can return to service. A laboratory has issued a result, but the site cannot connect it confidently to...

Choose Suppliers on Total Consequence, Not Price Alone

Choose Suppliers on Total Consequence, Not Price Alone

A supplier's quoted price is visible before many of the costs of using that supplier are known. A lower unit price can be valuable, especially when margins are tight. It can also be offset by extra assurance work, inconsistent material, longer lead times or...

Build One Evidence Chain Across an Investigation

Build One Evidence Chain Across an Investigation

An investigation can collect a large amount of information and still fail to explain an event. Production has its records, Hygiene has cleaning information, Engineering has maintenance history and a laboratory has a result. Each may be accurate within its own area....

Make Product Launch a Readiness Decision

Make Product Launch a Readiness Decision

A new product can have an agreed specification and a booked production slot while the operation that must make it is still preparing. The packaging may be awaiting approval, a line trial may have exposed a capacity limit, or the people who will run and check the...

Involve the People Who Will Make the Change Work

Involve the People Who Will Make the Change Work

A change can be technically sound on paper and awkward to carry out on a busy line. The proposed check may need access that disappears during production, information that arrives after the decision, or time that the shift does not have. People who will perform and...

Negotiate Competing Interests With Real Alternatives

Negotiate Competing Interests With Real Alternatives

Negotiation inside a food-manufacturing business often starts with firm positions. Production needs a date. Technical needs evidence. Procurement needs a workable supplier and price. Each position can sound like an obstacle to the others, even when each reflects a...

Know When Consultation Must Become a Management Decision

Know When Consultation Must Become a Management Decision

Disagreement often deserves more conversation. A manager may need to hear evidence held by another function, understand why two teams see a risk differently, or help people work together after a difficult exchange. But another meeting can also postpone a choice that...

When Recurring Conflict Needs a Governance Decision

When Recurring Conflict Needs a Governance Decision

When the same two functions argue over the same work every week, another appeal for better cooperation may bring a temporary pause. It will do little if neither function has the authority to settle the competing commitments. Repeated conflict can be a sign that the...

Take a Difficult Conversation from Evidence to Decision

Take a Difficult Conversation from Evidence to Decision

A difficult conversation at work should leave people better able to act. The immediate result may be an agreed change, a decision that one party dislikes, or a clearly owned escalation. Continuing to talk until everyone appears comfortable can leave the original...

Challenge the Reasoning Without Attacking the Specialist

Challenge the Reasoning Without Attacking the Specialist

A manager may need to decide how work proceeds after receiving specialist advice, even when the specialist knows far more about the technical subject. In a food factory, a maintenance specialist might report that a repaired machine can return to a proposed schedule....

Make It Possible to Raise Problems Before They Become Consequences

Make It Possible to Raise Problems Before They Become Consequences

An instruction can be clear to its author and still leave a person doing the work unsure how to apply it. Suppose a proposed packaging sequence changes during a shift, and an operator notices that the instruction does not fit the work in front of them. The immediate...

Give Every Management Message an Owner and a Real Receiver

Give Every Management Message an Owner and a Real Receiver

When several functions contribute to a management message, its content may be sound while its route to action remains uncertain. Maintenance can supply findings, quality can assess an implication, and operations can describe a planning constraint. Someone still needs...

Tailor Management Messages Without Changing the Truth

Tailor Management Messages Without Changing the Truth

A production plan may need a decision before every piece of supporting information is available. If a supplier's approval evidence is still under review, procurement, production planning and senior management cannot simply wait without knowing what to do. Yet a...

Preserve Decision Context in Shift and Site Handovers

Preserve Decision Context in Shift and Site Handovers

“Repair pending” may be a true entry in a shift handover. It tells the next team that work remains, but it does not explain why equipment is in its present condition, what has already been checked, which restriction still applies or who can decide when it returns to...

Communicate Decisions So the Work Actually Changes

Communicate Decisions So the Work Actually Changes

A manager may decide that one job now takes priority over another, announce the new order and assume the team will adjust. Yet the original deadline can remain in the schedule, materials can still be prepared for the old sequence, and people in other functions may...

Manage Performance Between Appraisals

Manage Performance Between Appraisals

An annual appraisal should bring together what a manager and colleague already understand about the year. If it is the first occasion on which a significant performance gap is discussed, the conversation arrives too late to help with much of the work it describes. The...

Diagnose Recurring Performance Problems Before Choosing a Remedy

Diagnose Recurring Performance Problems Before Choosing a Remedy

A manager gives feedback about a missed action. The same problem appears again, so the manager repeats the conversation with more emphasis. When it happens a third time, the temptation is to conclude that the person is unwilling to improve. That conclusion may be...

When to Coach, Instruct or Hold Someone Accountable

When to Coach, Instruct or Hold Someone Accountable

A manager sees a team member hesitate over a decision. Asking how they see the options might help them develop judgement. It might also leave them without a clear instruction when the work has an immediate boundary. Managers need to match the intervention to the work...

Make Feedback Specific, Timely and Proportionate

Make Feedback Specific, Timely and Proportionate

A manager notices that information needed at a shift hand-off was missing. By the time the issue is raised, the observation may have turned into an interpretation: the person was careless, did not take ownership or should have known better. None of those claims...

Judge Performance Fairly When Results Depend on Other Teams

Judge Performance Fairly When Results Depend on Other Teams

An improvement action misses its due date. The person named on the action appears to have failed, and the overdue figure enters a management report. Yet the next step may have required an assessment from another function, a decision outside that person's authority...

Set Expectations for Results, Evidence and Judgement

Set Expectations for Results, Evidence and Judgement

A person can complete every assigned activity and still leave the intended result unresolved. A check was performed, a meeting held or a report submitted, but the information needed for a decision is missing. If the manager described only the activity, both parties...

Make Roles Clear Where the Work Changes Hands

Make Roles Clear Where the Work Changes Hands

A job description can explain the broad purpose of a role, yet leave the next action unclear when work crosses a team boundary. One person gathers information, another reviews it, and a third is expected to approve a change. If the hand-off is incomplete or the...

Use Motivation Theories to Examine Work, Not Label People

Use Motivation Theories to Examine Work, Not Label People

Motivation theories can give managers useful ways to notice what work asks of people and what may support sustained effort. They become less useful when a framework is treated as a diagnosis of a particular person. A missed task does not reveal which need someone has,...

Recognise the Work That Keeps Problems from Growing

Recognise the Work That Keeps Problems from Growing

The work that attracts the most attention is often easy to see: a target reached, a difficult problem resolved or an urgent response delivered. Many valuable contributions in food manufacturing are quieter. A colleague keeps a routine check dependable, challenges...

Diagnose the Work Before Judging Motivation

Diagnose the Work Before Judging Motivation

When work is late, incomplete or repeatedly done in a way a manager has challenged, the behaviour is visible. The reason for it is less certain. A person may be unwilling to do the work as expected, but they may also lack time, information, authority or a workable...

Give People Real Responsibility Without Leaving Them Exposed

Give People Real Responsibility Without Leaving Them Exposed

People often develop sound judgement by taking responsibility for work that is less familiar or more consequential than their usual assignment. The experience has to be real: observation alone cannot reveal how someone weighs evidence, coordinates others or acts when...

Make Deputy Cover Work Before the Absence

Make Deputy Cover Work Before the Absence

A named deputy can be familiar with a manager's work and still be unable to keep it moving when that manager is away. The deputy may know how a task is performed but have no authority to make the decision it leads to. They may have approval rights in principle but...

Prove Competence in the Work, Not on the Training Record

Prove Competence in the Work, Not on the Training Record

A training record tells a manager that somebody attended, received an explanation or completed a learning activity. It rarely settles the decision that follows: can this person now do the work to the required standard, under the conditions in which it actually...

Stop High Performance Becoming a Single Point of Failure

Stop High Performance Becoming a Single Point of Failure

The most dependable person in a team is often the one everyone calls when work becomes difficult. They know which evidence matters, who needs to be involved and how an unusual case was resolved last time. Their contribution can keep the operation moving. It can also...

Keep Management Ownership Across Shift Changes

Keep Management Ownership Across Shift Changes

A shift can finish while a decision remains open. The next team may inherit an interim control, a delayed repair or an exception that needs further assessment. If the handover only reports that the issue exists, the receiving team may know about the problem without...

Lead Specialists Without Confusing Authority and Expertise

Lead Specialists Without Confusing Authority and Expertise

A manager can be accountable for delivering a result without being the person best qualified, or authorised, to make every technical decision within it. That distinction becomes especially important when a specialist reports to one manager but holds an approval...

Give Autonomy Without Losing Oversight

Give Autonomy Without Losing Oversight

A manager can hand over a piece of work and still find it returning to their desk every day. They may be asked to decide small matters that the colleague could handle, or they may intervene so often that the colleague waits for instructions before acting. The opposite...

Adapt Supervision to the Work and the Person

Adapt Supervision to the Work and the Person

Two people can hold the same job title and need different support for the work in front of them. One may have carried out a routine task reliably for years; the other may be competent in the role but new to that particular activity. Even the experienced colleague may...

Make the Cost of Deferred Work Visible

Make the Cost of Deferred Work Visible

An urgent production fault may need the only technician who can restore a critical piece of equipment. Releasing that person from planned work is a sensible decision if the immediate consequence warrants it. The decision also moves the planned work somewhere else in...

Set and Revise Priorities as the Evidence Changes

Set and Revise Priorities as the Evidence Changes

An agreed order of work that was sensible yesterday can become unsuitable today. A new result may widen the possible consequence of an open issue. A prerequisite may stall, leaving another team unable to continue. A specialist may become unavailable. Managers still...

Prioritise the Work, Not the Score on the Matrix

Prioritise the Work, Not the Score on the Matrix

A team has capacity for two pieces of work today and four credible claims on its time. An equipment fault needs a response, a verification activity is due, a corrective action is approaching its agreed date, and a planned improvement is aimed at reducing recurring...

Make Temporary Decision Authority Work Under Pressure

Make Temporary Decision Authority Work Under Pressure

An urgent problem can arrive when the person who normally makes the decision is absent. The team may know how to investigate, contain or report the issue, yet still be unsure who can authorise the next consequential step. Finding a name on an absence list helps only...

Make Cross-Functional Decisions Clear at the Hand-Off

Make Cross-Functional Decisions Clear at the Hand-Off

A decision can stall even when every function has done the work assigned to it. One team has obtained the supplier information, another has assessed the technical evidence, and a third is waiting to know whether the supplier can be used. If nobody owns the decision...

Who Performs, Owns, Approves and Answers for the Work?

Who Performs, Owns, Approves and Answers for the Work?

A responsibility chart can show one name beside an activity and still leave an important gap. The person who carries out the task may not own the wider programme. Someone who approves a proposed response may not have performed the work or managed its dependencies. A...

Escalate at the Right Point, Then Learn from the Pattern

Escalate at the Right Point, Then Learn from the Pattern

Managers are asked to take ownership of difficult work and to escalate matters that exceed their authority. Both expectations are sound, but neither tells a manager where the boundary lies in a particular case. Holding an issue locally for too long can conceal a...

Send Escalation to the Holder of the Missing Decision

Send Escalation to the Holder of the Missing Decision

An issue can travel through the expected reporting line and still come back without a decision. The recipient may understand its importance but lack the authority to release a resource, make a technical judgement or direct another function's work. Further upward...

Make Escalation Produce a Decision and Return Ownership

Make Escalation Produce a Decision and Return Ownership

Copying a senior manager into a difficult issue may increase visibility without changing what anyone can do. The operating team still faces the same decision, resource constraint or conflict. Escalation becomes useful when it identifies the intervention that cannot be...

Cross-Functional Delegation Needs a Receiving System That Can Act

Cross-Functional Delegation Needs a Receiving System That Can Act

An action can be clear in a tracker and impossible in the working week. A manager assigns a colleague in another function to provide information or complete part of a corrective action. The named person understands the request, but their team has not agreed its...

Adjust Delegated Autonomy as the Work Changes

Adjust Delegated Autonomy as the Work Changes

A delegation that was sensible on Monday may need a different boundary by Thursday. The person doing the work may have shown sound judgement and be ready to decide more independently. Alternatively, new evidence may reveal a greater consequence than anyone expected...

When Delegation Keeps Coming Back to the Manager

When Delegation Keeps Coming Back to the Manager

A manager can delegate a piece of work and still find it on their desk every day. A colleague has the action, but asks the manager to approve each next step, secure access to another team or resolve every difficult choice. The manager may respond quickly and keep the...

Delegate the Outcome and Define the Decision Space

Delegate the Outcome and Define the Decision Space

An assignment can have an owner and still leave that person unable to move the work forward. The manager expects initiative, while the person doing the work waits for approval of routine choices. The opposite problem is possible too: a delegate makes a consequential...

Give Decision Owners the Authority and Information to Act

Give Decision Owners the Authority and Information to Act

A decision can have a named owner and still wait for days. The person may know the work but lack permission to act. They may have permission yet be unable to see the evidence held in another system. Or the decision may formally sit with a senior manager who receives a...

Use Weighted Decision Tools to Clarify Management Trade-Offs

Use Weighted Decision Tools to Clarify Management Trade-Offs

A weighted decision matrix can give a management choice the appearance of precision. Each option receives a score, the scores are combined, and one option comes out ahead. The calculation may be correct while the decision remains poorly understood. A binding...

Record and Review Management Decisions Without Hindsight Bias

Record and Review Management Decisions Without Hindsight Bias

When a management decision produces an unwelcome result, the information available afterwards can make the earlier choice appear obvious. The manager who made it did not have that later information. A useful review therefore examines the basis for the decision at the...

Make Defensible Management Decisions When Certainty Is Unavailable

Make Defensible Management Decisions When Certainty Is Unavailable

Food businesses sometimes have to act while important facts are still being established. An equipment condition may interrupt a planned run, a supplier problem may disrupt an agreed schedule, or an incident may leave several possible explanations. Waiting can create...

Use Specialist Advice Without Losing Managerial Decision Ownership

Use Specialist Advice Without Losing Managerial Decision Ownership

A specialist recommendation can be well founded and still leave a management decision to be made. The specialist may establish what the evidence supports, which technical limits apply and which actions are technically viable. A manager may then need to decide how an...

Make Management Information Useful from Decision to Action

Make Management Information Useful from Decision to Action

A manager can receive a detailed report and still lack what is needed to make a decision. The report may describe the situation accurately yet leave the available options, consequences and authority unclear. Even a sound choice can lose its effect if nobody has been...

What Managers Still Need to Supervise When Work Is Automated

What Managers Still Need to Supervise When Work Is Automated

Automating a routine step can remove repeated manual action while making the remaining decisions more consequential. A system may detect a condition, record a result or divert an item without someone performing each movement by hand. When it reports an exception,...

Learn from Near Misses Before Harm Occurs

Learn from Near Misses Before Harm Occurs

An event can end without harm and still reveal a weakness worth acting on. A component is found loose before it enters a product area. A handover gap is noticed before a critical check is missed. The immediate outcome is reassuring, but it does not explain whether a...

Make One-to-One Meetings Useful for the Work and the Person

Make One-to-One Meetings Useful for the Work and the Person

A one-to-one meeting gives a manager access to something a dashboard rarely shows: how a person is managing the work behind the reported result. A task can be marked complete while its owner is still relying on an awkward workaround. A deadline can look secure while...

Delegating Technical Work Without Losing Managerial Accountability

Delegating Technical Work Without Losing Managerial Accountability

A manager can be responsible for an outcome without being the person best qualified to do its technical work. In a food business, an experienced specialist may understand a process, product or control far better than the person who manages the team. Giving that...

Continuous Improvement

Continuous Improvement

IntroductionContinuous improvement represents a foundational approach to operational excellence that has transformed industries worldwide over recent decades. This systematic methodology for enhancing products, processes, and services through incremental advancements...

A Practical Guide to Kaizen

A Practical Guide to Kaizen

IntroductionIn food manufacturing, finding ways to improve efficiency, maintain quality, and reduce waste is critical to staying competitive. This is where Kaizen, a Japanese philosophy of continuous improvement, offers a compelling solution. By focusing on small,...

Values-Driven Leadership in Food Manufacturing

Values-Driven Leadership in Food Manufacturing

IntroductionMaintaining a strong commitment to food safety and quality has become more important than ever. As a senior leader, you have the unique ability to shape the culture of your organisation and influence the values that guide your team. When you prioritise...

Six Sigma for Food Manufacturers

Six Sigma for Food Manufacturers

IntroductionAs a food manufacturer, you're likely always on the hunt for ways to enhance your production processes. Have you ever considered the Six Sigma methodology? This technique, focused on reducing defects and increasing efficiency, could drastically transform...

Management Concepts & How They Apply in Food Manufacturing

Management Concepts & How They Apply in Food Manufacturing

IntroductionMastering a range of management concepts and approaches is essential for operational efficiency and sustained growth. When you consider the intricate web of factors influencing the food industry, from fluctuating consumer demands to evolving regulatory...

Total Quality Management (TQM)

Total Quality Management (TQM)

IntroductionImplementing TQM in your food manufacturing processes can lead to a culture of continuous improvement, where every employee is committed to delivering products that meet or exceed customer expectations. By focusing on customer satisfaction, TQM helps food...

Management and Leadership: Approaches and Techniques

Management and Leadership: Approaches and Techniques

IntroductionManagement and leadership are expansive topics. In this post, will explore a range of approaches and techniques that you might find helpful as a manager in the food industry. The intention is to introduce you to a variety of management strategies, without...

5 Tips for Managers in The Food Manufacturing Industry

5 Tips for Managers in The Food Manufacturing Industry

IntroductionIn this post, we will explore five tips to help bolster your managerial outlook. From prioritising food safety practices to staying updated with industry regulations, these tips will not only help you maintain a smooth operation but also ensure the success...

All About Kaizen for Food Manufacturers

All About Kaizen for Food Manufacturers

IntroductionFood manufacturers face increasing pressure to improve efficiency and quality while reducing costs. In today's competitive market, finding ways to optimise processes and enhance productivity is crucial. That's where Kaizen comes in. This continuous...

How to Proactively Demonstrate Senior Management Commitment

How to Proactively Demonstrate Senior Management Commitment

Food manufacturing is an ever-changing industry that requires strong commitment and effort from senior management to ensure high quality, safe products are produced. Quality, safety, authenticity and compliance are key factors for success in this sector. To be...

Making Use of Persuasion Techniques for Management Success

Making Use of Persuasion Techniques for Management Success

Persuasion is an invaluable tool for a successful manager. Through the use of persuasive techniques, effective managers can generate team collaboration, engagement, and buy-in in order to achieve success. In this article we will examine how persuasion, defined as...

Begginer’s Guide to Management in The Food Industry

Begginer’s Guide to Management in The Food Industry

The food manufacturing industry can be a challenging landscape for first-time managers. Juggling the demands of personnel management, production processes, and tight deadlines is enough to overwhelm even experienced professionals. Thankfully, there are key steps that...

Food Industry Hub blog

The Food Industry Hub blog includes practical discussion for food manufacturing professionals across technical, cultural, management and professional themes.

This post is part of the category:

Stay connected with Food Industry Hub

Receive Food Industry Hub updates, resources and practical content for food manufacturing businesses and professionals.

Stay informed about new resources, articles, tools and Food Industry Hub service developments.

Raise the standard for how food gets made.