The Knowledge System Podcast cover art

The Knowledge System Podcast

The Knowledge System Podcast

By: Michael Carr
Listen for free

About this listen

 The Knowledge System Podcast explores how leaders can use systems thinking to create lasting organizational improvement. It translates the ideas of W. Edwards Deming and other thought-leaders into practical strategies for building smarter, more effective systems.

posts.knowledgesystem.comMichael Carr Economics Management Management & Leadership
Episodes
  • Five-minute Deming: Employee retention

    Five-minute Deming: Employee retention
    Apr 29 2026
    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 staysIn 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 resignationsLena 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 DemingLena 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 DemingOnce 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 ...
    Show More Show Less
    8 mins
  • Five-minute Deming: Profit

    Five-minute Deming: Profit
    Apr 22 2026
    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 systemDeming’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 DemingThat 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 losesRiverview 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 patternMost 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...
    Show More Show Less
    9 mins
  • Five-minute Deming: Control charts

    Five-minute Deming: Control charts
    Apr 15 2026
    Leaders today rarely suffer from a lack of data. The deeper problem is that we often do not know what the data is asking us to do. A number rises, and we feel pressure to respond. A number falls, and we assume something worked. In both cases, we may be reacting to movement without understanding meaning.Control charts matter because they help us separate ordinary variation from a real signal. That sounds technical. It is actually a practical discipline for calmer judgment, better decisions, and less wasteful management.Why this changes the work of leadershipControl charts are often treated as a specialist’s tool, useful for analysts or quality teams but distant from executive work. W. Edwards Deming saw them differently. He treated them as a way for management to distinguish what belongs to the system from what points to something unusual.That distinction changes the kind of leadership action that makes sense. If the chart shows a special cause, we investigate what changed. If the chart shows a stable but disappointing system, we stop chasing episodes and improve the design of the work itself.Deming captured the idea in one memorable line: “The control chart is the process talking to us.”The control chart is the process talking to us.— W. Edwards DemingThat is why the concept matters beyond reporting. A chart is not there to decorate a dashboard or make review meetings look disciplined. It is there to help us hear the system before we explain it, correct people for it, or reorganize around the latest fluctuation. A hospital story makes that distinction easier to see.What St. Anne’s learned in one meetingAt St. Anne’s Hospital, emergency department boarding times had become a recurring source of executive concern. Week by week, the numbers moved up and down. Patients waited too long for beds upstairs, complaints kept coming, and senior leaders felt pressure to show that they were taking charge.Elena, the chief operating officer, looked at the latest report and did what many capable leaders do under strain. She wanted urgency, accountability, and visible follow-through.“I want each unit leader in here this afternoon. If a floor is holding patients too long, I want to know why. And I want targets by Friday.”Marcus, the vice president of operations, had seen this pattern before. A bad week created urgency. A better week brought relief. Neither reaction was producing understanding.Instead of bringing Elena another dashboard, he brought her a control chart. He had plotted six months of emergency department boarding times and discharge completion before noon. Elena studied the page for a moment and asked the obvious question.“So what am I looking at?”Marcus answered without technical jargon.“Not just a trend line. This chart tells us whether we’re looking at the normal voice of the system or a signal that something unusual happened.”That was the turning point. Most of the points were inside the control limits, with no unusual pattern. The process was stable, even though the performance was still not good enough. But two points clearly broke the pattern. Those were signals.Elena leaned in. The weekly swings that had felt dramatic now looked different. Not like a fresh management failure every week, but like one repeating system interrupted twice.“What caused the two signals?”Marcus pointed to specific events. One week reflected a plumbing failure that reduced bed availability. The other reflected a cyberattack drill that slowed admissions and discharge orders. Those were special causes. They deserved investigation. But the larger boarding problem was built into the way the hospital was operating every day.That is the managerial value of the chart. It did not excuse the delays. It clarified the level of action required.Stable did not mean acceptable. It meant predictable under current conditions. Elena was no longer looking at a mystery that changed every week. She was looking at a system that was reliably producing an unsatisfactory result, with two real interruptions layered on top.“So the chart is telling us two things at once,” she said. “Chase the signals. Improve the system.”Exactly.That afternoon’s meeting changed shape. Elena canceled the ranking discussion. Instead, she asked for a review of the two special-cause events and a separate cross-functional look at bed management, discharge timing, transport delays, and nursing handoffs. Over time, genuine disruptions were investigated faster, while chronic system problems became easier to name and improve.That is how the problem began to resolve. The hospital stopped treating every fluctuation as a fresh crisis and started managing patient flow as a system.Why we keep getting this wrongMost of us do not misuse performance data because we are careless. We do it because pressure changes what feels responsible. When a number worsens, we want an explanation immediately. We want to know who owns the problem, what action ...
    Show More Show Less
    7 mins
No reviews yet