NR-539 Week 2 Building the Intervention Logic Model: How to Write It

What NR-539 Week 2 asks for

Take a pediatric weight-management effort in a community clinic that serves roughly 900 children aged five to eleven. The activity everybody reaches for is a nutrition class for parents. Write it into a chain and the problem shows itself instantly. Inputs: a dietitian at eight hours a week, a borrowed room, printed materials in two languages. Activities: twelve sessions delivered over the program period. Outputs: sessions delivered, caregivers attending, materials distributed. Short-term outcomes: caregivers can name portion targets and report changed purchasing. Intermediate outcome: reported daily sugary drink servings fall. Health outcome: body mass index percentile distribution shifts. Written out that way, the weak joint is visible before a dollar is spent, because nothing in the chain gets a family from knowing a portion target to buying different food when the corner store is the only store within a mile.

That is exactly what this stage is scored on. Rubric rows about program logic, theoretical framework or intervention design are asking whether each arrow is defensible on its own, not whether the boxes are filled. A model where a single arrow jumps from a teaching session to a clinical outcome has skipped the two links where population programs most often fail, and a grader who has read two hundred of these papers finds that jump in the first minute.

Deliverables here usually pair a visual model with a narrative that walks each link. Some sections ask instead for a written framework section describing the behavior-change or program-planning theory you are borrowing. If a discussion runs alongside, use it to test one arrow rather than to summarize the whole model, and write it as final copy, since posts do not reopen after submission in Canvas.

The NR-539 Week 2 method, step by step

Six moves that turn a set of boxes into an argument.

1. Draft the chain backwards from the outcome you committed to

   Start at the health outcome, ask what would have to change first for it to move, then what would have to change before that. Working forwards from activities produces a list of good ideas; working backwards produces a plan whose parts are necessary.

2. Separate outputs from outcomes and never let them merge

   An output is something your program produced: sessions held, families enrolled, texts sent. An outcome is something that changed in the population. Counting sessions and calling it an outcome is the single most common structural error in this course.

3. Attach a mechanism to every arrow

   Under each transition write one sentence naming why it should happen and what evidence supports it. Reminder messages change refill behavior through prompting and reduced planning burden, which is a mechanism; awareness leads to behavior change is not one, it is a wish.

4. Name the theory you are borrowing and use its vocabulary consistently

   Whether you take a behavior-change model, a program-planning framework or an implementation framework, say which one, cite it, and then use its actual constructs in your headings. Borrowing a theory and then never using its terms again reads as decoration and scores as such.

5. Mark the assumptions and the external factors explicitly

   Every model rests on conditions you do not control: continued funding, a school partner staying open, an interpreter being available, families having a working phone number. Listing them is not weakness, it is the part of the model that graders read as maturity.

6. Test the weakest arrow in writing before you submit

   Pick the link you would least like to defend, state the rival explanation, and either fix the model or say plainly what you will monitor to catch the failure early. A model with one honestly interrogated joint outscores a tidy one with six unexamined joints.

A layout and word budget for a logic model narrative

Our frame for the narrative that accompanies a model, sized for roughly 1,100 to 1,400 words with the visual carrying the detail. It is our own outline rather than anything the university issues, and your week's scoring guide outranks it wherever they disagree.

Evidence craft for program logic

Cite the framework where you first use it, not only in the reference list. Planning frameworks and behavior-change theories have authors, editions and revision histories, and naming the source with a year in the sentence converts a borrowed structure into a supported choice. A model presented as though it were self-evident forfeits the theoretical-basis row before the content is read.

Support the arrows, not just the boxes. The literature you cite in this stage should be about whether the mechanism works, not about whether the problem is serious. A study showing that recall messaging improved follow-up attendance in a pediatric clinic supports an arrow. A prevalence figure supports nothing about your design.

Quantify inputs in units a manager would recognize. Eight dietitian hours a week for twelve weeks, one room for two hours every other Tuesday, 400 printed booklets. Categories such as staff support and adequate materials cannot be costed later, and week four will ask you to cost them.

Say what the model cannot deliver in the time available. Body mass index percentile distributions do not move in eight weeks, and claiming they would is a credibility loss that a single honest sentence prevents. State which outcome is measurable inside the window and which is the longer-run claim the short-term measures are standing in for.

Five mistakes that cost points in this week's territory

• Boxes with no arrows argued. A filled template is not a logic model; the reasoning between columns is the graded part.
• Outputs promoted to outcomes. Sessions delivered and pamphlets handed out tell the reader about your effort, not about the population.
• A theory named once and abandoned. If the framework's constructs never appear again, the citation is doing no work.
• Assumptions omitted entirely. A plan that depends on a school partner and never says so looks either naive or evasive.
• An outcome timescale nobody could meet. Promising a measurable clinical shift inside a short program window invites the grader to disbelieve the rest.

Before you submit

• The chain was drafted backwards from the outcome and reads forward cleanly
• Outputs and outcomes appear in separate columns with no overlap in wording
• Each arrow carries one mechanism sentence with support behind it
• The framework is named, dated and used in the headings that follow
• Inputs are stated as quantities that could later be costed
• Assumptions and external factors are listed separately from each other

Questions students ask about this stage

Keep going