Apply PDSA to a behavior you want to build or break
Treat habit formation as a series of small experiments rather than a commitment you either keep or blow.
Why it works
Framing a new behavior as a committed identity ("I am going to exercise daily forever") creates binary success-or-failure outcomes. Framing it as a PDSA experiment ("I predict that if I lay out my shoes the night before, I will exercise three of five mornings this week") makes any result informative rather than a verdict on character. This reframing reduces shame and increases the willingness to keep iterating after a missed attempt.
How to do it
- Pick one behavior change you want to test this week.
- Write a specific prediction: "If I do X, then Y will happen [n] times."
- At the end of the week, score the result honestly and change exactly one variable for the next week.
Evidence
Framing goals as experiments rather than commitments is consistent with implementation-intention and self-compassion research, which both find that rigid all-or-nothing frameworks increase shame and reduce persistence after setbacks. (mechanistic)
The PDSA framing for habits is an applied extension of the industrial method; direct comparative trials are not available.
Common mistake
Running the experiment but never writing the prediction, which means the end-of-week review is a feeling ("I did okay") rather than a comparison point with information in it.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Plan–Do–Study–Act: Deming’s Loop for Personal Improvement
- Form a testable prediction before you act
State in advance what you expect to happen, so the result is evidence rather than noise.
- Run the smallest test that can answer the question
Shrink your experiment so the feedback cycle is fast and the cost of being wrong is low.
- Study the gap between prediction and result with honesty
Compare what you expected to what happened, and resist the urge to explain the gap away.
- Act on exactly one change before cycling again
Carry one specific modification into the next cycle — not a wholesale overhaul.
- Shorten your PDSA cycles until feedback is near-daily
More loops beat longer loops: compress the cycle time to accelerate learning.
- Keep a written PDSA log so the cycle has memory
Record each cycle so patterns across attempts are visible and the same mistake is not repeated indefinitely.
Related concepts
- Metacognition: Knowing What You Actually Know
Monitoring, calibrating, and steering your own understanding
- After-Action Review: The US Army’s Tool for Continuous Learning
A four-question debrief that turns experience into usable learning
- Deliberate Practice, Not Just Practice
Focused, feedback-driven practice at the edge of your ability