Using PDSA Cycle to enhance Santosha

What each one is actually for

PDSA Cycle

One loop at a time, carried through to its end, is the whole discipline. Plan-Do-Study-Act, named for the quality-improvement work of W. Edwards Deming, has four steps and a rule that they run in order. Plan means committing a prediction to writing in a form that could turn out false — not 'this should help' but 'if I move the run to before breakfast, I will skip fewer than one day in seven.' Do means running that exact change, small enough and short enough that being wrong is cheap, and recording what actually happened rather than what you meant to happen. Study means setting that record against the prediction you wrote down and taking the difference at face value, without supplying a reason the week was unrepresentative. Act means one of three verdicts, and the first of them is the one people forget is on the list: keep it exactly as it is and change nothing. Adjust and abandon are the other two. The cycle is not a licence for permanent tinkering; it is a way of earning the right to stop, because a change that has been tested and held up does not need testing again, and the next loop is supposed to be opened on a question you genuinely do not have an answer to yet.

Santosha

Santosha works by treating a feeling most people try to manage indirectly — the sense that something is still missing — as something you can address directly, by deliberately choosing to register what is already present as sufficient. This is not the same as telling yourself things are fine when they are not, and it is not passivity: a person practicing santosha can still want things, plan things, and act. What changes is the running commentary underneath the wanting, the quiet, constant sense that satisfaction is one step ahead of you and will arrive once the next thing lands. Practiced concretely, santosha looks like pausing before reaching for the next input — the next purchase, the next scroll, the next self-improvement idea — and asking, honestly, whether what is already here has actually been let in yet, or whether you moved on before it had the chance to register.

What you get out of pairing them

The Plan-Do-Study-Act cycle gives you something most self-improvement tends to lack: an honest way to find out whether a change is actually working, instead of running on the feeling that it probably is, which is a feeling people are notoriously bad at trusting correctly. That matters because acting on an untested hunch wastes effort on changes that were unlikely to help, while quietly convincing you that you are being disciplined and thorough. Santosha gives you something the testing habit does not include on its own, and in fact can actively work against: a way to stop the improvement itself from becoming the next thing you are chronically short of. Someone who has built a strong habit of testing changes can end up treating their own sense of enough-ness as just another metric to optimize — seemingly one more experiment away from finally being satisfied — and santosha is the specific check against exactly that pattern, asked honestly and often enough to actually catch it before it runs the whole show.

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.

What Santosha rests on

• Acceptance reduces struggle randomised trials
  Allowing an internal experience to be present without resisting or acting on it reduces the psychological struggle that resistance would otherwise intensify.
• Repeated practice builds new automaticity clinical practice
  Repeating a new response consistently over time makes that response itself automatic and displaces the old habitual response it replaces.
• Contentment uncouples wellbeing from acquisition practitioner report
  Practicing satisfaction with what is weakens the habitual link between wellbeing and acquiring more and reduces craving-driven suffering.

Where they actually meet

Both practices refuse to let an assumption about the future run unexamined. The Plan-Do-Study-Act cycle refuses to let "this change will probably help" stand as settled until it has been checked against a real result. Santosha refuses to let "the next thing will finally be enough" stand as settled either, checking it instead against your own accumulated history of how satisfaction has actually gone after the last several things that were supposed to deliver it. Different objects — one checks a specific planned action, the other checks a chronic background belief about acquisition — but the identical discipline: a claim about what will make things better is treated as something to verify, not something to simply act from because it feels true right now.

The principle underneath both

Strip the vocabulary away and what both are doing is refusing to hand a decision to an untested prediction. Plan-Do-Study-Act checks a specific claim — this change will work — against a measured result before it earns the right to be adopted. Santosha checks a much older, quieter claim — this next thing will finally be enough — against the plain fact of your own history, in which the last several things that were supposed to finally be enough were not, for long. Named plainly: an assumption gets to keep running your behavior only until it has actually been tested against what happens, and both of these practices are built to do exactly that testing, aimed at two different targets.

What that makes the real goal

If refusing to act on an unchecked assumption is the shared discipline, what both are actually working toward is the same thing: a decision, or a felt sense of having enough, that answers to what has actually happened rather than to a story that merely feels convincing in the moment. For the Plan-Do-Study-Act cycle that means a specific action gets adopted only after it has produced a measured result. For santosha it means your sense of sufficiency answers to your own lived evidence about what acquiring more has and has not delivered, rather than to the next attractive story about what would finally do it.

Other practices that serve the same goal

Cognitive behavioral thought records pursue a close cousin of the same target from the therapy side: a person writes down an automatic belief — "if I don't respond to this email tonight, something bad will happen" — and then deliberately checks it against what actually happens when they test it, with solid randomized-trial support for reducing anxiety this way. Affective forecasting research, most associated with psychologists Daniel Gilbert and Timothy Wilson, targets exactly the belief santosha is built to interrupt: across a large body of experimental work, people reliably and predictably overestimate how much a purchase, promotion, or achievement will improve how they feel, and for how long — which is close to a formal, measured version of "the next thing will not actually deliver what you expect it to," arrived at from outside any contemplative tradition at all.

A tradition that already does this

The Stoic distinction between what is and is not within your control, taught by Epictetus and collected in the Enchiridion, already draws almost exactly this line: work on, test, and try to change what is actually up to you, and deliberately accept what is not, rather than spending effort trying to control it or resenting that it will not move. That is not a specific ancestor of either the Plan-Do-Study-Act cycle or santosha by name, but it is an old and independent instance of the same two-part move — test what is testable, accept what is not — which suggests the pairing here is closer to rediscovering a durable pattern than to forcing two unrelated modern practices together.

Using the Plan-Do-Study-Act cycle to enhance santosha

Santosha is often taught as a general inner orientation — rest in what is already enough — which is honest advice but genuinely hard to know from the inside whether you are actually doing. Give it a falsifiable loop instead of a vague intention: write a specific, checkable prediction, for example "if I pause for one full minute before reaching for my phone each time I notice the urge to check it, for one week, the number of times I actually reach for it out of restlessness rather than a real need will drop by half." Run exactly that for the week, and keep a plain log rather than a vibe: how many pauses, how many times you reached anyway, what the moment actually felt like. At the end of the week, study the log honestly against the prediction — not "did I feel more content," which is hard to judge from inside, but the specific number you committed to in advance. This does not turn santosha into another performance metric if the thing being measured stays your behavior around chasing, not your feelings; it gives an inner practice that is easy to only imagine you are doing a way to actually check whether you are.

Using santosha to enhance the Plan-Do-Study-Act cycle

A person who has gotten good at running Plan-Do-Study-Act loops on their own life tends to have one running nearly nonstop — a new morning routine, a new productivity system, a new supplement stack — and the habit of testing can quietly stop asking whether the thing under test was worth testing at all. Before starting the next loop, run santosha's actual question on the plan itself: if this specific test succeeds and delivers exactly what it promises, will you actually stop looking for the next improvement, or is the looking itself the real, unexamined pattern? Answered honestly, that question does not tell you to stop testing — it tells you which tests are worth running. A test aimed at a real, specific friction, like the run you keep skipping, passes the question easily. A test aimed at a vague sense that you should be optimizing something, with no particular friction behind it, usually does not, and santosha's job here is to catch that difference before you spend a week measuring something that was never the actual lever.

Sunday night, planning the week, adding one more thing to try

It is Sunday evening and you are laying out next week, and somewhere in the middle of it you notice yourself adding a new morning routine to the list — cold shower, ten pages of reading, a different order for the same habits you already have — on top of the three things you are already tracking. There is a specific, familiar pull underneath it, a sense that this next tweak is the one that will finally make the mornings feel right, which is close to identical to the pull you felt about the last three tweaks. You stop before adding it and ask the santosha question plainly: if this new routine works exactly as intended, will the search actually stop, or is the search itself the thing running? Sitting with that honestly for a minute, you notice the truer answer is that mornings already work reasonably well and the itch is about restlessness, not a real gap. You close the new item on the list. The one habit you do keep testing — the run you have skipped four times this month — gets a real, dated prediction written next to it instead, because that one has an actual, specific friction behind it rather than a vague appetite for one more improvement.

When this is worth reaching for

The tracker has a new experiment queued before last week's has even finished, and noticing that pattern out loud is uncomfortable — santosha's question belongs right there, before the next loop starts rather than after. The reverse case also holds: someone leaning on santosha language to avoid a change a short, cheap test would clearly justify gets a corrective from writing a small, falsifiable prediction, because it turns a vague "I'm just practicing acceptance" into a concrete question that's much harder to dodge.

Where this does not apply

If you are in a genuine crisis — an unsafe living situation, a job that is actively harming you, a relationship with real danger in it — leading with santosha's "is this change actually needed" question is the wrong move entirely; that question is built for sorting restless optimizing from real friction, not for talking yourself out of a change that is clearly, obviously needed, and using it that way turns a contentment practice into a reason to stay somewhere you should leave. And if you have not yet run a structured test on anything in your own life before, introducing the "is this just chasing" filter on day one can become a new, more sophisticated way to avoid trying much of anything — in that case, run a few honest Plan-Do-Study-Act loops first and let santosha's question in only once you can tell, from experience, the difference between genuine restlessness and a real, worth-fixing friction.

What the evidence does and does not support

The Plan-Do-Study-Act cycle carries real evidence, though mostly from quality-improvement and healthcare settings rather than personal habit change specifically: closing the loop and comparing a result against a stated prediction measurably improves how well a change actually gets adopted, compared with acting on intuition alone, largely through observational and case-based studies rather than randomized trials. Santosha's underlying claim, that deliberately treating the present as sufficient reduces the psychological cost of chronic wanting, is supported at one remove by acceptance-based therapies, which do carry solid randomized-trial evidence for related mechanisms, though santosha as a specific named yogic practice has not itself been isolated and tested on its own. Nobody has studied using a testing loop to build a contentment practice, or using a contentment check as a filter for which tests are worth running — that specific combination is this page's own reasoning about two separately evidenced practices, not a claim that the pairing itself has been measured.