Using Noting Practice to enhance PDSA Cycle
And how PDSA Cycle sharpens Noting Practice in return.
Noting practice trains you to catch a thought as it arises rather than being carried by its content; the PDSA cycle (Plan, Do, Study, Act) tests a small change by comparing the real result to a prediction written down in advance. On this reading, the two share a single underlying move - creating a gap between something and your automatic acceptance of it - aimed at different material: a thought in one case, a story about a result in the other. Using a short noting exercise right before writing up a PDSA Study step is one way to catch the convincing explanation that arrives before the real result has actually been looked at, though the pairing itself has not been tested.
What each one is actually for
Noting Practice
Noting practice is a specific meditation technique, not meditation in general: the instant a thought, sound, or sensation arises in awareness, you apply a soft, one- or two-word label to it - "thinking," "hearing," "rising," "planning" - and then let it go, without following the content of the thought itself. If you notice you have been carried away into an actual train of thought (rehearsing an argument, planning dinner), the move is simply to note "thinking" or "wandering" and return attention to the next arising thing, over and over, for the length of the sit.
PDSA Cycle
Testing one change to your sit at a time, and finding out what it actually did, is the job the PDSA cycle — Plan, Do, Study, Act — was built for. Plan means picking a single specific change (twenty minutes instead of forty; sitting before coffee rather than after; noting the breath at the belly rather than the nostrils) and writing down, in advance, what you expect it will do — not "it should help," but something reality could contradict, like "in the second half I will get carried off into planning fewer times than I did last week." Do means running that change on a deliberately small scale, a week rather than a season, so that guessing wrong costs you almost nothing. Study means setting what actually happened next to the prediction you wrote before you started, and reading the gap honestly, including the places where the two did not match. Act means deciding on the strength of that comparison — keep the change, adjust it and run the loop again, or drop it and try something else. The written prediction is the whole mechanism: without it the mind supplies a story afterwards about what it always expected, and by then you cannot tell the story apart from the result.
What you get out of pairing them
Noting practice buys you a moment of actual distance between a thought arising and you being fully inside it - the difference between being swept into an argument you are rehearsing in your head and noticing "thinking, thinking" and stepping back out of it, which over time changes how much any single thought can commandeer your attention. PDSA buys you something related but pointed outward: protection from your own convincing story about why a change worked or did not, by forcing you to write the prediction down before you know the answer, so hindsight cannot quietly rewrite what you expected.
What Noting Practice rests on
-
Decentering from thought
randomised trials
Shifting attention from the content of a thought to observing it as a passing event in awareness creates distance from that content instead of fusion with it.
-
Affect labeling reduces arousal
randomised trials
Putting an emotion into words reduces the physiological and psychological intensity it would otherwise carry while unexamined.
-
Attention is trainable
randomised trials
Repeatedly practicing directing and redirecting attention strengthens the ability to control where it goes, making that control more available over time.
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
Noting practice creates a small gap between a thought and your identification with its content, by labeling the thought as an event ("thinking") rather than treating it as simply true and continuing to think it. PDSA creates a small gap between a change and your interpretation of its results, by writing the prediction down before you know the outcome, so the outcome has to be checked against something fixed rather than absorbed into whatever story feels right afterward. Both interrupt an automatic process, getting fused with a thought's content, or getting fused with a comfortable story about a result, by inserting a labeled, examined step in between.
The principle underneath both
An automatic, unexamined process (following a thought's content as if it were simply reality; believing a result confirms whatever you already expected) is more accurate and more useful once you decenter from it slightly, put a label on it, or a prediction against it, rather than remaining fused with it. Decentering is not distance for its own sake; it is what makes the thing being observed available for actual examination instead of automatic acceptance.
What that makes the real goal
If decentering from an automatic process is the engine, the objective underneath both practices is: create enough separation between something (a thought, a result) and your automatic acceptance of it that you can examine it honestly, rather than simply believing whichever version arrives first. That objective is a general cognitive move, not something owned by meditation or quality-improvement methodology specifically.
Other practices that serve the same goal
Other approaches aimed at the same objective: cognitive defusion techniques from Acceptance and Commitment Therapy, which use similar labeling moves ("I'm having the thought that...") specifically to decenter from a thought's literal content, with a solid trial base in the same territory as noting practice. On the results side, pre-registration in scientific research, publicly committing to a hypothesis and analysis plan before collecting data, is the institutional-scale version of PDSA's "write the prediction down first" discipline, built for exactly the same reason: to prevent a convincing story from being fitted to data after the fact instead of tested against a prior guess.
A tradition that already does this
The Toyota Production System, the direct ancestor of PDSA as it is used in modern quality improvement, already describes small experimental cycles as a discipline of humility about your own predictions, explicitly building in the expectation that the prediction will sometimes be wrong and treating that as useful information rather than failure. That is the same decentering move PDSA makes with results, in a tradition that predates the formal PDSA name.
Using Noting Practice to Enhance the PDSA Cycle
The Study step in PDSA is where most people quietly fail without noticing: comparing a real result to a prediction requires actually sitting with what happened rather than jumping straight to a story about why it happened, and the jump to story is exactly the kind of automatic thought-following noting practice trains you to catch. Before you write up the Study step, spend two or three minutes doing a short noting sit specifically on the thoughts arising about the result, you will likely notice several appear almost instantly ("this failed because I didn't plan enough," "this worked because I'm good at this"), and note each one as "thinking" rather than accepting it as the explanation. What is left after a few minutes of that is usually a plainer, less story-laden description of what actually happened, which is what the Study step actually needs.
Using the PDSA Cycle to Enhance Noting Practice
Noting practice is often taught and then abandoned within a few weeks because people cannot tell whether it is "working" - the benefit (a small gap between a thought and being carried by it) is subtle and easy to doubt without any real check. Borrow PDSA's discipline directly: before a week of noting practice, write down a specific, falsifiable prediction, "I predict I'll be able to notice at least three instances outside of formal sitting this week where a strong thought arose and I caught it with a label before acting on it," then actually track it. At the end of the week, compare the real count against the predicted one rather than relying on a vague sense of whether the practice "feels like it's working." This gives an inherently subtle, slow-building practice a concrete, checkable signal early enough to sustain motivation through the weeks before the benefit is otherwise obvious.
Thursday, Reviewing a Failed Two-Week Experiment
You ran a two-week PDSA cycle at work: predicted that moving your team's standup from morning to afternoon would reduce interruptions during your most productive hours. It did not, interruptions stayed the same. The instant thought arrives, fully formed: this whole PDSA thing is a waste of time, I already knew scheduling does not matter here. You catch it, note it, "thinking, thinking", and let it pass rather than writing it into the report as if it were simply true. What is left once that story drops away is plainer: the standup time changed, but the actual source of interruptions (people stopping by your desk) never touched the calendar at all. The prediction was wrong in an informative way, not a useless one, but only once the fused story about the method itself failing got noted and released instead of accepted as the conclusion.
When this is worth reaching for
You'll know it's the right cycle to try this on when a change process keeps producing a plausible-sounding story about the result, and the story never quite gets checked against what was actually predicted. It also suits a meditation practice that's stalled with no way to tell whether it's doing anything at all. It matters most in a role with real ego investment in the outcome — your own project, your own idea — since that's exactly when the pull to explain away an unwanted result is strongest, right when the Study step needs to be most honest.
Where this does not apply
If a PDSA cycle's result is unambiguous, a clear, large, hard-to-misread outcome, inserting a noting exercise to check for story-fusion is unnecessary ceremony; bring the practice in specifically around ambiguous or ego-relevant results, not every result. And noting practice on its own is a general attention-training method that does not need a business-process framework attached to be worthwhile - someone with no interest in structured experimentation loses nothing by practicing noting without ever hearing the words plan-do-study-act.
What the evidence does and does not support
Decentering from thought and the attention-training claim behind noting practice both have solid randomized-trial support from the broader mindfulness literature, and affect labeling's arousal-reducing effect is similarly well studied. PDSA's core claim, that comparing an actual result against a stated prediction corrects belief faster than judging a change by feel, rests on mechanistic and observational grounding from the quality-improvement literature rather than randomized trials of the cycle itself. No research has tested using a meditation technique to reduce narrative bias in a PDSA Study step; this pairing is a reasoned application of two separately-evidenced mechanisms to each other's known weak points.
Practice this with IX Coach
The two practices on their own
Other pairings with these practices
- 168 Hours Time Audit and Noting Practice
A time log is only honest if the entry doesn't get rewritten first. Noting practice trains the exact skill of catching that rewrite as it happens.
- 168 Hours Time Audit and PDSA Cycle (Plan-Do-Study-Act)
A time log without a next step is a diagnosis going nowhere. Run it through a plan-test-check loop and the same log becomes an actual experiment.
- Action Planning (Implementation Intentions) and Noting Practice
An if-then plan only fires if its cue is caught in time. Noting practice trains exactly that catch — here's the one seam where they meet.
- Action Planning (Implementation Intentions) and PDSA Cycle (Plan-Do-Study-Act)
A specific cue-and-response plan tells you what to do. It has no built-in way to tell you whether it actually worked. Here's the missing check step.
- Attention Management and PDSA Cycle (Plan-Do-Study-Act)
A protected focus block you never check against a prediction is a guess wearing a calendar entry. Pair it with a plan-test-check loop instead.
- Behavior Design (Environment Design) and Noting Practice
A cleared room stops most distractions before they start. Here is what to do with the pull that shows up anyway, once you are already sitting.
- Behavior Design (Environment Design) and PDSA Cycle (Plan-Do-Study-Act)
A redesigned default might not be doing anything. A plan-do-study-act loop is one way to actually check that, instead of assuming it.
- Collaborative Problem Solving and Noting Practice
Noting catches a rising reaction early enough to name it; Collaborative Problem Solving gives that catch something real to ask about next.
- Collaborative Problem Solving and PDSA Cycle (Plan-Do-Study-Act)
CPS finds the unsolved problem behind an outburst; PDSA checks whether the fix actually worked before trusting it. An unstudied pairing, honestly.
- Deep Work and Noting Practice
A closed door stops outside noise. On one reading, noting practice is how you catch the mind wandering off anyway, once the door is already shut.
- Deep Work and PDSA Cycle (Plan-Do-Study-Act)
A focus ritual can feel more productive without producing more. On one reading, a simple test-and-check step is how you'd actually know the difference.
- Dialectical Behavior Therapy (DBT) and Noting Practice
Noting drills the labeling reflex DBT depends on; DBT gives noting a sharper move for a real spike. Neither has been tested combined.
The principles underneath both
- decentering from thought
Shifting attention from the content of a thought to observing it as a passing event in awareness creates distance from that content instead of fusion with it. Shared by 21 practices in the corpus — here in Acceptance and Commitment Therapy (ACT).
- affect labeling reduces arousal
Putting an emotion into words reduces the physiological and psychological intensity it would otherwise carry while unexamined. Shared by 19 practices in the corpus — here in Active Listening.
- attention is trainable
Repeatedly practicing directing and redirecting attention strengthens the ability to control where it goes, making that control more available over time. Shared by 18 practices in the corpus — here in 5-4-3-2-1 Grounding.