The Knowledge System Podcast

On paper, the year looked exceptional. Demand was strong. The numbers were up and to the right. Everyone was happy. Inside the organization, the mood was confident, even relaxed. From the outside, it looked like success.

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.

It is easy to manage a business in an expanding market, and easy to suppose that economic conditions can only grow better and better.— W. Edwards Deming

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.

A company that is doing well is in an excellent position to improve management, product, and service, and moreover has the greatest obligation to improve. A company that is on the rocks can only think of survival short-term.— W. Edwards Deming

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.

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.

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

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

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

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

* Treat improvement as stewardship. Use favorable conditions not to relax, but to strengthen the sy…

Every December, leadership teams gather around spreadsheets and planning decks, and one thing slowly crowds out all the others: next year’s growth target. Ten percent. Twenty. “Double in two years.” The number starts to feel powerful, almost magical—as if declaring it clearly enough, and repeating it often enough, will somehow bend the organization into making it true.

But saying a number out loud does not change the future. A number can only describe what already happened. If an organization wants different results next year, it has to change what produces results in the first place. It has to change the system.

W. Edwards Deming gave us a simple place to start: “A system must have an aim. Without an aim, there is no system.” Growth targets can be energizing, but without an aim they become detached from purpose, values, and tradeoffs. Deming paired that idea with an equally blunt warning: “A numerical goal accomplishes nothing. Only the method is important, not the goal.” Deming was not opposed to bold goals; he was opposed to pretending that boldness alone could change outcomes.

Healthy end‑of‑year planning holds both truths at once. The aim sets direction. The method creates learning. Together, they turn ambition into something workable.

A numerical goal accomplishes nothing.Only the method is important, not the goal. By what method?— W. Edwards Deming

A year-end planning meeting

Consider a professional services firm, meeting to set its plan for the upcoming year. The work is demanding, the clients are impatient, and the pace has been relentless. Maya, the managing partner, carries pressure from every direction—revenue expectations, client satisfaction, and the quiet responsibility of not burning out her best people.

Jordan runs operations. He sees the firm not as departments, but as a flow: leads turn into proposals, proposals turn into delivery, delivery shapes the client experience, and that experience determines renewals and referrals. In Deming’s terms, Jordan is paying attention to the system.

On the screen is a single slide: “GROWTH TARGET +25%.”

The instinct is immediate. Translate the number into activity. More marketing. More outbound. More urgency. More everything. That reflex is common—and risky.

Deming described this trap with a word that sounds theatrical but proves painfully accurate: internal goals without a method are “a burlesque.” In other words, planning turns into performance. People look busy. Pressure goes up. Very little actually improves.

The meeting shifts when Jordan asks a question most teams never slow down long enough to consider: Is twenty‑five percent within what our system can deliver—without breaking quality or burning people out?

That question doesn’t lower ambition. It rescues ambition from fantasy.

Turning the target into an aim

Rather than debating the number, Jordan changes the conversation. The team stops arguing about outcomes and starts clarifying purpose. Jordan sketches how revenue actually happens—from first contact to repeat work—and asks where the system could be changed deliberately. This is the essence of system leadership: improving capability instead of demanding better results from existing capability.

The growth slide is rewritten. They replace the solitary percentage with an aim statement that speaks to purpose rather than outcomes: “Improve the reliability of the client experience, while building a system of work our people can sustain.” This is not wordsmithing. It is design. An aim makes tradeoffs visible before the year begins. It tells people what “better” means. And it prevents revenue—important as it is—from becoming the thing people optimize at the expense of everything else.

A system must have an aim. Without an aim, there is no system.— W. Edwards Deming

With the aim clear, the next step is practical. Jordan pulls up the last eighteen months of data—lead flow, close rate, delivery time, rework. Not to judge people. Not to explain every fluctuation. But to understand what the system currently makes likely.

Deming was blunt about this: “If you have a stable system, then there is no use to specify a goal. You will get whatever the system will deliver. A goal beyond the capability of the system will not be reached.” If the system is stable, effort alone will not change outcomes. Only changes to the system will.

A goal beyond the capability of the system will not be reached.— W. Edwards Deming

That’s why Jordan’s conclusion lands so clearly: The system is doing exactly what it has been built to do. If the firm wants a different result, it needs a different method. Ambition doesn’t disappear—it simply moves from wishing harder to building a better system. The growth target becomes a forecast—a best prediction given current capability—and a signal of whether the system is improving.

Replacing pressure with learning

Many organizations respond to ambitious targets by launching a long list of initiatives. The result is predictable: diluted focus, shallow execution, and exhausted teams.

Maya and Jordan choose a different approach. They select two focused improvement efforts—two places where change could meaningfully increase capability.

The first effort sits in proposals. If scope clarity improves and response time shortens, the close rate should rise without needing more leads.

The second effort sits in delivery. If intake and handoffs improve, rework should drop—freeing capacity without longer hours.

They run each effort through a learning cycle—the team states a prediction, tests it with a small group, studies the results, and decides what to adopt, adapt, or abandon. This is not goal chasing. It is disciplined learning. And disciplined learning is how real aspiration becomes real progress.

Substitute leadership—and make it safe

None of this works unless people can tell the truth. Deming’s guidance here is unmistakable: “Eliminate management by objective. Eliminate management by numbers, numerical goals. Substitute leadership.” In practice, leadership means resourcing improvement, removing obstacles, and reducing fear.

Maya makes one commitment explicit: no one will be punished for bad news from the measures. That single decision changes the tone completely. Weekly reviews become sources of insight rather than judgment. People stop managing impressions and start improving the system. Over time, that becomes a real competitive advantage.

Most firms set targets and hope for heroics. A Deming‑style firm builds capability and learns calmly. It becomes steadier, clearer, and more trustworthy—both to clients and to its own people.

Eliminate management by objective.Eliminate management by numbers, numerical goals.Substitute leadership.— W. Edwards Deming

Actionable Takeaways

You don’t need a perfect plan to start the year well. You need clarity and courage.

* Write an aim in one breath. Include what you refuse to sacrifice.

* Choose one or two improvement efforts that would meaningfully change the year. Improve where capability actually matters.

* Establish a simple weekly pulse to see whether you’re getting better. A few signals you can trust.

* Make it safe to surface problems. Bad news is information, not failure.

These steps turn planning from pressure into progress.

A better way to begin the year

End‑of‑year planning often feels like standing at the edge of a new year with a number in your hands, hoping it will be enough.

There is another way.

Carry the year on purpose. Start with an aim your people can recognize as true—how you want to serve, what you want to protect, and what you refuse to sacrifice. Then lead with method. Learn in the open. Improve deliberately.

When the aim is clear and learning is real, people don’t just comply. They commit.

And the year that follows doesn’t just look better on paper. It feels better to live through—steadier days, fewer knots in the stomach, and work that leaves people, and the organization, better off than they started.

You do not rise to the level of your goals.You fall to the level of your systems.— J…

Most leaders have lived some version of this: you coach a team, send follow-up emails, give a firm talk about accountability—but a few weeks later, the same problems are back. It’s easy to conclude that the issue is motivation or discipline. If people would just try harder, surely results would improve, right?

W. Edwards Deming suggested something very different. He argued that most performance comes not from the effort of individuals, but from the system they work in—the processes, policies, tools, measures, and handoffs that shape their day. In his words, “Everyone doing his best is not the answer.” The central leadership question is not, How do I get people to do their best? but rather, Have we designed a system in which their best is even possible?

This distinction between leading people and leading a system feels abstract until you see it play out in real work. The story of Maria and Jamal makes it concrete.

When “Be more careful” isn’t enough

Maria is the chief nursing officer at a busy regional hospital. On paper, the organization looks respectable. In practice, a pattern of small failures is beginning to add up.

Medication errors at discharge are creeping upward. Patients complain that instructions are confusing. Nurses stay late to clean up documentation. Readmission penalties are cutting into already thin margins. Turnover among experienced nurses is quietly rising as people burn out.

Maria does what many conscientious leaders do. She asks her team to slow down and be more careful. The hospital offers refresher training on medication safety. Posters appear in hallways reminding staff to double-check prescriptions.

For a few weeks, the numbers improve. Then, inevitably, problems return.

Maria finds herself repeating the same phrases: “We’ve covered this before.” “We just talked about this in the staff meeting.” “Why is this still happening?”

From a traditional leadership lens, the answer seems obvious: people are not paying attention. The solution is to lead the people harder—more reminders, sharper consequences, stronger language about accountability.

Jamal, a quality improvement specialist, suggests a different starting point. “What if we stop asking, ‘Who messed up?’” he says in a meeting, “and start asking, ‘Why is it so easy to make this mistake here?’”

That question quietly moves the focus from the people to the system.

Seeing the system instead of the individual

Jamal proposes that they study one recurring problem: medication errors at discharge. Rather than issuing another memo, they invite a small cross-functional group into a conference room—nurses, a hospitalist, someone from pharmacy, and an IT analyst. Together, they walk through an actual discharge step by step.

On the whiteboard, the discharge process quickly sprawls into a maze. There are seventeen separate steps. Three software systems do not share data cleanly, so staff copy and paste information between screens. Pharmacy hours do not align with the hospital’s peak discharge times, forcing last-minute workarounds. Two performance metrics quietly pull in opposite directions: nurses are praised for moving patients out quickly to make beds available, while physicians are scolded if documentation is anything less than perfect.

In this light, the recurring errors look less like carelessness and more like the predictable output of a tangled system. Maria voices the realization that has been forming in her mind. “So every day we’re telling people, ‘Go faster and be flawless,’ inside a process that practically guarantees rework.”

The workers are handicapped by the system, and the system belongs to management.— W. Edwards Deming

Deming’s point lands with new clarity. The nurses are not the system. They are working inside the system. As long as that system remains unchanged, no amount of exhortation will deliver reliable improvement.

Changing the work, not the willpower

Instead of launching a grand initiative, the group starts with small, deliberate experiments—PDSA cycles (Plan–Do–Study–Act). Each cycle is designed to change the work itself, not to add more reminders.

First, they standardize the discharge checklist so that nurses, physicians, and pharmacy all use the same list in the same order. This simple change reduces variation in how discharges are prepared.

Next, they adjust scheduling to ensure that a pharmacist is explicitly available for discharge consults during the busiest hours, rather than assuming someone will “fit it in.”

IT builds a single medication summary view so staff no longer have to copy and paste between systems. Information that previously lived in three places now appears on one screen.

At each step, Jamal keeps returning to the same principle: “Let’s not ask people to remember one more thing,” he says. “Let’s change the work so the right thing is the easy thing.”

Over the next few weeks, the tone of incident reviews begins to change. Nurses bring forward near-misses caught by the new checklist. Physicians note that final medication lists are clearer. There are still exceptions, but the patterns are different.

“You know what’s strange?” Maria says during a review. “We’re not seeing ‘careless nurse’ anymore. We’re seeing ‘the new checklist caught an issue before discharge.’”

They have not changed the people. They have changed the system those people work in. Medication errors decline. Readmissions begin to fall. Patient satisfaction nudges upward. Turnover among experienced nurses slows.

Deming summarized this shift succinctly: “The job of management is not supervision, but leadership.” In this context, leadership means taking responsibility for the system, not searching for better slogans to give to already overworked staff.

Leading the system is a competitive advantage

Maria’s hospital does not suddenly become perfect. But it becomes different from many of its peers in one crucial way: it has begun to treat recurring problems as clues about the system rather than as evidence of individual failure.

While other organizations double down on performance reviews, stricter policies, and motivational campaigns, Maria and Jamal invest their energy in redesigning how the work works. They reduce unnecessary variation. They remove non–value-adding steps. They align measures so that people are not pulled in contradictory directions.

Deming estimated that roughly 94% of results come from the system, not from individuals—making improvement chiefly a management responsibility.

This orientation becomes a quiet competitive advantage. Results improve, yes—but something deeper shifts as well. People feel safer raising problems. Frontline staff see that leadership is willing to change processes, not just tighten expectations. Improvement becomes part of the daily conversation instead of an occasional project.

The same pattern applies far beyond healthcare. In software, manufacturing, education, professional services, and nonprofits, leaders face the same choice: spend another year trying to “fix” people, or learn to lead the system they work in.

Actionable takeaways for leaders

If you want to move from leading people to leading a system, you do not need a massive reorganization. You can start small, the way Maria and Jamal did.

1. Treat recurring problems as system signals. When the same issue appears across shifts, locations, or teams, assume it is designed into the work. Ask, “What about our process makes this outcome likely?” before you ask, “Who is at fault?”

2. Go and see the actual flow of work. Dashboards and reports are not enough. Spend time where the work happens. Watch a process from start to finish with the people who live inside it. Have them talk you through every step.

3. Involve the people who do the work in redesigning it. Maria’s breakthrough came not from a closed-door meeting, but from a cross-functional group mapping the discharge process together. The people who touch the work every day are best positioned to see where it fights them.

4. Change the environment, not just the message. Instea…

On paper, sales quotas and commissions look perfectly reasonable. You want growth, so you set a target. You want motivation, so you tie money to the target. The spreadsheet glows with projected revenue.

W. Edwards Deming saw the trap. He warned that when leaders rely on numerical goals and incentives instead of leadership and system design, people will do exactly what you pay them to do—even if it quietly harms customers, coworkers, and the long-term business. Quotas, he argued, invite distortion and fear rather than learning and improvement.

This article explores how that plays out in a mid-sized manufacturing company and how one leadership team used Deming’s ideas to redesign their sales system. The punchline: removing traditional quotas and commissions didn’t make the sales team soft. It made the whole company stronger—and gave them a competitive advantage their rivals couldn’t easily copy.

A sales engine that looked great on paper

Maria was the CEO of a mid-sized manufacturer of machined components for industrial equipment. Tom led sales. Their model was familiar and, at first glance, sensible: annual sales quotas by territory, rich individual commissions, and a flashy “Top Gun” trophy for the top performer every quarter. On the conference-room whiteboard, the plan looked clean. Each year, quotas climbed. Stretch goals triggered bigger bonuses. The trophy promised bragging rights and status.

But the story on the shop floor felt very different.

By the third week of every month, the plant lurched into firefighting mode. Orders flooded in at the end of the quarter as reps scrambled to “make their number.” Customers had been promised delivery dates the factory could not reliably meet and discounts that operations had never signed off on. Forecasts swung wildly and were rarely believed. Overtime spiked. So did stress. Inside the business, an odd phrase kept popping up in meetings: “We’re winning deals, but we’re losing money.”

One Thursday afternoon, Maria finally pulled Tom into her office. “Everywhere I go,” she said, “I hear the same complaint: we’re growing, but we’re exhausted and margins are shrinking. What is going on?”

Tom sighed. “We are winning deals,” he said, “but operations is overwhelmed. The reps will agree to almost anything to hit quota. But if we take away quotas and commissions, how do I keep them hungry?”

It was an honest question—and a common one.

What Deming saw in quotas and numerical goals

Deming’s answer begins with a simple observation: most of the performance of a system comes from the system itself, not from individual effort. Sales results are shaped by pricing, product fit, lead times, available capacity, reputation, and dozens of other factors outside a salesperson’s direct control. When leaders pretend otherwise, they push variation and frustration into the organization.

Deming argued that numerical goals and quotas create three predictable patterns:

* Distortion of the system. People learn to game the metrics—pulling orders forward, discounting aggressively, or pushing the wrong products—because their pay depends on it.

* Fear and short-termism. When missing a number threatens income or status, people naturally become defensive and cautious. They protect themselves, not the system.

* Sub-optimization. Individuals or departments “win” while the company loses. Sales hits its quota while operations burns out and customers get unreliable service.

In Deming’s view, the proper role of management is not to demand higher numbers but to work on the system so that good results are the natural outcome. “Substitute leadership,” he urged, in place of quotas and numerical goals. That means understanding how work actually flows, designing stable processes, and helping people collaborate instead of compete.

Eliminate management by objective.Eliminate management by numbers, numerical goals.Substitute leadership.— W. Edwards Deming

Maria had bumped into exactly the pattern Deming described. Her sales plan was producing visible wins on the scoreboard and invisible damage everywhere else.

Mapping the real sales system

After that Thursday meeting, Maria didn’t rush to rewrite the compensation plan. Instead, she changed her question. Rather than asking, “How do we motivate salespeople?” she asked, “What is the system of sales here?”

She sat in on customer visits. She listened to calls. She walked the plant during those painful end-of-month spikes. She talked with customer service about complaints and cancellations.

A few themes emerged:

* Reps offered deep discounts at the end of each month to close deals and hit quota.

* They promised lead times and configurations that were easiest to sell, not necessarily what the factory could deliver reliably or what was best for the customer’s long-term performance.

* Early-month activity was relatively quiet; then everything surged at the end of the reporting period.

* Forecasts were treated as fiction by operations because they were routinely blown apart by last-minute deals.

The compensation plan, Maria realized, had become a machine for converting fear into distorted orders. The more pressure they applied to hit the number, the more chaos they created downstream.

One evening, Tom found Maria in a small conference room, staring at a wall covered in charts: margins by order, rush charges, late deliveries, rework, and customer churn. “So… you’re really thinking about changing comp,” he said.

“I’m thinking about changing the system,” Maria replied. “Deming says the job of management is to work on the system, not just motivate people. Right now, our system pays people to create chaos.”

For Tom, it was a disorienting moment. But he couldn’t deny the data on the wall.

Redesigning sales to support the whole system

Rather than retreating to a closed-door executive session, Maria and Tom formed a small cross-functional team: sales, operations, finance, and service. The question in front of them was straightforward but radical: How could they design the sales system so that the easiest way to earn a good living was to do the right thing for the customer and for the company’s long-term health?

Over several working sessions, they made three major changes.

1. Shift from individual quotas to shared aims

They eliminated individual sales quotas. Instead of each rep chasing a personal number, the company adopted a small set of shared aims:

* Profitable growth at the company level.

* Smoother flow of orders across the month and quarter.

* Higher retention of the right customers—the ones who valued reliability and partnership.

This didn’t mean sales stopped measuring anything. It meant they stopped treating individual quota attainment as the ultimate scoreboard. The new focus was on whether the business as a whole was getting healthier.

2. Shift from spiky commissions to stable income

Next, they changed compensation. The old plan featured aggressive commissions that swung income dramatically from month to month. The new design paid a solid base salary, with a smaller, shared bonus tied to overall results and customer experience.

The intent was not to punish top performers, but to remove fear. Reps would no longer have to choose between telling a difficult truth and paying their mortgage. Income would be stable enough that they could focus on long-term relationships.

In a rollout meeting, Tom voiced the question hanging over the room. “If there’s no personal quota,” he asked, “what does a ‘good month’ look like for a rep?”

Maria answered, “A good month is when you help customers choose the right work, when you place orders early enough that we can build smoothly, and when we all win—customers, the plant, and you. The bonus will follow that, not just the last-minute number on a chart.”

3. Shift from volume obsession to system health

Finally, they changed what they paid attention to. Instead of obsessing over monthly volume by rep, they reviewed:

* On-time delivery and schedule adherence.

* Reorder rates and customer retention.

* The accuracy and usefulness of forecasts.

* Simple signals of cus…

How many people in your organization could clearly explain why their work matters—how what they do connects to the larger purpose of the business? If the answer is “not many,” you’re in good company. Most employees see their part of the process but not how it fits into the whole. They may know what their job is, but not why it exists. Dr. W. Edwards Deming believed this was one of the great failings of modern management. He wrote that “a system must have an aim. Without an aim, there is no system.” And the responsibility for understanding and communicating that aim falls squarely on the manager.

When a manager helps people understand how their work contributes to the system’s aim, something profound happens. Confusion turns into clarity. Competition between departments gives way to cooperation. Instead of optimizing their own metrics, people begin improving the whole. This is not management as control; it’s management as education. And it begins with explaining the meaning of a system.

A manager understands and conveys to his people the meaning of a system. He explains the aims of the system. He teaches his people to understand how the work of the group supports these aims. — W. Edwards Deming

A story from the floor

Let’s imagine a mid-sized manufacturer of specialty packaging—nothing glamorous, but a steady business with loyal customers. Karen is the operations manager. Luis runs one of the die-cutting machines on the production floor. One morning, Luis approaches Karen with frustration written all over his face.

“Karen, I keep getting told to cut faster,” he says, “but then quality sends half my sheets back. If I slow down, I get scolded for falling behind. Which one do you want?”

Karen sighs. She’s heard this before—from Luis, from others. The plant’s metrics emphasize speed, but rework and late shipments are rising. The problem isn’t Luis—it’s the system.

“Let’s talk about that,” Karen replies.

Later that morning, she gathers her team around a whiteboard. In three boxes, she writes Sales → Production → Customer.

“Our system isn’t about ‘more output,’” she begins. “It’s about on-time delivery of defect-free packaging that delights the customer. Every part of our process exists for that purpose.” She explains how cutting speed affects quality, how rework delays shipping, and how delays disappoint customers and strain sales. The group begins to see that “production” isn’t a standalone department—it’s part of an interdependent system.

Luis nods slowly. “So,” he says, “it’s not about cutting faster. It’s about helping the next step succeed.”

Karen smiles. “Exactly. You’re part of a system that depends on you.”

What Deming meant by “Understanding the system”

Deming described a system as “a network of interdependent components that work together to try to accomplish the aim of the system.” The word interdependent matters here. Each part relies on the others. When one part improves at the expense of another, the system as a whole suffers.

That’s why managers must resist the temptation to push local optimization—like demanding faster output from Luis—without considering the broader effects. It might make a chart look better in one department, but it often creates waste, frustration, and loss elsewhere.

Deming warned against this kind of “sub-optimization,” noting that “every system is perfectly designed to get the results it gets.” If your system produces conflict, rework, or burnout, that’s not a failure of your people—it’s a reflection of how the system is managed.

Karen’s shift in focus—from individual targets to system aims—transformed how her team worked together. She didn’t just issue new orders; she provided understanding.

From supervision to leadership

A manager who explains the meaning of a system becomes more than a supervisor of tasks—they become a teacher of purpose. Deming wrote in The New Economics, “The job of management is not supervision, but leadership.” Leadership, in his sense, is about helping people see the system, learn from it, and contribute to its continual improvement.

The job of management is not supervision, but leadership. — W. Edwards Deming

Karen’s story may be fictional, but the lesson is very real. In every business—manufacturing, software, healthcare, education—the same principle applies. People cannot improve what they do not understand.

When you teach your team how their work supports the system’s aim, you align energy and creativity toward a shared purpose. You replace blame with curiosity. You move from firefighting to improvement.

And that understanding, Deming would say, is a competitive advantage.

Actionable Takeaways

If you’re a manager or business owner, here are four practical steps you can take this week to put Deming’s principle into action:

* Clarify the aim of your system.Write one clear sentence: What is our organization for? Every process, policy, and decision should connect to that aim.

* Make the interdependencies visible.Draw your workflow on a whiteboard. Show how each part affects the others. Discuss the handoffs, not just the silos.

* Teach through examples.Identify one situation where local optimization hurt the whole system. Use it as a learning moment.

* Reinforce purpose constantly.In meetings, reviews, and planning sessions, ask: “How does this serve the aim of our system?” Keep that question alive.

Managers who help people understand the system don’t just improve performance—they build trust, pride, and shared responsibility. As Deming reminded us, “The transformation is everyone’s job.” But it begins with leaders who are willing to teach the meaning of the system.

The transformation is everybody’s job. — W. Edwards Deming

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

When a company struggles with motivation, most leaders reach for incentives — bonuses, competitions, maybe a few gold stars. It’s instinctive. If people aren’t performing, we assume they just need more motivation. But what if the very tools we use to “motivate” people are quietly destroying their motivation?

W. Edwards Deming thought deeply about this question. In his System of Profound Knowledge, one of the four interrelated components is psychology — understanding human behavior, what drives people, and what stifles them. He believed that management must understand psychology not to manipulate people, but to work with human nature instead of against it.

Let’s bring this to life through a story.

A misguided incentive

Sarah manages a small team of eight. She’s sharp, caring, and determined to help her team succeed. But lately, sales have flattened, customer complaints are rising, and morale has taken a hit. People seem to be coasting. So, Sarah decides to inject some energy into the team.

“Starting this quarter,” she announces, “we’re rolling out a new incentive program. Top performer each month gets a $500 bonus. Let’s make it fun — a little friendly competition!”

Across the table, Alex, one of her most reliable employees, shifts in his chair. He frowns slightly before asking, “So… if I help Sam with his project, that means I’m lowering my score, right?”

And there it is — the quiet sound of trust leaving the room.

Deming warned us about this. He once said, “The greatest waste in America is failure to use the abilities of people.” And one of the fastest ways to waste human potential is to create systems that pit people against one another instead of aligning them toward a shared aim.

The greatest waste in America is failure to use the abilities of people. — W. Edwards Deming

The psychology of intrinsic motivation

Deming believed people are born with intrinsic motivation — a natural desire to learn, contribute, and take pride in their work. Children, for example, are naturally curious and eager to improve. They don’t need to be bribed to explore. But in many workplaces, management replaces that inner drive with a maze of extrinsic motivators: contests, rankings, bonuses, and “Employee of the Month” plaques.

These incentives may create bursts of short-term performance, but they do long-term damage. They teach people to chase rewards instead of mastery. They shift focus from the joy of good work to the fear of losing. They undermine teamwork, creativity, and — ironically — quality.

Deming’s insight was that when management uses rewards and punishments as levers, it signals something deeper: “We don’t trust your internal drive.” And that message quietly corrodes pride and engagement.

From manipulation to support

Back in our story, Sarah begins noticing side effects. Alex stops volunteering ideas. Sam rushes through his tasks, cutting corners to stay ahead in the leaderboard. Collaboration fades. She’s unintentionally turned teammates into competitors.

Frustrated, Sarah meets with her mentor, who offers a different lens: “Instead of trying to motivate your people, try to understand what’s demotivating them. Remove the barriers that keep them from doing good work.”

So, Sarah cancels the contest and calls a new meeting. “I realized we’ve been competing instead of collaborating,” she admits. “I want to know what’s getting in your way — what makes it hard to do your best work?”

Alex speaks up first. “Honestly? The reporting software is so slow, it eats up hours every week. We’re wasting time we could be spending helping customers.”

That’s real psychology in action — uncovering frustration instead of disguising it with prizes.

Sarah takes action. She works with IT to fix the reporting system, streamlining workflows. She also invites the team to design their own quality checks. Within a few months, customer complaints drop. Sales improve. But what stands out most isn’t the numbers — it’s the energy. People care again.

Deming’s lesson: Help people do a better job

Deming put it simply: “The aim of leadership should be to improve the performance of man and machine, to improve quality, to increase output, and simultaneously to bring pride of workmanship to people.” The manager’s role is not to motivate through fear or rewards, but to create conditions for pride in workmanship. That means removing obstacles, clarifying purpose, and showing respect for the human need to grow and contribute. Psychology, in Deming’s view, isn’t a soft skill — it’s a management science. It’s the art of building systems that align with human nature, not fight it. When you do that, you don’t have to push people to perform. You simply stop holding them back.

The aim of leadership should be to improve the performance of man and machine, to improve quality, to increase output, and simultaneously to bring pride of workmanship to people. — W. Edwards Deming

Actionable takeaways

* Stop trying to “motivate” people. Assume your employees are already motivated — your job is to avoid killing that motivation.

* Remove barriers to pride in workmanship. Ask, “What frustrates you about doing good work?” Then fix it.

* Replace competition with collaboration. Design systems where everyone wins when the customer wins.

* Honor intrinsic motivation. Recognize effort, learning, and contribution — not just outcomes.

* Lead with respect for human nature. As Deming taught, “People are different. They are born with different abilities, and management must be aware of these differences.” Treat variation in people as a strength to be understood, not a flaw to be corrected.

Understanding psychology, as Deming defined it, is not about managing emotions. It’s about understanding the system of human motivation — and building organizations where people can take pride in their work. When you do that, quality, innovation, and joy naturally follow. Because in the end, the real competitive advantage isn’t control — it’s trust.

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

Imagine you’re running a business that’s always in motion. New marketing ideas, process changes, team initiatives — all in the name of improvement. But deep down, you feel like you’re guessing. Some efforts work beautifully, others fizzle, and you can’t quite explain why. You’re getting results, but not understanding.

That’s where W. Edwards Deming’s Theory of Knowledge comes in. It’s the part of his System of Profound Knowledge that deals with how we learn, not just how we act. Deming believed that experience alone doesn’t teach us much — unless we start with a theory that predicts what will happen. As he famously said, “Experience by itself teaches nothing. Without theory, there is no learning.”

Experience by itself teaches nothing. Without theory, there is no learning. — W. Edwards Deming

The problem: Acting without understanding

Consider Sarah, an operations manager in a mid-sized manufacturing company. She’s bright, dedicated, and deeply frustrated. “We keep launching improvement projects,” she tells her team, “But I can’t tell what’s actually making the difference.”

Across the table, Leo, one of her front-line employees, nods. “Every few months, there’s a new initiative,” he says. “We collect data, we make changes, but honestly — we’re just guessing.”

Sarah and Leo’s situation is common. They’re reacting to results rather than understanding the system that produces them. Without a theory — without an explanation of cause and effect — every improvement becomes an isolated experiment. Something works? Great. But why did it work? Will it still work next quarter? In another department? Under different conditions? They have no way to know.

Deming captured this idea simply: “Management is prediction.” In other words, every decision a manager makes is, at its core, a prediction about the future — an expression of belief that if we do this, then that will happen. To make sound predictions, we need theory first.

Management is prediction. — W. Edwards Deming

The turn: From guessing to learning

Sarah decided to try something different. At the start of her next improvement project, she asked her team a simple question: “Before we make this change, what’s our theory? Why do we think this will help?”

The room went quiet. Then Leo spoke up. “We think if we shorten our daily huddles from twenty minutes to ten, we’ll have more time to solve problems on the floor — without losing communication quality.”

That statement was their theory — a small, testable prediction connecting cause (shorter meetings) to effect (more time for problem-solving). For the first time, they weren’t just changing things; they were learning.

After a month, they measured the results. Productivity had improved, but only when team leads posted a short, written summary after each huddle. Without that follow-up, communication gaps reappeared. So, they revised their theory: the improvement came not from shorter meetings alone, but from pairing brevity with written follow-through.

In that moment, Sarah’s team crossed an invisible line. They stopped being operators of a process and became students of it. They were no longer guessing — they were learning through prediction and revision. That is Deming’s Theory of Knowledge in action.

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

What this means for you

In business, it’s easy to confuse action with progress. We change processes, restructure teams, and roll out new strategies — but unless we understand why those changes work, we’re just rearranging pieces on the board. The Theory of Knowledge reminds us that improvement without theory is luck; improvement with theory is learning. It’s the difference between reacting to outcomes and building a body of understanding that compounds over time. Deming urged managers to ground every action in prediction and reflection. When our predictions fail, it isn’t a setback — it’s feedback. The theory was wrong, and that’s valuable information. As Deming put it, “Knowledge comes from theory. Without theory, there is no learning.”

Knowledge comes from theory. Without theory, there is no learning. — W. Edwards Deming

Actionable takeaways

* Start every improvement with a theory. Before making a change, write down what you believe will happen and why. This creates a baseline for learning.

* Make predictions explicit. Treat every initiative as a hypothesis: If we do X, then Y should happen because...

* Compare results to your predictions. When outcomes differ, don’t blame the data or the people — revisit your theory. What did you misunderstand about the system?

* Document what you learn. Keep a “theory log” — a living record of your team’s experiments and evolving understanding. Over time, this becomes your most powerful management asset.

* Value learning over being right. Progress comes from refining your understanding, not from defending your initial ideas.

Sarah’s story ends simply. Her team didn’t just fix a meeting problem — they learned how to think. They moved from reacting to results to developing knowledge about why results occur.

That’s the quiet power of Deming’s Theory of Knowledge: it replaces the illusion of control with the practice of learning. When managers lead with theory — when they predict, test, and revise — they stop chasing outcomes and start compounding understanding. And in business, understanding is the only sustainable competitive advantage.

Every day, leaders make decisions — sometimes by the numbers, sometimes by gut feel. But what if those numbers don’t mean what we think they do? In the world of management, few concepts are as powerful or as misunderstood as variation. Dr. W. Edwards Deming, the father of modern quality and systems thinking, believed that our ability to understand variation — to truly see the difference between signal and noise — determines whether we manage with wisdom or with chaos.

A spike in defects

Meet Sarah, the operations manager of a small manufacturing company that produces precision components for electric motors. Every morning, she checks a dashboard showing yield rates, defect counts, and output per hour. Her team is competent, disciplined, and proud of their work.

One morning, Sarah notices that the defect rate has jumped from 1.8% to 2.9%. Frowning, she calls in Tom, one of her most experienced line supervisors. “Tom,” she says, “this is the second time this month the defect rate has gone up. What’s going on down there?”

Tom shifts uncomfortably. “We’ve been doing everything the same,” he says. “Same people, same materials. Honestly, it just feels like normal ups and downs.”

Normal ups and downs. Sarah doesn’t realize it yet, but that phrase holds the key to the entire situation.

Common causes vs. special causes

Dr. Deming taught that all processes — in business, in production, even in life — show variation. No two days, no two products, no two employees perform identically. Some variation is built into the system; other variation comes from something unusual. Deming called these common causes and special causes.

* Common causes are the natural, predictable fluctuations in a stable process — the everyday randomness of reality.

* Special causes are signals — events or factors outside the system that create unusual variation.

When managers fail to distinguish between the two, they make destructive decisions. As Deming warned, “A manager who does not understand variation is doomed to react to every change as if it were a special cause.”

A manager who does not understand variation is doomed to react to every change as if it were a special cause. — W. Edwards Deming

Mistaking noise for signal

Sarah assumes that something special caused the spike in defects. Her instinct is to act — to tighten inspections, retrain staff, or revise procedures. But what if Tom is right? What if this is just noise — part of the natural rhythm of a stable system?

If Sarah were to plot her daily defect rates over time — a simple run chart, or better yet, a control chart — she might see that her process consistently varies between 1.5% and 3.2%. In that case, 2.9% isn’t a problem. It’s just where the data happens to fall today.

When managers react to every wiggle in the numbers, they introduce instability. They adjust, reassign, and “fix” things that aren’t broken. Deming called this tampering — changing a stable system based on random fluctuation. Over time, tampering increases variation, lowers morale, and degrades performance.

Tom feels this firsthand. “We make adjustments every time she sees a change,” he tells a colleague, “And the next day it swings the other way. We can’t win.” He’s right. When leaders mistake noise for signal, they punish people for patterns the system itself creates. The result is frustration, fear, and a loss of faith in management.

Seeing the system

Dr. Deming often said, “If you can’t describe what you are doing as a process, you don’t know what you’re doing.” Understanding variation is part of that knowledge. It’s not just a statistical exercise — it’s a lens for seeing how work really happens.

If you can’t describe what you are doing as a process, you don’t know what you’re doing. — W. Edwards Deming

Here’s what Sarah could do differently, and what any leader can apply immediately:

* Plot data over time.Don’t rely on single numbers or isolated reports. Patterns tell stories that point data never can.

* Ask if the process is stable.If variation is random and predictable, focus on improving the system itself — better methods, clearer processes, smarter design — not blaming individuals.

* Only act when there’s evidence of a special cause.A point outside the control limits, or a non-random pattern, signals something new. Investigate then — not before.

Deming put it simply: “Management of a system requires knowledge of the interrelationships between the components of the system and of the variation within it.” In other words, leadership begins with understanding what can be predicted, and what cannot.

Management of a system requires knowledge of the interrelationships between the components of the system and of the variation within it. — W. Edwards Deming

Leading with knowledge, not reaction

When leaders grasp variation, they move from firefighting to stewardship. They stop chasing yesterday’s numbers and start designing systems that improve tomorrow’s outcomes. They ask better questions, make fewer mistakes, and earn the trust of the people who do the work.

The next time your numbers fluctuate — a sales dip, a customer complaint, a change in productivity — take a breath. Ask yourself: Is this a signal, or just noise? Because reacting to noise doesn’t improve the process. It only adds confusion.

Understanding variation isn’t just for statisticians. It’s a management skill — and perhaps the most important one of all. It’s how we move from managing by fear to managing by knowledge. And in Deming’s words, “Without data, you’re just another person with an opinion.” But without understanding variation, even data can lead you astray.

Without data, you’re just another person with an opinion. — W. Edwards Deming

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

Apply this in your organization

If you want to start applying Deming’s lesson on variation in your own organization, try this:

* Pick one key metric you review regularly — quality rate, revenue, customer satisfaction, anything.

* Graph it over time. Don’t look at daily or weekly snapshots; look at the flow.

* Look for stability. Are you seeing predictable fluctuations, or true signals of change?

* Resist the urge to react to every up and down. If the process is stable, focus on improving the system, not the people.

This week, aim to be more like Tom — patient enough to see the pattern — and less like Sarah before she learned the lesson. In Deming’s philosophy, understanding variation isn’t about statistics. It’s about respect for reality.

Most business leaders believe performance problems come from people. Someone didn’t care enough, didn’t try hard enough, or just “messed up.” But W. Edwards Deming — one of the most influential thinkers in management history — taught something radically different. He said, “A bad system will beat a good person every time.” In other words, even your most talented people can’t succeed if the system they work in is designed to fail. And most of the time, that’s exactly what’s happening.

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

This lesson, part of Deming’s System of Profound Knowledge, is called Appreciation for a System. It’s about understanding that every organization is a network of interdependent parts — departments, teams, and processes — working toward a shared purpose.

And crucially, Deming reminded us that every system must have an aim — a clear, meaningful purpose that benefits everyone touched by the organization: customers, employees, suppliers, and society. Without a shared aim, even good people and good processes will pull in different directions.

Let’s bring this idea to life through a familiar story.

A familiar problem

Meet Sarah, a manager at a mid-sized manufacturing company that makes precision parts for electric bicycles. For months, she’s been frustrated. Production numbers are down. Customer complaints are up.

One afternoon, she pulls Jason, one of her best machinists, into her office. “Jason, we’ve got to pick up the pace,” she says. “The board’s on my back about these delays. Can you stay late and help hit the quota?”

Jason hesitates. “I can,” he says, “but honestly, half my time is spent fixing the measurements from the CAD files. Engineering keeps changing specs after we start cutting. We never know which version’s the right one.”

Sound familiar? Sarah thinks she has a worker problem. But Jason is describing a system problem. The real issue isn’t in his effort — it’s in how the parts of the organization interact.

Understanding the system

Deming’s idea of Appreciation for a System is simple, but profound. Every organization is made up of interdependent parts — each performing a function, but none existing in isolation. If you improve one part without considering its connection to others, you risk making the whole worse. When Sarah pressures Jason without understanding the upstream design process, she creates short-term motion but long-term waste.

To truly see the system, leaders must ask:

* How do our processes connect?

* Where do handoffs create friction?

* Who depends on whom — and for what?

* And what’s the aim we’re all working toward?

Deming taught that the job of management is to optimize the system as a whole, not to judge or reward individual parts in isolation. When leaders act as if each department is an island, they unknowingly create competition where cooperation should exist. As Deming put it, “The aim of leadership should be to improve the performance of man and machine, to improve quality, to increase output, and simultaneously to bring pride of workmanship to people.”

The aim of leadership should be to improve the performance of man and machine, to improve quality, to increase output, and simultaneously to bring pride of workmanship to people. — W. Edwards Deming

A shift in thinking

A week later, Sarah decides to do something she’s never done before: map the entire workflow. She invites people from engineering, production, and quality control into the same room. “I realize I’ve been asking each of you to go faster,” she admits, “but I never stopped to ask how your work connects. Let’s map it together.”

As the group starts drawing out their process, a pattern emerges. Engineering updates CAD files after production begins — and those updates don’t automatically reach the shop floor. The result? Jason and his team cut parts from outdated specs.

Jason leans forward. “So, if we just sync file versions daily, we’d stop cutting the wrong parts?”

The lead engineer nods. “Exactly. We can automate that alert in the system.”

Then Sarah asks one more question. “What’s the aim of all this work? Why are we here?”

After some discussion, the team agrees that their purpose isn’t just to ship parts faster — it’s to build components that make electric bicycles safer, more reliable, and more enjoyable for riders — in a way that supports customers, respects employees, and sustains the business. That aim reframes everything. It’s not just about speed or quotas. It’s about delivering value to everyone touched by their work.

Within weeks, productivity improves — not because people worked harder, but because they finally worked together, guided by a shared aim.

Lessons for leaders

Sarah’s story illustrates a truth most leaders eventually learn the hard way: you can’t manage outcomes if you don’t manage the system that produces them.

Here are four takeaways you can apply right now.

* See your organization as a system. Draw the flow of work from customer request to delivery. Where are the loops, the delays, the rework? Visualize it — because you can’t improve what you can’t see.

* Look between departments, not just within them. Deming reminded us that most problems occur “at the interfaces” — the handoffs no one owns. Pay attention to those boundaries.

* Shift blame from people to process. When something goes wrong, resist the reflex to ask, “Who messed up?” Instead, ask, “What in our system made this the likely outcome?”

* Give the system a meaningful aim. Make sure everyone knows the ultimate purpose of their work — one that serves customers, employees, suppliers, and society. Profit follows, but it isn’t the aim.

Deming believed leadership is about designing the conditions for success. Your job isn’t to motivate people to do better work inside a broken system; it’s to create a better system so they can do their best work naturally.

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

Closing thoughts

In Sarah’s case, the breakthrough didn’t come from heroics. It came from humility — the willingness to see her team as part of a living, interdependent system. Once she did, improvement followed naturally.

Your organization — whether it builds bicycles, software, or sandwiches — is also a system. The question is: do you see it that way? Because once you do, everything changes. You stop managing by firefighting and start managing by design. You stop blaming individuals and start improving interactions. And you begin to understand what Deming really meant when he said, “It is not enough to do your best; you must know what to do, and then do your best.”

It is not enough to do your best; you must know what to do, and then do your best. — W. Edwards Deming

Leadership isn’t about driving people harder — it’s about shaping the system they work in. When you see your organization as a system, you stop chasing symptoms and start solving causes. That’s how sustainable improvement begins. So, take a page from Deming — and from Sarah. Step back. Look across the whole. Because once you see the system, you’ll never see your business the same way again.