• 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
    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
    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 分
  • Five-minute Deming: Profit
    2026/04/22
    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...
    続きを読む 一部表示
    9 分
  • Five-minute Deming: Control charts
    2026/04/15
    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 ...
    続きを読む 一部表示
    7 分
  • Five-minute Deming: Plan-Do-Study-Act
    2026/04/08
    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 ...
    続きを読む 一部表示
    10 分
  • Five-minute Deming: Quality before inspection
    2026/04/01
    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 ...
    続きを読む 一部表示
    8 分
  • Five-minute Deming: "Common sense"
    2026/03/25
    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 ...
    続きを読む 一部表示
    7 分