Using Scout Mindset to enhance PDSA Cycle

What each one is actually for

Scout Mindset

Scout Mindset, a term from Julia Galef's writing on reasoning, describes a specific stance you take toward your own beliefs: instead of asking a belief to win an argument, you ask it to survive an honest search for the evidence that would kill it. In practice this looks like naming, in advance, what result would make you change your mind, then actually going looking for that result instead of only the result that would confirm you were right. A scout checking territory for an army does not report only the safe routes; they report the ambush too, even when it means the mission has to change. The mechanism is the willingness to look, deliberately, for the thing you would least want to find.

PDSA Cycle

The PDSA Cycle, developed for quality-improvement work and often credited to W. Edwards Deming, is a loop for testing a change on a small scale before committing to it everywhere. Plan: state exactly what you are changing and, crucially, write down what you predict will happen if it works. Do: run the change, on a small enough scale that being wrong costs little. Study: compare what actually happened against the prediction you wrote down in the Plan step, not against a vague sense of whether things feel better. Act: based on that comparison, adopt the change, adjust it, or abandon it, then decide whether to run another cycle. The mechanism is the prediction — writing it down before you know the answer is what turns the Study step into a real check rather than a story you tell afterward.

What you get out of pairing them

Scout Mindset earns you clean information you would otherwise lose to your own investment in being right, which matters most exactly when you have put in the work of running a PDSA cycle and now have something to protect. PDSA earns Scout Mindset a place to land — a written prediction, made before the outcome is known, that turns whether you actually held a belief accountable from a private, fuzzy question into a comparison you can run: this number, against that number, decided in advance. Neither habit does much alone against the specific failure of a person grading their own homework after they already know the grade they wanted. Put them in the same loop, and the prediction gives the scout something concrete to check, and the scout's willingness to be wrong gives the prediction a fair reading instead of a flattering one.

What Scout Mindset rests on

• Self distancing improves judgment randomised trials
  Evaluating a situation from a distanced, third-person vantage point instead of an immersed first-person one improves the quality of judgment about it.
• Actively seeking disconfirmation improves accuracy observational studies
  Deliberately searching for evidence that would prove a belief wrong rather than only confirming evidence produces beliefs that track reality more accurately.
• Curiosity eases belief updating practitioner report
  Treating being wrong as interesting rather than threatening increases willingness to update beliefs when new evidence appears.

What PDSA Cycle rests on

• Feedback against prediction corrects belief plausible mechanism
  Comparing the actual result of a change against the predicted result before adopting it corrects mistaken beliefs faster than adopting or rejecting changes based on intuition alone.
• Small scale testing precedes scaling observational studies
  Running a change through a small planned test cycle before wider adoption reveals real-world effects while limiting the risk of being wrong.

Where they actually meet

Both practices refuse to let the person who wants a result be the only judge of whether it happened. Scout Mindset does this by making disconfirmation a target you go looking for on purpose, not an accident you hope to stumble into. PDSA does the identical thing structurally, by forcing a prediction onto paper before the data exists to argue with it, so the Study step compares two fixed things rather than one fixed thing against a memory that can quietly reshape itself. Different material — a general belief in one case, a specific forecast about one change in the other — but the same underlying refusal: no grading your own test after you have already seen how it feels to pass.

The principle underneath both

A person who only looks for evidence that confirms what they hoped is true will find it almost every time, whether or not the hope was accurate, because confirming evidence is nearly always available if you are not also looking at what would count against you. Deliberately searching for the disconfirming evidence, or fixing your prediction before the outcome exists to bias your memory of it, is what breaks that failure. It is not more effort in general; it is effort aimed specifically at the evidence that could prove you wrong, which is the only kind of evidence that actually updates an inaccurate belief.

What that makes the real goal

If that is the mechanism, the goal both practices are chasing is a belief that has actually been tested against reality rather than one that merely feels earned. Scout Mindset tests a belief by hunting for what would break it; PDSA tests a specific change by comparing it against a prediction made in advance. Either way, the target is the same: a conclusion you can trust because it survived a real attempt to disprove it, not because it was the conclusion you wanted.

Other practices that serve the same goal

Structured Analytic Techniques used in intelligence analysis, particularly Analysis of Competing Hypotheses, chase the identical target from a different direction: an analyst lists every plausible explanation for the evidence, including the ones they find personally unappealing, and systematically looks for evidence that would rule each one out rather than building a case for a preferred conclusion, a method with a documented track record of catching analytic bias that unstructured judgment misses. Forecasting tournaments in the tradition of Philip Tetlock's research on political and economic prediction pursue it through calibration training and scorekeeping — forecasters who track their own hit rate against explicit numeric predictions over time become measurably more accurate than those who reason from confidence alone, a randomized and observationally replicated finding. A team premortem, where a group imagines a project has already failed and works backward to explain why before it starts, aims at the same target by front-loading the disconfirming search to a point before ego is attached to a specific outcome.

A tradition that already does this

Analysis of Competing Hypotheses itself, developed by CIA veteran Richards Heuer in the 1970s specifically to counter analysts' tendency to lock onto an early hypothesis and then read incoming evidence as support for it, is close to a direct precedent for pairing the two moves here: it forces analysts to write down what each hypothesis predicts before new evidence arrives, the same structural trick PDSA uses, and it scores hypotheses by how well they survive attempts to disconfirm them, the same stance Scout Mindset asks of an individual belief. The pairing proposed here is closer to a rediscovery of an existing method than an invention.

Using Scout Mindset to enhance PDSA Cycle

Most PDSA cycles die quietly in the Study step, not because the prediction was wrong but because the person running the cycle already knows, by the time Study arrives, which answer they want the data to give — usually the one that justifies the time already spent in Do. Bring Scout Mindset into Study specifically by writing a second line next to your original prediction, before you look at the result: here is the result that would make me kill this change. Then look at the actual number against both lines, not just the one you hoped would win. If you find yourself explaining away a result that matches your kill line — the numbers are off because of X — that explaining-away is the exact moment Scout Mindset is built to interrupt: ask whether you would accept that same explanation from someone else's data pointing the other way. If the honest answer is no, the change fails, however much work went into it.

Using PDSA Cycle to enhance Scout Mindset

Scout Mindset can stay comfortably abstract — a general commitment to being open-minded that never actually costs you anything, because it is never checked against a specific, falsifiable claim. PDSA's Plan step fixes that by forcing a belief you hold generally into a small, testable version with a written prediction attached. If you believe, in general, that you communicate clearly under pressure, do not just resolve to seek disconfirming evidence about it in the abstract; run a specific small test — record your own explanation of a decision to a colleague, predict in writing whether they can repeat it back accurately, then actually check. The general commitment to updating on evidence becomes a specific loop with a real answer at the end of it, which is where Scout Mindset stops being a personality trait you claim and starts being a habit you can point to instances of.

Wednesday afternoon, the numbers from your new onboarding flow

You changed the sign-up flow three weeks ago, wrote down a prediction that completion would rise from sixty to seventy percent, and now the dashboard says sixty-three. Sixty-three feels close enough to call a win, and you have already drafted, in your head, the sentence you will say in the team update: early signs are positive. Before you send it, you go back to the line you wrote in the Plan step, the one where you specified in advance what result would count as the change not working — anything under sixty-eight. Sixty-three is under that line. You notice the pull to add a reason the number does not really count, a slow week, a tracking glitch you have not verified, and you notice that you would not extend that same generosity to a colleague's disappointing result. You sit with that for a moment, and you write the honest version instead: the change did not clear the bar you set, and the next cycle should test why, not declare victory early.

When this is worth reaching for

At the Study step, the change was one you personally proposed and are personally invested in seeing succeed. More generally: a prediction you wrote down is coming back close to, but not quite past, the line you set for success — the exact zone where motivated reasoning does its quietest work.

Where this does not apply

If you are running PDSA on something genuinely low-stakes, a font size, a button color, where no ego or budget is riding on the outcome, adding a formal scout-mindset check is unnecessary weight; the loop's normal comparison against the prediction is already sufficient. And Scout Mindset applied mid-crisis, while a team is actively deciding whether to keep a system running during an outage, can slow a decision that needs speed more than certainty; save the disconfirmation-seeking for the post-incident study, not the moment itself.

What the evidence does and does not support

PDSA's core discipline, writing a prediction before observing a result, is standard practice across quality-improvement literature with strong observational support for improving decision accuracy in organizational settings, though PDSA as a named four-step label is a management tool rather than a laboratory-tested protocol. Scout Mindset's core claim, that deliberately searching for disconfirming evidence produces more accurate beliefs than confirmation-seeking, rests on a mix of observational research on motivated reasoning and the forecasting-calibration literature rather than a single trial of scout mindset as a branded technique; treat it as well-grounded in the surrounding science, not independently validated as a named protocol. Nobody has run a study on inserting a scout-style disconfirmation check specifically into a PDSA Study step; the case above extends two separately supported ideas, it does not report a finding about their combination.