A Personal PDSA: Small Experiments on Your Daily Routine

Most of us tinker with our routines all the time. We try a new alarm time, a different way to pack lunches, a new spot for the laundry basket. But we rarely treat those tweaks as experiments. We don't say what we expect to happen, we don't check, and a week later we can't remember whether the change helped.

The improvement cycle that factories, hospitals and labs use to test changes works just as well on a Tuesday morning. It's called PDSA, for plan-do-study-act, and its close cousin PDCA, for plan-do-check-act. This guide shows how to run a small, personal version on your own routine, with a worked example and a simple way to keep track.

The point isn't to turn your life into a spreadsheet. It's to make your small changes teach you something, so each one leaves you a little better off than the last.

PDSA, PDCA and why "study" matters at home

According to The W. Edwards Deming Institute, the PDSA cycle is "a systematic process for gaining valuable learning and knowledge for the continual improvement of a product, process, or service." The Institute explains that the cycle was first introduced to Deming by his mentor, Walter Shewhart of Bell Laboratories, and that Deming emphasized "study" rather than "check." Ronald Moen's history of the cycle, which the Institute publishes, traces the steps: Shewhart's cycle of 1939, the Deming wheel Deming presented at a 1950 seminar for Japanese managers and engineers, the Japanese PDCA of 1951, and Deming's final PDSA version in 1993.

The difference is useful for personal experiments. In the Institute's account, Deming found that "check" leans toward judging whether a change succeeded or failed, while "study" means predicting the result, comparing it with what actually happened and revising your thinking. At home, that's the difference between "the new morning routine didn't work" and "I expected to leave ten minutes earlier, I left three minutes earlier, and the delay is still finding shoes."

The Lean Enterprise Institute (LEI) notes that kaizen itself is based on PDCA cycles, so whichever name you prefer, you're practicing the same habit of small, tested improvements.

Plan: one question, one prediction

The Institute for Healthcare Improvement (IHI) uses the Model for Improvement, developed by Associates in Process Improvement, which pairs PDSA cycles with three questions:

1. What are we trying to accomplish?
2. How will we know that a change is an improvement?
3. What change can we make that will result in improvement?

For a personal experiment, answer them in a sentence each:

• Aim: what you want to be different, and by when. IHI says a good aim statement is time-bound and measurable.
• Measure: one simple thing you can observe, such as the time you leave the house, the number of evenings you cooked, or minutes spent looking for things.
• Change: the single change you will try.

Then add a prediction. Write down what you think will happen. The prediction is what turns a tweak into an experiment, because it gives you something to compare against.

Do: keep it small and short

IHI describes PDSA as testing a change on a small scale, giving the example of "one patient, one day," in a real-world setting. The personal version is one routine, for a few days or a week.

Small tests have real advantages at home:

• If the change doesn't work, the cost is a few slightly awkward mornings.
• You can try the change before asking anyone else in your household to adopt it.
• You learn faster, because you can run several short cycles in the time one big overhaul would take.

While you run the test, jot down anything surprising. Notes like "kids woke up late on Wednesday" will help you interpret the results.

Study: compare what happened with what you expected

At the end of the test, look at your measure and your prediction side by side. Ask:

• Did the result match the prediction? Better, worse or about the same?
• What explains the difference?
• Did anything unexpected happen, good or bad?

IHI notes that teams use both quantitative and qualitative data to learn whether a change is an improvement. For a personal experiment, that might be a number (minutes, days, dollars) plus a sentence about how it felt. A change that saves time but leaves everyone frazzled may not be the improvement you wanted.

Act: adopt, adapt or abandon, then make it standard

The Deming Institute describes the Act step as integrating what you learned, which can mean adjusting the goal, changing methods or expanding a small experiment into a larger plan. For personal use, that boils down to three choices:

• Adopt: the change worked. Keep it and make it the new normal.
• Adapt: it partly worked. Adjust and run another cycle.
• Abandon: it didn't help. Drop it and try a different idea.

If you adopt a change, write it down as your new standard, even if it's just a note on the fridge. LEI quotes Taiichi Ohno, who in Toyota's own account helped establish the Toyota Production System: "There can be no kaizen without a standard." A written routine is what keeps a good change from slipping away, and it becomes the baseline for your next experiment.

IHI adds that after testing under varying conditions, teams make a change permanent by building the support needed to sustain it. At home, that support might be a checklist, a set place for an item, or a reminder on your phone.

A worked example: the morning rush

For example, imagine a parent whose weekday mornings always end with a scramble out the door.

• Aim: leave the house by 7:45 on at least four of five school days within two weeks.
• Measure: actual departure time, written on a sticky note by the door.
• Baseline: last week, they left on time once.
• Change: pack backpacks and set out shoes the night before.
• Prediction: on-time departures on four of five days.

After one week, they left on time three days out of five. Studying their notes, they see that the two late days both involved a search for a missing permission slip or library book. The prediction was close, but the cause of the remaining delay was paperwork, not shoes.

They adapt: a single folder by the door for anything that needs signing. The next week they hit their aim. They write "backpacks packed and folder checked by 9 p.m." on the fridge as the new standard and pick the next small problem to work on.

Keep a simple log and look back

You don't need a special app. A notebook page or a note on your phone with five lines per experiment is enough: aim, measure, change, prediction and result.

Once a month, read back through the log. LEI describes hansei as the Japanese term for "self-reflection" and notes that it is sometimes compared to the "check" step of PDCA. Looking back over several experiments shows patterns you can't see in one, such as which kinds of changes tend to stick for you and which ones you abandon.

Key takeaways

• PDSA, Deming's plan-do-study-act cycle, grew out of a cycle he learned from his mentor Walter Shewhart, and it works on everyday routines.
• Answer three questions before you start: what you want, how you'll know, and what you'll change.
• Write a prediction so you can compare it with the result.
• Test small and short, such as one routine for a week.
• Adopt, adapt or abandon, and write successful changes down as your new standard.
• Keep a short log and review it monthly to spot patterns.

Sources

• The W. Edwards Deming Institute, PDSA Cycle
• Ronald Moen, Foundation and History of the PDSA Cycle (The W. Edwards Deming Institute)
• Institute for Healthcare Improvement, Model for Improvement
• Lean Enterprise Institute, Kaizen: A Resource Guide
• Lean Enterprise Institute, Hansei
• Toyota Motor Corporation, Toyota Production System