NR-707B Week 2 Workflow and Readiness Analysis: How to Write It

What NR-707B Week 2 asks for

A medical-surgical charge nurse once described a new screening step as "forty seconds that arrive at 0730." That sentence is a better readiness analysis than most of the paragraphs written about the same change, because it locates the burden in time and in the shift, and it implies the failure mode. Forty seconds is nothing at 1400 and impossible at 0730 when four admissions are landing at once. The writing task at this stage is to produce that level of specificity in a document, systematically, for every point where the change touches work that already exists.

The boundary that governs this manual. The hours you spend on the unit, the log that records them, encounter tallies, site paperwork, and any evaluation signed by a preceptor or mentor are your own record of your own work, verified by your school and your organization. They are never drafted, reconstructed, or estimated with help of any kind. The written layer is what can be supported: how a workflow analysis is organized, how a readiness assessment is argued from what you observed, how a barrier is described so that a reader can weigh it. Everything drawn from real practice enters your writing de-identified, at the level of roles and aggregates.

Readiness at doctoral level is not a mood measurement. It is a structured judgment about whether a setting has the capacity, the authority, the tools, and the attention to sustain a change, and the useful version of it names each of those separately. Capacity is staffing and time. Authority is whether someone with the standing to require the change has actually required it. Tools are whether the build exists in the record system, whether the telehealth queue has the right disposition codes, whether the printed material is where the nurse stands. Attention is whether three other initiatives are competing for the same huddle. A document that reports all four honestly is far more valuable than one that reports enthusiasm.

Expect the deliverable to be an analytic write-up of the setting and the workflow, often with a process map or a table, sometimes folded into a broader progress document, and frequently accompanied by a posted discussion where classmates compare barriers across settings. If your section runs that discussion, write it as final copy: posts do not reopen after submission in Canvas, and a barrier described vaguely in week two is a barrier you will have to describe twice.

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

Six analytic moves for turning what you saw on the unit into a document a reader can weigh.

1. 1. Map the current state before you draw the future one

   Write the existing sequence step by step as it actually runs, including the workaround everyone uses and nobody documents. A future-state map drawn against an idealized current state describes a change to a process that does not exist.

2. 2. Locate the insertion point in time, not in the diagram

   Say when in the shift the new step lands and what else is happening then. Forty seconds at shift change and forty seconds mid-afternoon are different interventions, and the distinction predicts adoption more reliably than any attitude survey.

3. 3. Quantify what the change displaces

   Every added step removes something, even if the something is slack. Name what gets shortened or skipped when the unit is busy. A change that has no displacement cost is usually one that is not actually being performed.

4. 4. Separate the four dimensions of readiness

   Report capacity, authority, tools, and attention as distinct findings rather than as one paragraph about buy-in. A setting can be enthusiastic and entirely unready, and only the separated version tells a reader which lever to pull.

5. 5. Attribute each barrier to a level of the system

   Individual, team, unit, organization, or external. The level determines who can remove the barrier, and a barrier written without its level is a complaint. A missing order set is an organizational item; a nurse who was never told is a team communication item.

6. 6. Convert each barrier into a written mitigation with an owner

   Barrier, level, mitigation, owner by role, and the date by which you will know whether it worked. A barriers list with no owners is a list that will still be true in week seven, and your closing report will have to say so.

A layout for a workflow and readiness write-up

Our frame for this stage's analytic document, sized for roughly 1,200 to 1,500 words plus a process map. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.

Evidence craft for readiness and workflow writing

Observation is data when it is written like data. "Staff seemed receptive" is an impression. "Of the six nurses present at three consecutive morning huddles, four asked where the form lived and two had not heard of the change" is an observation with a denominator, and it belongs in a doctoral document. Count what you saw, say across how many occasions, and let the reader form the judgment alongside you.

Use a named readiness or determinants framework and use it consistently. Implementation literature offers structured ways to categorize the factors that help or hinder a change, and adopting one gives your barriers section a spine a faculty reader recognizes. Cite it with a year, use its actual categories rather than renaming them, and do not mix two frameworks' vocabularies inside the same table.

Distinguish anticipated barriers from encountered ones. The barriers you predicted in a proposal and the ones the unit actually produced are different classes of evidence, and a strong write-up marks which is which. An anticipated barrier that never materialized is worth a sentence, because it tells the reader your prediction model was imperfect and that you noticed.

Keep improvement language out of research territory. You are describing a local process and a local setting. Nothing here establishes what would happen elsewhere, and the write-up should not imply otherwise. Where a determination about human subjects oversight applies at your organization, describe the process you followed rather than forecasting its result.

De-identify people by role, always. On a thirty-four bed unit with two night charge nurses, "the night charge nurse who objected" is identifying. Write "one of the charge nurses raised" or aggregate to "concerns were raised at two of four huddles." The same discipline applies to telehealth staff, where small teams make individuals easy to recognize.

Five mistakes that cost points in this week's territory

• A future-state map with no current state. Without the existing sequence, the reader cannot see what changed or judge whether the change is plausible.
• Readiness reported as one adjective. Receptive, engaged, and supportive are moods. Capacity, authority, tools, and attention are findings.
• Barriers with no system level. If the write-up does not say who could remove a barrier, it cannot say anything about whether it will be removed.
• Ignoring the workaround. Every established process has one, and the change either uses it or fights it. Pretending it is absent guarantees a surprise in week four.
• Impressions without denominators. Two comments from two nurses is a small observation honestly reported; "the staff feel" is an unsupported claim about a population.

Before you submit

• The current-state process is written as it actually runs, workarounds included
• The insertion point is located in the shift, with its time cost stated
• What the change displaces under load is named explicitly
• Capacity, authority, tools, and attention are reported as four separate findings
• Every barrier carries a system level, an owner by role, and a check date
• All observations appear with counts and occasions, and all people appear as roles

Questions students ask about this stage

Keep going