W. Edwards Deming saw a deeper problem: management can either protect the human desire to learn and contribute, or quietly damage it. Quality depends on judgment, cooperation, and learning. Those cannot be forced into existence.

The harder question behind performance

It is easy to assume that poor performance means people need more pressure. When results disappoint, leaders often reach for sharper targets, clearer rankings, stronger incentives, or more visible accountability. These methods feel practical because they create attention quickly.

But attention is not the same as improvement. People can pay attention to a score while the work gets worse. They can learn how to look good on a dashboard while customers experience delay, confusion, or uneven service.

Deming placed motivation inside the psychology element of his System of Profound Knowledge. His warning was not that pay, goals, or recognition have no effect. It was that leaders must understand what these devices do to people, especially when they replace purpose, learning, and cooperation.

He stated the danger plainly: “Extrinsic motivation in the extreme crushes intrinsic motivation.”

Northstar Clinics shows how easily a reasonable performance idea can become a barrier to better work.

The score was not the same as the work

Northstar Clinics operated nine outpatient clinics. Wait times were uneven. Access was slipping. Turnover was rising. Elena, the operations leader, wanted a plan with force to change behavior.

She came to a leadership meeting with a dashboard proposal. Each clinic would receive a monthly productivity score. The top clinic would be recognized; the bottom clinic would submit a plan.

Elena explained the idea directly.

“We need people to know this matters. If we recognize the top performers, the others will have a reason to catch up.”

Marcus studied the draft dashboard. He understood why Elena wanted accountability, but something about the design bothered him.

“Maybe. But what if the score changes what people pay attention to?”

Elena pushed back. “They should pay attention to access, callbacks, and visit flow. That is the point.”

“Or they may pay attention to looking good on the dashboard,” Marcus said. “A clinic can lift the score and still make the work worse.”

That was the uncomfortable turn. Elena wanted focus. Marcus was asking whether the proposed system would improve the work or merely change behavior around the measurement.

“Then what are you suggesting? We cannot just ask everyone to care more.”

Marcus answered quietly.

“I do not think caring is the problem. I think the system is wearing people down.”

The room went still. The issue was no longer whether the dashboard was clear enough. The issue was whether management understood the conditions under which people were working.

The team began studying the clinics instead of ranking them. One served more complex patients. Another had lost two exam rooms to equipment problems. A third had nurses covering refills, triage, and insurance paperwork. These differences were not excuses. They were part of the system producing the results.

Elena visited one clinic the following week. She watched a medical assistant search for a working blood pressure cuff while a physician waited for misrouted lab results. No one looked indifferent. They looked worn down by repeated obstacles.

Later, Elena asked a nurse what would help.

“If you could change one thing about the system, what would it be?”

Marcus added, “Take your time. This is not a performance review.”

That sentence mattered. People were used to explaining bad numbers, not naming barriers without fear.

Deming connected this directly to performance: “No one can put in his best performance unless he feels secure.”

Security did not mean comfort or low standards. It meant people could tell the truth about obstacles, broken methods, confusing handoffs, and unreliable tools.

The nurse said the team did not need another campaign. They needed clearer refill rules, working equipment, and time to fix handoff problems. In other words, they needed management to improve the conditions of work.

Elena changed the plan. Northstar still measured access, callbacks, and patient experience, but the monthly meeting no longer ranked clinics. Managers studied variation, common barriers, and where the system made good work harder than it needed to be.

Each clinic selected one problem to study: a refill workflow, a daily equipment check, or message routing. The tone changed slowly. People began to speak more plainly about the system. The clinics improved unevenly, but honestly.

Northstar did not need to manufacture motivation with a contest. It needed to stop draining it.

Why we reach for pressure first

We reach for rankings and incentives because they seem concrete. They show seriousness and fit a common assumption: if people cared more, tried harder, or competed intensely, results would improve.

The difficulty is that much performance is shaped by the system. Tools, methods, patient mix, handoffs, training, and leadership habits all affect results. When we rank people without understanding those conditions, we may mistake system effects for personal merit.

Deming warned about the damage: “No one can enjoy his work if he will be ranked with others.”

Ranking changes the psychology of work. Instead of asking, “How do we improve this system?” people ask, “How do I avoid being at the bottom?” Instead of sharing learning, teams may protect their position.

We do this with good intentions. We want accountability and urgency. But when accountability becomes judgment without knowledge, it can weaken the very cooperation the organization needs.

Short-term thinking makes the habit more tempting. A contest or rating system can be launched quickly, while system improvement requires patience. We may mistake faster pressure for better leadership, especially when the effects on trust and learning are harder to see.

These habits do not only affect morale. They affect quality, cost, service, and trust. Preserving learning and pride in work builds a capability that is hard to copy.

Subscribe now

What leaders can do instead

Deming’s point is not that leaders should ignore results. It is that they should understand how results are produced. Motivation improves when management removes barriers and helps people contribute to a clear aim.

1. Begin with respect for purpose. Assume that most people want to do work they can respect. Start by asking what helps or blocks that desire before adding more pressure.

2. Study the system before judging performance. Look for the conditions shaping results: methods, tools, handoffs, workload, training, and variation. A number is a starting point for learning, not a verdict.

3. Remove fear from problem reporting. Make it normal for people to name obstacles without turning every conversation into an evaluation. Leaders need the truth more than they need polished explanations.

4. Replace ranking with shared improvement. Use measures to understand the work, not to set people against one another. Cooperation improves when people can learn across boundaries without losing status.

5. Protect pride in workmanship. Give people a real chance to do good work by clarifying purpose and removing recurring frustrations. Better service and steadier results grow from that capability.

Deming also warned: “The merit system destroys cooperation.”

That is hard because merit systems feel fair on the surface. But if the system teaches people to compete for standing instead of cooperate for improvement, the organization pays a hidden price.

The work improves when people can care

The common mistake is to treat motivation as something management injects from outside. The system perspective is different. People already bring curiosity, judgment, care, and the desire to contribute. Management’s responsibility is to stop crushing those qualities with fear, ranking, and misplaced rewards.

This is not a softer standard. It is a more demanding one. Leaders must understand the work deeply enough to improve the system that shapes performance. When they do, intrinsic motivation has room to survive, and better service can grow from better management.

That is exactly why it is dangerous.

The problem is not the desire for fewer defects. The problem is what happens when we turn that desire into a slogan, a target, or a public demand on people who do not control the system that produces the work. What feels like leadership can quietly become a substitute for leadership.

What the slogan hides from us

W. Edwards Deming’s criticism of zero defects is often misunderstood. He was not arguing for tolerance of poor quality. He was arguing against the managerial habit of demanding an outcome without changing the conditions that make the outcome possible.

That distinction matters in every industry. In manufacturing, it shows up in defect goals that do not address process capability. In software, it shows up in release pressure that ignores unstable requirements and weak handoffs. In safety, it shows up in signs that celebrate days since last injury while the underlying hazards remain in place.

We are drawn to slogans because they simplify reality. They give us something visible to say and something visible to measure. But the ease is deceptive. When the system stays the same, the number becomes the object of management, and the work of improvement gets pushed aside.

That is where the trouble starts.

What happened at Northstar Flow

Northstar Flow sold workflow software to mid-sized manufacturers. The company had hit a rough stretch. Three releases in a row had produced customer-facing bugs that should have been caught earlier. Support tickets were climbing. Sales was uneasy. The executive team wanted to show control, and fast.

At the Monday leadership meeting, the COO wrote four words on the whiteboard: Zero Defects Next Release.

The line had force. It was clean, memorable, and easy to repeat.

Within days, dashboards appeared. Teams were compared by escaped defects. Release reviews got tighter. People spoke more sharply. Product managers defended requirement changes. Engineers argued over classifications. Testers spent more time debating the count than learning from it.

Maya, who led product, felt the pressure immediately.

“We cannot do another release like the last one. Customers are tired of hearing that we are fixing it in the next patch.”

Daniel, the engineering leader, agreed with the urgency but not with the response.

“I agree. But the board on the wall is changing behavior. People are protecting the number.”

That was the turning point. The company had not become more capable. Requirements were still changing late. Test environments were still inconsistent. Handoffs between product, engineering, and support were still rushed. But now fear had entered the system in a more organized way.

At the next review, one team delayed logging a defect until after a release decision because no one wanted another mark against the group. Another team resisted a customer-reported issue by calling it a configuration problem until support escalated it twice. The visible count improved a little. The customer experience did not.

Deming warned directly against this kind of move: “Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity.”

Once Maya and Daniel saw the pattern, the conversation changed. They stopped asking who had let the company down and started asking which conditions made escape likely. Late requirement changes were entering sprint work without a reliable review path. Regression coverage was uneven across older modules. Support was learning about release risk after key decisions had already been made.

They started with three changes. No release would be judged by a single defect number. Every release candidate would get a cross-functional review of requirement changes, test coverage risk, and support exposure. And escaped defects would be reviewed jointly, not to assign blame, but to separate recurring patterns from one-off events.

The next release was not perfect. But it was calmer. Fewer issues escaped. The ones that did appear were easier to trace. Support was prepared. Customers heard a clearer explanation. Trust began to recover because the company looked less frantic and more competent.

Maya said it plainly: “We finally look more serious now that we stopped promising perfection.”

And Daniel answered with the real shift in thinking: “Because now we are improving the work, not just demanding a result.”

Where managers get trapped

Most of us do not fall into the zero-defects trap because we do not care about quality. We fall into it because pressure makes visible promises feel like responsible action.

When numbers get worse, we want to show resolve. We want a message everyone can understand. We want the organization to know we are taking the problem seriously. So we set a target, publish a board, or attach consequences to the result. We tell ourselves that clarity will create performance.

Sometimes it creates compliance theater instead.

This is where Deming’s teaching is still unsettling. He forces us to admit that many of the outcomes we react to are produced by the system more than by individual effort. If we do not understand variation, we will treat every bug, delay, or accident as proof that someone needs more pressure. If we misunderstand incentives, we will reward the appearance of control while the underlying process stays weak.

Deming said it directly: “[Zero defect] exhortations only create adversarial relationships, as the bulk of the causes of low quality and low productivity belong to the system and thus lie beyond the power of the work force.”

That is not soft management. It is demanding management. It asks more from leaders, not less. It asks us to study the work, redesign the conditions, and remove the causes that keep reproducing the same disappointments. When we fail to do that, we do not just weaken internal performance. We weaken trust, reliability, and the kind of reputation that strengthens position over time.

Subscribe now

What leaders can do instead

1. Replace slogans with method. When performance slips, resist the urge to lead with a banner or a demand. Ask first what method will actually change the conditions producing the result.

2. Study the system before judging the people. Look at requirements flow, handoffs, definitions, tools, timing, and feedback loops before concluding that effort or commitment is the problem.

3. Separate recurring patterns from one-off events. A leader’s job is not to react emotionally to every data point. It is to learn whether the problem is built into the process or coming from a distinct special cause.

4. Design reviews that improve learning, not fear. If a metric can be improved by hiding, reclassifying, or delaying bad news, the metric is teaching the wrong lesson. Build review routines that surface patterns early and safely.

5. Define quality in customer terms. Conformance matters, but customers experience quality as reliability, clarity, fit, and trust over time. Improvement becomes more valuable when it strengthens those things, not just the internal count.

6. Treat durable advantage as a consequence, not the aim. Better systems create steadier service, fewer surprises, and stronger confidence. Over time, that becomes hard for competitors to copy, but only because the management capability underneath it is real.

The leadership standard that matters

Deming's point was never that defects do not matter. His point was that demanding perfection is not the same as building capability. Even if the count improves for a while, leadership still has to improve the whole system in ways customers can feel.

He put it with typical bluntness: “No defects, no jobs, can go together. Something other than zero defects is required.”

What is required is better leadership: clearer method, better cooperation, and steady improvement in the work itself. That is how quality becomes real.

If that is true, retention is not a side issue. It becomes a signal about whether management is preserving dignity, pride, and trust inside the work. And that signal matters long before a resignation lands on someone’s desk.

The real question behind who stays

In Deming’s view, people do not arrive at work empty. They come with curiosity, energy, and some desire to do a job well. Management does not create those qualities from nothing. More often, management either protects them or steadily crushes them.

That is why employee retention deserves deeper attention than it usually gets. When people withdraw, go quiet, or leave, we are often seeing the combined effects of system friction and damaged psychology. Conflicting priorities, weak handoffs, judgment-heavy reviews, and fear of speaking plainly can make even capable people feel trapped between doing the job and protecting themselves.

The usual leadership response is to ask how to make people stay. Deming would push us to ask a harder question first: what kind of management makes staying feel worthwhile?

That question becomes easier to see in a small company, where every resignation carries operational consequences. It also becomes easier to avoid, because leaders can tell themselves the issue is personal fit, labor market pressure, or attitude. A story helps make the distinction clearer.

What Lena finally saw in the resignations

Lena ran a growing service company with about thirty employees. Over the last year, three experienced people had left. Two newer hires were already interviewing elsewhere. Customers were beginning to notice uneven service, and Lena had settled on a simple explanation: people were becoming less committed.

So she responded the way many leaders do. She tightened expectations, increased pressure around the numbers, and added a pay increase with a retention bonus. For a week or two, the operation looked sharper.

Then the same problems returned.

Work was rushed. Mistakes repeated. One employee resigned with almost no warning.

Then Marcus, a team lead who rarely complained, asked for a private conversation.

“People aren’t leaving because they don’t care,” he said. “They’re leaving because it’s getting harder to do a good job and harder to say that out loud.”

Lena pushed back. She pointed to the changes she had already made.

“We made changes. We listened. I can’t just lower the standard because people feel pressure.”

Marcus did not argue about standards.

“This isn’t about lowering the standard,” he said. “It’s about what the work feels like now. Priorities change in the middle of the day. One manager says speed matters most. Another says not to miss a single detail. Suggestions disappear. And when the numbers look bad, people start protecting themselves.”

That conversation stayed with her because it explained more than turnover. It explained the silence. Questions were being delayed until problems became urgent. Small defects were being fixed quietly instead of discussed. People were cooperating less because the system had taught them that caution mattered more than candor.

Deming captured the psychological core of the issue in one direct line: “No one can put in his best performance unless he feels secure.”

Lena began to see resignations differently. They were not isolated decisions made by disconnected individuals. They were clues about the conditions people were working in.

At the next staff meeting, she stopped talking about commitment and said something else.

“If the work is getting in your way, I need to know. If our management methods are making it harder to serve customers well, that’s on us to fix.”

Marcus answered quickly. “Fix the handoffs first. That’s where the day starts going wrong.”

She did. Lena removed the quiet individual comparisons that had become rankings. She simplified priorities so people were not being pulled in opposite directions. She asked supervisors to surface recurring barriers and respond to them visibly instead of explaining them away.

The room did not become candid overnight. But people kept naming the same obstacles: missing information at handoff, last-minute changes, and reviews that felt more like judgment than help.

Deming named that danger clearly too: “Evaluation of performance nourishes fear.”

Once Lena could see the pattern, she stopped treating turnover like a mystery. She treated it like evidence. Within a few months, fewer people were talking about leaving. Problems reached supervisors earlier. Rework began to drop. Customers noticed steadier service because the work itself was becoming easier to do well.

And that mattered in the market. Not because Lena launched a retention initiative, but because better management was starting to produce more reliable service than nearby competitors could easily match.

Why we keep misreading turnover

Many of us were taught to read turnover at the level of the individual. We ask who lacked commitment, who wanted more money, or who was not resilient enough for the pace. Sometimes those factors are real. But when the pattern repeats, that lens becomes dangerously incomplete.

We miss the system that is shaping behavior.

We also underestimate how quickly fear changes the quality of information we receive. When people believe that bad news will be used against them, they soften it, delay it, or keep it to themselves. When performance reviews feel like judgment, people manage appearances. When priorities conflict, they choose self-protection over cooperation. From the outside, this can look like disengagement. Inside the system, it is often a rational response.

Deming’s point was that common reward and evaluation practices can drain intrinsic motivation and replace it with self-protection.

That is why superficial retention efforts so often disappoint. Bonuses, slogans, and urgent recruiting can help at the margin, but they do not remove the conditions that are pushing people away. If anything, they can deepen cynicism when employees are asked to care more while the system still makes good work unnecessarily hard.

When we react to resignations without studying the conditions behind them, we do not just weaken internal performance. We weaken learning, continuity, and long-term trust with customers. Over time, that becomes a competitive problem as well as a people problem.

Subscribe now

What thoughtful leaders can do next

Deming’s aim was not merely to reduce fear. It was to create conditions in which people could contribute with interest, confidence, and pride. As he wrote: “[A leader] tries to create for everybody interest and challenge, and joy in work.”

That is a demanding management standard. It means we cannot treat retention as a human resources metric detached from how the work is designed and led.

1. Study the pattern, not the last resignation. Look at turnover alongside rework, absenteeism, customer complaints, overtime, and silence. Those patterns often reveal the recurring barriers that make people feel ineffective or unsafe.

2. Remove fear where information should flow. Examine reviews, rankings, and judgment-heavy routines that teach people to protect themselves. Better information begins when people believe honesty will lead to improvement rather than punishment.

3. Improve the work before asking for more commitment. Clarify priorities, repair handoffs, and respond visibly to recurring obstacles. People trust management more when they can see that leaders are trying to improve the process.

4. Protect dignity as a management responsibility. Pride in workmanship is not sentimental. It grows when people can do work they respect, understand the aim, and contribute to better methods without political risk.

5. Treat retention as an outcome of system capability. When management preserves knowledge, cooperation, and steadier service, the result is not only fewer departures. It can also strengthen reputation and customer trust in ways that become hard to copy over time.

The point is not to create a softer tone around the same broken system. The point is to build a system in which good work, honest reporting, and mutual help are more natural than self-defense.

Better retention starts with better systems

Employee retention looks different when we view it through Deming’s psychology. It is not simply about who stayed and who left. It is about whether leadership created the conditions for security, pride, and truthful work.

When leaders remove fear and improve the system people work in, they do more than reduce turnover. They make better performance possible. And when people begin to feel respected, useful, and safe again, they are far more likely to stay where tomorrow looks more workable than today.

But the deeper question is harder. If profit really matters, why do so many management habits reduce trust, increase waste, and make the organization less capable over time? That is the Deming challenge. Profit is real. It is necessary. But it is not managed well by chasing it directly.

Why chasing the number breaks the system

Deming’s view of profit is more demanding than the usual financial conversation. He did not treat profit as optional, but he did reject the idea that leaders can secure it by applying more pressure to visible figures. He saw profit as the result of better management of the whole system over time.

He put it bluntly: “Emphasis on short-term profit defeats constancy of purpose and long-term growth.”

That sentence is uncomfortable because it names a pattern many organizations normalize. Under pressure, leaders narrow their time horizon. They defer maintenance. They cut learning. They treat quality work as a cost center. They ask each department to maximize its own result and assume the whole organization will somehow benefit.

It usually does not. And that is where the real trouble begins.

To see why, it helps to look at a story.

When every department wins and the organization loses

Riverview Health Network was under familiar pressure. Margins were tight. Labor costs were rising. Denied claims were getting more attention from the board. Senior leaders responded in a way many organizations would recognize: they asked each vice president to improve the financial performance of his or her own area.

Andrea, the chief operating officer, took the assignment seriously. She tightened staffing controls, pushed harder on throughput, and made departmental targets more visible. Radiology watched utilization. Registration watched speed. Billing watched collections. Clinic managers were told to monitor overtime closely.

When Marcus raised concerns early, Andrea answered the way many executives would.

“I understand that. But we cannot ignore the numbers. If every department improves its margin, the organization improves.”

For a short while, the reports looked better. Overtime dipped. A few local targets moved in the right direction. The monthly review felt calmer.

Then the strain showed up elsewhere. Patient complaints increased. Claims were denied because registration was incomplete. Nurses were calling managers about delays in imaging and discharge paperwork. Billing teams were spending more time on rework. Staff tension rose because every department was defending its own scorecard and pushing problems downstream.

Marcus, who led patient access, finally said what the system was already revealing.

“We are improving each piece on paper, but the whole thing feels harder to run.”

Later, standing at a whiteboard with the patient journey mapped from scheduling to billing, he made the problem even plainer.

“We are managing this like separate profit centers.”

That was the turning point. Andrea could see that no single department looked wildly broken on its own. Yet the system as a whole was producing delay, hidden cost, frustration, and lost trust.

At the next leadership meeting, she changed the conversation.

“We keep saying profit is the priority. But if that were really true, we would stop making decisions that increase total waste. We are protecting monthly appearances and creating bigger losses underneath them.”

The room went quiet. Then she took the next step.

“We need to manage patient flow, information quality, and cooperation across the system. We cannot ask each area to win separately and expect the whole network to win.”

Profit still mattered. But now she could see that the organization had been protecting appearances while creating bigger losses underneath them.

So Riverview stopped treating departmental targets as the main story. Leaders studied handoffs, duplicate work, and points where one team’s local savings created losses somewhere else. They reduced repeated data entry. They gave front-line teams time to improve coordination. They stopped rewarding savings that only looked good because another department absorbed the pain later.

Not every local measure improved immediately. Some looked worse before the whole system stabilized. But within a few months, denied claims fell, patient complaints eased, and financial performance became steadier because the organization was wasting less effort.

That is not soft thinking. It is better management.

Why we keep falling into this pattern

Most of us have worked inside systems that teach us to manage from the numbers backward. If the margin is down, squeeze harder. If costs rise, freeze spending. If one area looks weak, push that area to perform. We do not usually mean to damage the organization. We are trying to be responsible.

That is why this pattern is so persistent. It feels practical. It feels serious. It feels financially mature.

But when we react that way, we often confuse local measures with system performance. We treat symptoms as causes. We misread variation. We reward visible action even when it increases hidden waste. And because each team is pressed to defend its own result, internal competition begins to replace cooperation.

Deming saw the danger clearly: “A system must be managed. It will not manage itself. Left to themselves, components become selfish, competitive, independent profit centers, and thus destroy the system.”

That does not just weaken internal performance. Over time, it weakens the organization’s position in the market as well. Customers experience the friction. Employees feel the strain. Rework consumes capacity. Trust erodes.

Meanwhile, an organization that manages flow, reliability, and cooperation is building something much harder to copy.

Subscribe now

Four ways to care about profit more seriously

1. Define the aim before chasing the numbers. Financial results matter, but they cannot be the only language of leadership. Clarify what the organization exists to do well for customers, patients, employees, and the future, then manage profit as a result of fulfilling that aim better.

2. Read the system, not just the scorecard. When one number moves, resist the urge to react immediately. Ask what in the system is creating the result. Look at handoffs, rework, delays, and recurring failure points before you tighten pressure on any one group.

3. Stop rewarding local wins that create total loss. A department can improve its own figures while making the whole organization slower, more expensive, and less trusted. Financial discipline becomes more real, not less, when leaders refuse savings that only shift cost somewhere else.

4. Invest in capability while pressure is high. Training, redesign, better methods, and stronger cross-functional cooperation are often the first things leaders cut when margins tighten. Deming’s view is the reverse: those are the conditions from which healthier profit grows.

Deming wrote: “Profit comes from repeat customers—those that boast about the product or service.” Trust, reliability, and coordinated service do more than make an organization admirable. Over time, they strengthen its position in ways competitors struggle to match.

What profit looks like in a better system

The management mistake is not caring too much about profit. The mistake is caring about it in a shallow way, as if harder pressure on visible numbers could substitute for improvement of the system that produces them.

The better alternative is more demanding and more hopeful. Build a system people can trust. Reduce the waste that leaders usually cannot see at first. Help departments work together instead of defending their own scorecards. Improve the conditions under which good work gets done.

Then the numbers begin to mean something better.

When leaders do that, profit stops being a slogan and starts becoming evidence that the organization is becoming more capable. That is the deeper Deming idea. Healthy profit is not extracted from the system. It grows from it.

Control charts matter because they help us separate ordinary variation from a real signal. That sounds technical. It is actually a practical discipline for calmer judgment, better decisions, and less wasteful management.

Why this changes the work of leadership

Control charts are often treated as a specialist’s tool, useful for analysts or quality teams but distant from executive work. W. Edwards Deming saw them differently. He treated them as a way for management to distinguish what belongs to the system from what points to something unusual.

That distinction changes the kind of leadership action that makes sense. If the chart shows a special cause, we investigate what changed. If the chart shows a stable but disappointing system, we stop chasing episodes and improve the design of the work itself.

Deming captured the idea in one memorable line: “The control chart is the process talking to us.”

That is why the concept matters beyond reporting. A chart is not there to decorate a dashboard or make review meetings look disciplined. It is there to help us hear the system before we explain it, correct people for it, or reorganize around the latest fluctuation. A hospital story makes that distinction easier to see.

What St. Anne’s learned in one meeting

At St. Anne’s Hospital, emergency department boarding times had become a recurring source of executive concern. Week by week, the numbers moved up and down. Patients waited too long for beds upstairs, complaints kept coming, and senior leaders felt pressure to show that they were taking charge.

Elena, the chief operating officer, looked at the latest report and did what many capable leaders do under strain. She wanted urgency, accountability, and visible follow-through.

“I want each unit leader in here this afternoon. If a floor is holding patients too long, I want to know why. And I want targets by Friday.”

Marcus, the vice president of operations, had seen this pattern before. A bad week created urgency. A better week brought relief. Neither reaction was producing understanding.

Instead of bringing Elena another dashboard, he brought her a control chart. He had plotted six months of emergency department boarding times and discharge completion before noon. Elena studied the page for a moment and asked the obvious question.

“So what am I looking at?”

Marcus answered without technical jargon.

“Not just a trend line. This chart tells us whether we’re looking at the normal voice of the system or a signal that something unusual happened.”

That was the turning point. Most of the points were inside the control limits, with no unusual pattern. The process was stable, even though the performance was still not good enough. But two points clearly broke the pattern. Those were signals.

Elena leaned in. The weekly swings that had felt dramatic now looked different. Not like a fresh management failure every week, but like one repeating system interrupted twice.

“What caused the two signals?”

Marcus pointed to specific events. One week reflected a plumbing failure that reduced bed availability. The other reflected a cyberattack drill that slowed admissions and discharge orders. Those were special causes. They deserved investigation. But the larger boarding problem was built into the way the hospital was operating every day.

That is the managerial value of the chart. It did not excuse the delays. It clarified the level of action required.

Stable did not mean acceptable. It meant predictable under current conditions. Elena was no longer looking at a mystery that changed every week. She was looking at a system that was reliably producing an unsatisfactory result, with two real interruptions layered on top.

“So the chart is telling us two things at once,” she said. “Chase the signals. Improve the system.”

Exactly.

That afternoon’s meeting changed shape. Elena canceled the ranking discussion. Instead, she asked for a review of the two special-cause events and a separate cross-functional look at bed management, discharge timing, transport delays, and nursing handoffs. Over time, genuine disruptions were investigated faster, while chronic system problems became easier to name and improve.

That is how the problem began to resolve. The hospital stopped treating every fluctuation as a fresh crisis and started managing patient flow as a system.

Why we keep getting this wrong

Most of us do not misuse performance data because we are careless. We do it because pressure changes what feels responsible. When a number worsens, we want an explanation immediately. We want to know who owns the problem, what action will be taken, and how soon the result will move back in the right direction.

That instinct feels practical, but it often drives poor management. Much of the time, the result in front of us comes from the system’s ordinary behavior. Yet we treat a routine rise or drop as proof that something specific went wrong. Then, on other occasions, we miss a genuine signal because we have trained ourselves to regard every fluctuation as noise.

Deming was explicit about the stable case: “When a control chart indicates no special cause present, the process is said to be in statistical control, or stable. The average and limits of variation are predictable with a high degree of belief, over the immediate future. Quality and quantity are predictable. Costs are predictable.”

That is the situation leaders face more often than they realize: a system performing exactly as it is currently designed to perform, even when the result is disappointing.

But Deming was equally clear about the less common case: “A point outside the control limits is a signal (an operational definition for action) of a special cause, which indicates the need for action—try to identify the special cause, and if it can recur, eliminate it.”

Taken together, those two statements define the management problem. We get into trouble when we treat ordinary variation like a special event, or when we treat a real signal as just another routine fluctuation.

When we fail to see that, we tamper. We reshuffle priorities, pressure teams, explain every point, and make promises the system cannot yet keep. The cost is not just internal confusion. Over time, it also weakens service, trust, and the kind of dependable performance that becomes hard for competitors to copy.

Subscribe now

What better leadership looks like

Before any leader turns a chart into a verdict on people or a call for hurried intervention, the first job is to understand what kind of variation the system is showing.

1. Ask what kind of variation you are seeing. Before reacting, decide whether the result points to a special cause or to the normal behavior of the current system.

2. Separate investigation from improvement. A signal calls for inquiry into what changed. A stable but unsatisfactory pattern calls for redesign of the work, not more pressure on individuals.

3. Stop rewarding explanations without evidence. When we insist on a story for every movement in the numbers, we train managers to narrate noise instead of learning from the process.

4. Treat predictability as a leadership asset. A stable process, even a weak one, gives us a clearer starting point for improvement because it tells us what the system is consistently capable of producing.

5. Build capability that lasts. Leaders who improve systems instead of chasing fluctuations create better service, stronger trust, and more resilient performance over time.

Listening before reacting

The common misconception is easy to understand: if a number worsens, leadership should respond immediately. Deming’s view is more demanding. First understand the variation. Then choose the action that fits.

That is what control charts make possible. They help us know when to investigate, when to improve the system, and when to stop reacting to noise. In that sense, they are not merely a technical tool. They are a practical way to lead with more clarity, offer better service, and build a more dependable organization.

Try it!

In-browser interactive control chart demo

That is why W. Edwards Deming’s Plan-Do-Study-Act matters. It gives leaders a way to slow down certainty without slowing down improvement. In the long run, it produces better service, lower waste, and a steadier reputation.

Why leaders need more than a pilot

Plan-Do-Study-Act (PDSA) is often described as an improvement cycle. That is true, but it can sound smaller than Deming intended. PDSA is a way to connect theory, prediction, action, and learning.

Plan means more than choosing an idea. It means stating what you think is happening, what change you want to test, and what you predict will follow. Do means carrying out that test, usually on a limited scale. Study means comparing the result with the prediction and taking surprises seriously. Act means deciding whether to adopt the change, abandon it, or run another cycle with a better theory.

Deming put the underlying point simply: “Management in any form is prediction.”

That is what many change efforts skip. We move from concern to action without ever being clear about the theory behind the action. Then we mistake activity for learning, or a short-term result for proof.

A story from commercial property management makes the problem easy to see.

What Harbor Point learned by slowing down

At Harbor Point Property Group, the executive team was under pressure. Tenants in three downtown office buildings were complaining about slow maintenance work, repeat visits, and weak communication from the service desk. Renewal season was approaching, and nobody wanted owners asking why routine service felt unreliable.

Claire, the head of operations, opened a Monday meeting with a familiar managerial move. She wanted speed, clarity, and a visible response.

“We need faster resolution times. I want every building manager under four hours for routine maintenance requests by next month.”

It sounded decisive. Complaints were rising. The pressure to look responsive was real.

But Jordan, the regional operations director, had spent the previous week reading work-order notes from the buildings. He saw something Claire’s demand did not explain. Some tickets stayed open too long. Others were closed quickly, then reopened. Vendor dispatches were inconsistent. Tenant descriptions were often incomplete. The pattern looked messy, not simple.

When Claire pressed him, Jordan answered with the line that changed the meeting.

“I think we know the symptom. I’m not sure we know the problem yet.”

That was the turning point. Instead of accepting a broad portfolio-wide push for faster close times, Jordan proposed a PDSA cycle. One building. One category of request. Two weeks. Plumbing calls in Franklin Tower only.

“Two weeks feels slow,” Claire said.

“Only if we confuse motion with learning,” Jordan replied.

This was the Plan stage, and he made it concrete. The service desk would ask three new intake questions before dispatching a plumber. Building staff would classify each request by severity. Vendors would receive tighter work orders with tenant access details and photos when available. Jordan’s prediction was clear: first-visit completion would improve, repeat visits would fall, and tenant updates would improve even if average close time did not improve right away.

That kind of planning is not paperwork.

It is disciplined thinking.

As Deming wrote: “Step 1 [Plan] is the foundation of the whole cycle.”

The Do stage followed. For two weeks, Franklin Tower used the revised intake method only for plumbing calls. The service desk logged the new questions. Building staff tagged urgency consistently. Jordan reviewed requests daily to make sure the test was being carried out as planned.

Then came Study. The headline result was mixed. Average close time improved only slightly. If Harbor Point had judged the test by a single visible metric, the effort might have been dismissed as disappointing.

But the rest of the evidence told a more useful story. First-visit completion improved sharply. Repeat visits fell. Complaints about poor communication dropped. And one surprise stood out: the biggest delays were not coming from the plumbers. They were coming from incomplete tenant access information and late approvals for after-hours entry.

Claire saw it immediately. The dispatch script had helped, but not in the way they first expected.

“Right,” Jordan said. “We learned more than whether the average moved. We learned where the friction actually is.”

That answer captured the real value of the cycle.

That led to Act. Harbor Point kept the stronger intake questions, added a clearer path for access approvals, and ran another cycle in a second building with a different tenant mix. The second round confirmed some of the original theory and corrected the rest. The intake method held up. The approval issue mattered even more than they first thought. One vendor adapted quickly; another needed coaching.

In time, Harbor Point did standardize parts of the process. But they did not do what the first meeting had nearly produced. They did not issue a broad demand to close tickets faster and hope for the best. They acted on what the cycles taught them. Tenant complaints fell. Repeat work declined. Service became more reliable.

That is what PDSA looks like in practice.

Not delay. Learning strong enough to justify action.

Where we usually go wrong

Most of us do not resist PDSA because we dislike learning. We resist it because pressure makes immediacy feel responsible. When complaints rise, costs increase, or customers get restless, we want to show movement.

That impulse is understandable. It is also risky.

We often confuse a visible response with a thoughtful one. We roll out a policy, tighten a target, or announce a new standard before we have stated the theory behind it. Then, when numbers move, we read the movement as proof. If the result looks better, we congratulate ourselves too early. If it looks worse, we abandon the effort too quickly.

In both cases, we may learn very little.

Another problem is that we study outcomes too narrowly. We look for one summary number to tell the whole story. But systems rarely teach in a single measure. A useful test may reveal that the real issue lies in a handoff, an approval path, a vendor interaction, or a classification rule.

This weakens internal performance. Organizations that learn poorly create rework, inconsistency, and distrust. Organizations that learn well build steadier service and stronger trust.

Subscribe now

What leaders can do instead

1. Make prediction explicit. In every serious improvement effort, ask what theory is being tested and what result is being predicted. If we cannot answer those two questions, we are not ready to learn from the effort.

2. Start smaller than your urgency prefers. A limited test is not a retreat from action. It improves the quality of action by creating learning with less cost and disruption.

3. Study more than the headline result. A test may miss its most visible target and still reveal something crucial about approvals, timing, handoffs, demand, or coordination. The lesson may sit beside the metric we first cared about.

4. Treat surprises as valuable evidence. When results differ from the prediction, resist the urge to defend the original idea. The gap between expectation and reality is often where the system becomes visible.

5. Use Act as a leadership decision, not a ritual ending. Adopt what clearly helped. Abandon what did not. Revise the theory where the test exposed weak assumptions, then run another cycle. That is how management capability grows.

The discipline behind better improvement

The misconception is easy to understand: if a problem is urgent, the answer must be faster action. Deming’s point is different. Better results come from better learning, and better learning comes from method.

PDSA gives leaders that method. It asks us to think before acting, predict before judging, study before declaring success, and act only after the system has taught us something worth trusting.

That is not slower management. It is wiser management. Over time, it leads to what every organization says it wants: a better theory, a better system, and a better future built one thoughtful cycle at a time.

But that habit can quietly raise cost, normalize rework, and keep management from seeing the deeper problem. The real issue is not what we catch at the end. It is what our system keeps producing in the first place.

The management trap

One of the easiest mistakes in management is to confuse detection with improvement. When something goes wrong, we naturally look for a way to catch it sooner, sort it faster, or keep it from reaching the customer. That instinct is understandable. It is also incomplete.

A company can become very good at finding defects and still remain trapped in a weak process that keeps making them. W. Edwards Deming said it plainly: “[Using] inspection to improve quality is too late, ineffective, costly.”

The force of that statement is easy to miss. He was not arguing against all inspection. He was arguing against the belief that inspection is where quality is achieved.

Quality is shaped upstream, in design, methods, training, maintenance, scheduling, and in the way management coordinates the whole system.

To see how easily leaders drift into the opposite habit, consider a small manufacturer that had become highly disciplined at catching defects and surprisingly tolerant of producing them.

A small manufacturer, a familiar pattern

Hartwell Fixtures made custom metal display racks for local retailers. It was a solid Main Street manufacturer with a good reputation and steady orders. Elena, the owner, took pride in the fact that every rack was inspected before shipment.

From a distance, that looked like discipline.

On the floor, it looked different.

Welds were sometimes rough. Powder coating occasionally bubbled. Mounting holes did not always line up. None of those issues alone threatened the business. But together, they created a constant drag on the work. Final inspection kept finding defects, and rework kept absorbing time, attention, and overtime.

When a shipment was late for the third time in a month, Elena walked into inspection and saw what had gradually become normal: carts full of rework, operators waiting for decisions, and inspectors arguing over borderline pieces.

“What’s the fastest way to get this back under control?” she asked.

Marcus, her operations manager, answered with the logic the company had been living inside for months.

“We are catching most of the bad units,” he said. “If we add one more inspector on second shift, we can clear the backlog.”

That answer was practical. It was also revealing.

More inspection had already been the answer for months. Yet the backlog remained. Scrap was up. Overtime was up. Customers were becoming less patient. Hartwell was not dealing with a few isolated mistakes. It was operating inside a predictable system.

Later that day, Elena and Marcus looked at the recurring defects together. One week the problem centered on drilling. Another week it was coating. Another week it was warped tubing from a supplier. The pattern moved around, but the burden stayed in the same place: at the end, where the company tried to sort, repair, and rescue what the system had already produced.

Deming captured that logic memorably: “Our system of make-and-inspect, if applied to making toast, would be expressed: ‘You burn, I’ll scrape.’”

That was Hartwell’s system in miniature. Make the rack. Find the defect. Grind it. Redrill it. Recoat it. Expedite it. Apologize for it. At some point, the company had confused recovery with quality.

That realization changed the conversation.

“If inspection is our main defense,” Elena said, “then we are planning to make defects.”

“Then where do we start,” Marcus asked, “if not at the end?”

Instead of asking how to strengthen the inspection wall, Elena and Marcus started tracing the defects upstream. They found fixture wear at the drilling station. They reviewed variation in incoming tubing from one supplier. They discovered that a setup shortcut had become normal on busy days. They also saw coating problems rise when rushed scheduling changes caused parts to sit too long between steps.

Inspection did not disappear. But it changed purpose. It became feedback about the process, not the company’s main theory of quality.

Marcus began tracking defect patterns to learn where the system was unstable. Supervisors stopped treating rework totals as proof that quality control was working. Elena stopped celebrating heroic saves that depended on overtime and last-minute sorting.

The result was not perfection overnight. Some defects still appeared. But rework began to shrink. Lead times became more predictable.

Inspectors spent less time debating borderline pieces. Operators had clearer standards and better equipment. Supplier conversations improved. The same people who had been blamed for defects started taking pride in racks that moved through without repair.

Hartwell did not improve because it got better at catching defects. It improved because management stopped pretending that catching defects was the same thing as creating quality.

Why we fall into this

This pattern is common because it flatters our instincts.

When a defect shows up, we want an immediate answer. We want action we can see. An extra inspection point, another signoff, a tighter approval step, or a fresh reminder to be careful all feel like responsible leadership.

They create motion. They create reassurance. They also let us avoid the harder work of asking what in the system keeps generating the same trouble.

We struggle here because symptoms are visible and systems are not. Rework has a location. Scrap has a number. Inspection has a department.

But the causes are often spread across design, training, maintenance, scheduling, supplier relationships, and unclear methods. No single problem screams for ownership, so we manage what we can see.

We also struggle because detection feels safer than redesign. Catching a defect at the end seems concrete. Improving the process that made it requires thought, patience, and cross-functional cooperation. It asks more of management.

That is why Deming’s reminder matters so much: “The quality of the product is the responsibility of management, working with the customer.”

If we hand that responsibility downward to operators or inspectors alone, we divide accountability in exactly the place it must remain integrated.

The difficulty is not that leaders do not care. It is that we can easily mistake visible control for actual improvement.

Subscribe now

What leaders can do instead

1. Redefine what inspection is for. Inspection can provide useful feedback, but it should not be your main strategy for achieving quality. Treat it as a way to learn about the process, not as proof that the process itself is sound.

2. Follow defects upstream. When the same kinds of problems keep appearing, resist the urge to respond only at the point of discovery. Ask what in design, methods, materials, training, maintenance, or scheduling is making those outcomes likely.

3. Stop rewarding recovery more than prevention. Heroic saves feel admirable, but they can hide an unhealthy system. Leaders should be careful not to praise overtime, sorting, and rework more than the quieter work of building stable flow and capable processes.

4. Keep accountability where it belongs. Operators and inspectors can contribute insight, but they do not control the whole system. Management does. That means leaders have to coordinate across functions instead of treating quality as a department or a final checkpoint.

5. Remember the business consequence. A system that produces dependable quality does more than lower internal friction. It builds trust, strengthens responsiveness, and becomes a competitive advantage over time because customers learn who they can rely on.

A better question

The hopeful part of this idea is that it gives leaders a better question to ask. Not, “How do we catch more defects?” but, “What kind of system are we asking people to work in?”

That question leads away from blame and toward learning. It leads away from scraping burned toast and toward making good toast in the first place.

And when leaders make that shift, something important starts to come back: calmer operations, better work, pride in workmanship, and trust.

That is where real quality begins.

But this familiar management reflex can quietly prevent improvement. When leaders rely on “common sense” explanations, they often focus on the individual closest to the problem instead of the system that produced it.

W. Edwards Deming warned that this habit does more than miss the cause—it can keep organizations trapped in the very patterns they are trying to fix.

Why “common sense” fails in management

Most managers have experienced the moment when something goes wrong. A customer receives the wrong order, an appointment is missed, or a deadline slips by.

The explanation appears obvious: someone made a mistake. Our instinct is to correct the person involved—remind them to be careful, encourage better judgment, or send a note to the team about paying closer attention.

These responses feel practical because work is done by people. But Deming argued that most recurring problems do not originate with individual effort or attention.

They are produced by the way work is designed—the methods, priorities, handoffs, and pressures that shape everyday decisions. When leaders overlook that reality, the same cycle repeats: correct the person, see temporary improvement, and then watch the problem return.

A small service company illustrates how easily this pattern develops—and what changes when a leader begins looking at the system instead.

A scheduling problem that kept returning

Maria owns a home services company that schedules technicians for repairs and installations across her city.

Over several months, customer complaints began to increase. Appointments were occasionally missed, technicians sometimes arrived without the right parts, and a few customers reported waiting all day for a visit that never appeared on the schedule.

One afternoon a customer called after waiting five hours for a technician who never arrived. Maria reviewed the call recording and quickly discovered the problem: the job had been placed into the wrong time slot.

It looked like a simple scheduling error.

Later that day she spoke with her operations supervisor, David.

“This one should have been obvious,” Maria said. “People just need to slow down and use some common sense when they’re entering these jobs.”

David agreed the mistake appeared straightforward, and the team reminded dispatchers to double-check their entries. For a short time the complaints seemed to ease.

But two weeks later another scheduling problem surfaced. Then another.

While reviewing scheduling logs, David noticed something unusual. The same type of error appeared across different dispatchers and across different shifts. It did not look like one employee being careless.

The team began examining the scheduling process itself. Service requests arrived through phone calls, website forms, and callbacks from technicians in the field.

The information customers provided varied widely, and dispatchers often had to guess which technician should handle a job. At the same time they were expected to answer calls quickly while entering appointments into the system.

During busy periods dispatchers were juggling two demands at once: respond to customers immediately and figure out incomplete job details. The errors appeared most often when call volume spiked and dispatchers rushed to keep up.

Deming described this common management reaction in The New Economics: “Common sense [mistakenly] tells us to speak to the operator about it when a customer reports something wrong with a product or with a service. ‘We have spoken to the operator about it; it won’t happen again.’”

Maria realized her earlier response had followed exactly that pattern. She corrected the person closest to the problem while leaving the process unchanged.

The team redesigned the scheduling system. They standardized intake questions so dispatchers received consistent information, clarified which technician handled each type of job, and adjusted call targets so dispatchers were not forced to rush scheduling decisions.

Within weeks the number of scheduling problems began to fall—not because employees suddenly became more attentive, but because the system guiding their work had improved.

As Deming wrote: “Action taken today may only produce more mistakes tomorrow. It may be important to work on the process that produced the fault, not on him that delivered it.”

Why leaders blame people first

Most of us do not intend to blame people unfairly. When something goes wrong, we simply want the problem fixed quickly.

But this instinct often leads us toward the most visible explanation instead of the most accurate one. When a failure appears, the person closest to the event becomes the natural focus of attention.

We see the dispatcher entering the wrong time slot, the technician forgetting a part, or the salesperson skipping a step. Because the action is visible, it feels like the cause.

What we often overlook is the system surrounding that moment—the incomplete information, conflicting priorities, or time pressure that shaped the decision.

Deming repeatedly warned leaders about relying on intuition alone. As he wrote in Out of the Crisis: “Best efforts are essential. Unfortunately, best efforts, people charging this way and that way without guidance of principles, can do a lot of damage.”

Without a method for studying the system, we naturally react to effort instead of design. We ask people to try harder, be more careful, or use better judgment.

Sometimes that produces a short burst of improvement. But if the system creating the conditions remains unchanged, the same patterns quietly return.

Subscribe now

What leaders can do instead

1. Study the system before reacting. When a problem occurs, pause before correcting the individual involved. Examine the conditions that made the outcome possible and look for gaps in the process.

2. Look for patterns instead of isolated mistakes. A single incident rarely explains much. Recurring problems across time, shifts, or teams often reveal systemic causes that individual events cannot explain.

3. Reduce the need for judgment calls. Many service errors occur when employees must interpret incomplete information or conflicting priorities. Clear methods and operational definitions reduce variation.

4. Align incentives with thoughtful work. When speed targets or short-term metrics conflict with careful decisions, people naturally respond to the pressure they feel most strongly.

5. Improve the design of work continuously. Sustainable improvement comes from refining the system itself—clarifying processes, simplifying decisions, and removing barriers that prevent people from doing good work.

The system behind the mistake

Organizations depend on the judgment and effort of the people doing the work. But judgment works best when the system around it provides clarity, stability, and guidance.

When leaders move beyond “common sense” explanations and begin studying the systems that shape everyday decisions, improvement becomes far more predictable.

Instead of repeatedly correcting individuals, leaders begin redesigning the conditions that produce better outcomes in the first place.

That shift—from reacting to problems to improving systems—lies at the heart of Deming’s management philosophy.

But what if the very practice meant to improve performance quietly prevents real improvement from happening?

W. Edwards Deming believed annual performance reviews were not merely ineffective. He argued they were one of the most damaging management practices in modern organizations because they direct leadership attention toward judging individuals instead of improving the system that produces results.

To understand why, we have to rethink what actually creates performance in the first place.

Why Deming challenged performance appraisals

Leaders want to understand how well their organizations are performing. That instinct is healthy; good leadership requires visibility into results and a clear understanding of where improvement is needed.

Annual performance reviews promise a structured way to do this. They compress a year of work into scores, ratings, and rankings that guide compensation, promotion, and recognition.

But Deming argued that this approach misunderstands how organizations actually produce results. He wrote: “Basically, what is wrong is that the performance appraisal or merit rating focuses on the end product, at the end of the stream, not on leadership to help people.”

In other words, reviews judge outcomes after the work is finished rather than improving the conditions that produce those outcomes in the first place. This difference—between judging results and improving the system that creates them—sits at the heart of Deming’s philosophy of management.

To see how this dynamic unfolds in practice, consider the experience of a school district wrestling with teacher evaluations.

A school district confronts the problem

In the Brookfield School District, evaluation season arrived every spring with predictable tension.

Teachers prepared documentation of their work while principals conducted classroom observations. District administrators compared performance scores across schools, and those numbers shaped pay increases, promotions, and professional reputations.

Marcus Lee, principal of Brookfield Middle School, had participated in the process for years, and each cycle followed the same pattern. Teachers worried about their scores, principals debated ratings, and district leaders reviewed charts comparing one school to another.

Yet the classrooms themselves seemed to change very little.

During a district leadership meeting, Marcus raised the concern with Superintendent Elena Ramirez.

“We keep having the same conversations,” he explained. “We review the ratings, we talk about who did well and who didn’t. But the classrooms themselves aren’t improving much.”

Ramirez understood the frustration, but she also saw the system as necessary.

“The reviews help us identify our strongest teachers,” she said. “Without them, how do we know who is performing well?”

Marcus paused before answering.

“That’s the problem,” he replied. “We think the scores explain performance. But most of the time they reflect the conditions teachers are working in.”

He pointed to several examples. Some teachers had consistent collaboration time with colleagues, while others rarely had time to work together. Some classrooms included far more complex student needs, and others had significantly more curriculum support.

The more Marcus studied the situation, the more he saw a pattern emerging.

As evaluation season approached, teachers became cautious. Collaboration slowed, and fewer people experimented with new lesson ideas because trying something new carried personal risk when results were judged individually.

The system was doing exactly what it was designed to do: judge individuals.

But something else was happening as well. Teachers began protecting their own standing rather than sharing openly, and leaders spent hours debating scores instead of studying the conditions shaping learning—curriculum support, scheduling, classroom composition, and collaboration time.

Slowly, the conversation shifted away from improving teaching and toward explaining ratings.

Deming warned about this dynamic decades ago: “Merit rating rewards people that do well in the system. It does not reward attempts to improve the system.”

That comment stayed with Ramirez after the meeting. If the ratings were not revealing true performance, what should leadership be studying instead?

The answer emerged as district leaders began examining the system around teachers rather than the teachers themselves. They studied scheduling practices, collaboration time, curriculum support, and class composition. As these conditions became visible, many apparent differences in “performance” began to make sense.

The district gradually shifted its approach. Instead of relying on a single high‑stakes annual score, principals began holding ongoing coaching conversations with teachers, and teams studied classroom practices together while sharing what they were learning.

Over time the tone inside the schools began to change. Less energy went into defending ratings, and more attention went toward improving how teaching actually happened.

Why leaders keep returning to ratings

Most leaders adopt evaluation systems for understandable reasons. We want fairness, accountability, and a clear way to recognize strong contribution. Annual reviews appear to offer all three.

But Deming believed the deeper issue lies in how we interpret performance itself.

We often assume differences in results are primarily caused by individual effort or ability. When outcomes vary, we instinctively look for the person responsible, and the evaluation system becomes the mechanism for judging those differences.

In reality, most variation in performance within organizations is produced by the system people work within—its processes, resources, training, incentives, and leadership practices. When leadership focuses primarily on judging individuals, these systemic influences remain largely invisible.

The result is a familiar management cycle. Leaders react to outcomes rather than studying causes, and teams debate individual ratings instead of examining the conditions producing those results.

Over time, the evaluation process begins shaping behavior. People manage appearances, protect their own standing, and hesitate to take risks that might affect their ratings.

From a systems perspective, these responses are entirely predictable because the structure of the evaluation system quietly teaches people how to behave.

Subscribe now

What systems-oriented leadership looks like

If judging individuals rarely produces improvement, where should leaders focus instead?

Deming’s answer was clear: study the system.

Leaders who want better performance begin by understanding the conditions shaping the work.

1. Study the system before judging the individual. When results differ, examine the environment in which people are working. Work design, training, tools, workload, and incentives often explain far more variation than most organizations realize.

2. Move leadership attention upstream. Evaluation systems tend to examine results after the work is finished. Systems-oriented leadership focuses earlier in the process—how work is designed, how knowledge flows, and where obstacles appear.

3. Create environments that support learning. Improvement requires experimentation and honest discussion of problems. Organizations improve faster when people feel safe sharing what they are discovering and where work is difficult.

4. Focus conversations on the work itself. Productive leadership conversations explore how work actually happens—how decisions are made, how teams collaborate, and where friction slows progress.

These discussions reveal opportunities for improvement that ratings alone can never capture.

Where real improvement begins

Improving performance is one of the central responsibilities of leadership.

But Deming believed the path to improvement rarely begins with judging individuals. It begins with curiosity about the system that shapes their work.

When leaders study that system—how the work is designed, how people collaborate, and where obstacles appear—they begin to see opportunities that ratings could never reveal.

Methods improve. Cooperation grows. Learning accelerates.

And something else begins to return to the workplace.

People rediscover pride in what they do.

They rediscover joy in work.

Slowly, the organization becomes a place where improvement is simply part of the work itself—growing naturally, every day.

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.”

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.”

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.

Subscribe now

What leaders can do instead

1. 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.

2. 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.

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

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

5. 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.

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.”

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.

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.

Subscribe now

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.

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

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

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

4. 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.

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.

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.

Subscribe now

Actionable Takeaways

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

1. 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.

2. 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.

3. 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.”

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.

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.

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.

Subscribe now

Actionable Takeaways

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

1. 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.

2. 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.

3. 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.

4. 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.

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.

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.

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.

Actionable Takeaways

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

1. 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.

2. 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.

3. 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.

4. 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. Conditions can be improved. People who appear disengaged often surprise us when the work finally makes sense and success is possible.

“The greatest waste in America is failure to use the abilities of people,” Deming warned. When leaders shift from blame to understanding, organizations don’t get softer. They become more humane, more capable, and more effective.

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.

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.

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.

Subscribe now

Actionable Takeaways

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

1. 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.

2. 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.

3. 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.

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.

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.

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.”

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.

Subscribe now

Actionable takeaways

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

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

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

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

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

5. 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.

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 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.

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.”

Subscribe now

Actionable takeaways

These are not tactics to apply all at once. They are starting points—ways to begin aligning daily management decisions with the logic of the chain reaction.

1. Measure rework, not effort. For a short window—one or two days—track how often work loops back: clarifications, missing inputs, avoidable exceptions, reschedules, callbacks, and other “cleanup.” Treat the count as a map of where the system is failing, not a scorecard on people.

2. Define “quality” as entry-point reliability. Make “ready” explicit: required information, prerequisites, and clear handoffs. Build these conditions into the process (templates, required fields, checklists, upstream agreements) so downstream teams don’t have to rescue the work.

3. Follow the chain in order. Look first for fewer snags—less rework, fewer interruptions, fewer delays. Then watch capacity return. Only after that should you expect productivity and results to improve. Resist the temptation to start in the middle.

Taken together, these actions help leaders stay anchored to the first link. They keep attention where improvement actually begins, even when pressure pushes hard in the opposite direction.

Start the chain reaction

Deming’s chain reaction isn’t about doing more. It’s about starting in the right place. When leaders improve quality, they remove the causes of rework and delay that quietly drain their systems. Capacity returns. Productivity improves as a consequence, not a demand. Stability becomes possible. Once this way of thinking takes hold, it’s hard to unsee. Cost and productivity stop looking like levers to pull and start looking like outcomes to be earned.

If improvement is the aim, hold the line on the first link. Quality first.

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.

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.

Subscribe now

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.

1. 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.

2. 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.

3. 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.

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.

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.”

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.

Subscribe now

Actionable Takeaways

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

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

3. 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.

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

5. 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.

That is exactly the moment W. Edwards Deming warned leaders about.

He once observed, “It is easy to manage a business in an expanding market, and easy to suppose that economic conditions can only grow better and better.” His point was not that success is a problem, but that success can quietly disguise weakness.

A very good year

To see what Deming meant, consider a nonprofit serving families through food assistance and job‑readiness programs. It had been a banner year. A new corporate partnership boosted funding. A positive media story brought in volunteers. Enrollment climbed. The board was pleased. Staff morale was high.

At a routine leadership meeting, the updates sounded exactly like you would expect in a good year.

Marcus, who oversaw operations, went first. “We’re serving more families than ever,” he said. “The handoffs are smoother, the wait is shorter, and volunteers are showing up.”

Elena, the executive director, added the development update. “Donors are leaning in,” she said. “We’re ahead of plan, and the support feels steady—for now.”

All of it was true. And yet Elena felt a quiet tension she couldn’t shake. It wasn’t fear. It wasn’t urgency. It was a question that didn’t quite fit the celebratory tone of the room: Are we improving… or are we just busy?

Deming would have recognized that moment instantly. When conditions are favorable, results can improve even if the underlying system stays weak. A strong economy, a generous donor cycle, or a surge of goodwill can lift outcomes without strengthening capability at all.

The tailwind trap

Strong results tell leaders what has happened. They do not explain why it happened, or whether it will happen again. In an expanding environment, ordinary management can look exceptional. Leaders can easily mistake momentum for capability and luck for skill. The danger is not celebrating success—it is assuming success proves the system is sound.

Deming warned that decline rarely announces itself. It arrives like dusk, so gradually that people don’t notice it happening. One day the numbers soften. Then variation increases. Then firefighting becomes normal. By the time leaders recognize the pattern, the room to maneuver has largely disappeared.

Elena sensed that risk, even though nothing appeared broken. Instead of asking for bigger goals or tighter targets, she asked a different kind of question. “If things got tighter next year,” she said, “if funding dipped or demand spiked, what would we wish we’d strengthened while we still had room to breathe?”

The room went quiet—not because the question was threatening, but because it was unfamiliar. Marcus answered first. “Cross-training,” he said after a pause. “Right now, a few people are holding too many threads.”

That one sentence revealed more about the system than any dashboard had. When performance depends heavily on a handful of individuals, results can look excellent right up until someone gets sick, leaves, or burns out. At that point, the organization discovers it has not built a system; it has built a reliance.

Elena heard it clearly. This wasn’t a staffing issue. It was a design issue.

From outcomes to capability

Deming taught that an organization doing well is in the best position—and has the greatest obligation—to improve. When survival pressure is low, leaders have something rare: the capacity to learn.

In a crisis, organizations default to urgency. Controls tighten. Pressure increases. Short‑term output becomes the priority. Sometimes that response is unavoidable. But Deming warned that improvement driven by pressure usually optimizes for speed, not learning, and leaves the system weaker in the long run. Good times create a different opportunity. They allow leaders to shift attention away from celebrating outcomes and toward strengthening capability.

Up to this point, Elena and Marcus had been talking about results. The question now was how to see the system underneath those results. Elena wanted to know whether the organization understood what actually made the work hold together—and whether it could keep holding together when conditions shifted.

A small experiment

Rather than launching a major initiative, Elena proposed a modest experiment. For several weeks, the team would track a few measures of capability—not outcomes. They chose three: the time from first contact to receiving help, the rate of rework caused by missing or unclear information, and the time it took to onboard a new volunteer.

Marcus frowned slightly. “Those numbers are going to move around week to week.”

“Exactly,” Elena said. “If it’s normal noise, we won’t chase it. If there’s a real cause, we’ll go fix the cause.”

That distinction—between a normal wobble and a meaningful change—is central to Deming’s thinking. Most organizations do the opposite. A rough week triggers pressure. A complaint triggers correction of people. A delay triggers urgency. Deming warned that overreacting to everyday variation can make systems worse, not better.

Within weeks, patterns began to emerge. Delays clustered on Mondays. Rework spiked after a partner changed a form. Volunteer onboarding slowed dramatically whenever one staff member was out. None of this showed up in the headline numbers. Funding was still strong. Participation was still high. But the system was quietly revealing where it was brittle.

Instead of setting new targets, the team improved the system. They cross‑trained a role that had become a bottleneck. They standardized intake so rework didn’t depend on who answered the phone. They simplified onboarding so volunteers weren’t stranded when one person was unavailable. The changes were unremarkable on the surface, but their effect was profound. The work became more predictable. Learning accelerated. Capacity grew. The organization became less dependent on heroics and more resilient by design.

Why Deming matters most in good times

Deming once said that a healthy organization is in the best position to improve, and has the greatest obligation to do so. The nonprofit’s experience made that idea tangible: improvement was not driven by fear or crisis, but by foresight. This is why Deming matters most when things are going well. Good times provide the margin to learn, to see the system clearly, and to strengthen it before conditions change.

In any industry, organizations compete not just for customers or funding, but for resilience. They compete against complacency, against the belief that what worked this year will work next year, and against the slow drift of brittleness that success can conceal.

Subscribe now

Actionable takeaways

If you want to use good times wisely, start small and keep it practical. Here are five moves that translate Deming’s insight into day-to-day leadership.

1. Pick one or two capability measures. Choose measures that reveal how strong the system is (flow, rework, onboarding, lead time), not just outcomes.

2. Review enough data to see patterns. Look at performance over time so you can distinguish a normal week-to-week wobble from a meaningful change.

3. Ask the “tightened conditions” question regularly. What would you wish you had strengthened if funding dipped, demand spiked, or staffing changed?

4. Improve the system, not the slogans. Crosstrain bottlenecks, standardize handoffs, and simplify steps where the process is brittle.

5. Treat improvement as stewardship. Use favorable conditions not to relax, but to strengthen the system that carries the aim forward.

Taken together, these steps turn momentum into resilience—so you’re not relying on good conditions to keep getting good results.

A closing thought

Good times are a gift. They are also a test.

They test whether leaders can resist the comfort of applause and invest instead in capability. They test whether organizations can strengthen their systems when they do not have to, so they can endure when they must.

Deming’s message is not to be afraid. It is to be wise.

If things are going well today, you have something precious: room to learn.

Use it.