| Course | NURS 8301 Effectively Leading Organizations in Quality Improvement Initiatives |
|---|---|
| Week | Week 6 |
| Paper type | Driver diagram paper |
| Length | About 1,060 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Nursing Practice (DNP) |
| Updated | September 2026 |
Free sample paper for NURS 8301 Week 6
A Theory of Change Drawn as a Tree: A Driver Diagram for Reducing Avoidable Day-of-Surgery Cancellations
Student Name
College of Nursing, Walden University
NURS 8301: Effectively Leading Organizations in Quality Improvement Initiatives
Instructor Name
Month Day, Year
A Theory of Change Drawn as a Tree: A Driver Diagram for Reducing Avoidable Day-of-Surgery Cancellations
Purpose
A driver diagram is a theory of change drawn as a tree. It shows what the team believes must change to reach its aim, and because every branch is a belief, every branch can be tested. In the improvement literature, the diagram links an aim to the system factors believed to drive it and then to specific changes, giving the team's reasoning a form others can inspect (Langley et al., 2009). This paper presents the driver diagram for the composite outpatient surgery department's aim: to reduce avoidable patient-readiness cancellations in general surgery and urology so that the share of cases lost this way falls to 1.5% within nine months, against an illustrative starting point of 3.8%. It then attaches measures to each level, so that the theory can be checked as the project runs.
How the Drivers Were Chosen
The primary drivers came from three sources: the reason codes in the department's cancellation log, a process map of patient preparation built with preoperative nurses, schedulers and surgeon office staff, and short interviews with twelve patients whose surgery had been canceled. Each primary driver is a system condition that, if absent, produces a known category of cancellation. The secondary drivers are the parts of the process that shape each primary driver. Change ideas are specific, testable actions. The link between preparation and fewer cancellations is supported by earlier work showing that patients seen in a preoperative clinic had fewer day-of-surgery cancellations (Ferschl et al., 2005), though this department's changes are lighter than a full clinic visit.
The Driver Diagram
Table 1 presents the diagram in rows, reading from left to right: each primary driver, its secondary drivers and the change ideas attached to them.
Table 1
Driver Diagram: Aim, Primary Drivers, Secondary Drivers and Change Ideas
| Primary driver | Secondary drivers | Change ideas |
|---|---|---|
| 1. Patients receive one clear, consistent set of instructions | Surgeon offices and the department use different wording; instructions given only on paper and in English; timing of instructions varies | Single shared instruction sheet agreed by offices and anesthesia; instructions sent by text in the patient's preferred language; teach-back at the office visit |
| 2. Every patient is reached before the day of surgery | Calls made the afternoon before during work hours; voicemail not followed up; wrong phone numbers | Readiness call two business days before; evening call hours twice a week; second attempt by text with a callback line; phone number confirmed at scheduling |
| 3. Medications are managed safely before surgery | Contradictory anticoagulant instructions; diabetes medication rules unclear; no single owner of the medication plan | Anesthesia-approved medication hold guide; pharmacist review for patients on anticoagulants; medication plan documented in one place |
| 4. Practical barriers are removed | No escort arranged; testing not completed; transport problems | Escort confirmed at scheduling and again on the readiness call; testing checklist tracked by schedulers; list of community transport options |
Aim (top of the tree): avoidable patient-readiness cancellations in general surgery and urology brought to 1.5% by month nine and held there, from an illustrative 3.8%.
Measures Attached to the Diagram
Each level of the diagram carries measures, so that the team can see whether a change moved its driver and whether the driver moved the aim.
Table 2
Measures Mapped to the Driver Diagram
| Level | Measure | Type | Data source |
|---|---|---|---|
| Aim | Avoidable patient-readiness cancellations as a percentage of scheduled cases, monthly | Outcome | Cancellation log with reason codes |
| Driver 1 | Share of patients who received the shared instruction sheet in their preferred language | Process | Scheduling record |
| Driver 2 | Share of patients reached by the readiness call at least one business day before surgery | Process | Call log |
| Driver 3 | Share of patients on anticoagulants with a documented medication plan reviewed by a pharmacist | Process | Preoperative record |
| Driver 4 | Share of patients with escort confirmed on the readiness call | Process | Call log |
| Balancing | Preoperative nurse time spent on calls per scheduled case | Balancing | Call log timestamps |
| Balancing | Cancellations for reasons outside the five avoidable categories | Balancing | Cancellation log |
The second balancing measure checks that cancellations are not simply being recoded into other categories.
Reading the Diagram as a Theory
The diagram makes four claims, one per primary driver: that consistent instructions, reliable contact, safe medication management and removed barriers together determine whether patients arrive ready. Each claim can fail. If the readiness call reaches nearly every patient but cancellations for fasting violations do not fall, then contact alone is not enough, and the content of the call or the instructions must be the problem. If medication-related cancellations fall only for patients seen by the pharmacist, the change works but needs wider reach.
The theory also has limits. It does not address cancellations caused by patients' new illnesses or by surgeon and room factors, which are outside the aim by definition. And the diagram assumes the drivers act independently, when in practice a patient who cannot be reached may also be the one without an escort. The team will watch for these overlaps in the reason codes.
Sequence of Testing
The team will not test every change at once. It will start with driver 2, reliable contact, because the call log shows it is a precondition for drivers 3 and 4, and because the evening call hours and earlier timing can be tested quickly by the preoperative nurses. The shared instruction sheet will be developed in parallel with the surgeon offices, since agreement will take several weeks. Medication and logistics changes will follow once the call process is stable. Each change will be tested through PDSA cycles with predictions recorded in advance, as the Model for Improvement expects (Langley et al., 2009).
Reed and Card (2016) caution that PDSA cycles are often treated as a simple checklist, when the method depends on iterative learning, realistic scale and the support needed to act on what each cycle reveals. The team will therefore keep a cycle log that records, for each test, the driver it targets, the prediction, what happened and the decision that followed. When a cycle's result contradicts the diagram, for example if earlier calls reach more patients but fasting cancellations stay flat, the team will revise the diagram itself rather than simply trying another change. Keeping the diagram current in this way is what makes it a working theory rather than a poster on the wall.
References
Ferschl, M. B., Tung, A., Sweitzer, B., Huo, D., & Glick, D. B. (2005). Preoperative clinic visits reduce operating room cancellations and delays. Anesthesiology, 103(4), 855-859. https://doi.org/10.1097/00000542-200510000-00025
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
What the NURS 8301 Week 6 instructions ask for
The Week 6 assignment typically has you build a diagram linking your aim to primary drivers, secondary drivers and change ideas, and to attach measures. Expect several pages in APA style with the diagram or a table version of it. Explain where the drivers came from, such as cause analysis, process maps or interviews, rather than a brainstorm alone. Keep primary drivers few and distinct. Attach an outcome measure to the aim, a process measure to each primary driver and at least one balancing measure. Then read the diagram as a theory: say how each branch could fail and what that would teach you. Close with the order in which changes will be tested.
How the NURS 8301 Week 6 example is put together
The opening section defines a driver diagram and states the aim. A section explains that drivers came from reason codes, a process map and twelve patient interviews, and cites Ferschl and colleagues. Table 1 lists four primary drivers, their secondary drivers and change ideas such as a shared instruction sheet, evening calls, a pharmacist review and escort confirmation. Table 2 maps the outcome, four process measures and two balancing measures to their sources. A theory section explains how each branch could fail and notes overlaps among drivers. A testing section starts with reliable contact, runs the instruction sheet in parallel and adds a cycle log in response to Reed and Card.
Reading the NURS 8301 Week 6 rubric
Driver diagrams are generally assessed on the logic linking aim, drivers and changes, the source of the drivers, the measures attached and the use of the diagram as a testable theory. Logic credit rewards drivers that are distinct and clearly connected to the aim. Source credit goes to diagrams built from cause work rather than guesswork. Measures earn credit when each level has one and balancing measures are included. Theory credit rewards stating how branches could fail. A readable diagram, correct references and credible sources earn the rest, and faculty tend to credit a testing sequence that explains why one driver comes first.
NURS 8301 Week 6 help from the desk
Driver diagrams lose marks when primary drivers overlap or when change ideas are listed with no link to a driver. Another common loss is a diagram with no measures, so none of its claims can be checked. Some papers treat the diagram as finished when it should change as tests reveal what works. Others list too many drivers for a small team to address. Build drivers from cause work, keep them distinct, attach measures at every level, state how each branch could fail and sequence testing. The desk can draft a driver diagram for your own aim. Test each branch by asking whether achieving it would plausibly move the aim; if not, it probably belongs elsewhere.
Get a NURS 8301 Week 6 example written to your instructions
Include the aim your instructor approved, any cause analysis already done and the Week 6 template or rubric. A custom driver diagram and narrative arrive in 24-48h, the first free, delivered as a figure you can edit, with measures placed on the aim and on each primary driver.
More NURS 8301 papers and DNP samples
- NURS 8301 Week 1: Improvement History Post
- NURS 8301 Week 2: QI Framework Comparison Paper
- NURS 8301 Week 3: QI Problem and Aim Statement
- NURS 8301 Week 4: QI Culture and Readiness Post
- NURS 8301 Week 5: QI Framework Selection Paper
- NURS 8301 Week 7: Stalled Adoption Post
- NURS 8301 Week 8: PDSA Cycle Plan
- NURS 8301 Week 9: Spread and Sustainment Post
- NURS 8301 Week 10: Executive QI Proposal
- NURS 8301 Week 11: QI Leadership Reflection
- NURS 8310 Week 6: Predictive Value Post
- NURS 8250 Week 6: Middle-Range Theory Application
- NURS 8512 Week 6: DNP Setting and Stakeholder Section
- NURS 8211 Week 6: Missing Data and Bias Post
NURS 8301 Week 6 questions, answered
What is the difference between primary and secondary drivers?
Primary drivers are the few system components that most directly influence the aim; secondary drivers are the more specific factors that influence each primary driver, and change ideas act on secondary drivers. In the sample, team ready is primary, and an agreed arrival time for surgeon and anesthesia is one of its secondary drivers. Keeping the levels distinct is what lets a reader follow a change idea back to the aim.
Does a driver diagram need measures on it?
Many course templates ask for them, and placing measures on the diagram shows what each level claims. The sample puts the outcome measure on the aim, one process measure on each primary driver and a balancing measure apart from the tree. Detailed definitions, data sources and collection plans usually belong to a separate measurement stage, so the diagram names each measure without specifying it fully.
Where can I find a free NURS 8301 Week 6 sample paper?
The complete driver diagram paper, with both tables and the testing sequence, can be read on this page free. A diagram for your own aim can be requested.
What are the primary drivers in the NURS 8301 Week 6 diagram?
Consistent instructions, reliable contact with every patient before surgery, safe medication management and removal of practical barriers such as missing escorts and testing.
Why does testing start with reliable contact?
The call log shows it is a precondition for the medication and logistics drivers, and the evening call can be tested quickly by the preoperative nurses.