The Knowledge System Podcast

Five-minute Deming: Tampering

A leader can make a process worse while trying very hard to improve it. That is the danger of tampering. When every disappointing result triggers a new rule, a new explanation, or a new adjustment, management may be reacting to routine variation as if something unusual happened. The result is more noise, more frustration, and less learning. The better question is not, What changed yesterday? The better question is, Do we know what kind of variation we are seeing? The temptation to chase the last number W. Edwards Deming used a simple funnel experiment to make this problem visible. Imagine dropping a marble through a funnel toward a target. Even if the funnel stays in the same position, the marble will not land in exactly the same place each time. The natural impulse is to move the funnel after each miss, trying to compensate for the last result. That feels sensible. It feels active. It feels like control. But if the process is already stable, repeated adjustment can spread the results farther from the target. The act that feels like control becomes a source of instability. Management can fall into the same pattern whenever it treats the latest result as a command. A dashboard turns red. A customer complains. A weekly number dips. Someone asks for an explanation, and the organization rushes to change the work. Sometimes that response is necessary. A real special cause deserves attention. But when the process is stable, the better work is to improve the system, not chase each point. That is the problem ClearStep, a mid-sized B2B software company, faced when its support leaders tried to improve response time by changing the process after every bad day. The support dashboard that would not settle down ClearStep sold project management software to manufacturers. Its support team handled setup questions, bug reports, billing issues, and urgent support calls. The team was capable, but its work arrived unevenly. Rina, ClearStep’s head of customer support, watched one number more than any other: median first response time. When it rose, customers complained. When it fell, the executive team relaxed. Monday morning, the dashboard looked bad. Response time had jumped from twenty-three minutes to thirty-seven. Rina opened the team meeting with a decision already forming. “We need a new rule. For the rest of the week, no one works on follow-up tickets until the new queue is under control.” Marcus, the operations analyst who helped the support team study workflow data, hesitated. He had been plotting daily response time for the past six months. “I know thirty-seven minutes looks bad,” Marcus said. “But it is still inside the range we have seen before.” “Customers do not care about ranges,” Rina said. “They care that we were slow.” “Agreed,” Marcus said. “But if we change the rule every time the number moves, we may be adding variation ourselves.” That was not what Rina wanted to hear. She was trying to be responsive, not careless. The team had already changed the escalation rule twice that month. One week, senior agents took every urgent ticket first. The next week, new tickets came first. By Thursday, response time improved, but reopenings were up. Customers got quick replies that did not resolve the issue. The team was moving faster and learning less. Deming named the trap plainly: “Mistake 1. To react to an outcome as if it came from a special cause, when actually it came from common causes of variation.” Mistake 1. To react to an outcome as if it came from a special cause, when actually it came from common causes of variation.— W. Edwards Deming Rina asked Marcus to show the chart again. The bad Monday was unpleasant, but it was not outside the usual pattern. The system had been predictable for months. Response time bounced within a wide band because of uneven ticket routing, inconsistent urgency definitions, and too few agents trained on integration issues. “So doing nothing is the answer?” Rina asked. “No,” Marcus said. “Studying the system before we change the rules is the answer.” “Then what do we change?” “Not the queue every morning. We change the conditions that keep creating these wide swings.” That distinction changed the conversation. ClearStep still investigated real signals: outages, product releases, unusual customer spikes. But it stopped rewriting queue rules after ordinary variation. Rina’s team clarified urgency definitions, cross-trained agents on integration questions, and reviewed blocked tickets each day to remove causes of delay. The solution was not inaction. It was action aimed at the system. Why we keep treating noise like a signal We drift into tampering because the pressure to respond is real. A leader sees a bad number and feels responsible for it. A customer is waiting. A team is anxious. An executive wants an explanation. In that moment, studying variation can sound like delay. But the demand for an explanation can create its own distortion. If every up and down requires a story, people will supply stories. Some will be true. Some will be guesses. Some will be shaped by what seems safest to say. The organization may become better at explaining variation than reducing it. Deming’s warning is uncomfortable because it challenges a common picture of leadership. We often equate visible reaction with accountability. We expect the manager to change something, tighten something, or call someone into the room. But if the latest point came from common causes, the visible reaction may make the system harder to understand. Deming put the problem sharply: “They were tampering with a stable system, making things worse.” This is not only an internal efficiency problem. A company that keeps changing priorities teaches employees to protect themselves from the latest swing. It teaches customers to expect inconsistency. Over time, reliability becomes harder to deliver, and trust becomes harder to earn. The management habit that looks decisive in the moment can quietly weaken the system that customers experience. What leaders can do instead Before choosing a response, leaders need a way to separate movement that calls for investigation from movement that calls for system improvement. Deming was not arguing for passivity. He was arguing for action that fits the evidence. * Observe the system before reacting. Do not treat the latest point as a command. Look at performance over time and ask whether the process is showing a real signal or behaving as it has behaved before. * Separate urgency from interpretation. A customer problem may need immediate care, but that does not mean the process itself needs a new rule. Serve the customer, then study what the result means. * Ask better management questions. Instead of asking, “Who caused yesterday’s miss?” ask, “What conditions keep producing this range of results?” The second question moves attention from blame to capability. * Improve the sources of variation. Work on definitions, training, handoffs, equipment, priorities, and decision rules. These are less dramatic than a new order from management, but they are usually closer to the real causes. * Build reliability as a management advantage. When a company reduces unnecessary variation, people can plan, customers can trust the service, and leaders can learn faster. That consistency is hard to copy because it comes from the way the system is managed. The key is to avoid confusing energy with improvement. Activity can make management feel involved while leaving the process worse than before. Better leadership starts by seeing variation Tampering is tempting because action feels responsible. But leadership is not measured by how quickly a manager changes something after a bad number. It is measured by whether the action fits the evidence. Some results call for investigation. Some call for patience and system improvement. The skill is knowing the difference. When leaders stop chasing noise, they create the conditions for steadier work, clearer learning, and better performance tomorrow. That is the practical promise of understanding variation: better action, taken for better reasons. Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit posts.knowledgesystem.com [https://posts.knowledgesystem.com?utm_medium=podcast&utm_campaign=CTA_1]

Five-minute Deming: Intrinsic motivation

Most people do not begin meaningful work hoping to do the minimum. They want to contribute, solve problems, serve people well, and take pride in what they do. Yet many organizations manage as if motivation must be manufactured from the outside through rankings, bonuses, contests, pressure, or fear. 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.” Extrinsic motivation in the extreme crushes intrinsic motivation.— W. Edwards Deming 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.” No one can put in his best performance unless he feels secure.— W. Edwards Deming 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.” No one can enjoy his work if he will be ranked with others.— W. Edwards Deming 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. 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. * 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. * 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. * 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. * 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. * 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.” The merit system destroys cooperation.— W. Edwards Deming 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. All anyone asks for is a chance to work with pride.— W. Edwards Deming Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit posts.knowledgesystem.com [https://posts.knowledgesystem.com?utm_medium=podcast&utm_campaign=CTA_1]

Five-minute Deming: Zero defects

Zero defects sounds like seriousness. It sounds like standards. It sounds like the kind of phrase a responsible executive should say when quality slips. 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.” Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity.— W. Edwards Deming 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.” [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.— W. Edwards Deming 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. What leaders can do instead * 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. * 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. * 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. * 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. * 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. * 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. No defects, no jobs, can go together. Something other than zero defects is required.— W. Edwards Deming Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit posts.knowledgesystem.com [https://posts.knowledgesystem.com?utm_medium=podcast&utm_campaign=CTA_1]

Five-minute Deming: Employee retention

Most leaders talk about employee retention as if it were mainly a hiring problem, a pay problem, or a culture problem. W. Edwards Deming points us somewhere more demanding. What if people leave because the system makes good work too hard, and honest work too risky? 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.” No one can put in his best performance unless he feels secure.— W. Edwards Deming 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.” Evaluation of performance nourishes fear.— W. Edwards Deming 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. 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.” [A leader] tries to create for everybody interest and challenge, and joy in work.— W. Edwards Deming 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. * 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. * 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. * 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. * 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. * 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. All anyone asks for is a chance to work with pride.— W. Edwards Deming Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit posts.knowledgesystem.com [https://posts.knowledgesystem.com?utm_medium=podcast&utm_campaign=CTA_1]

Five-minute Deming: Profit

Most leaders would never say profit does not matter. The problem is almost the opposite. They talk about profit constantly. Budgets tighten. Targets multiply. Departments are pressed to improve their own numbers. On the surface, that can look like discipline. 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.” Emphasis on short-term profit defeats constancy of purpose and long-term growth.— W. Edwards Deming 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.” 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.— W. Edwards Deming 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. Four ways to care about profit more seriously * 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. * 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. * 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. * 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. Profit comes from repeat customers—those that boast about the product or service.— W. Edwards Deming 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. The aim proposed here for any organization is for everybody to gain—stockholders, employees, suppliers, customers, community, the environment—over the long term.— W. Edwards Deming Thanks for reading The Knowledge System! Subscribe for free to receive new posts and support my work. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit posts.knowledgesystem.com [https://posts.knowledgesystem.com?utm_medium=podcast&utm_campaign=CTA_1]