NR-723 Week 7 The Data to Decision Memo: How to Write It

What NR-723 Week 7 asks for

Eighteen months of summative simulation scores sat in a shared drive at one academic medical center, tidily organized by cohort. Every scenario had been run, every checklist scored, every file saved. When a new education director asked what had changed as a result, the answer was that the scenario order had been adjusted once, informally, because a facilitator thought it flowed better. Nobody could say what the data had shown, who had looked at it, or whether the adjustment had been re-measured. The program had a measurement system and no improvement system, and those are different things that people routinely confuse.

The written work at this stage is an interpretation and a decision, in that order. Interpretation means saying what the numbers mean rather than restating them: not the pass rate was 71 percent, but 24 of 34 residents met the escalation criterion, that the ten who did not clustered in one cue-recognition item, and that the pattern is consistent across two cohorts rather than a one-time result. Decision means naming what will change, at what level, owned by whom, effective when. A memo that ends in further monitoring is warranted has produced no improvement and will be scored as such.

The analytic discipline this stage rewards is caution about causes. When a result moves, the temptation is to attribute it to the intervention. Educational leaders should hold the same skepticism a quality improvement analyst holds: cohorts differ, faculty change, the scoring may have drifted, an unrelated policy may have shifted practice on the units where learners work. Say what else could explain the movement before you claim it as an effect of your curriculum change, and prefer several data points over two, because two points is not a trend no matter how encouraging the direction.

Expect this deliverable to be a memo, a report to a committee or an improvement plan of 900 to 1,300 words. Its reader is a group with authority and no patience: a curriculum committee, a practice council, a department leadership team. That reader wants the recommendation early, the evidence compact, and the ask explicit. If a discussion runs alongside, post the decision rather than the data, because the decision is what your colleagues can respond to, and write it as final copy since posts do not reopen after submission in Canvas.

The NR-723 Week 7 method, step by step

Seven moves for turning an evaluation result into a documented improvement.

1. Find out from the rubric whether interpretation or action carries the weight

   Some stages score the analysis of results, some score the improvement plan, and the two need very different word allocations. Mark the rows, price them, and write to the distribution rather than to your own interest.

2. State the result with its base and its window

   Twenty-four of 34 residents in the spring cohort, measured at the end of orientation, against a criterion set the previous year. Bases and dates are what let a reader judge whether the number is meaningful, and proportions alone hide both.

3. Disaggregate before you interpret

   Look at the result by item, by group, by site, by cohort. The useful finding is almost never in the total. It is in the one criterion where everyone struggled or the one group whose results diverge from the rest, and that is what points to an actionable cause.

4. Write the competing explanations before your preferred one

   Scoring drift, cohort composition, a facilitator change, a change in staffing on the units, a small denominator. Naming these first is what makes your eventual interpretation credible rather than promotional.

5. Choose an action proportional to the evidence

   A single cohort's dip justifies a targeted change and closer monitoring. A two-year pattern across cohorts justifies a curricular change that costs faculty time. Overreacting to noise is as much an error as ignoring a signal, and doctoral readers score the proportionality.

6. Attach a name, a date and an authority to the decision

   Approved by the curriculum committee on a stated date, owned by a named role, effective in a stated term. Without those three, no reader can tell whether a decision was made or merely discussed, and the loop is not documented.

7. Specify the re-measurement before you finish

   Same instrument, same collection point, stated cohort, and the threshold that would count as improvement. A change with no re-measurement plan cannot be evaluated, which means the next cycle begins in exactly the position this one did.

A layout and word budget for a decision memo

Our frame for a data-to-decision report to a committee, sized for roughly 900 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 improvement reporting

Name your improvement framework and use its vocabulary. Structured improvement approaches exist and are published; saying which one you are working within, with its year, tells a reader what kind of cycle you are describing and lets them check your steps against a standard rather than against your instincts.

Two points are not a trend. Say how many cycles of data you have and let that number set the strength of your language. A change observed once is a signal to watch. A change sustained across three cohorts is a basis for a curricular decision, and the difference belongs in the verb you choose.

Distinguish process measures from outcome measures. How many facilitators completed calibration training is a process measure. Whether resident escalation performance improved is an outcome measure. Improvement work fails most often because the process moved, the outcome did not, and nobody separated the two in the report.

Report what was actually delivered. If the revised simulation sequence ran in five of eight cohorts because of scheduling, say so. Fidelity to the change is the first thing to check when a result disappoints, and a memo that omits it invites the wrong conclusion about the intervention.

Keep the visual honest if you include one. A run chart with a truncated axis manufactures a trend that is not there. Show enough time before the change to make the baseline visible, mark when the change took effect, and label the axis with the base as well as the rate.

Five mistakes that cost points in this week's territory

• Data with no decision. A report that ends in continued monitoring has documented a measurement system, not an improvement system, which is the exact failure this stage exists to correct.
• Causal claims from one cohort. Attributing a movement to your change without weighing scoring drift, cohort differences and small denominators is the most common analytic error here.
• Recommendation buried on page three. Committee readers decide in the first paragraph whether to keep reading, and the ask belongs there.
• No owner or date. An action assigned to the education team, at some point, is not a decision anyone can be held to.
• Improvement plans with no re-measurement. The loop is only closed when the next measurement is specified, and stopping at the action leaves the cycle open.

Before you submit

• The recommendation appears in the first paragraph
• Every number carries its base, its instrument and its collection window
• The result is disaggregated to the level where the finding actually lives
• Competing explanations are named before the preferred interpretation
• The decision carries an approving body, an owner and an effective date
• A re-measurement is specified with its instrument, cohort and timing

Questions students ask about this stage

Keep going