A clever idea is not yet an improvement. It becomes an improvement when the evidence shows it works in the context that matters.
Understand the idea
Plan–Do–Study–Act (PDSA) is an iterative improvement approach: formulate a prediction, run a small test, analyze what happened and decide whether to adapt, repeat or broaden the change.
PDSA is most useful when uncertainty is real. It encourages a team to make predictions and observe outcomes rather than launching a new process everywhere based on enthusiasm. Different from a one-time rollout, repeated cycles refine the idea.
Why it matters at work
Small tests limit the consequences of a poor change and generate actionable learning quickly. They also create opportunities for frontline staff to help design a process they will actually use.
How to use it, step by step
- Plan: specify the problem, desired outcome, prediction, test population and data to collect.
- Do: test on a small, appropriate scale and document deviations.
- Study: compare actual results to the prediction, including unintended consequences.
- Act: decide whether to adapt, abandon, repeat or test in a wider setting.
- Record what was learned and assign the next cycle owner.
Worked workplace example
A service team wants to reduce incomplete handovers. Rather than changing every shift, it trials a two-minute confirmation checklist with one team for a week. The team tracks missing information and staff effort. If omissions fall but the checklist causes delays, the next cycle removes redundant fields rather than assuming the first design was perfect.
Limitations and common mistakes
PDSA is not a reason to experiment without safeguards. For high-risk work, ensure approvals and risk controls before testing. Avoid declaring victory based on tiny samples or judging a change using only one convenient measure. Consider process, outcome and balancing measures.
Reflection and practice
Choose a low-risk process bottleneck. Write a prediction, one measure and one possible unintended effect before suggesting any change.
Use this as a thinking aid, not a substitute for organizational policies, technical expertise or professional judgement.