NR-707B Week 5 Unintended Consequences: How to Write It

What NR-707B Week 5 asks for

A discharge-education change on a medical-surgical unit did exactly what it was designed to do and produced a complaint from the pharmacy. The new teaching step required an updated medication list at the moment of discharge, which meant the pharmacist was being paged during the two hours when they were verifying overnight orders. The project's own measures looked excellent. The pharmacy's turnaround time did not. Nobody had counted that, because nobody had chosen it as a balancing measure, and the first written record of it was an email from a director. That is the failure this stage exists to prevent.

The boundary that governs this manual. Practicum hours, the hour log, encounter counts, site paperwork, and any evaluation completed by a preceptor or mentor are your own record of your own work, verified by your school and your organization, and they are never drafted, estimated, or reconstructed with help. What can be supported is the written layer: how a balancing analysis is structured, how an unintended effect is described proportionately, how an escalation is documented in scholarly prose. Real events enter your writing de-identified, as roles, counts, and aggregates, and a safety concern is raised through your site's own reporting route before it is ever a paragraph in an assignment.

There is a category distinction here that doctoral readers watch for. An unintended consequence is an effect of your change on some other part of the system: workload, turnaround, satisfaction, a downstream process. A safety event is something that harmed or could have harmed a patient, and it belongs first to your organization's incident reporting system and your mentor, not to your paper. Your academic writing about it describes the process you followed, not a clinical adjudication you are not positioned to make. Conflating the two, or writing about a safety event as though it were an interesting data point, is one of the few genuinely serious errors available at this stage.

Expect the deliverable to be an analytic section on balancing measures and unintended effects, often inside a mid-to-late progress document, sometimes with its own table, and often a posted discussion where classmates surface the consequences they did not anticipate. A 192-hour block has enough live weeks behind it by now that these effects are visible; smaller blocks frequently end before the second-order effects appear at all, which is one of the real advantages of the hours you are carrying.

The NR-707B Week 5 method, step by step

Six analytic moves for reporting what your change did besides what it was meant to do.

1. 1. Interrogate the balancing measure you already chose

   Report it with the same rigor as the outcome: counts, denominator, window, direction. A balancing measure that appears only as a reassuring sentence was never a measure; it was a promise made in week three.

2. 2. Trace the workflow one step downstream and one step upstream

   Ask who receives the output of your change and who supplies its input. Second-order effects almost always live in those two places, and a systematic look at them is a doctoral move that a project summary never makes.

3. 3. Quantify the burden the change created

   Minutes per case, pages per shift, additional handoffs, extra clicks in the record. Burden written in units is a finding; burden written as "staff report it is time-consuming" is a rumor with a citation.

4. 4. Separate signal from noise before you name a consequence

   Two bad weeks in a small denominator is often variation, not effect. Say how many periods you looked at, what the pre-change range was, and why this movement is or is not outside it. Overclaiming a harm damages credibility as much as ignoring one.

5. 5. Route safety concerns through the site, then describe the route

   Any event with patient safety implications goes to your organization's reporting system and to your mentor first. Your written work then records that the process was followed, on what date, to whom by role, without adjudicating cause or outcome.

6. 6. Decide and state what changes as a result

   Accept the trade-off with a written rationale, modify the change, or pause a component. Each is legitimate. What is not legitimate is documenting a consequence and continuing unchanged without saying why that was the right call.

A layout for a balancing and consequences section

Our frame for this stage's written work, sized for roughly 1,100 to 1,400 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

Evidence craft for writing about consequences

Proportion is the whole skill. A consequence reported without magnitude reads as either alarmism or dismissal. Write how large, across how many cases, over what period, compared with what it was before. Three additional pages per night shift across two weeks is a claim a reader can weigh; increased burden on pharmacy is not.

Attribute cautiously and say so. Your evaluation cannot separate your change from everything else that happened on the unit during the same weeks. If census rose, if two experienced nurses left, if another initiative launched, name those and say they are rival explanations you cannot exclude. That sentence costs nothing and buys the reader's trust in every other sentence.

Keep improvement evaluation out of research claims. Nothing here establishes causation the way a trial would, and nothing here generalizes beyond your setting. Write local, temporal, and plausible rather than caused and demonstrated. Where a determination about human subjects oversight applies at your organization, describe the process you followed rather than predicting its outcome.

Cite the literature on the consequence, not only on the intervention. Alert fatigue, documentation burden, workload shifting, and unintended effects of process change all have published bodies of work behind them. Bringing one into this section shows that you recognized the phenomenon rather than merely encountering it, and it is the easiest scholarly upgrade available in this stage.

De-identify staff at the aggregate level. On a unit where three people staff the evening shift, "the evening nurse said" is identifying. Write "concerns were raised by evening staff on two of the three weeks observed." The same care applies to a small telehealth team, where a single named role can identify a person.

Five mistakes that cost points in this week's territory

• A balancing measure promised and never reported. The reader will look for it, and its absence reads as a result you did not like.
• Consequences described without magnitude. Adjectives cannot be weighed, and a doctoral reader weighs everything.
• Calling two bad weeks an effect. Small denominators move on their own, and overclaiming harm is as damaging as concealing it.
• Treating a safety event as a data point. It goes through the site's own reporting route first, and your writing records that the route was followed.
• Documenting a problem and changing nothing. A decision, even the decision to accept a trade-off, has to appear with its reasoning.

Before you submit

• The balancing measure is reported with counts, denominator, window, and direction
• One step upstream and one step downstream have each been examined explicitly
• Added burden appears in units rather than adjectives
• Rival explanations for any movement are named and not dismissed
• Any safety concern is recorded as having gone through site channels, with no clinical adjudication
• A decision with a date and a rationale closes the section

Questions students ask about this stage

Keep going