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
  • 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 ...
    Show More Show Less
    10 mins
  • 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 ...
    Show More Show Less
    8 mins
  • Five-minute Deming: "Common sense"

    Five-minute Deming: "Common sense"
    Mar 25 2026
    In many organizations, the phrase “use common sense” sounds perfectly reasonable. A mistake happens, a customer complains, or a process fails, and the instinctive response is to remind people to slow down and think.But this familiar management reflex can quietly prevent improvement. When leaders rely on “common sense” explanations, they often focus on the individual closest to the problem instead of the system that produced it.W. Edwards Deming warned that this habit does more than miss the cause—it can keep organizations trapped in the very patterns they are trying to fix.Why “common sense” fails in managementMost managers have experienced the moment when something goes wrong. A customer receives the wrong order, an appointment is missed, or a deadline slips by.The explanation appears obvious: someone made a mistake. Our instinct is to correct the person involved—remind them to be careful, encourage better judgment, or send a note to the team about paying closer attention.These responses feel practical because work is done by people. But Deming argued that most recurring problems do not originate with individual effort or attention.They are produced by the way work is designed—the methods, priorities, handoffs, and pressures that shape everyday decisions. When leaders overlook that reality, the same cycle repeats: correct the person, see temporary improvement, and then watch the problem return.A small service company illustrates how easily this pattern develops—and what changes when a leader begins looking at the system instead.A scheduling problem that kept returningMaria owns a home services company that schedules technicians for repairs and installations across her city.Over several months, customer complaints began to increase. Appointments were occasionally missed, technicians sometimes arrived without the right parts, and a few customers reported waiting all day for a visit that never appeared on the schedule.One afternoon a customer called after waiting five hours for a technician who never arrived. Maria reviewed the call recording and quickly discovered the problem: the job had been placed into the wrong time slot.It looked like a simple scheduling error.Later that day she spoke with her operations supervisor, David.“This one should have been obvious,” Maria said. “People just need to slow down and use some common sense when they’re entering these jobs.”David agreed the mistake appeared straightforward, and the team reminded dispatchers to double-check their entries. For a short time the complaints seemed to ease.But two weeks later another scheduling problem surfaced. Then another.While reviewing scheduling logs, David noticed something unusual. The same type of error appeared across different dispatchers and across different shifts. It did not look like one employee being careless.The team began examining the scheduling process itself. Service requests arrived through phone calls, website forms, and callbacks from technicians in the field.The information customers provided varied widely, and dispatchers often had to guess which technician should handle a job. At the same time they were expected to answer calls quickly while entering appointments into the system.During busy periods dispatchers were juggling two demands at once: respond to customers immediately and figure out incomplete job details. The errors appeared most often when call volume spiked and dispatchers rushed to keep up.Deming described this common management reaction in The New Economics: “Common sense [mistakenly] tells us to speak to the operator about it when a customer reports something wrong with a product or with a service. ‘We have spoken to the operator about it; it won’t happen again.’”Common sense [mistakenly] tells us to speak to the operator about it when a customer reports something wrong with a product or with a service. ‘We have spoken to the operator about it; it won’t happen again.’— W. Edwards DemingMaria realized her earlier response had followed exactly that pattern. She corrected the person closest to the problem while leaving the process unchanged.The team redesigned the scheduling system. They standardized intake questions so dispatchers received consistent information, clarified which technician handled each type of job, and adjusted call targets so dispatchers were not forced to rush scheduling decisions.Within weeks the number of scheduling problems began to fall—not because employees suddenly became more attentive, but because the system guiding their work had improved.As Deming wrote: “Action taken today may only produce more mistakes tomorrow. It may be important to work on the process that produced the fault, not on him that delivered it.”Action taken today may only produce more mistakes tomorrow. It may be important to work on the process that produced the fault, not on him that delivered it.— W. Edwards DemingWhy leaders blame people ...
    Show More Show Less
    7 mins
  • Five-minute Deming: Annual performance reviews

    Five-minute Deming: Annual performance reviews
    Mar 18 2026
    Most organizations rely on annual performance reviews to evaluate contribution, allocate rewards, and create accountability. The logic feels straightforward: measure results, rate people, and recognize the strongest performers. For decades, this ritual has been treated as a basic tool of management.But what if the very practice meant to improve performance quietly prevents real improvement from happening?W. Edwards Deming believed annual performance reviews were not merely ineffective. He argued they were one of the most damaging management practices in modern organizations because they direct leadership attention toward judging individuals instead of improving the system that produces results.To understand why, we have to rethink what actually creates performance in the first place.Why Deming challenged performance appraisalsLeaders want to understand how well their organizations are performing. That instinct is healthy; good leadership requires visibility into results and a clear understanding of where improvement is needed.Annual performance reviews promise a structured way to do this. They compress a year of work into scores, ratings, and rankings that guide compensation, promotion, and recognition.But Deming argued that this approach misunderstands how organizations actually produce results. He wrote: “Basically, what is wrong is that the performance appraisal or merit rating focuses on the end product, at the end of the stream, not on leadership to help people.”Basically, what is wrong is that the performance appraisal or merit rating focuses on the end product, at the end of the stream, not on leadership to help people.— W. Edwards DemingIn other words, reviews judge outcomes after the work is finished rather than improving the conditions that produce those outcomes in the first place. This difference—between judging results and improving the system that creates them—sits at the heart of Deming’s philosophy of management.To see how this dynamic unfolds in practice, consider the experience of a school district wrestling with teacher evaluations.A school district confronts the problemIn the Brookfield School District, evaluation season arrived every spring with predictable tension.Teachers prepared documentation of their work while principals conducted classroom observations. District administrators compared performance scores across schools, and those numbers shaped pay increases, promotions, and professional reputations.Marcus Lee, principal of Brookfield Middle School, had participated in the process for years, and each cycle followed the same pattern. Teachers worried about their scores, principals debated ratings, and district leaders reviewed charts comparing one school to another.Yet the classrooms themselves seemed to change very little.During a district leadership meeting, Marcus raised the concern with Superintendent Elena Ramirez.“We keep having the same conversations,” he explained. “We review the ratings, we talk about who did well and who didn’t. But the classrooms themselves aren’t improving much.”Ramirez understood the frustration, but she also saw the system as necessary.“The reviews help us identify our strongest teachers,” she said. “Without them, how do we know who is performing well?”Marcus paused before answering.“That’s the problem,” he replied. “We think the scores explain performance. But most of the time they reflect the conditions teachers are working in.”He pointed to several examples. Some teachers had consistent collaboration time with colleagues, while others rarely had time to work together. Some classrooms included far more complex student needs, and others had significantly more curriculum support.The more Marcus studied the situation, the more he saw a pattern emerging.As evaluation season approached, teachers became cautious. Collaboration slowed, and fewer people experimented with new lesson ideas because trying something new carried personal risk when results were judged individually.The system was doing exactly what it was designed to do: judge individuals.But something else was happening as well. Teachers began protecting their own standing rather than sharing openly, and leaders spent hours debating scores instead of studying the conditions shaping learning—curriculum support, scheduling, classroom composition, and collaboration time.Slowly, the conversation shifted away from improving teaching and toward explaining ratings.Deming warned about this dynamic decades ago: “Merit rating rewards people that do well in the system. It does not reward attempts to improve the system.”Merit rating rewards people that do well in the system.It does not reward attempts to improve the system.— W. Edwards DemingThat comment stayed with Ramirez after the meeting. If the ratings were not revealing true performance, what should leadership be studying instead?The answer emerged as district leaders began examining the system ...
    Show More Show Less
    8 mins
  • Five-minute Deming: Putting out fires

    Five-minute Deming: Putting out fires
    Mar 11 2026
    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 ...
    Show More Show Less
    7 mins