Couverture de The Knowledge System Podcast

The Knowledge System Podcast

The Knowledge System Podcast

De : Michael Carr
Écouter gratuitement

À propos de ce contenu audio

 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 Economie Management Management et direction
Épisodes
  • 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 ...
    Afficher plus Afficher moins
    7 min
  • Five-minute Deming: Plan-Do-Study-Act

    Five-minute Deming: Plan-Do-Study-Act
    Apr 8 2026
    Many management teams are praised for speed. They launch new initiatives and talk about momentum as if motion itself were evidence of progress. But fast action without disciplined learning creates a different problem: we spread assumptions through the system before we know whether they are sound.That is why W. Edwards Deming’s Plan-Do-Study-Act matters. It gives leaders a way to slow down certainty without slowing down improvement. In the long run, it produces better service, lower waste, and a steadier reputation.Why leaders need more than a pilotPlan-Do-Study-Act (PDSA) is often described as an improvement cycle. That is true, but it can sound smaller than Deming intended. PDSA is a way to connect theory, prediction, action, and learning.Plan means more than choosing an idea. It means stating what you think is happening, what change you want to test, and what you predict will follow. Do means carrying out that test, usually on a limited scale. Study means comparing the result with the prediction and taking surprises seriously. Act means deciding whether to adopt the change, abandon it, or run another cycle with a better theory.Deming put the underlying point simply: “Management in any form is prediction.”Management in any form is prediction.— W. Edwards DemingThat is what many change efforts skip. We move from concern to action without ever being clear about the theory behind the action. Then we mistake activity for learning, or a short-term result for proof.A story from commercial property management makes the problem easy to see.What Harbor Point learned by slowing downAt Harbor Point Property Group, the executive team was under pressure. Tenants in three downtown office buildings were complaining about slow maintenance work, repeat visits, and weak communication from the service desk. Renewal season was approaching, and nobody wanted owners asking why routine service felt unreliable.Claire, the head of operations, opened a Monday meeting with a familiar managerial move. She wanted speed, clarity, and a visible response.“We need faster resolution times. I want every building manager under four hours for routine maintenance requests by next month.”It sounded decisive. Complaints were rising. The pressure to look responsive was real.But Jordan, the regional operations director, had spent the previous week reading work-order notes from the buildings. He saw something Claire’s demand did not explain. Some tickets stayed open too long. Others were closed quickly, then reopened. Vendor dispatches were inconsistent. Tenant descriptions were often incomplete. The pattern looked messy, not simple.When Claire pressed him, Jordan answered with the line that changed the meeting.“I think we know the symptom. I’m not sure we know the problem yet.”That was the turning point. Instead of accepting a broad portfolio-wide push for faster close times, Jordan proposed a PDSA cycle. One building. One category of request. Two weeks. Plumbing calls in Franklin Tower only.“Two weeks feels slow,” Claire said.“Only if we confuse motion with learning,” Jordan replied.This was the Plan stage, and he made it concrete. The service desk would ask three new intake questions before dispatching a plumber. Building staff would classify each request by severity. Vendors would receive tighter work orders with tenant access details and photos when available. Jordan’s prediction was clear: first-visit completion would improve, repeat visits would fall, and tenant updates would improve even if average close time did not improve right away.That kind of planning is not paperwork.It is disciplined thinking.As Deming wrote: “Step 1 [Plan] is the foundation of the whole cycle.”Step 1 [Plan] is the foundation of the whole cycle.— W. Edwards DemingThe Do stage followed. For two weeks, Franklin Tower used the revised intake method only for plumbing calls. The service desk logged the new questions. Building staff tagged urgency consistently. Jordan reviewed requests daily to make sure the test was being carried out as planned.Then came Study. The headline result was mixed. Average close time improved only slightly. If Harbor Point had judged the test by a single visible metric, the effort might have been dismissed as disappointing.But the rest of the evidence told a more useful story. First-visit completion improved sharply. Repeat visits fell. Complaints about poor communication dropped. And one surprise stood out: the biggest delays were not coming from the plumbers. They were coming from incomplete tenant access information and late approvals for after-hours entry.Claire saw it immediately. The dispatch script had helped, but not in the way they first expected.“Right,” Jordan said. “We learned more than whether the average moved. We learned where the friction actually is.”That answer captured the real value of the cycle.That led to Act. Harbor Point kept the stronger intake questions, added a clearer ...
    Afficher plus Afficher moins
    10 min
  • Five-minute Deming: Quality before inspection

    Five-minute Deming: Quality before inspection
    Apr 1 2026
    Many leaders think inspection is what protects quality. If defects slip through, the answer seems obvious: add another check, another review, another pair of eyes at the end. It feels careful. It feels responsible.But that habit can quietly raise cost, normalize rework, and keep management from seeing the deeper problem. The real issue is not what we catch at the end. It is what our system keeps producing in the first place.The management trapOne of the easiest mistakes in management is to confuse detection with improvement. When something goes wrong, we naturally look for a way to catch it sooner, sort it faster, or keep it from reaching the customer. That instinct is understandable. It is also incomplete.A company can become very good at finding defects and still remain trapped in a weak process that keeps making them. W. Edwards Deming said it plainly: “[Using] inspection to improve quality is too late, ineffective, costly.”[Using] inspection to improve quality is too late, ineffective, costly.— W. Edwards DemingThe force of that statement is easy to miss. He was not arguing against all inspection. He was arguing against the belief that inspection is where quality is achieved.Quality is shaped upstream, in design, methods, training, maintenance, scheduling, and in the way management coordinates the whole system.To see how easily leaders drift into the opposite habit, consider a small manufacturer that had become highly disciplined at catching defects and surprisingly tolerant of producing them.A small manufacturer, a familiar patternHartwell Fixtures made custom metal display racks for local retailers. It was a solid Main Street manufacturer with a good reputation and steady orders. Elena, the owner, took pride in the fact that every rack was inspected before shipment.From a distance, that looked like discipline.On the floor, it looked different.Welds were sometimes rough. Powder coating occasionally bubbled. Mounting holes did not always line up. None of those issues alone threatened the business. But together, they created a constant drag on the work. Final inspection kept finding defects, and rework kept absorbing time, attention, and overtime.When a shipment was late for the third time in a month, Elena walked into inspection and saw what had gradually become normal: carts full of rework, operators waiting for decisions, and inspectors arguing over borderline pieces.“What’s the fastest way to get this back under control?” she asked.Marcus, her operations manager, answered with the logic the company had been living inside for months.“We are catching most of the bad units,” he said. “If we add one more inspector on second shift, we can clear the backlog.”That answer was practical. It was also revealing.More inspection had already been the answer for months. Yet the backlog remained. Scrap was up. Overtime was up. Customers were becoming less patient. Hartwell was not dealing with a few isolated mistakes. It was operating inside a predictable system.Later that day, Elena and Marcus looked at the recurring defects together. One week the problem centered on drilling. Another week it was coating. Another week it was warped tubing from a supplier. The pattern moved around, but the burden stayed in the same place: at the end, where the company tried to sort, repair, and rescue what the system had already produced.Deming captured that logic memorably: “Our system of make-and-inspect, if applied to making toast, would be expressed: ‘You burn, I’ll scrape.’”Our system of make-and-inspect, if applied to making toast, would be expressed: ‘You burn, I’ll scrape.’— W. Edwards DemingThat was Hartwell’s system in miniature. Make the rack. Find the defect. Grind it. Redrill it. Recoat it. Expedite it. Apologize for it. At some point, the company had confused recovery with quality.That realization changed the conversation.“If inspection is our main defense,” Elena said, “then we are planning to make defects.”“Then where do we start,” Marcus asked, “if not at the end?”Instead of asking how to strengthen the inspection wall, Elena and Marcus started tracing the defects upstream. They found fixture wear at the drilling station. They reviewed variation in incoming tubing from one supplier. They discovered that a setup shortcut had become normal on busy days. They also saw coating problems rise when rushed scheduling changes caused parts to sit too long between steps.Inspection did not disappear. But it changed purpose. It became feedback about the process, not the company’s main theory of quality.Marcus began tracking defect patterns to learn where the system was unstable. Supervisors stopped treating rework totals as proof that quality control was working. Elena stopped celebrating heroic saves that depended on overtime and last-minute sorting.The result was not perfection overnight. Some defects still appeared. But rework began to shrink. Lead times became ...
    Afficher plus Afficher moins
    8 min
Aucun commentaire pour le moment