The Knowledge System Podcast

Many organizations run on urgency. Something breaks. A customer complains. A deadline slips. Leaders jump in to fix the problem. The system is restored, the crisis passes, and everyone moves on to the next issue. It feels productive. It feels responsible. Sometimes it even feels heroic.

But constant firefighting can hide a deeper truth: restoring a system after a problem occurs is not the same as improving it. W. Edwards Deming warned that many organizations stay trapped in cycles of reaction because leaders confuse solving problems with improving the system that creates them.

The trap of solving today’s problems

Leaders are trained to respond quickly when problems appear. A delivery runs late. A customer complains. A system breaks. Responsible managers step in, solve the issue, and get operations back on track. In the moment, this feels like effective leadership.

But Deming argued that reacting to problems is often only temporary relief. When the same kinds of problems appear again and again, the issue is rarely a single mistake or a careless employee. More often, the system itself is producing the outcomes we see.

This is one of the hardest ideas for managers to accept. When an organization is busy and customers need help, stepping back to study the system can feel like the wrong response. Yet without understanding how the system works, leaders may spend years solving the same problems over and over.

A small service company illustrates how this cycle unfolds—and how a different way of thinking can finally break it.

A business that lived in constant emergencies

Carlos owned a growing neighborhood HVAC service company. Business was strong. Phones rang throughout the day. Trucks were constantly on the road.

From the outside, the company looked successful. Inside the office, however, each afternoon felt chaotic.

Technicians called needing parts. Customers demanded urgent visits. Jobs ran longer than expected and the carefully planned schedule began to unravel. Dispatchers scrambled to rearrange appointments while Carlos jumped in to solve problems as quickly as they appeared.

“Move that install to tomorrow,” he told the dispatcher one afternoon. “Send Mike over to Mrs. Jenkins. I’ll call the supplier and see if we can rush that part.”

The day would stabilize. Customers were helped. Emergencies were handled. But the next day looked almost exactly the same. By midweek the technicians were exhausted, dispatchers were frustrated, and Carlos felt like he spent every day racing from one crisis to the next.

Eventually he began to notice something important. The emergencies were not random. They followed patterns.

Jobs were scheduled too tightly. Some technicians were handling complex repairs before they had enough experience. Parts needed for common repairs were not always available when technicians arrived at a job. None of these problems were unusual events. They were built into the way the system operated.

Deming described this distinction clearly in Out of the Crisis: “Putting out fires is not improvement of the process. This only puts the process back to where it should have been in the first place.”

Putting out fires is not improvement of the process. This only puts the process back to where it should have been in the first place.— W. Edwards Deming

Carlos slowly realized something uncomfortable. His daily heroics were not improving the business. They were simply restoring the system to where it had been before the latest disruption.

At the next team meeting he made an unexpected announcement.

“We’re not fixing today’s schedule,” he told the group. “We’re studying how our schedule works.”

The team began mapping a typical service day. They looked at travel times between neighborhoods. They tracked which types of jobs commonly ran long. They identified repairs that frequently required parts technicians did not carry.

Gradually they began changing the system. Service appointments were spaced differently. New technicians received more structured training. Trucks were stocked with the parts most commonly needed for repairs.

And over time something surprising happened. The emergencies began to fade. Carlos realized that his technicians had never been the problem.

As Deming often reminded leaders: “A bad system will beat a good person every time.”

A bad system will beat a good person every time.— W. Edwards Deming

Once the system improved, the daily firefighting that once dominated the company began to disappear.

Why leaders keep fighting the same fires

Most managers recognize the exhaustion that comes from constant firefighting. Yet many organizations remain trapped in that pattern for years.

Part of the reason is psychological. Solving problems feels productive. When a leader steps in and rescues a situation, the result is immediate and visible. Customers are satisfied. The crisis ends. The day is saved.

System improvement is different. It requires stepping back. Studying patterns. Slowing down long enough to understand how the work actually functions. In organizations that value speed and responsiveness, this can feel uncomfortable.

We also tend to interpret problems as individual failures. A technician made a mistake. A dispatcher scheduled something incorrectly. A customer service representative handled a call poorly.

But when the same types of issues appear repeatedly, a more useful question emerges: What in the system allowed this to happen?

Without this shift in thinking, managers spend enormous energy reacting to symptoms while the underlying system remains unchanged. And the result is predictable. Tomorrow, the same fires return.

What leaders can do instead

* Distinguish between restoring and improving. Solving a problem often restores the system to where it was before the disruption. Improvement means changing the system so the problem is less likely to occur again.

* Look for patterns before reacting. When similar issues appear repeatedly, assume the system may be producing them. Studying patterns reveals far more than reacting to isolated events.

* Examine how the work is designed. Scheduling rules, training, handoffs, information flow, and resource availability often shape outcomes more than individual effort.

* Stop rewarding firefighting. Organizations often celebrate the people who rescue crises. A healthier culture recognizes leaders who prevent those crises by improving the system.

* Shift leadership attention upstream. Instead of focusing only on today’s problems, ask how the system itself might be redesigned to produce better results tomorrow.

Improvement begins when firefighting ends

Every organization encounters problems. That will never disappear.

But leaders shape how their organizations respond. Some spend their days racing from crisis to crisis—restoring the system after each disruption. Others step back and study how the system itself produces those disruptions.

Deming believed the difference between these two approaches defines the difference between activity and improvement.

Thoughtful leaders focus not only on solving today’s problems, but on building systems that produce better outcomes tomorrow.

Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work.

Most organizations assume the path to better performance is straightforward: Motivate individuals. Reward top performers. Rank employees. Offer incentives for beating targets. At first glance, the logic seems sound. If individuals push harder, the organization should perform better.

But many leaders eventually discover an unintended consequence. Systems designed to reward individuals often create internal competition that quietly weakens the organization itself. People begin protecting their own results. Information flows more slowly. Cooperation becomes optional instead of natural.

W. Edwards Deming warned leaders about this dynamic decades ago. He argued that organizations are not collections of independent performers—they are systems. As Deming explained, “A system is a network of interdependent components that work together to try to accomplish the aim of the system.”

A system is a network of interdependent components that work together to try to accomplish the aim of the system.— W. Edwards Deming

When leaders forget that truth, incentives can pull people apart instead of bringing them together. The shift from “Me” thinking to “We” thinking is often the difference between an organization that struggles internally and one that improves steadily over time.

A retail store that learned the difference

Karen owned a small clothing boutique on a busy downtown street. Her store had loyal customers and a hardworking team of associates. Like many business owners, Karen believed motivation was the key to growth. To encourage stronger sales, she introduced commissions and a monthly leaderboard recognizing the store’s top sellers.

At first, the results looked promising. Sales increased slightly. Associates competed enthusiastically. The leaderboard created excitement on the sales floor.

But slowly, subtle problems began appearing. Customers sometimes waited longer for help even when several employees were nearby. Associates quietly argued about who greeted a shopper first. Employees hesitated to assist customers who were already speaking with another associate.

One evening after closing, Karen sat down with her store manager, Miguel.

“I thought commissions would motivate everyone,” Karen said. “But lately the store feels tense.”

Miguel nodded. “I’ve noticed it too,” he replied. “Everyone’s watching their own numbers. If someone else starts helping a customer, the rest of the team just stays back.”

Karen began reviewing the previous three months of store data. Sales had increased slightly. But other indicators were moving in the wrong direction. Returns were rising. Customers were buying fewer items per visit. A few online reviews mentioned inconsistent service.

Karen leaned back in her chair. “Maybe we’ve built a system where everyone is competing inside the same store,” she said.

Miguel shrugged. “That’s how retail usually works.”

Karen paused for a moment. “Maybe that’s the problem.”

The moment the system became visible

Deming warned leaders about systems that reward individual competition. “The merit rating nourishes short-term performance, annihilates long-term planning, builds fear, demolishes teamwork, and nourishes rivalry and politics,” he wrote.

The merit rating nourishes short-term performance, annihilates long-term planning, builds fear, demolishes teamwork, and nourishes rivalry and politics.— W. Edwards Deming

Karen suddenly saw her commission system differently. The leaderboard rewarded individual wins—even when those wins hurt the customer experience or the team. In other words, the system encouraged employees to think “Me” instead of “We”.

Rather than reacting quickly, Karen decided to try a small experiment. First, she removed the leaderboard ranking associates against one another. Second, she replaced individual commissions with a shared store bonus tied to overall performance and customer satisfaction. Finally, she changed the question she asked during team meetings. Instead of asking who made the most sales, she began asking something different: “How well did we serve customers together?”

Within weeks, Miguel noticed subtle changes across the store. Associates stepped in to help each other without hesitation. Customers were greeted faster. Product knowledge began flowing more freely between employees. The tension that had crept into the store started to fade.

And the results followed. Average purchase size increased. Customer reviews improved. Repeat customers returned more often. Sales rose—not because individuals competed harder, but because the system itself worked better.

Where managers often get misled

When results decline, many of us instinctively focus on individuals. We assume people need more motivation, clearer goals, or stronger incentives.

But Deming taught that most performance differences come from the system people work within. When we create systems that reward individual victories, people naturally begin protecting their own results. Collaboration becomes risky. Helping a colleague can feel like sacrificing personal success.

From the outside, these behaviors may look like personality issues or poor attitudes. In reality, they are predictable responses to the environment we created. When we design systems that reward “Me,” we should not be surprised when people act that way.

The alternative is to design systems that make cooperation the easiest and most natural choice.

Actionable Takeaways

Leaders who want to move from Me to We do not need dramatic changes. Small adjustments in how work is designed can dramatically shift behavior.

* Examine your incentives. Ask whether your current rewards encourage people to outperform colleagues—or to improve the results of the entire organization.

* Look at how success is discussed. If conversations focus primarily on ranking people, the system may be encouraging competition rather than cooperation.

* Encourage shared responsibility. When employees help one another succeed, recognize the behavior as valuable to the whole system.

* Focus on improving the system. Instead of asking who performed best, ask what changes would help everyone perform better.

These small shifts begin moving an organization away from individual victories and toward a shared aim.

The power of “We”

When organizations shift from Me thinking to We thinking, something remarkable happens. Cooperation becomes normal. Problems surface earlier. Learning spreads faster. Customers feel the difference because they are served by a coordinated team rather than disconnected individuals. The organization becomes calmer, more capable, and more resilient—qualities that, over time, can become a genuine competitive advantage.

The lesson is simple. When leaders design systems that reward Me, they get competition. When leaders design systems that encourage We, they get cooperation.

And cooperation is where the real strength of an organization begins.

Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work.

Most leaders say they want more innovation. They ask for ideas, listen closely to customers, and push teams to ship faster. Yet the breakthroughs they’re hoping for rarely arrive. What shows up instead is a steady stream of incremental features—busy, responsive, and oddly unsatisfying.

W. Edwards Deming challenged a deeply held assumption behind this pattern: that customers will tell you what to build next. He argued that this belief doesn’t make organizations more innovative. It quietly removes one of management’s most important responsibilities.

When customer-driven becomes customer-designed

Being “customer‑driven” sounds unquestionably right. Leaders want to respect customers, respond quickly, and avoid building things nobody asked for. Over time, this mindset becomes embedded in roadmaps, prioritization rituals, and product reviews. Requests are collected, ranked, and delivered with discipline.

Deming warned that something subtle is lost in this approach. Customers are experts in their own frustration, but they are not responsible for inventing your future. That work belongs to leadership—using theory, prediction, and learning.

Innovation, in Deming’s view, is not a burst of inspiration or a lucky insight. It is management work. And like any other responsibility, it either gets designed and managed—or it slowly degrades into noise.

A team that listened—and still missed it

Brightwave Software sold workflow tools to mid‑sized operations teams. Internally, the company appeared to be doing everything right. Sprints were predictable. Support tickets were trending down. Feature requests were delivered faster than ever.

Still, growth had started to flatten.

Alex, the CEO, struggled to reconcile the dashboards with the results. Renewal rates were softening, but no one could explain why. The metrics were green. Customer satisfaction scores were stable. On paper, execution looked strong.

“Everything looks healthy,” Alex said during one leadership meeting. “But renewals are flattening, and I can’t connect the dots.”

Maria, the head of product, explained the team’s approach. Customer requests drove the roadmap. The most common asks were reviewed quarterly and prioritized carefully.

“We’re doing exactly what customers ask for,” she said. “If something were wrong, we’d see it in the data.”

That logic felt sound. It was also incomplete.

As the leadership team talked, another possibility emerged. What if customers weren’t articulating their next problem because they couldn’t? What if the friction wasn’t tied to any single feature, but to how fragmented the overall experience had become as customers scaled?

Instead of gathering more requests, the team articulated a theory. They believed customers were struggling with cognitive load—too many options, too many configuration paths, too much effort to keep work flowing smoothly.

They designed a small experiment. One cohort of customers received a simplified, opinionated workflow that removed choices instead of adding them. The team predicted adoption would improve for new users and stall for experienced ones.

The results surprised them. New users adopted the workflow quickly. More unexpectedly, experienced users did as well. Reducing choice reduced friction and freed up attention.

The breakthrough didn’t come from asking customers what to build. It came from leadership taking responsibility for learning.

Deming put it bluntly: “Does the customer invent new product or service? The customer generates nothing.” His point was not to dismiss customers, but to prevent leaders from outsourcing their job.

Does the customer invent new product or service?The customer generates nothing.— W. Edwards Deming

Where good intentions quietly derail innovation

Most organizations do not struggle with innovation because they ignore customers. They struggle because they confuse listening with leading.

When roadmaps are treated as collections of requests, innovation becomes reactive by default. Teams ship faster, but learning slows down. Output increases while insight declines. Over time, the organization becomes very good at responding to yesterday’s problems.

We often reinforce this pattern unintentionally. Requests, votes, benchmarks, and competitor features feel objective. They feel safe. They give leaders something concrete to point to when decisions are questioned.

Deming put it plainly: “Experience without theory teaches nothing.” Without a clear prediction about how the system will behave, organizations accumulate activity rather than knowledge—and motion gets mistaken for progress.

The result is frustration. Teams feel busy but ineffective. Leaders ask for more innovation while maintaining systems that quietly prevent it.

Experience without theory teaches nothing.— W. Edwards Deming

Actionable Takeaways

There is a more disciplined path forward, and it begins by reclaiming innovation as management work.

* Separate customer input from customer design. Customers provide invaluable insight into pain, context, and constraints. But solutions belong to the organization. Treat requests as data to be studied, not instructions to be followed.

* Require theory before action. Every innovation effort should begin with a prediction: what will change, for whom, and why. Shipping without prediction creates noise, not learning.

* Use PDSA to systematize innovation. Plan with a hypothesis. Do on a small scale. Study results honestly. Act by standardizing what works—or revising what doesn’t. This turns innovation from a gamble into a learning system.

Bringing innovation back where it belongs

Innovation is not about guessing what customers will ask for next. It is about taking responsibility for what they will need before they can say it. Deming captured the challenge succinctly: “It is necessary to innovate, to predict needs of the customer, give him more.”

It is necessary to innovate, to predict needs of the customer, give him more.— W. Edwards Deming

When leaders stop outsourcing innovation and start managing it as a system of learning, something changes. The organization becomes calmer. Choices become clearer. Progress stops feeling accidental.

Innovation, done the Deming way, isn’t heroic. It is intentional. And that is what makes it sustainable.

When pressure rises, leaders look sideways. A competitor simplifies an offer, tightens pricing, or adopts a new tool—and suddenly it feels irresponsible not to follow. After all, they’ve already tested it. The market seems to respond. What’s the harm in borrowing what works?

W. Edwards Deming warned that this instinct is more dangerous than it looks. Copying competitors feels like learning, but it isn’t. It replaces understanding with imitation—and over time, it quietly erodes the capabilities that create lasting advantage.

Looking sideways feels sensible

Competitive awareness is often praised as strategic discipline. Leaders are taught to benchmark, compare, and react. When growth slows or margins tighten, this behavior intensifies. Decisions increasingly begin with familiar questions: What are they offering? How are they pricing? What tools are they using?

Deming didn’t argue that leaders should ignore the outside world. He argued something more subtle—and more demanding: examples without theory don’t teach improvement. When you copy a result without understanding the system that produced it, you’re not learning. You’re guessing.

The temptation to guess is strongest when results are hard to observe directly. Success is shaped by hidden conditions: workflow design, skills, decision rights, feedback loops, and constraints. Those don’t appear in a competitor’s marketing or pricing sheet. What does appear are surface features—offers, promises, and positioning—and those are the easiest things to imitate.

A familiar story

Alex ran a mid-sized professional services firm with smart people, loyal clients, and a solid reputation. For years, growth had been steady. Then sales began to slow. Deals dragged. Clients hesitated.

At the same time, a competitor started winning work with a clean, packaged offering. Fixed scope. Fixed price. Confident messaging. Prospects mentioned it repeatedly.

“Everyone keeps bringing them up,” Alex said in a leadership meeting. “Clients say, ‘They make it simpler.’ We’re losing deals we used to win.”

The pressure to respond was immediate.

“They’re just repackaging what everyone else does,” Morgan replied. “We could roll this out in a month.”

“If clients want simple, let’s give them simple,” Alex agreed. “Same structure. Same price points. We can’t afford to look complicated.”

The firm moved fast—new packages, new website copy, new proposal templates. From the outside, they looked competitive again.

Inside, things unraveled.

“Delivery’s struggling,” Morgan said a few weeks later. “The teams keep escalating scope questions. The package assumes things we don’t actually control.”

“But that’s how they sell it,” Alex replied, gesturing toward the competitor’s brochure on the table.

“Yes—but we don’t know how they deliver it.”

Deming warned about this exact trap: copying the visible example while ignoring the invisible system. The firm had copied the promise, not the capability. The packaging assumed standardized work, predictable inputs, and stable handoffs—none of which the firm had invested in.

Projects began running over. Staff felt squeezed between rigid promises and messy reality. Clients noticed the growing gap between what was sold and what actually showed up.

“We fixed the sales problem,” Alex finally admitted, “and created a delivery problem.”

That pause mattered. Instead of doubling down—tightening enforcement, blaming teams, or discounting harder—Alex asked a different question: What theory are we operating under? What did they believe actually created value for clients? And what system was required to deliver that value reliably?

The firm began studying its own work. Where projects slowed. Where rework came from. Which clients benefited most, and why. They ran small tests before changing external promises—clarifying scope boundaries, simplifying internal handoffs, and making client responsibilities explicit.

“The competitor’s package wasn’t wrong,” Morgan observed. “It just wasn’t ours.”

Over time, the firm rebuilt its offering around outcomes it could actually deliver. Sales stabilized—not because the firm looked like everyone else, but because its promises finally matched its system.

Where leaders go wrong

Most leaders don’t copy competitors out of laziness. They do it out of urgency. Comparison feels like action. It provides cover. If everyone is moving in the same direction, the risk feels shared and defensible.

The trouble is that copying shifts attention away from the system that produces results. It encourages leaders to manage appearances instead of capability. Organizations become skilled at changing what they say—new offers, new pricing, new tools—while leaving how work actually gets done largely untouched.

Deming captured this dynamic with a sharp observation: “What would some people do without their competitors?” When competitors become the primary reference point, learning stalls. Decisions become reactive. Improvement turns into imitation rather than inquiry.

What would some people do without their competitors?— W. Edwards Deming

There’s a second cost that’s easier to miss. As Deming also noted, “The fact is that the customer expects only what you and your competitor have led him to expect. He is a rapid learner.” Copying competitors doesn’t just follow the market—it trains it. Expectations ratchet upward, margins compress, and organizations find themselves competing harder while improving less.

In that environment, leaders can feel busy and responsive while the system itself remains fragile. The work becomes harder, not because people lack effort or skill, but because the organization hasn’t invested in understanding how results are actually produced.

Actionable Takeaways

Moving beyond imitation doesn’t require ignoring competitors. It requires changing how their ideas are used—and what questions leaders ask first.

* Start with aim. Be explicit about who you serve, what problem you solve, and what “better” means over time. Without a clear aim, competitor behavior quietly becomes your strategy.

* Turn examples into hypotheses. Instead of copying what worked elsewhere, ask why it might work—and what conditions would need to be true in your system for it to succeed. Treat every borrowed idea as something to test, not adopt.

* Study the delivery system first. Offers, pricing, and positioning are system decisions. If you change the front end without strengthening the back end, you create stress—not improvement.

* Use theory to learn. Deming said, “Experience teaches nothing… Without theory there is no learning.” Improvement requires prediction, testing, and reflection—not imitation.

A simple test helps ground this thinking. Before approving a competitor-inspired change, ask what capability must improve for the promise to be kept. If you can’t name it, you’re not improving the system—you’re decorating it.

Closing

Copying competitors feels safe because it spreads the risk. If everyone’s doing it, it can’t be wrong—right?

Deming challenged that comfort. When leaders stop borrowing answers and start building knowledge about their own work, something shifts. Learning replaces imitation. Confidence grows from understanding, not comparison.

Real competitive advantage comes from knowing your system well enough to improve it deliberately. When improvement becomes steady and capability compounds over time, the focus moves away from keeping up—and toward building something others struggle to copy.

Experience teaches nothing… without theory there is no learning.— W. Edwards Deming

When leaders hear that most problems belong to the system, it can sound like an accusation—or worse, an invitation to lower standards. So nobody’s lazy? Nobody incompetent? That reaction is understandable. It’s also costly. The real question isn’t whether individuals ever contribute to problems. It’s whether leaders are aiming their time and energy at the place where improvement actually lives. Today we’ll explore why blaming workers feels decisive, why it so often misses the mark, and how a clearer way of thinking leads to better results.

Why blaming the worker feels obvious

W. Edwards Deming never asked leaders to take anything on faith. He asked them to study evidence. Yet his ideas are frequently dismissed as naïve because they seem to collide with lived experience. Leaders have seen missed deadlines, chronic rework, and visible disengagement. They’ve had hard conversations. They’ve replaced people—and sometimes things really did improve.

So when Deming says that most problems belong to the system, it can sound like an absolutist claim that denies reality. It isn’t. What Deming challenged was a habit of mind: explaining outcomes by pointing at people instead of understanding the conditions that shape their work. When the same problems repeat across teams and across individuals, he argued, we are not observing human failure. We are observing a system doing exactly what it was built—and allowed—to do.

To see how this misunderstanding plays out, consider a familiar manufacturing setting.

Reconsidering where problems come from

Midwest Components manufactures precision parts for heavy equipment. Late orders have become routine. Scrap rates swing from week to week. Supervisors are worn down by constant firefighting.

At the center of it are two leaders. Jack, the plant manager, came up through operations. He prides himself on knowing the floor and holding people accountable. Maria, the operations director, was brought in to stabilize performance and reduce chronic volatility.

Jack is blunt about his frustration. “Look,” he says, “I don’t buy this idea that it’s all the system. I’ve been here twenty years. I know when someone just doesn’t care.”

Maria doesn’t dispute that people matter. “I’m not saying people don’t matter,” she says. “I’m asking a different question. If we swap operators between lines and the problems stay with the line, what are we really seeing?”

They review six months of data together. Late orders spike predictably at month end when schedules compress. Scrap jumps whenever a specific alloy lot is introduced. Training records show three operators rushed onto a new machine with minimal setup instruction.

Jack pushes back. “So what,” he asks, “nobody’s accountable?”

Maria draws a distinction. Accountability isn’t the same as blame. The patterns they’re seeing don’t belong to one person. They belong to how work is planned, supplied, and taught.

This is the pivot Deming insisted on. In Out of the Crisis, he wrote, “The supposition is prevalent the world over that there would be no problems in production or in service if only our production workers would do their jobs in the way that they were taught. Pleasant dreams. The workers are handicapped by the system, and the system belongs to management.”

That statement isn’t a moral judgment. It’s a diagnostic one.

The supposition is prevalent the world over that there would be no problems in production or in service if only our production workers would do their jobs in the way that they were taught. Pleasant dreams. The workers are handicapped by the system, and the system belongs to management.— W. Edwards Deming

Maria reframes the discussion in plain language. “First,” she says, “are things running the way they usually do? If they are, blaming the worker for random ups and downs doesn’t fix anything. Second, if something truly unusual happened—something you don’t normally see—then we treat it as a special cause and deal with it directly.”

They chart downtime and defects. Most of what they see sits inside predictable limits. One incident stands out clearly: a machine was deliberately bypassed after a safety interlock failed.

Jack agrees immediately. “That one’s on the person,” he says.

Maria agrees too. “Yes,” she says. “And because it’s clearly unusual, we can handle it firmly and directly—without pretending it explains everything else that’s been happening.”

Deming was explicit about this balance. “I should estimate that in my experience most troubles and most possibilities for improvement add up to proportions something like this: 94% belong to the system (responsibility of management) 6% special.”

That six percent matters. It includes negligence, misconduct, and genuine inability. But treating ninety-four percent as if it were six is expensive.

I should estimate that in my experience most troubles and most possibilities for improvement add up to proportions something like this: 94% belong to the system (responsibility of management) 6% special.— W. Edwards Deming

As Midwest Components changes its approach, conversations on the floor change as well. Supervisors stop asking who screwed up and start asking what conditions made outcomes likely. Training is stabilized. Scheduling is smoothed. Supplier variation is addressed. The one true special-cause issue is resolved and doesn’t need to be recycled as a warning story.

Performance improves—not because people suddenly became better, but because the system stopped working against them.

Where leaders get stuck

Most of us don’t blame workers because we enjoy it. We do it because it feels decisive. Someone must have caused the problem, and identifying that person creates a sense of action.

But when results are driven by the system, this habit quietly backfires. We demand explanations for normal ups and downs. We reward and punish based on noise. Fear increases. Stories replace learning. Leaders stay busy while the underlying causes remain untouched.

There’s also a subtler trap. When we believe outcomes are mainly about individual effort, we start to see disengagement as a personal flaw instead of a signal. We miss opportunities to redesign work so that success is the natural outcome, not a heroic one.

Deming warned against this explicitly when he urged leaders to eliminate slogans and exhortations. They create adversarial relationships, he argued, because the bulk of the causes of low quality and low productivity lie beyond the power of the workforce.

The result isn’t higher standards. It’s frustration on both sides.

Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work.

Actionable Takeaways

The alternative to worker blame is not indulgence. It’s discipline.

* Stop demanding explanations for routine variation. When things are running the way they usually do, stories won’t help. Improvement comes from changing the system, not interrogating individuals.

* Make the distinction between common and special causes explicit. Leaders and supervisors should know the rules. When evidence shows the system produced the result, leadership owns the fix. When evidence shows a true special cause, address it directly and respectfully.

* Redesign supervision around enablement. The job is not to motivate people to care more. It’s to make it possible for people to succeed through clear methods, adequate training, sensible workload, and timely feedback.

* Treat pride of workmanship as a leadership responsibility. When barriers are removed instead of blame being assigned, problems surface earlier—when they are smaller, safer, and cheaper to fix.

These actions don’t lower standards. They raise them—by aiming effort where it actually matters.

Closing

Deming didn’t ask leaders to deny what they’ve seen. He asked them to look more deeply at it. Yes, some problems are caused by individuals. Far more are created by systems that quietly shape behavior, day after day, often without anyone intending harm.

There is something profoundly hopeful in this. Systems can be redesigned. C…

Most leaders believe pay is the lever that keeps people accountable. Tie raises to individual performance, and people will work harder. Untie them, and standards will slip. That belief feels especially strong in operations where timing matters—where a late start cascades into lost output, overtime, and frustration. But what if the very tools meant to enforce accountability are quietly making the system worse?

W. Edwards Deming spent much of his career challenging a deeply held management assumption: that individual performance can be measured, ranked, and rewarded in a way that reliably improves results. His critique was not philosophical. It was grounded in how real work actually happens.

Deming was blunt about the damage caused by this assumption. He wrote that “evaluation of performance, merit rating, or annual review” is a management disease—one that builds fear and undermines cooperation instead of improving results.

A deadly disease: evaluation of performance, merit rating, or annual review— W. Edwards Deming

In most organizations, especially those that operate in shifts, results are produced by systems—by schedules, handoffs, training, equipment readiness, and staffing decisions. When leaders focus compensation on judging individuals instead of improving systems, fear replaces learning, and supervisors become referees instead of leaders.

This tension is often dismissed as a white‑collar concern. But the opposite is true. The more tightly coupled the work, the less individual performance explains outcomes—and the more management decisions shape results.

That reality plays out clearly at Sunrise Acres, a large egg farm running multiple barns across three shifts.

When measurement isn’t enough

Sunrise Acres depends on precision. Every shift change affects feeding schedules, sanitation routines, and downstream quality. When crews start late, the consequences ripple through the day.

Miguel, the operations manager, is exhausted by the problem. “We track everything,” he says. “Names. Minutes late. Warnings. We even tie raises to attendance—and it still doesn’t stick.”

Late starts keep happening.

Sarah, the farm’s general manager, doesn’t argue with him. “What if the problem isn’t the people?” she asks. “What if it’s the way the day starts?”

Together, they walk the process from parking lot to first task. The issues surface quickly. The time clock is deep inside the barn. Protective equipment is stored in multiple locations. New hires aren’t clear on relief coverage. Buses arrive with built‑in variability. And supervisors are stretched thin at shift change.

No one would blame a single hen for a flock problem. Seeing the system end to end makes it clear that punctuality has been treated like a character trait, even though the system makes being on time unnecessarily hard.

They make practical changes: moving the clock closer to the entrance, pre‑staging PPE kits, adding a short overlap for handoffs, and using visual start‑time cues. A bilingual lead helps direct arrivals. Attendance improves almost immediately.

One employee, Rosa, is still late. Instead of issuing another warning, Miguel follows Sarah’s lead and starts a conversation. Rosa explains that her childcare opens at the same time her shift begins. A small schedule adjustment and cross‑training resolve the issue completely.

What becomes clear is that most lateness was common‑cause—built into the system. A few cases required individual action, but only after the system barriers were removed.

When raises come due, Miguel hesitates. “So… no merit scores?”

Sarah is explicit. Base pay is set by role and market. Raises come through skill blocks—what people are trained and qualified to do. Any shared upside is tied to farm‑level performance. Attendance expectations remain firm, and willful noncompliance is addressed directly. What they abandon is the fiction that a yearly rating caused punctuality.

Deming warned that “evaluation of performance, merit rating, or annual review” builds fear and rivalry while demolishing teamwork. He also cautioned that it is “unfair, as it ascribes to the people in a group differences that may be caused totally by the system that they work in.” At Sunrise Acres, supervisors stop keeping secret tallies and start removing barriers in the work. Training accelerates. Turnover slows. Late starts drop—and so do the hidden costs that came with them.

[Performance-based pay] is unfair, as it ascribes to the people in a group differences that may be caused totally by the system that they work in.— W. Edwards Deming

Where managers go wrong

Most leaders don’t rely on merit pay because they enjoy ranking people. They do it because it feels like control—especially when schedules slip or output falters.

Deming warned that this instinct leads managers to confuse numbers with knowledge. When results vary, rating people feels decisive, even when the variation comes from the system itself.

When attendance problems show up, the instinct is to tighten enforcement, add documentation, or raise the stakes. But in tightly coupled systems, this approach confuses accountability with judgment. It treats variation created by schedules, transportation, training gaps, and process design as individual failure.

We tell ourselves that without performance‑based pay, standards will collapse. In practice, the opposite often happens. Fear drives people to protect themselves rather than surface problems. Supervisors spend their time policing instead of improving the work.

This doesn’t mean ignoring behavior. Deming never argued for permissiveness. He argued against blaming people for problems built into the system. True accountability comes after leaders have done their part: designing work so success is possible, and making expectations clear and achievable.

[Performance-based pay] nourishes short-term performance, annihilates long-term planning, builds fear, demolishes teamwork, nourishes rivalry and politics.— W. Edwards Deming

Actionable Takeaways

Stepping back from merit pay does not mean stepping back from leadership. It means redirecting leadership toward the work itself.

* Separate pay from judgment. Set base pay by role and market. Use clear skill progression for raises—certifications, cross‑training, demonstrated capability. If you share gains, do it at the system level so people improve together.

* Design attendance into the process. Map the start of a shift the same way you would any critical operation. Remove friction, clarify handoffs, and make expectations visible. Measure patterns and causes, not personalities.

* Be clear about accountability. When behavior remains willful after support and system fixes, address it directly and promptly. Don’t outsource leadership to a rating form.

When pay decisions are predictable and fair, they stop dominating attention. That frees leaders to focus on what actually improves results—building capable people and reliable systems.

All anyone asks for is a chance to work with pride.— W. Edwards Deming

Closing

The question was never whether people should be accountable. The question was whether pay and ratings are the right tools to achieve it.

Deming argued that pay systems should be predictable and fair, writing that “the people of a group that form a system will all be subject to the company’s formula for raises in pay.” That idea runs counter to merit pay—but it aligns closely with how real systems actually work.

At Sunrise Acres, removing merit pay didn’t weaken standards. It strengthened them. By focusing on system design instead of individual judgment, leaders created conditions where showing up on time was no longer a battle to be fought, but a normal part of professional work.

When systems are designed well, people don’t need to be threatened into compliance. They can take pride in doing the work right—because the work finally works for them.

Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work.

Public recognition is one of the most familiar tools leaders use to motivate people. It feels generous. It feels human. It feels like an easy way to say, “This matters here.”

But recognition is never just a moment of appreciation. It is a signal that lingers. Over time, it teaches people what the organization truly values, what kind of work is safest to pursue, and what quietly carries risk.

In interdependent work—where outcomes are shaped by systems, not individuals—that lesson compounds. Recognition keeps teaching long after the applause fades.

Recognition is a system choice

Most leaders don’t design awards because they enjoy competition. They do it to build energy, reinforce values, and show that effort is noticed. Public recognition feels like a low-cost, low-risk way to encourage performance.

What often goes unexamined is how recognition behaves inside a system. When awards are scarce and visible, they begin to function like ranking—even when leaders explicitly reject that intent. People adapt quickly. They gravitate toward work that gets attention. They protect credit. They deprioritize work that is essential but less visible, such as mentoring, prevention, and improving methods.

W. Edwards Deming urged leaders to look past intentions and examine effects. His concern was not appreciation itself, but the habit of confusing outcomes with merit in environments where outcomes are shaped largely by the system. When leaders reward results without studying the conditions that produced them, they unintentionally teach people to manage visibility instead of improving the work.

To see how this dynamic unfolds—and how it can be redirected—consider what happened inside one professional services firm.

When recognition becomes ranking

Brightline Advisory is a mid-sized professional services firm whose work depends on collaboration, shared methods, and careful coordination across teams. After a demanding year marked by heavy workload and rising attrition, leadership introduced a monthly public recognition program called Bright Star. Each month, one individual would be publicly celebrated for strong performance.

At first, the program landed exactly as intended. People appreciated the acknowledgment. Leaders felt they were reinforcing the right behaviors. Over time, however, the meaning of the recognition began to change—not because anyone altered the rules, but because the system itself was teaching a lesson. Sarah, who led one of the delivery groups, noticed the shift before it showed up in reports or metrics. She brought her concerns to Tom, a managing partner.

“At first people seemed energized,” she said. “But after a while, something shifted—and not in a good way.”

She wasn’t describing morale problems. She was describing how work was unfolding. Knowledge sharing slowed. Junior consultants hesitated to ask for help. Conversations about who would present results grew tense. Work that attracted attention felt safer than work that prevented future problems.

Tom kept returning to intent. “We weren’t trying to rank anyone,” he said. “We just wanted to acknowledge great work.”

“I know,” Sarah replied. “That’s what makes this tricky. It lifted up a few—and it changed what everyone else feels they have to do to be seen.”

Nothing in Bright Star instructed people to compete. But recognition was scarce and highly visible. In an interdependent system, that combination quietly invites comparison. People adjust their behavior to the signal, not the slogan.

Deming warned leaders about this pattern. “Abolish ranking and the merit system,” he wrote. In its place, he urged leaders to “manage the whole company as a system.” What follows from ranking is not better performance, but predictable distortion.

Abolish ranking and the merit system.Manage the whole company as a system.— W. Edwards Deming

As months passed, leaders began to see what Sarah had been describing. Certain projects drew disproportionate attention. Riskier work was avoided. Helping another team felt like a tradeoff against personal visibility.

The conversation changed when leadership stopped debating whether Bright Star was motivating and asked a different question: What is this recognition teaching people to do? That question slowed things down. Instead of choosing winners more carefully, leaders began studying variation—project mix, timing, staffing, and handoffs. They began to see that Bright Star rewarded outcomes without improving the system that produced those outcomes.

Only then did the solution emerge. The monthly award was retired. In its place, teams began sharing what they were learning: improvements to methods, prevention practices, and collaboration. Recognition shifted away from status and toward understanding how good work was produced.

Over time, the effects became visible. Knowledge moved more freely. Cooperation increased. Results stabilized—not through competition or heroics, but through better system design. As Deming put it, leaders must “remove barriers that rob people … of their right to pride of workmanship.”

Remove barriers that rob people … of their right to pride of workmanship.— W. Edwards Deming

Where managers often get tripped up

When we look at stories like this, it’s tempting to say the original recognition program was “wrong.” That framing isn’t very helpful.

What usually happens is that we underestimate how powerful recognition really is. We treat it as encouragement rather than as system design. We assume people will hear praise as appreciation, not as instruction.

In interdependent work, people are constantly scanning for signals about what is safe, what is valued, and what advances their standing. When recognition is scarce and public, it inevitably creates comparison—even if we never use the language of rank.

We also tend to over-attribute results to individuals. When outcomes look good, we reward the visible contributor without asking how much of that outcome was shaped by project mix, timing, staffing, or client behavior. That makes recognition feel fair in the moment while quietly distorting behavior over time.

None of this comes from bad intent. It comes from managing people instead of managing the system they work in. Deming’s reminder was simple and uncomfortable: most performance belongs to the system. Recognition that ignores that reality will eventually work against us.

Actionable takeaways

So how can leaders design recognition that strengthens the system instead of distorting it?

* Map your recognition ecosystem. Examine all forms of recognition—formal and informal—and ask what behaviors they encourage, and what they crowd out.

* Separate appreciation from ranking. Express gratitude freely, but avoid designs that create winners and losers in interdependent work.

* Recognize methods, not just outcomes. Highlight prevention, mentoring, improved handoffs, and practices others can reuse.

* Treat results as inputs for study. When outcomes are strong, ask “By what method?” and spread that learning without attaching status.

* Design for pride of workmanship. Invest in systems that make good work the norm, not something that requires heroics to achieve.

When recognition works this way, it becomes part of how the organization learns and improves.

Closing

Awards feel generous. Public praise feels motivating. That is exactly why leaders need to treat recognition as a system choice, not a gesture.

In interdependent work, recognition can strengthen cooperation or quietly undermine it. When leaders align recognition with learning and system improvement, appreciation becomes more than applause—it becomes a foundation for lasting performance.

Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work.

Most leaders feel pressure in the same places. Costs creep up. Capacity feels tight. Customers wait longer than they should. Staff are busy, sometimes exhausted, and still the results don’t seem to move. The natural response is familiar. Push productivity. Raise targets. Add oversight. Ask people to move faster. It feels responsible. It looks like leadership.

And yet, very often, it quietly makes things worse.

W. Edwards Deming offered a different way to think about improvement—one that runs counter to that instinct. In Out of the Crisis, he described what he called the chain reaction: a cause‑and‑effect sequence that begins not with cost or productivity, but with quality. Deming was clear that this was not a motivational idea. It was an explanation of how systems actually improve.

If you improve quality, Deming said, “The result is a chain reaction—lower costs, better competitive position, happier people on the job, jobs, and more jobs.” Each outcome depends on the one before it. Miss the starting point, and the rest of the chain never really takes hold.

The result [of improving quality] is a chain reaction—lower costs, better competitive position, happier people on the job, jobs, and more jobs.— W. Edwards Deming

The logic behind the chain

At first glance, Deming’s chain reaction looks almost too simple: improve quality, and good things follow. But Deming was not offering encouragement or aspiration. He was offering a way of thinking that depends on sequence. The chain reaction works only when its links unfold in the right order.

It starts with quality. When quality improves, costs come down—not because someone demanded savings, but because waste leaves the system. Deming described the mechanism plainly: “Improvement of quality transfers waste of man‑hours and of machine‑time into the manufacture of good product and better service.” In practice, this shows up as less rework, fewer mistakes, and fewer delays and snags. Time that was once spent fixing problems is freed to do useful work.

Improvement of quality transfers waste of man‑hours and of machine‑time into the manufacture of good product and better service.— W. Edwards Deming

As that waste leaves, capacity returns. Only then does productivity improve—not because people are working harder, but because the system is able to work as intended. Over time, better quality and lower total cost translate into better value. Trust strengthens. Performance stabilizes. The organization can stay viable—or, in mission‑driven settings, continue to serve. Jobs become easier to protect, and growth becomes possible.

The meaning of quality

In many organizations, the word quality is narrowed to outputs, results, or compliance measures. Deming’s meaning was broader and explicitly managerial. He tied quality to meeting the needs of the customer, present and future, and placed responsibility squarely with leadership. Quality, in Deming’s sense, is not about effort. It is about how the work itself is designed.

Operationally, quality shows up as reliability. The work arrives ready. Prerequisites are clear and present. Information is complete. Handoffs do not require rescue. The process is capable of producing a good result without looping back on itself. When those conditions are not met, the system creates rework—and that rework is where cost and capacity quietly disappear.

Watching the chain reaction at work

Riverview Health System’s specialty clinic had an eight-week wait for new appointments. Pressure was mounting. Access needed to improve, but headcount was frozen. Maria, the clinic operations director, saw the same pattern week after week. The clinic was full. The staff were busy. And the backlog wasn’t moving.

“Everyone is working flat out,” she said during a Monday review. “But the waiting list isn’t changing.”

Instead of asking people to work harder, Maria asked a different question: where is the system creating rework? She and the medical director agreed to look more closely.

“Let’s stop guessing,” he said. “Let’s count how often work comes back.”

For two days, the team tracked repeat work. They categorized callbacks, delays, and corrections tied to referral defects, missing prerequisites, authorization issues, unclear orders, and documentation rework. When they reviewed the results, the answer was unmistakable.

“Nearly a third of our calls aren’t new demand,” Maria said quietly. “They’re cleanup.”

That made the starting point clear. Quality had to be addressed at the entry point. They focused on new rheumatology referrals. The core problem wasn’t clinical judgment. It was incomplete information. Intake staff chased labs. Nurses re-triaged. Visits ran late because prerequisites were missing.

“If we fixed this upstream,” the medical director observed, “the whole day would change.”

The team redesigned the referral process. Required fields were clarified. Prerequisites were explicit. If something was missing, the visit wasn’t scheduled; a clear request went back immediately. Within weeks, the day felt different.

“The phones are quieter,” one scheduler noted. “We’re not constantly fixing things.”

Phone calls dropped. Reschedules declined. Visits started on time more often. Costs fell because rework fell. As correction work faded, capacity returned. With the same staffing level, the clinic completed more work that stayed complete. Access improved. The waiting list began to shrink. Productivity improved—not because people were pushed harder, but because failure demand no longer consumed capacity. Over time, reliability strengthened trust with referring practices and patients. Performance stabilized. Leaders could plan instead of firefighting. Jobs were protected not through cuts, but through predictability.

The improvement didn’t come from working harder or managing tighter. It came from choosing the right starting point—and then letting the rest of the chain do its work. Once quality was addressed upstream, the system began to change on its own. Rework fell, capacity returned, and productivity followed without being forced. What looked at first like a stubborn access problem turned out to be a design problem, and fixing that design made improvement both durable and calm.

Putting the chain reaction to work

Under pressure, it’s tempting to start the chain in the middle. Lower costs become mandates. Productivity becomes a target. But cost and productivity are outcomes of a system. When leaders pressure outcomes without improving the system that produces them, rework grows, delays lengthen, and capacity shrinks. This is why Deming insisted on quality as the starting point. Without it, the later links have nothing solid to stand on.

The chain reaction becomes practical when leaders shift where they put their attention. Rework is a good place to begin. Treated as noise, it’s frustrating. Treated as data, it’s revealing. Rework shows where the system isn’t capable and where quality is breaking down upstream. That perspective reshapes how quality is defined. Instead of abstract goals, quality becomes observable. What does “ready” actually mean at the entry point? What conditions must be present so work flows forward instead of circling back?

With those questions in view, improvement naturally moves upstream. Ambiguity is reduced. Prerequisites stabilize. Handoffs become clearer. Downstream teams no longer have to compensate for what the system failed to provide. Progress then appears in a predictable order. Callbacks decline. Reschedules ease. Overtime falls. These are early signs that cost is coming down because rework is leaving the system. As capacity returns, productivity follows.

Seen this way, the chain reaction isn’t a technique. It’s a discipline of starting points. As Deming warned, “A bad system will beat a good person every time.”

A bad system will beat a good person every time.— W. Edwards Deming

Actionable takeaways

These are not tactics to apply all at once. They are starting points—ways to begin aligning daily management decisions with …

Fear is expensive.

It doesn’t appear on financial statements, but it shows up everywhere else—late reporting, hidden problems, padded numbers, quiet compliance, and people doing just enough to stay out of trouble. W. Edwards Deming captured the effect in a single line: “Fear invites wrong figures.” When fear is present, organizations don’t see reality clearly, because reality feels unsafe to report.

Many leaders treat fear as a cultural or interpersonal issue. Deming did not. In Out of the Crisis, he was explicit: “Drive out fear, so that everyone may work effectively for the company.” He described fear as a management problem—created, reinforced, and sustained by the way the system is designed. Until fear is addressed at the system level, improvement efforts may stall, no matter how capable or well‑intentioned the people involved may be.

Drive out fear, so that everyone may work effectively for the company.— W. Edwards Deming

Fear is rational—and systemic

People don’t hide problems because they lack integrity. They hide problems because the system has taught them what happens when they speak up. Fear is rational. When the cost of surfacing a problem is higher than the cost of hiding it, people adapt. They delay. They soften the message. They adjust the numbers. Over time, the organization becomes exactly as honest as the system allows it to be.

This is why Deming warned that many of the most important figures managers need are unknown or unknowable. When fear governs behavior, the data itself becomes unreliable—not because people are dishonest, but because honesty feels dangerous.

A familiar pattern

Consider an organization running behind schedule. Elena, a frontline operator, notices a subtle change in how a process is behaving. Nothing dramatic. Output is still within spec. But something feels off. Stopping the process might turn out to be unnecessary—and attract criticism. Letting it run might result in scrap or rework later. Either way, the risk feels personal.

“If I stop it and nothing’s wrong, I’ll get blamed,” she thinks. “If I don’t stop it and it fails, I’ll get blamed worse.” So the process keeps running.

Hours later, failure occurs. Scrap spikes. Downtime stretches longer than it would have if the issue had been addressed earlier. Later, James, a senior leader, asks why no one spoke up sooner.

“Why didn’t we hear about this earlier?” he asks. The answer is predictable: people have been burned before.

This isn’t a failure of motivation or training. It’s a predictable outcome of the system: people do what keeps them safe. Deming warned that fear suppresses information long before it shows up as failure, because people learn to survive within the system they are given.

What changes when fear is removed

Now imagine a different response.

James changes the way he responds when problems surface. Instead of asking who made the wrong call, James asks what signals were present and how the system made responding risky.

“Where did the first signal show up,” James asks, “and what did we make risky about acting on it?” They make it explicit, then demonstrate through their actions, that surfacing problems early will not be punished.

The next time a similar signal appears, the process stops sooner. The issue is confirmed. Downtime is brief. Loss is limited. Nothing changed about the equipment. Nothing changed about the people. What changed was the risk calculation in their heads.

When the system punished early signals, those signals disappeared. When the system protected early signals, learning sped up. As Deming cautioned, without trust, people cannot work together to improve the system, no matter how skilled they are.

Fear as a competitive issue

This is where fear stops being a cultural concern and becomes a strategic one. Organizations that surface problems early learn faster than organizations that hide them. Over time, speed of learning—not size, not technology, not even experience—becomes the real competitive advantage.

Teams that operate without fear adapt faster, recover sooner, and avoid repeating the same mistakes. That advantage compounds quietly but relentlessly, because competitors can copy tools and processes, but they struggle to copy systems that consistently tell the truth.

Here’s how you can eliminate fear

Driving out fear does not require grand programs or slogans. It requires consistent management behavior, especially in moments when problems surface.

* Establish a non‑punitive escalation rule.Make it explicit that surfacing a problem early will never be punished. Write it down. Repeat it often. Most importantly, enforce it through your reactions when bad news appears.

* Change the first question leaders ask.Replace “Who did this?” with “What in the system made this likely?” The first sentence out of a leader’s mouth teaches everyone what is safe.

* Use a simple learning review after problems occur.After any defect, delay, or stoppage, ask what signal appeared, what decision was made, and what the system made easy or hard in that moment.

A simple daily learning review captures what abnormality was observed, when the earliest signal appeared, what risk people perceived at the time, and what will be changed so the right action feels safe next time.

The point of driving out fear

Fear doesn’t disappear because leaders say the right words. It disappears when people see—again and again—that telling the truth is safer than hiding it.

In every organization, improvement begins as a small signal: a question, a hesitation, a quiet sense that something isn’t quite right. When fear is present, those signals are swallowed. When fear is removed, they become the starting point for learning.

Driving out fear isn’t about being kind or permissive. It’s about creating the conditions where people can contribute what they actually know, not just what feels safe to say. It’s about shifting energy away from self‑protection and toward shared purpose.

Fear is a management choice, whether intentional or not—and so is its absence. Deming was clear that fear undermines pride of workmanship, because people cannot take pride in work they are afraid to speak honestly about. When fear governs, people brace themselves and problems arrive late. When fear is driven out, people speak sooner, learn faster, and take pride in getting things right.

That is the point of driving out fear. It’s the moment when people stop bracing themselves and start bringing their whole selves to the work—and when improvement stops being forced and starts becoming something people believe in.

All anyone asks for is a chance to work with pride.— W. Edwards Deming

Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work.

Every organization—whether a small consultancy or a global enterprise—is a web of interdependent parts. Yet most are managed as if each department, team, or individual were a separate machine to be tuned in isolation. Targets are set, bonuses awarded, and dashboards celebrated—all without asking how those local victories affect the system as a whole. W. Edwards Deming warned that this “sub-optimization” is one of management’s most costly blind spots: the parts can perform beautifully while the enterprise itself underperforms. To see what this looks like in practice—and how to escape it—consider the story of a professional services firm that learned the hard way that optimizing individual parts can quietly destroy the whole.

When every team wins—and the company loses

At a growing professional services firm—busy, modern, and full of smart people—something didn’t add up. Each department was celebrating its own success. Operations had reduced delivery time by 25 percent, and the sales team had exceeded its revenue targets. On paper, things looked great. Yet, customers were increasingly dissatisfied. Complaints about rushed projects, inconsistent service, and miscommunication were rising. Internally, tension brewed between departments.

The operations manager, Marcus, pointed to his metrics. “We’ve hit every efficiency target,” he said. The client services lead, Lila, countered that customer satisfaction was slipping. The sales director, Tom, defended his team: “Our job is to bring in business. Maybe operations needs to adjust.” Each spoke with conviction, each confident they were doing their job well.

But as Deming explained, the performance of any part or person in an organization can only be understood in terms of its contribution to the system’s overall aim. In other words, when departments pursue their own metrics without understanding how their work affects the rest of the organization, they may be “winning” locally while the company loses as a whole.

Deming warned that “Left to themselves, components become selfish, competitive, independent profit centers, and thus destroy the system.” He defined a system as “a network of interdependent components that work together to accomplish the aim of the system.” Each part of an organization—sales, operations, finance, customer support—relies on the others. Success requires harmony, not competition.

Left to themselves, components become selfish, competitive, independent profit centers, and thus destroy the system.— W. Edwards Deming

Seeing the process to improve it

At the firm, the realization came slowly. The leadership team began to map how work actually flowed from one department to another. Sales commitments became project delivery constraints. Delivery schedules shaped customer satisfaction. Customer feedback influenced sales renewals. For the first time, everyone could see that their work didn’t exist in isolation. Deming once noted, “If people do not see the process, they cannot improve it.”

If people do not see the process, they cannot improve it. — W. Edwards Deming

Once the team visualized their interdependencies, conversations shifted from blame to curiosity. They began asking, “What is the aim of our entire system?” rather than “How can my team hit its number?” Together, they agreed that the true aim was not merely to increase short-term output or revenue, but to deliver reliable, high-quality service that built long-term relationships.

Transforming through cooperation

With this shared aim, they adjusted their incentives and measures. Sales began setting expectations based on delivery capacity, not just closing speed. Operations shifted from rushing projects to focusing on consistency and quality. Client services joined early in the process to anticipate customer needs before issues arose.

Six months later, the firm’s revenue per client had grown by nearly twenty percent, but the deeper transformation was cultural. Complaints dropped sharply. Referrals increased. Employees reported less frustration and more pride in their work. As Marcus put it, “We didn’t work harder—we just stopped working against each other.”

Managing the system, not the people

Deming famously said, “A system must be managed. It will not manage itself.” Systems do not improve through pressure or exhortation, but through understanding and design. When leaders focus only on optimizing subsystems—each department, team, or metric—they unintentionally sub-optimize the whole. True improvement requires managing interdependence, not independence.

The lesson is timeless and universal: when a business, school, or agency learns to see itself as one system with a shared aim, performance improves naturally. The parts no longer compete; they collaborate. And the result is not just better numbers, but greater stability, learning, and joy in work.

Actionable Takeaways

* Draw the system. Create a simple flow diagram showing how work moves across departments. Clarity reveals waste, rework, and misalignment.

* Redefine success. Evaluate each team’s performance by how it contributes to the organization’s overall aim, not by isolated metrics.

* Remove local targets that conflict with the system. If a goal drives one group to optimize at the expense of others, it’s the wrong goal.

* Foster cooperation over competition. Encourage departments to solve problems together rather than negotiate boundaries.

* Lead with purpose. The role of management is to optimize the whole system—helping every component work together for customers, employees, and the organization’s future.

When an organization learns to see itself as one system, improvement becomes continuous and sustainable. That, Deming would remind us, is not just better management—it’s a competitive advantage.

A system must be managed. It will not manage itself. — W. Edwards Deming

Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work.