There is a scene that plays out in manufacturing plants and distribution centers across the country almost every day. A shipment goes out late. A production run gets interrupted. A key order falls short. The phones start ringing, the emails start flying, and within the hour, someone is standing in a conference room trying to explain what happened.

The instinct in those moments is deeply human: find the person who dropped the ball. Identify the failure. Assign accountability. Move on.

But what if that instinct, as natural as it feels, is precisely what is keeping your operations from ever truly improving?

This is the central challenge that supply chain and operations leaders face, and it is far more consequential than most organizations realize. The question of who is to blame is almost always the wrong question. The right question is almost always this: what is wrong with the system that allowed this to happen?

The Blame Game Is a Leadership Problem, Not a People Problem

In a recent episode of IndustryWeek’s Behind the Curtain: Adventures in Continuous Improvement podcast, hosts Dr. Mohamed Saleh and John Dyer made a point that deserves to be heard in every operations meeting in America. When things go wrong on the plant floor or in the supply chain, front-line workers are rarely the real culprit. The broken system is. And the people who own the system, who design it, fund it, and choose not to fix it, are the leaders and executives sitting at the top.

Dyer shared a story from his time at General Electric where a cascade of failures brought production to a halt and cost the company real revenue. The causes? Delayed preventive maintenance. A lack of spare parts. Neither of those things was within the control of the workers being scrutinized in the aftermath. They were squarely the responsibility of the management structure that had failed to build a system that could prevent or flag those problems in advance.

The broken system is the culprit. And the people who own the system are the leaders and executives, not the workers.

This pattern is not unique to General Electric. It plays out in midmarket manufacturers, distributors, and retailers every single week. And it points to something much deeper than poor individual performance. It points to an industry-wide gap between the decisions that need to be made and the infrastructure available to make them well.

What Continuous Improvement Research Has Been Telling Us for Decades

The tradition of systems thinking in operations is not new. Dr. W. Edwards Deming, whose work transformed manufacturing quality in the twentieth century, was emphatic on this point. His research essentially argues that the vast majority of quality problems in any organization are the result of faulty systems, not faulty people. He estimated that around 94 percent of operational problems could be traced back to the system itself, including the processes, tools, information flows, and decision structures that workers are operating within, rather than to individual human error.

Deming’s twelfth point for management goes even further: remove the barriers that rob hourly workers of their right to pride of workmanship. That framing is worth sitting with. The idea that systemic failures do not just hurt operational efficiency but actively steal something from the people doing the work. They take away the ability to do a good job, to feel capable, to bring real skill and judgment to bear. And then they blame those same people when the results are poor.

This is not just a management philosophy problem. It is a practical, daily reality for planners, schedulers, procurement teams, and operations managers working inside organizations where the information they need to make good decisions is scattered across dozens of spreadsheets, siloed in legacy ERP systems, or simply not available in real time.

The Hidden Architecture of Operational Failure

To understand why the blame culture persists, you have to understand what the decision-making environment actually looks like inside most midmarket manufacturing and distribution organizations.

Picture a senior planner who arrives at work on Monday morning and needs to make a production scheduling decision that accounts for current inventory levels, supplier lead times, customer demand signals, labor availability, and machine capacity. In an ideal world, that information would be integrated, current, and presented in a way that allows the planner to apply their expertise and experience to reach a good decision quickly.

In the actual world that most planners inhabit, that information lives in 24 different spreadsheets. Some of it is updated weekly. Some of it is updated by whoever remembered to update it. The planner spends the first several hours of their day just aggregating data before they can begin to think about the actual decision. By the time the analysis is complete, some of the inputs are already stale.

This is not a hypothetical. One A2go customer, a $400 million industrial manufacturer called TACO, was doing exactly this, spending 18 hours across 24 spreadsheets to produce a production schedule that was already partially out of date the moment it was finished. The planner was not failing. The system was failing the planner.

When a scheduling error eventually led to a downstream problem, who do you imagine got the phone call?

This is the architecture of operational failure. It is not built out of incompetence. It is built out of disconnected information systems, insufficient decision support tools, and an assumption that skilled people can compensate for broken infrastructure through sheer effort and experience. They can, for a while. Until they cannot.

Why Finger-Pointing Makes the System Worse, Not Better

There is a particular irony in the blame game that deserves attention: the act of blaming individuals for systemic failures does not just fail to fix the underlying problem, it actively makes the system harder to fix over time.

Here is why. When people in an organization learn that making a mistake, or even being visible in the vicinity of a mistake, leads to scrutiny, criticism, or consequences, they adapt. They adapt by hedging their decisions. By waiting for explicit instruction before acting. By avoiding the kind of proactive, judgment-based decision-making that good operations actually requires. By not sharing bad news until it absolutely cannot be hidden anymore.

Deming called this dynamic driving out the ability to work effectively through fear. His eighth point for management is explicitly about this: drive out fear, so that everyone may work effectively for the company. Fear does not produce better decisions. It produces slower decisions, more conservative decisions, and, critically, decisions that are made in the dark because the information that would have improved them was not shared in time.

In supply chain terms, this translates directly to the bullwhip effect. Demand signals get distorted as they pass through the chain because each node is managing its own uncertainty, hoarding its own buffer, and making its own conservative assumptions rather than operating from shared, transparent intelligence. The systemic result of individual fear is systemic volatility.

The solution is not to demand better individual performance under the same broken conditions. The solution is to redesign the decision-making environment so that good information reaches the right people at the right time, in a form they can actually use.

Decision Debt: The Operational Equivalent of Technical Debt

Software engineers are familiar with the concept of technical debt, the accumulation of quick fixes, workarounds, and shortcuts that solve immediate problems but create larger structural problems over time. At some point, the debt comes due, usually at the worst possible moment.

Operations leaders are dealing with the exact same phenomenon, though it rarely gets named as clearly. Call it decision debt.

Decision debt accumulates every time a planner makes a scheduling call without full visibility into supplier constraints. Every time a procurement team places a purchase order based on a demand forecast that is six weeks old. Every time a safety stock level is set by a formula in a spreadsheet that nobody has revisited in three years. Every time an S&OP process produces a plan that three different departments interpret differently because there is no shared source of truth.

Each of those moments represents a decision made with incomplete information, using inadequate tools, under time pressure that does not allow for better analysis. Individually, many of those decisions will be fine. But they accumulate. They interact. They compound. And eventually, when the system produces a significant failure, the organization looks for who made the bad decision rather than recognizing the weight of accumulated debt that made any individual decision nearly impossible to get right.

When you understand that most operational failures are the product of decision debt, the response changes from ‘who do we hold accountable?’ to ‘what do we fix in the system?’

That is a fundamentally different conversation. And it is a much more productive one.

The Role of Leaders in Building Accountable Systems

None of this is an argument against accountability. Accountability is essential. But there is a critical distinction between holding people accountable for the quality of their decisions given the information and tools available to them, versus holding people accountable for the outcomes of a system that was never designed to produce consistently good outcomes in the first place.

True leadership accountability in operations means asking a different set of questions after a failure:

Was the planner working with current, accurate information? If not, why not, and what would it take to provide it? Was the decision process clearly defined, so the planner knew what inputs to consider and how to weigh them? Did the planner have the tools to model different scenarios and understand the downstream implications of each option? Was there a mechanism for the planner to escalate uncertainty, to flag that this decision was outside their confidence level and needed additional review?

These are the questions that build better systems. They are also, not coincidentally, the questions that build more engaged, more capable, and more loyal teams. People who are given good tools, clear processes, and real information to work with will produce better results than brilliant people straining against broken infrastructure. Every time.

The Intelligence Gap in Midmarket Operations

One of the most consistent patterns across midmarket manufacturers and distributors is what might be called the intelligence gap. These organizations are often extremely sophisticated in their actual operations, in the craftsmanship of what they make, in their relationships with customers and suppliers, in the institutional knowledge held by their experienced teams. But their decision-making infrastructure has not kept pace with the complexity of the decisions they are being asked to make.

The global supply chain has become dramatically more volatile over the past decade. Supplier networks are more extended and more interdependent. Customer demand patterns are less predictable. Regulatory environments are more complex. The margin for error on key decisions, what to stock, when to order, how to sequence production, how to allocate limited capacity, has shrunk while the number of variables affecting those decisions has grown.

The tools most midmarket organizations are using to manage that complexity have not kept pace. Legacy ERP systems were built to record transactions, not to support real-time decision-making. Spreadsheets are powerful and flexible, but they are not designed for the kind of dynamic, multi-variable scenario analysis that modern supply chain decisions require. And the institutional knowledge held by experienced planners, invaluable as it is, is not scalable, not transferable, and not available at two in the morning when a supplier sends an alert that changes everything.

The result is an intelligence gap: a widening distance between what the decision environment demands and what the decision-making infrastructure can provide. And the people working inside that gap are the ones who end up holding the bag when the gap produces a failure.

From Reactive to Proactive: What Better Decision Infrastructure Looks Like

Closing the intelligence gap requires more than incremental improvement to existing tools. It requires rethinking the architecture of how decisions are made in the first place.

What would it mean for a production planner to have real-time visibility into every constraint affecting their scheduling decision, integrated into a single decision environment rather than distributed across dozens of disconnected systems? What would it mean for a procurement team to receive an alert not just that a supplier has a capacity problem, but that the problem affects three specific SKUs that are within 14 days of a stockout, and here are four alternative sources ranked by lead time and cost?

What would it mean for an S&OP team to run their planning process against a shared, continuously updated model of demand and supply rather than a set of competing spreadsheets that each department manages independently?

The answer to each of those questions is the same: it would mean that the people making those decisions could make them better. Not because they suddenly became smarter or more experienced, but because the system finally gave them what they needed to apply their intelligence effectively.

This is the shift from reactive operations, where the organization is constantly responding to failures that have already occurred, to proactive operations, where the system surfaces issues and options before they become crises. It is the difference between doing a post-mortem on a stockout and preventing the stockout. Between explaining why a production run was interrupted and scheduling around the constraint that would have caused it.

That shift does not happen by blaming people harder. It happens by building better systems.

Culture Follows Infrastructure

One thing that operations leaders sometimes underestimate is the relationship between decision infrastructure and organizational culture. The assumption is often that culture is something you build through communication, values statements, leadership behavior, and team development. And all of those things matter.

But culture is also built by what people experience when they come to work every day. If the daily experience of a planner is that they spend most of their time aggregating data from broken systems, making decisions under time pressure with incomplete information, and then getting scrutinized when those decisions do not produce perfect outcomes, that experience shapes culture. It produces a culture of defensiveness, of risk-aversion, of minimal information sharing, of quiet disengagement.

Conversely, when the daily experience is that the systems provide the information needed, that decisions are made with confidence and transparency, that the reasoning behind decisions is captured and reviewable, that errors are treated as signals about the system rather than indictments of the individual, that experience also shapes culture. It produces a culture of engagement, of initiative, of continuous improvement, of trust.

You cannot build a culture of accountability without first building the infrastructure that makes good decisions possible. The culture follows the infrastructure. Always.

A2go: Decision Intelligence That Fixes the System, Not the People

Everything described in this post, the decision debt, the intelligence gap, the blame cycle, the reactive operations culture, is precisely the problem that A2go was built to solve.

A2go is an Agentic Decision Intelligence Platform (ADIP) designed specifically for midmarket manufacturers, distributors, and retailers. It works as an ERP-agnostic overlay, which means it does not require a rip-and-replace of existing systems. It integrates with the data and systems you already have and transforms that raw material into structured, actionable decision intelligence, delivered in weeks, not months or years.

At the core of the A2go platform is the Data Orchestration Layer, which pulls information from across the organization into a unified, continuously updated model of the business. That model powers a suite of Supply Chain Agents, including Safety Stock Optimization, Ship Complete Excellence, S&OP Intelligence, Purchase Order Excellence, Bill of Operations Intelligence, and Master Production Scenario Intelligence.

The Judgment Layer: Auditing the System, Not the Person

What makes A2go genuinely different is the Judgment Layer.

The Judgment Layer does something no spreadsheet and no traditional ERP system can do: it captures the reasoning behind decisions. Not just what was decided, but why, what information was considered, what trade-offs were weighed, what conditions led to a particular recommendation. This is exactly the capability that transforms the whodunit conversation from a blame exercise into a systems improvement exercise.

When something goes wrong, A2go gives leadership the ability to trace back through the decision chain and understand what the system knew, what it recommended, what the planner decided, and what conditions changed between the decision and the outcome. That is auditable, improvable, and, critically, honest. It tells you whether the decision was wrong or whether the outcome was the result of information that was not available at the time. Those are very different things. And knowing the difference is the first step toward actually fixing the system.

Proven Results

A2go’s customer results validate this approach. TACO, the $400 million industrial manufacturer, reduced its production scheduling process from 18 hours across 24 spreadsheets to 15 minutes, with a 400 percent return on investment. JBS, the $8 billion global protein processor operating across 37 facilities and 27 regulatory regimes, deployed A2go to bring coherent decision intelligence to a supply chain of staggering complexity.

In both cases, the result was not just operational improvement. It was the creation of a decision environment where planners could do their jobs well, where leadership could see clearly what was happening and why, and where the question shifted from who messed this up to how do we make this better.

That is what good decision infrastructure makes possible. Not perfection, supply chains will never be perfect. But clarity. Transparency. The ability to learn from what goes wrong and build systems that go wrong less often. And a working environment where talented people are set up to succeed rather than set up to fail.

If your organization is still stuck in the whodunit cycle, still running post-mortems that end with blame rather than systems improvement, it may be time to ask whether the problem is really the people, or the system those people are working inside.

The answer, more often than not, is the system. And the good news is: systems can be fixed.

Frequently Asked Questions

The following questions and answers are designed to address common search queries from supply chain and operations leaders researching these topics.

Why do most operational failures get blamed on individuals rather than systems?

Blaming an individual feels actionable. You can hold a person accountable, discipline them, replace them. Fixing a system is harder to see, harder to execute, and requires leaders to take ownership of something that implicates their own decisions and investments. Research in continuous improvement going back to Deming’s work in the mid-twentieth century consistently shows that the vast majority of operational failures, some researchers estimate upward of 90 percent, are rooted in systemic issues rather than individual error. The blame instinct is understandable, but it is almost always misdirected.

What is decision debt, and how does it affect manufacturing operations?

Decision debt is the accumulation of suboptimal decisions made over time due to inadequate information, outdated tools, and insufficient decision support infrastructure. Every time a production plan is built on stale demand data, every time a safety stock level goes unreviewed for months, every time a procurement call is made without visibility into supplier constraints, that is decision debt accruing. Like financial debt, it compounds. The operational failures that seem sudden and dramatic are usually the moment when accumulated decision debt becomes impossible to absorb. Addressing decision debt requires investing in better decision infrastructure, not just demanding better individual performance.

How does agentic AI help supply chain teams make better decisions without replacing human judgment?

Agentic AI in supply chain planning operates by doing what humans cannot do at scale: continuously monitoring dozens of data streams simultaneously, flagging issues before they become crises, modeling scenarios and their downstream implications, and presenting that analysis to human decision-makers in a form they can act on quickly. The human remains in the decision seat, bringing contextual knowledge, stakeholder awareness, and judgment that no algorithm can fully replicate. What changes is the quality and completeness of the information available to that human at the moment of decision. Agentic AI removes the intelligence gap without removing the human. It makes planners more effective, not redundant.

What does a Judgment Layer do that a traditional ERP or planning tool cannot?

Traditional ERP systems are designed to record and process transactions. Advanced planning and scheduling tools can model scenarios. But neither captures the reasoning behind decisions in a way that is auditable and improvable over time. A Judgment Layer records not just what decision was made, but what information was considered, what trade-offs were evaluated, and what logic led to the recommendation. This creates an organizational memory of decision-making that makes it possible to review decisions after the fact, understand whether outcomes were the result of bad decisions or unexpected conditions, and continuously refine the decision logic over time. It is the difference between a system that produces decisions and a system that learns.

How quickly can a midmarket manufacturer or distributor expect to see results from a decision intelligence platform?

Implementation timelines vary based on data readiness and the complexity of existing systems, but ERP-agnostic platforms designed for midmarket organizations are specifically architected for rapid deployment. Unlike large enterprise software implementations that can take 12 to 24 months before delivering value, a modern agentic decision intelligence platform deployed as an overlay can begin delivering meaningful results, including reduced planning cycle times, improved fill rates, and better inventory positioning, within weeks. The key is that the platform works with your existing data infrastructure rather than requiring you to replace it. The goal is time-to-value measured in weeks, not years.