NR-707A Week 2 The Implementation Narrative: How to Write It

What NR-707A Week 2 asks for

Consider two sentences describing the same event. The first says that staff education was completed and the protocol went live. The second says that the education session ran twice, on two consecutive Tuesdays, reaching 19 of the 27 nurses assigned to the unit, that the remaining eight received a recorded version and a competency check completed over the following ten days, and that the protocol was activated in the record on the second Monday of the block. Both are true. Only one can be evaluated, and only one lets a reader understand later why uptake on nights lagged. That difference is the entire content of this stage.

The boundary, restated because it governs the whole session. Every hour you spend implementing, every entry in your practicum hour log, every count of encounters, every site form and every evaluation completed about you belongs to you and to the people who verify it. None of it is ever drafted, reconstructed or estimated with assistance from anyone. What is legitimately supported here is the writing craft that turns work you personally did into a doctoral-quality narrative: sequencing, specificity, analytic framing and register. Every patient or staff detail entering that narrative is de-identified before it reaches the page.

Doctoral narrative differs from professional reporting in one respect worth stating. A workplace status report is written to reassure. A doctoral implementation narrative is written to be examined, which means it records what did not go as planned with the same precision as what did. A reader who finds an account in which nothing deviated will not conclude that the implementation was flawless; they will conclude that the author did not look.

Expect the deliverable to be a written section, sometimes framed as a progress narrative, sometimes as part of a running project document, and often paired with a discussion post about early implementation. Treat the section as a draft chapter of the final project document rather than a disposable assignment. Written once, properly, at the time, it will be edited rather than rewritten at the end of the block.

The NR-707A Week 2 method, step by step

Six moves for writing an implementation narrative that holds up under examination.

1. Build the timeline before you write prose

   List every event of the block in date order from your working record: preparation completed, materials distributed, education delivered, activation, first use, first problem, first adjustment. The prose then narrates a spine that already exists.

2. Attach a count to every claim of activity

   How many sessions, how many attendees out of how many assigned, how many eligible cases, how many times the change was applied. A verb without a number is an impression, and impressions do not survive a doctoral reading.

3. Name roles rather than people, consistently

   Unit educator, charge nurse, informatics analyst, pharmacy lead. Consistent role naming keeps colleagues protected, makes the account readable to an outside reviewer, and quietly demonstrates that you are writing about a system.

4. Record decisions with the reason available at the time

   When the sequence changed or a component was deferred, write what was known when the decision was made, not what you learned later. Retrospective tidiness destroys exactly the reasoning trail an examiner wants to follow.

5. Separate what was delivered from what was received

   Delivery is an activity you performed; reach is what landed with the people or patients concerned. Keep the two in different sentences, because conflating them is the most common way an implementation narrative overstates itself.

6. Close each passage with an analytic sentence

   After the events, one sentence that says what the pattern means for the implementation: which assumption held, which did not, and what you changed as a result. Narrative without interpretation is a log; a doctoral section needs both.

A layout that makes an implementation narrative examinable

Our frame for an early implementation narrative, sized for roughly 1,300 to 1,600 words plus a timeline. 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 implementation writing

Dates are evidence. A narrative in which events carry actual dates reads as contemporaneous, and one written in vague sequence markers reads as reconstructed. Use the week of the block or the calendar date consistently, and pick one convention rather than alternating.

Denominators travel with counts. Nineteen nurses attended is half a fact. Nineteen of 27 assigned to the unit is a fact with a meaning, and it is the version that lets you say something about coverage later.

Attribute the framework you are implementing under. If your project uses a named implementation or improvement model, its stages should be visible in how you organize the account, and it should be cited with a year. A framework mentioned in the proposal and abandoned in the narrative is a gap a committee will notice.

Write in the past tense and the active voice. The unit educator delivered two sessions is clearer and more accountable than two sessions were delivered. Passive constructions in implementation writing usually conceal who did something, which is precisely what a reader wants to know.

De-identify without vagueness. Removing identifiers does not mean removing detail. A 62-year-old admitted on the fourth becomes an eligible medical admission in the first week; the clinical specificity that matters survives, the identifying specificity does not.

Five mistakes that cost points in this week's territory

• Narrative written from memory. It reads differently, it loses the counts, and at doctoral level the difference is obvious in the first paragraph.
• Activity without reach. Reporting what you delivered while omitting what landed overstates the implementation and undermines your later data.
• Cleaning up the decisions. Rewriting a choice so it looks better informed than it was destroys the reasoning trail that makes the account scholarly.
• Naming individuals. Colleagues and patients belong in the account as roles and aggregates, never as identifiable people.
• Pure chronicle. Events with no interpretation is a log; the doctoral requirement is a narrative that also judges.

Before you submit

• Every event carries a date and, where activity is claimed, a count with a denominator
• Delivery and reach appear as separate statements
• Each decision records the information available when it was made
• People appear as roles; no patient or staff identifiers survive anywhere in the text
• At least one deviation from plan is recorded plainly
• Each major passage closes with an analytic sentence, not a summary

Questions students ask about this stage

Keep going