David M. Williams, PhD, Improvement Advisor, TrueSimple Improvement
Have trouble viewing this video? Read the transcript.
Learning Objectives: At the end of this activity, you will be able to:
Explain why PDSA cycles should be iterative.
Discuss why it can sometimes be necessary to test more than one change at a time.
Recognize why it can be confusing to mix too many PDSA cycles at the same time.
Description: Improvement can be slow and methodical, and sometimes it makes sense to test two changes at the same time. What should you keep in mind in these situations? And what should you be wary of when you run multiple PDSA cycles? Improvement Advisor David Williams shares his expert knowledge.
- Why should you take learning from one PDSA cycle and apply it to subsequent cycles?
- Why isn’t one independent change likely to result in improvement of a system?
- Why is it important to isolate changes when working on improvement?
- Have you ever run two (or more) concurrent PDSA cycles during an improvement project? What was your experience?