『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: Putting out fires

    Five-minute Deming: Putting out fires
    2026/03/11
    Many organizations run on urgency. Something breaks. A customer complains. A deadline slips. Leaders jump in to fix the problem. The system is restored, the crisis passes, and everyone moves on to the next issue. It feels productive. It feels responsible. Sometimes it even feels heroic.But constant firefighting can hide a deeper truth: restoring a system after a problem occurs is not the same as improving it. W. Edwards Deming warned that many organizations stay trapped in cycles of reaction because leaders confuse solving problems with improving the system that creates them.The trap of solving today’s problemsLeaders are trained to respond quickly when problems appear. A delivery runs late. A customer complains. A system breaks. Responsible managers step in, solve the issue, and get operations back on track. In the moment, this feels like effective leadership.But Deming argued that reacting to problems is often only temporary relief. When the same kinds of problems appear again and again, the issue is rarely a single mistake or a careless employee. More often, the system itself is producing the outcomes we see.This is one of the hardest ideas for managers to accept. When an organization is busy and customers need help, stepping back to study the system can feel like the wrong response. Yet without understanding how the system works, leaders may spend years solving the same problems over and over.A small service company illustrates how this cycle unfolds—and how a different way of thinking can finally break it.A business that lived in constant emergenciesCarlos owned a growing neighborhood HVAC service company. Business was strong. Phones rang throughout the day. Trucks were constantly on the road. From the outside, the company looked successful. Inside the office, however, each afternoon felt chaotic.Technicians called needing parts. Customers demanded urgent visits. Jobs ran longer than expected and the carefully planned schedule began to unravel. Dispatchers scrambled to rearrange appointments while Carlos jumped in to solve problems as quickly as they appeared.“Move that install to tomorrow,” he told the dispatcher one afternoon. “Send Mike over to Mrs. Jenkins. I’ll call the supplier and see if we can rush that part.”The day would stabilize. Customers were helped. Emergencies were handled. But the next day looked almost exactly the same. By midweek the technicians were exhausted, dispatchers were frustrated, and Carlos felt like he spent every day racing from one crisis to the next.Eventually he began to notice something important. The emergencies were not random. They followed patterns.Jobs were scheduled too tightly. Some technicians were handling complex repairs before they had enough experience. Parts needed for common repairs were not always available when technicians arrived at a job. None of these problems were unusual events. They were built into the way the system operated.Deming described this distinction clearly in Out of the Crisis: “Putting out fires is not improvement of the process. This only puts the process back to where it should have been in the first place.”Putting out fires is not improvement of the process. This only puts the process back to where it should have been in the first place.— W. Edwards DemingCarlos slowly realized something uncomfortable. His daily heroics were not improving the business. They were simply restoring the system to where it had been before the latest disruption.At the next team meeting he made an unexpected announcement.“We’re not fixing today’s schedule,” he told the group. “We’re studying how our schedule works.”The team began mapping a typical service day. They looked at travel times between neighborhoods. They tracked which types of jobs commonly ran long. They identified repairs that frequently required parts technicians did not carry.Gradually they began changing the system. Service appointments were spaced differently. New technicians received more structured training. Trucks were stocked with the parts most commonly needed for repairs.And over time something surprising happened. The emergencies began to fade. Carlos realized that his technicians had never been the problem.As Deming often reminded leaders: “A bad system will beat a good person every time.”A bad system will beat a good person every time.— W. Edwards DemingOnce the system improved, the daily firefighting that once dominated the company began to disappear.Why leaders keep fighting the same firesMost managers recognize the exhaustion that comes from constant firefighting. Yet many organizations remain trapped in that pattern for years.Part of the reason is psychological. Solving problems feels productive. When a leader steps in and rescues a situation, the result is immediate and visible. Customers are satisfied. The crisis ends. The day is saved.System improvement is different. It requires stepping back. Studying patterns. Slowing down ...
    続きを読む 一部表示
    7 分
  • Five-minute Deming: "Me" vs. "We" thinking

    Five-minute Deming: "Me" vs. "We" thinking
    2026/03/04
    Most organizations assume the path to better performance is straightforward: Motivate individuals. Reward top performers. Rank employees. Offer incentives for beating targets. At first glance, the logic seems sound. If individuals push harder, the organization should perform better.But many leaders eventually discover an unintended consequence. Systems designed to reward individuals often create internal competition that quietly weakens the organization itself. People begin protecting their own results. Information flows more slowly. Cooperation becomes optional instead of natural.W. Edwards Deming warned leaders about this dynamic decades ago. He argued that organizations are not collections of independent performers—they are systems. As Deming explained, “A system is a network of interdependent components that work together to try to accomplish the aim of the system.”A system is a network of interdependent components that work together to try to accomplish the aim of the system.— W. Edwards DemingWhen leaders forget that truth, incentives can pull people apart instead of bringing them together. The shift from “Me” thinking to “We” thinking is often the difference between an organization that struggles internally and one that improves steadily over time.A retail store that learned the differenceKaren owned a small clothing boutique on a busy downtown street. Her store had loyal customers and a hardworking team of associates. Like many business owners, Karen believed motivation was the key to growth. To encourage stronger sales, she introduced commissions and a monthly leaderboard recognizing the store’s top sellers.At first, the results looked promising. Sales increased slightly. Associates competed enthusiastically. The leaderboard created excitement on the sales floor.But slowly, subtle problems began appearing. Customers sometimes waited longer for help even when several employees were nearby. Associates quietly argued about who greeted a shopper first. Employees hesitated to assist customers who were already speaking with another associate.One evening after closing, Karen sat down with her store manager, Miguel.“I thought commissions would motivate everyone,” Karen said. “But lately the store feels tense.”Miguel nodded. “I’ve noticed it too,” he replied. “Everyone’s watching their own numbers. If someone else starts helping a customer, the rest of the team just stays back.”Karen began reviewing the previous three months of store data. Sales had increased slightly. But other indicators were moving in the wrong direction. Returns were rising. Customers were buying fewer items per visit. A few online reviews mentioned inconsistent service.Karen leaned back in her chair. “Maybe we’ve built a system where everyone is competing inside the same store,” she said.Miguel shrugged. “That’s how retail usually works.”Karen paused for a moment. “Maybe that’s the problem.”The moment the system became visibleDeming warned leaders about systems that reward individual competition. “The merit rating nourishes short-term performance, annihilates long-term planning, builds fear, demolishes teamwork, and nourishes rivalry and politics,” he wrote.The merit rating nourishes short-term performance, annihilates long-term planning, builds fear, demolishes teamwork, and nourishes rivalry and politics.— W. Edwards DemingKaren suddenly saw her commission system differently. The leaderboard rewarded individual wins—even when those wins hurt the customer experience or the team. In other words, the system encouraged employees to think “Me” instead of “We”.Rather than reacting quickly, Karen decided to try a small experiment. First, she removed the leaderboard ranking associates against one another. Second, she replaced individual commissions with a shared store bonus tied to overall performance and customer satisfaction. Finally, she changed the question she asked during team meetings. Instead of asking who made the most sales, she began asking something different: “How well did we serve customers together?”Within weeks, Miguel noticed subtle changes across the store. Associates stepped in to help each other without hesitation. Customers were greeted faster. Product knowledge began flowing more freely between employees. The tension that had crept into the store started to fade.And the results followed. Average purchase size increased. Customer reviews improved. Repeat customers returned more often. Sales rose—not because individuals competed harder, but because the system itself worked better.Where managers often get misledWhen results decline, many of us instinctively focus on individuals. We assume people need more motivation, clearer goals, or stronger incentives.But Deming taught that most performance differences come from the system people work within. When we create systems that reward individual victories, people naturally begin protecting their ...
    続きを読む 一部表示
    6 分
  • Five-minute Deming: Innovation

    Five-minute Deming: Innovation
    2026/02/25
    Most leaders say they want more innovation. They ask for ideas, listen closely to customers, and push teams to ship faster. Yet the breakthroughs they’re hoping for rarely arrive. What shows up instead is a steady stream of incremental features—busy, responsive, and oddly unsatisfying.W. Edwards Deming challenged a deeply held assumption behind this pattern: that customers will tell you what to build next. He argued that this belief doesn’t make organizations more innovative. It quietly removes one of management’s most important responsibilities.When customer-driven becomes customer-designedBeing “customer‑driven” sounds unquestionably right. Leaders want to respect customers, respond quickly, and avoid building things nobody asked for. Over time, this mindset becomes embedded in roadmaps, prioritization rituals, and product reviews. Requests are collected, ranked, and delivered with discipline.Deming warned that something subtle is lost in this approach. Customers are experts in their own frustration, but they are not responsible for inventing your future. That work belongs to leadership—using theory, prediction, and learning.Innovation, in Deming’s view, is not a burst of inspiration or a lucky insight. It is management work. And like any other responsibility, it either gets designed and managed—or it slowly degrades into noise.A team that listened—and still missed itBrightwave Software sold workflow tools to mid‑sized operations teams. Internally, the company appeared to be doing everything right. Sprints were predictable. Support tickets were trending down. Feature requests were delivered faster than ever.Still, growth had started to flatten.Alex, the CEO, struggled to reconcile the dashboards with the results. Renewal rates were softening, but no one could explain why. The metrics were green. Customer satisfaction scores were stable. On paper, execution looked strong.“Everything looks healthy,” Alex said during one leadership meeting. “But renewals are flattening, and I can’t connect the dots.”Maria, the head of product, explained the team’s approach. Customer requests drove the roadmap. The most common asks were reviewed quarterly and prioritized carefully.“We’re doing exactly what customers ask for,” she said. “If something were wrong, we’d see it in the data.”That logic felt sound. It was also incomplete.As the leadership team talked, another possibility emerged. What if customers weren’t articulating their next problem because they couldn’t? What if the friction wasn’t tied to any single feature, but to how fragmented the overall experience had become as customers scaled?Instead of gathering more requests, the team articulated a theory. They believed customers were struggling with cognitive load—too many options, too many configuration paths, too much effort to keep work flowing smoothly.They designed a small experiment. One cohort of customers received a simplified, opinionated workflow that removed choices instead of adding them. The team predicted adoption would improve for new users and stall for experienced ones.The results surprised them. New users adopted the workflow quickly. More unexpectedly, experienced users did as well. Reducing choice reduced friction and freed up attention.The breakthrough didn’t come from asking customers what to build. It came from leadership taking responsibility for learning.Deming put it bluntly: “Does the customer invent new product or service? The customer generates nothing.” His point was not to dismiss customers, but to prevent leaders from outsourcing their job.Does the customer invent new product or service?The customer generates nothing.— W. Edwards DemingWhere good intentions quietly derail innovationMost organizations do not struggle with innovation because they ignore customers. They struggle because they confuse listening with leading.When roadmaps are treated as collections of requests, innovation becomes reactive by default. Teams ship faster, but learning slows down. Output increases while insight declines. Over time, the organization becomes very good at responding to yesterday’s problems.We often reinforce this pattern unintentionally. Requests, votes, benchmarks, and competitor features feel objective. They feel safe. They give leaders something concrete to point to when decisions are questioned.Deming put it plainly: “Experience without theory teaches nothing.” Without a clear prediction about how the system will behave, organizations accumulate activity rather than knowledge—and motion gets mistaken for progress.The result is frustration. Teams feel busy but ineffective. Leaders ask for more innovation while maintaining systems that quietly prevent it.Experience without theory teaches nothing.— W. Edwards DemingActionable TakeawaysThere is a more disciplined path forward, and it begins by reclaiming innovation as management work.* Separate customer input from ...
    続きを読む 一部表示
    7 分
まだレビューはありません