『The Knowledge System Podcast』のカバーアート

The Knowledge System Podcast

The Knowledge System Podcast

著者： Michael Carr
無料で聴く

概要

 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 マネジメント マネジメント・リーダーシップ 経済学
エピソード
  • Five-minute Deming: Intrinsic motivation

    Five-minute Deming: Intrinsic motivation
    2026/05/13
    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 performanceIt 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 DemingNorthstar Clinics shows how easily a reasonable performance idea can become a barrier to better work.The score was not the same as the workNorthstar 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 DemingSecurity 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. ...
    続きを読む 一部表示
    8 分
  • Five-minute Deming: Zero defects

    Five-minute Deming: Zero defects
    2026/05/06
    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 usW. 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 FlowNorthstar 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 DemingOnce 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 trappedMost 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...
    続きを読む 一部表示
    8 分
  • Five-minute Deming: Employee retention

    Five-minute Deming: Employee retention
    2026/04/29
    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 ...
    続きを読む 一部表示
    8 分
adbl_web_anon_alc_button_suppression_c
まだレビューはありません