| Course | IHP 435 Performance Improvement Measurement and Methodologies |
|---|---|
| Module | Module 3 |
| Paper type | short paper on plan-do-study-act cycles |
| Length | About 1,060 words, 6 pages |
| Format | APA 7 student paper |
| School | Southern New Hampshire University |
| Program | BS Healthcare Administration |
| Updated | September 2026 |
Free sample paper for IHP 435 Module 3
Doing PDSA Right: Redesigning a Failed Registration Change as Small Tests
[Student Name]
Southern New Hampshire University
IHP 435: Performance Improvement Measurement and Methodologies
Module Three Short Paper
[Instructor Name]
[Date]
Doing PDSA Right: Redesigning a Failed Registration Change as Small Tests
Plan-do-study-act is the most widely taught improvement method in health care, and it may be the most often misused. At Cedar Point Medical Center, registration managers wanted to shorten the time before emergency patients were seen, so they introduced quick registration at the bedside, capturing only name, date of birth and complaint on arrival and completing full registration later. They launched it for every patient on every shift on the same Monday. Staff were confused about who should do what, insurance details went missing and after two weeks the change was abandoned as unworkable. This paper explains why that approach was not really PDSA, what research says about how PDSA is used and how the change could be tested properly.
The Idea Behind PDSA
Berwick (1996) described improvement as a process of learning, in which teams set an aim, choose measures and then test changes on a small scale to find out which ones actually help. Each test is a cycle: plan the change and predict what will happen, do it on a small scale, study the results against the prediction and act by adopting, adapting or abandoning the change. Small tests reduce risk, because a failed test affects few patients and little is lost, and they speed learning, because several cycles can run in the time one large change takes. Spreading comes only after a change has worked under a variety of conditions.
How PDSA Is Actually Used
Taylor et al. (2014) reviewed published health care projects that reported using PDSA and judged each against the method's key features: iterative cycles, small-scale testing, predictions, regular data collection over time and use of what was learned. Very few projects met all these features. Many described a single cycle, often large, and reported one before-and-after comparison. Relatively few made explicit predictions or collected data repeatedly. The authors concluded that PDSA is frequently used as a label rather than a method, which may explain why its results are inconsistent.
Cedar Point's rollout fits the common pattern exactly: one large change, no prediction, no data collected during the test and a decision based on impressions.
Why PDSA Is Harder Than It Looks
Reed and Card (2016) argued that PDSA's simple four-letter structure hides real difficulty. Teams underestimate the planning needed to define a test and a prediction, skip the study phase because they are eager to act and treat PDSA as a way to implement a decided solution rather than to learn whether it works. They also noted that complex problems may need several linked cycles, that teams need time, data support and skills in measurement and that organizations often expect quick wins from a method designed for gradual learning. PDSA is best seen, they suggested, as one part of a broader improvement approach that includes understanding the problem before testing solutions.
What the Failed Rollout Missed
Measured against these accounts, the rollout missed nearly every element. There was no written prediction, such as expecting door-to-provider time to fall by five minutes. The test was not small; it involved every patient and every shift at once. No data were collected systematically during the test, so the team could not tell whether waits fell. Problems that surfaced, like missing insurance details, were not studied and fixed but treated as proof the idea failed. And the managers had not first mapped the registration process to understand where delays actually occurred.
A Better Design: Four Small Cycles
The redesigned effort begins with a two-hour process walk by the registration supervisor, a triage nurse and an emergency physician to map the current path from arrival to provider. The walk showed that full registration at the front desk took about six minutes per patient during peak hours, creating a line before triage. The aim is to reduce median door-to-provider time from 42 to 30 minutes within three months without increasing insurance errors.
Four cycles follow. Cycle one: one registrar performs quick registration for five walk-in patients during one weekday morning, predicting that each will take under two minutes and that full registration can be completed at the bedside within an hour. Cycle two: the same registrar tests it for a full four-hour peak period, predicting no insurance information will be missing at discharge. Cycle three: two registrars test it on one evening shift, predicting door-to-provider time for those patients will be at least five minutes shorter than the shift's baseline. Cycle four: quick registration runs for all walk-in patients for one week, with ambulance arrivals excluded until the process is stable.
Table 1. Planned PDSA Cycles for Quick Registration
| Cycle | Scale | Prediction | Measure | Decision rule |
|---|---|---|---|---|
| 1 | One registrar, five patients, one morning | Under 2 minutes each; bedside completion within 1 hour | Timed registrations | Adapt script if any exceed 3 minutes |
| 2 | One registrar, one 4-hour peak | No missing insurance at discharge | Discharge audit | Adapt handoff if any missing |
| 3 | Two registrars, one evening shift | Door-to-provider 5+ minutes shorter | Time stamps vs baseline | Proceed if prediction met |
| 4 | All walk-ins, one week | Median door-to-provider under 35 minutes | Weekly run chart | Adopt, adapt or abandon |
Note. Each cycle's result shapes the next.
Studying and Acting
After each cycle the team meets for fifteen minutes to compare results with the prediction. If quick registrations take three minutes rather than two, the team studies why, perhaps because the screen requires extra fields, and adapts before the next cycle. If insurance details go missing, the handoff to bedside registration is redesigned. The decision at the end of each cycle is recorded in a simple log with the prediction, what happened and what will change. Door-to-provider time and insurance error rates go onto run charts, making trends across cycles visible rather than relying on memory.
Support the Method Needs
Following Reed and Card, the design includes the support PDSA requires: the registration supervisor has four protected hours a week, the quality department supplies a weekly time-stamp report and a quality coach meets the team every two weeks. Leaders agreed in advance that a cycle that fails its prediction is a success for learning, not a failure of the team, which encourages honest reporting.
Conclusion
Cedar Point's first attempt was a large, unmeasured change labeled as improvement. Running the same idea as small cycles with predictions, measures and decisions turns a gamble into a series of inexpensive experiments, each teaching the team something before the next. That is what PDSA was designed to do.
References
Berwick, D. M. (1996). A primer on leading the improvement of systems. BMJ, 312(7031), 619-622. https://doi.org/10.1136/bmj.312.7031.619
Reed, J. E., & Card, A. J. (2016). The problem with Plan-Do-Study-Act cycles. BMJ Quality & Safety, 25(3), 147-152. https://doi.org/10.1136/bmjqs-2015-005076
Taylor, M. J., McNicholas, C., Nicolay, C., Darzi, A., Bell, D., & Reed, J. E. (2014). Systematic review of the application of the plan-do-study-act method to improve quality in healthcare. BMJ Quality & Safety, 23(4), 290-298. https://doi.org/10.1136/bmjqs-2013-001862
What the IHP 435 Module 3 instructions ask for
The IHP 435 PDSA assignment usually asks you to explain the plan-do-study-act method and apply it to an improvement idea, sometimes by critiquing a past effort. Expect two to four APA 7 pages. Describe each phase accurately, stress small-scale testing and predictions and show how cycles build on one another. Apply the method with a concrete example that includes an aim, a prediction for each cycle, a measure and a decision rule, ideally in a table. Draw on research about how PDSA is used and misused, and explain the support a team would need, since instructors reward realistic plans over tidy but idealized ones. IHP 435 graders notice clean headings in IHP 435 papers. IHP 435 names and dates need checking before IHP 435 submission.
How this IHP 435 Module 3 pdsa short paper example is built
This paper examines a composite hospital's bedside quick registration, launched for every emergency patient at once and abandoned after two weeks. Berwick's primer explains PDSA as small-scale learning, Taylor and colleagues show that most published projects skip iterative cycles and repeated data and Reed and Card explain PDSA's hidden demands. After a process walk and an aim to cut median door-to-provider time from 42 to 30 minutes, four cycles scale from five patients to a full week, each with a prediction, a measure and a decision rule. Run charts, a cycle log, protected time and coaching support the work. IHP 435 students can reuse this structure for IHP 435 work. IHP 435 claims here trace to cited IHP 435 sources.
Where the IHP 435 Module 3 rubric puts the points
PDSA papers in IHP 435 get marked on how faithfully the method is explained, the quality of the worked example, explicit predictions and measures, logical progression of cycles, use of evidence on PDSA practice, attention to support and context, scholarly support and APA 7. Strong papers start small, predict before testing, study results honestly and let each cycle shape the next. Papers lose points when they describe a single large change as PDSA, omit predictions, skip the study phase or present cycles that are all identical in scale. A cycle table with decision rules is often credited as evidence of real understanding. IHP 435 marks favor careful formatting across IHP 435 sections. IHP 435 citations keep every IHP 435 argument credible.
IHP 435 Module 3 help: the mistakes that cost points
In IHP 435, PDSA papers often lose points for treating PDSA as a synonym for implementation, for missing predictions, for cycles without data and for ignoring what the team learned. Another common gap is skipping any effort to understand the problem before testing a solution. Explain the method accurately, map the process first, design small cycles with predictions and decision rules and plan support. If your project has a different change idea, add it to your IHP 435 notes and the cycles will be designed around it. IHP 435 drafts start well from a IHP 435 outline. IHP 435 feedback already received guides IHP 435 revisions.
Get IHP 435 Module 3 written to your instructions
Send the IHP 435 PDSA prompt and the change you want to test. The paper will explain the method accurately, map the problem, design small cycles with predictions, measures and decision rules and plan the support the team needs, within 24 to 48 hours, free the first time. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.
More IHP 435 papers and related BS Healthcare Administration samples
- IHP 435 Module 1 Discussion: Three Questions Every Improvement Effort Answers
- IHP 435 Module 2 Measurement Short Paper: A Family of Measures for Emergency Department Waits
- IHP 355 Module 8 Discussion: Compliance as Culture, Not Paperwork
- HCM 340 Module 1 Delivery System Components Discussion
- IHP 310 Module 4 Endocrine and Neural Case Study
- IHP 410 Module 4 Final Project Milestone Two
IHP 435 Module 3 questions, answered
Where can I find a free IHP 435 Module 3 PDSA Short Paper sample?
Everything is on this page: why PDSA cycles often fail and a failed registration change redesigned as four small cycles with predictions.
What are the steps of a PDSA cycle?
Plan the change and predict the result, do it on a small scale, study results against the prediction and act by adopting, adapting or abandoning it.
Why should PDSA tests start small?
Small tests limit risk and speed learning, letting teams run several cycles and fix problems before spreading a change.
How is PDSA commonly misused?
Research found many projects run one large change without predictions or repeated data, using PDSA as a label rather than a method.
Why do PDSA cycles need predictions?
Comparing results with a prediction turns a test into learning, showing whether the team's understanding of the process was right.