NR-446 Week 7 Leading a Unit Change: How to Write It

What NR-446 Week 7 asks for

What does a change attempt look like while it is quietly failing? Sit at the back of a staff meeting on a Tuesday afternoon, in the borrowed conference room where the unit holds them, half the chairs filled by people who came off nights and want to go home. The educator has ten minutes and a laminated card. From Monday, she says, the handoff will happen at the bedside with the patient awake and included, and here is the card that lists what to say. Everyone nods. Nobody asks a question. Two weeks later the handoff is back at the nurses' station where the coffee is, the cards are in a drawer, and when someone asks why, the answers are all logistical and none of them were ever solicited: the rooms are shared, the mornings are stacked, the card takes four minutes nobody has. Nothing about that change was wrong except the changing of it, and this week's writing is where you learn to build the other version.

What separates a proposal from an opinion? Three things a rubric can find. The first is an evidenced gap: not the unit should communicate better, but a specific practice you observed, held against a specific standard or published expectation, with the distance between them stated. The second is an intervention somebody else has already tested, cited, so that your proposal is an application of evidence rather than an invention of yours. The third is a change framework used as a working tool, its stages filled with your unit's actual people and messages and obstacles, which is where the week separates students who read the chapter from students who used it. Papers that carry all three read as management. Papers that carry only conviction read as a complaint with citations attached.

What has to stay on the page rather than on the floor? All of it. This is a written proposal for a change you are not authorizing, launching or running, and that distinction should be visible in your grammar as well as your intent. You are writing what a change would require, who would own each part, and how it would be judged, in the conditional; you are not reporting an implementation, and you must not describe having rolled anything out on a unit where you are a guest. The observation feeding the proposal is de-identified as always, roles rather than names, no facility identifiers beyond what your section permits. Real change on a real floor belongs to the people who work there and to the approvals they answer to, and a paper that respects that boundary loses nothing; the reasoning is what gets graded.

The NR-446 Week 7 method, step by step

Six moves for writing a change proposal a charge nurse would read twice.

1. Start from a gap you can evidence, not a grievance you can feel

   Name the current practice as you observed it, name the standard or published expectation it falls short of, and state the distance in one sentence. Everything downstream inherits its credibility from this pairing, and a gap that rests only on your irritation cannot support a proposal.

2. Borrow an intervention that already has evidence behind it

   Find published work where someone tested a fix for this kind of gap, in a setting close enough to argue transfer, and adopt it rather than inventing something. Cite it, say what it changed, and say plainly which parts of it your unit could not run as studied.

3. Choose a change model for fit and then actually fill it in

   Pick from the families your course teaches, justify the pick against the shape of this change in two sentences, and then populate every stage with your unit's specifics: who is spoken to, in what order, with what message, against what resistance. An unfilled model is a citation, not a plan.

4. Do the stakeholder arithmetic before you write the sequence

   List the roles the change touches, and beside each one write what it costs them and what it buys them, honestly. Night shift, techs, the unit secretary and the providers all pay different prices, and a plan that has not priced them will be surprised by the people who quietly refuse.

5. Write influence, not authority

   A senior student cannot mandate anything, so the leadership in your plan has to be the kind that works without a title: early conversations with the informal leaders, the one nurse whose adoption moves six others, evidence shared in a form busy people will read, a request routed to the person who does hold the authority. Name that person by role and name what you would ask them for.

6. Attach a measure and a date the plan gets looked at again

   One thing that would be counted, one comparison that would give the count meaning, one interval at which someone reviews it, and one sentence on what would keep the change alive after attention moves on. Changes without a review point revert, which is the story the failing example above is telling.

A layout and word budget for a unit change proposal

Our frame for this stage, sized for roughly 1,000 to 1,300 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 change writing

The gap and the fix need separate sources. One body of work establishes that this kind of shortfall matters; a different one establishes that this kind of intervention moves it. Students routinely cite only the first and then assert the second, which leaves the actual proposal uncited at the exact point a grader is looking hardest.

Credit the change theorist, then stop quoting. Name the model and its originator once, define its stages in your own compact sentences, and spend the rest of the section on your unit. A page of paraphrased theory with a unit sentence bolted to the end inverts the ratio the rubric wants.

Resistance claims are analysis and deserve support. Saying night shift will resist because the change adds documentation is a prediction; anchor it in what you observed about workload at night, or in what the implementation literature reports about added charting burden, and it becomes a finding. Cite one source on why practice changes fail and your resistance section stops sounding like guesswork.

Write the whole plan in the conditional. Would be piloted, would be reviewed, would ask the manager for. The tense is not timidity; it is accuracy about a proposal, and it keeps the paper from implying you ran something on a unit you were visiting. Reserve past tense strictly for what you observed.

Five mistakes that cost points in this week's territory

• A change born of preference. Proposals that begin with what would make the shift easier for you, rather than an evidenced gap, lose the analysis rows before the plan starts.
• A model chosen for its fame. Naming the best-known framework and then not filling its stages with unit specifics is decoration, and every grader in this course has read forty of them.
• Resistance read as ignorance. Treating objections as things to be educated away, rather than as accurate reports of what the change costs, is the reasoning error the week exists to correct.
• The launch without the after. A plan that ends at go-live has proposed an event rather than a change, and the sustainment sentence is the cheapest point in the assignment to lose.
• Success with nothing attached to it. Improved teamwork and better communication cannot be reviewed at an interval; if nobody could count it, the plan cannot be judged and neither can your reasoning.

Before you submit

• The gap is stated as observed practice against a cited standard, de-identified
• The intervention is borrowed from published work, not invented, and its source is named
• The change model is justified for fit and every stage carries unit specifics
• Each affected role has both its cost and its benefit written down
• The leadership described is influence at student scope, with the authority request routed by role
• One measure, one comparison, one review interval and one sustainment mechanism appear

Questions students ask about this stage

Keep going