DNP860 Module 6 assignment: PDSA cycles versus one-shot implementation discussion post, a full sample

Reviewed by Maren Hollowell, MSN, RN Aspen University True APA form Annotated

A complete DNP860 Module 6 example: the module's discussion post in full, contrasting a sister hospital's one-week, all-staff rollout of blood culture diversion devices (3.9 to 3.6 percent after six months) with small, predicted, iterative PDSA cycles, and adding the critique that cycles are often applied superficially, with evidence on how rarely true iteration is documented.

1

Module 6 Discussion: Initial Post

One Week, Every Nurse, No Change: What a One-Shot Rollout Teaches About Plan-Do-Study-Act Cycles

Before our project began, a sister hospital in our system tried to reduce blood culture contamination in its emergency department by purchasing initial specimen diversion devices and training every nurse in a single week. Six months later, its contamination rate had moved from 3.9 to 3.6 percent. When our team asked what happened, three problems emerged. Many cultures were still drawn through newly placed catheters, where the device offered less benefit. Nurses on nights, who had been trained in a rushed session, often skipped the device when busy. And no one had looked at the data until month six, so none of these problems were found while they could have been fixed.

That is the typical failure of one-shot implementation: a change is launched at full scale, on a prediction no one wrote down, and judged after it is too late to learn. The Model for Improvement offers the alternative of testing changes through small, iterative plan-do-study-act cycles, each beginning with a prediction and ending with a decision to adopt, adapt, or abandon (Langley et al., 2009). Had the sister hospital tested the device with two nurses on one shift for a week, it would have seen quickly that catheter draws undercut the benefit and that night staff needed a different approach.

Cycles are not a guarantee, though. Reed and Card (2016) argue that the apparent simplicity of plan-do-study-act has led to superficial use, and that effective cycles depend on genuine iteration, prediction, measurement, and organizational support rather than on the four words alone. A systematic review found that few published projects documented a true sequence of iterative cycles or used frequent data to guide them (Taylor et al., 2014). A single rollout relabeled as a cycle is still a one-shot implementation.

For our project, the lesson is concrete: test each bundle component with a small group first, write the prediction before starting, look at the data weekly, and expect the second and third cycles to change the design. We will also keep a simple cycle log, one page per test, recording the prediction, what happened, and the decision, so that the project's final report can show the actual sequence of learning rather than a tidy story written afterward. Scaling up will follow evidence from the cycles: a component spreads to the next shift only when it has held up on the last one.

Has anyone seen a change that failed at full scale but might have worked if it had been tested small first?

What this page is doingThe post uses a concrete comparison case to show the failure mode of one-shot implementation, contrasts it with PDSA cycles using the model's source, adds a critique and evidence on how cycles are misused, and ends with practical commitments and a question for peers. The highlighted sentence names the key trap.
2

References

Langley, G. J., Moen, R. D., Nolan, K. M., Nolan, T. W., Norman, C. L., & Provost, L. P. (2009). The improvement guide: A practical approach to enhancing organizational performance (2nd ed.). Jossey-Bass.

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

How this DNP 860 Module 6 example is structured

DNP860 Module 6 discussions often compare PDSA cycles with one-shot implementation and its failures. Aspen does not publish module deliverables, so check your classroom for the exact prompt. This example uses one concrete case, explains what cycles would have revealed, adds a critique of how cycles are misused and ends with practical commitments and a question.

DNP860 Module 6 questions, answered

What does DNP860 Module 6 usually ask for?

The module's discussion often asks you to compare iterative PDSA cycles with one-shot, full-scale implementation and discuss why one-shot changes fail. Aspen does not publish module deliverables, so your classroom's instructions govern.

Why do one-shot implementations often fail?

They launch a change at full scale without a written prediction or early data, so problems in real conditions are discovered only after months, when it is hard to adjust or learn what went wrong.

What makes a PDSA cycle genuine?

A written prediction, a small-scale test, frequent data compared with the prediction, a decision to adopt, adapt or abandon, and a sequence of cycles that builds on what each one learned.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.

Request this one custom, free All DNP860 module samples All courses