26.262 - Let Consequences Revise the Method

September 2026WisdomReflective Practice
Written By YC

“In other words, there must be a method to achieve an aim. By what method?”

W. Edwards Deming, The New Economics for Industry, Government, Education, second edition (2000), p. 41. Excerpt reproduced by the W. Edwards Deming Institute.

🧭🔄📊

The line got shorter. The question was who could still join it.

W. Edwards Deming, a statistician and management thinker, asked organizations to examine the systems behind their results. Deming did not regard an admirable aim or an impressive target as a workable method. His question, “By what method?”, appears in an argument about demanding numerical improvement without providing the means and resources to achieve it.

Consider an illustrative community-service center that moves appointments online to reduce waiting. Visitors with booked appointments spend less time in line. That improvement is real. Yet the people who cannot complete an online booking may never enter the calculation. Deming's question becomes sharper when the desired result is not simply a shorter wait for those admitted, but useful service that people can reach. What happens when a good intention reaches some people by closing a route used by others?

The Shorter Line Has an Entrance

On the illustrative center's dashboard, the recorded waiting time for visitors who arrive with bookings falls. The online form assigns time slots and spreads demand across the day. Staff had wanted to spare visitors a long, uncertain wait. The chart suggests that, for people who secured a slot, they have.

The manager has every reason to be pleased. A shorter wait means less time away from work, fewer crowded hours, and a more predictable visit for those who successfully book. Someone proposed a useful change, and a relevant measure moved in the hoped-for direction. The number deserves to be taken seriously.

At the front desk, a different account begins to accumulate. A visitor says the form stopped before confirming a slot. Another comes back because the required device was not available the first time. A staff member notices people asking how to make an appointment after walk-in scheduling has ended. Reports like these need checking; they do not establish that the booking change caused every difficulty. But they ask a question the wait-time dashboard cannot answer.

Who is included in its average?

The dashboard measures how long successfully booked visitors waited. It may report that experience accurately. A person who attempted to book and gave up has no completed appointment to time. A person who returned twice before securing a slot appears, if at all, only when the final visit succeeds. The shorter line can be both a genuine benefit for one group and an incomplete description of access to the service.

This is more precise than saying the metric is bad. Improvement guidance distinguishes outcome measures, which track a desired result, from process measures, which track whether a step works as intended, and balancing measures, which check whether a gain creates a burden elsewhere. The manager could keep measuring booked-visitor wait time while also examining whether attempted bookings become appointments and whether the new process shifts work onto visitors or staff. Institute for Healthcare Improvement

The RE-AIM framework calls another part of the question reach: how many eligible people participate, which people do, and who does not. Its developers urge attention to eligible nonparticipants and reasons for not participating. For the center, even obtaining a trustworthy count of people who tried but did not complete the form may take work. Front-desk accounts are a reason to investigate that boundary, not a ready-made denominator or proof of cause. Glasgow et al., 1999; RE-AIM Reach

A result can be truthful and still be too narrow for the promise attached to it. When a measure improves, ask not only what changed within its frame but who had to get inside that frame to be seen.

The problem is not necessarily that the measure lies. It may tell the truth about the people who made it into the measure.

Loyalty to the Aim Can Look Like Changing the Plan

The manager's goal was not to make a dashboard look good. It was to make service easier to use. Online scheduling was one proposed way to pursue that goal, and shorter booked-visitor waits suggest part of the proposal worked. Nothing about a reported barrier requires the manager to disown the original concern or declare the whole system a failure.

It does require separating five things that are easy to treat as one. The value is fair access to useful service. The strategy is an orderly schedule with shorter waits. The action is asking people to secure appointments online. The signal on the dashboard is waiting time after a booking succeeds. The reported consequence is friction for some visitors before a booked wait can begin. When these become interchangeable, changing the action can feel like betraying the value, even if that action may be keeping the value from reaching some people.

Suppose the manager says, “We cannot afford to return to open-ended walk-ins.” That may be a serious constraint. Reopening the old line might restore one access route while recreating an hours-long wait or overwhelming a small team. The choice is not between defending an online-only form forever and discarding scheduled appointments altogether. It may be possible to preserve the schedule while providing assisted booking by phone or at the desk, or to authorize an alternative route when a person cannot complete the form. Each option has costs, staffing implications, and possible risks of its own. Those implications belong in the decision rather than in an unexamined refusal to change.

Having built a method can make revising it uncomfortable. There may also be good operational reasons to keep part of it while investigating a complaint. Still, prior effort is not, by itself, evidence that the method continues to serve its aim.

Deming's Plan-Do-Study-Act cycle offers a different posture. State what you expect a change to improve, make a bounded change, compare what occurred with the prediction, and use what you learn to decide the next action. Study asks more than “Did our favorite number improve?” It asks what else changed, whether the prediction holds across the relevant people and conditions, and what theory of the system now needs revision. W. Edwards Deming Institute

Study also guards against a different error: rebuilding a process every time a number wiggles. Variation, other concurrent changes, and incomplete information matter. A surprising report calls for investigation and, when needed, protection. It does not automatically prove that every feature of the method is wrong. Equally, a series of stable booked wait times cannot settle an access concern that the measure never captured.

The better question for the manager is not “Was the online form a mistake?” It is “What method, within our real constraints, now has the best chance of delivering the value we said we cared about?”

Changing a route can be a stronger expression of the destination than defending the route that missed it.

Keep the North, Redraw the Route

The manager asks the booking lead and front-desk staff to describe where a visitor's path stops. They review available form errors and invite people who have encountered barriers to share only what they wish to share through an accessible, safe channel. No one visitor is asked to represent all visitors. Staff accounts and partial records give the team hypotheses, not a causal verdict.

They propose a limited assisted-booking route by phone and at the front desk alongside the online form. The booking lead owns the test; the manager authorizes a defined number of staff hours and clarifies what information an employee may collect, how to protect it, and when an exception must be escalated. The team predicts that people unable to complete the form unaided will be more likely to obtain an appointment without restoring the old long wait.

Then they specify what would challenge that prediction. The online system's booked-visitor wait time remains visible. For a proposed two-week observation window, the team also checks attempted appointments, reports of turnaways or repeat visits, and the time needed to help someone book. An increase in secured appointments would not settle the matter if the front desk fell behind or callers waited so long to request a slot that the delay had merely changed address. Where counts are incomplete, the team says so. It sets the review date before the test begins, and staff and visitors who supplied feedback are told what will be examined and when they can expect an update.

This is not a fictional success story. The assisted route might improve access, might relocate delay to the phone, or might require more staffing than the center can sustain. Some visitors may need a different accommodation altogether. At the review, the manager can retain the change, adapt it, add resources, or explain why another route is needed. The decision should be based on the fuller pattern, not merely on whether the original dashboard remains green.

If a barrier creates an immediate safety, rights, or discrimination concern, the center should use its appropriate protective and formal processes now. People should not be asked to wait for a small experiment to confirm whether they deserve access. A reflective improvement cycle is not an excuse to defer protection.

The four steps are distinct: a consequence was heard; a method was changed; the result was measured again; improvement remains to be demonstrated. Skipping the final distinction turns a promising repair into a new assumption. Closing the loop with affected people, including those who could not enter the original metric, is part of knowing whether the aim has become more reachable.

The sustainable version of the method matters too. An access route that works only by quietly exhausting staff is not a completed repair. A balancing signal helps the team see whether the correction can keep working for the people who must operate it.

A compass is not proof that the chosen road is passable.

🧭🔄📊

Practice: The Value-Method-Impact Review

Choose one routine, rule, or process you influence that has produced an unexpected result. Keep it specific and non-emergency. You do not need perfect data to name a question, but do not turn one report into a settled diagnosis. Use these six fields to prepare one feasible revision or proposal, with the person who has authority to carry it forward and a date to revisit the result.

1. Value: What good is this process meant to protect or make possible? State the value without naming the current method as though it were the value.

Prompt: “The value I am trying to serve is __________.”

2. Intended Effect: What did you expect the current method to change, for whom, and through which step? Name the method separately.

Prompt: “We chose __________ because we expected __________ for __________.”

3. Observed Effect: What happened, according to what you can actually observe? Note one benefit and one possible cost, and mark what you have not yet established.

Prompt: “We observed __________. We have a reason to investigate __________, but do not yet know __________.”

4. People Affected: Who benefits, who encounters friction, and who might never appear in the current measure? Seek another vantage point without assuming one person's account represents a whole group. Choose a safe, accessible way to ask; do not demand repeated uncompensated proof from people bearing the cost.

Prompt: “The current measure includes __________ and may miss __________. A safe way to learn more is __________.”

5. Change: Name one bounded alteration, the person who can authorize it, and the resources or safeguards it requires. If the change is outside your authority, make it a proposal with an honest route to the decision-maker.

Prompt: “We can test or propose __________. The owner is __________. The required support or safeguard is __________.”

6. Signal: What result would show progress toward the value, and what balancing signal would show whether the change transfers a burden? Set a review date and state what would make you reconsider the method.

Prompt: “We will look for __________ while checking __________. We will review this by __________ and reconsider if __________.”

Treat this Practice as a reflection and planning tool, not a validated measure or a causal test. If the consequence involves safety, rights, discrimination, or another serious risk, use appropriate protective, reporting, and qualified professional processes without waiting for an informal pilot.

Learn moreThe Value Method Impact Review worksheet

Scientific Summary

Deming argued that an aim needs a method and resources; his Plan-Do-Study-Act framework organizes a prediction, a bounded test, examination of what happened, and a decision informed by learning. This is guidance for studying systems, not evidence that a particular booking change improves access. His work on variation also cautions against treating every fluctuation as a signal to redesign a process. Deming, 2000; Deming Institute, PDSA

The Institute for Healthcare Improvement distinguishes outcome, process, and balancing measures. That distinction can help a team pair a desired result with evidence about the steps delivering it and burdens the change may create elsewhere. Its guidance comes from healthcare improvement, and our community-center application is an analogy. Glasgow and colleagues' RE-AIM framework adds reach, which concerns participation among eligible people and the representativeness of those who participate. Counting nonparticipants or understanding why they are missing may be difficult, but a measure defined only around successful visits cannot answer an access question on its own. The original RE-AIM publication offers an evaluation framework, not an experiment on online appointments. IHI, Establishing Measures; Glasgow et al., 1999; RE-AIM Reach

Proctor and colleagues distinguish outcomes of implementing a process, including adoption and feasibility, from outcomes of the service itself. This conceptual distinction warns against equating a smoothly operated online form with fair access to help; it does not establish that such a form is harmful. In a systematic review of healthcare reports, Taylor and colleagues found that many articles did not document PDSA cycles sufficiently to appraise their application, and only a minority fully reported iterative sequences. Naming an improvement cycle is not the same as carrying it out carefully. The review does not establish the cycle's efficacy in every setting. Proctor et al., 2011; Taylor et al., 2014

Staw's 1976 laboratory experiment asked 240 undergraduates to make hypothetical financial allocations. Participants who had been personally responsible for an earlier choice and received adverse feedback committed more resources to it than participants in other conditions. It suggests one possible difficulty in revising a personally owned method, not a universal response or an explanation of the illustrative manager's motives. The community-center scene and six-field Practice are editorial examples, not observed cases, validated interventions, or proof of cause and effect. Reports of barriers, a before-and-after wait-time comparison, and even a successful small pilot can be influenced by variation, selection, and concurrent changes. The defensible invitation is to keep an honest aim, examine what the method delivers to whom, make an accountable change where warranted, and study whether the fuller consequence is actually better. Staw, 1976


Bibliography

Legal Disclaimer: The content published on Lucivara is provided for informational, educational, and reflective purposes only and is not intended to constitute medical, psychological, legal, or professional advice. Lucivara does not diagnose conditions, prescribe treatments, or provide therapeutic or professional services. Readers are encouraged to consult qualified professionals regarding any personal, medical, psychological, or legal concerns. Use of this content is at the reader’s own discretion and risk. Copyright Notice: © 2026 Lucivara. All rights reserved. This content is protected by copyright laws and is intended for individual, personal, and non-commercial use only. No part of this publication may be reproduced, distributed, transmitted, displayed, published, or broadcast in any form or by any means without prior written permission from Lucivara. Acceptable Use: The content published on Lucivara is intended for individual, personal, and non-commercial use only. Readers may access, read, and engage with the content for their own reflective, educational, or informational purposes. Except for such ordinary human use, no portion of this content may be copied, reproduced, redistributed, republished, transmitted, stored, scraped, extracted, indexed, modified, translated, summarized, adapted, or incorporated into derivative works without prior written permission from Lucivara. This restriction expressly includes, without limitation, the use of Lucivara content for training, fine-tuning, prompting, testing, benchmarking, or operating artificial intelligence systems, machine learning models, automated agents, bots, or any other computational or data-driven systems, whether commercial or non-commercial. By accessing or using this site, readers acknowledge and agree to Lucivara’s Terms and Conditions.

YC
Next

26.261 - What Your Position Prevents You From Seeing