NR-669 · Week 7 of 8 · Stakeholder presentation design

NR-669 Week 7 Stakeholder Presentation Design: How to Write It

The short answer

A talk is not a paper read aloud. Its unit of measurement is minutes, and stage seven of NR-669 is where you build a presentation for people at the organization who can actually act: a structure that leads with the ask, slides that carry one idea each, speaker notes written in speech rather than prose, and a rehearsal against a clock. Students lose points here they did not expect to lose. Your section may print this as NR 669 or NR669; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.

NR-669 Week 7 grading scale at Chamberlain, the criterion levels this assessment is scored on, from Chamberlain Tutors
How Chamberlain grades NR-669 Week 7, visualized by Chamberlain Tutors.

What NR-669 Week 7 asks for

Picture the room. A clinic operations committee meets for fifty minutes, works through six agenda items, and has given you twelve. The medical director wants to know whether the newborn follow-up visit change is worth keeping. The practice manager wants to know what it costs in staff time. The front desk lead, who actually made it work, wants to know whether anyone noticed. You have one figure worth showing and one request worth making. A presentation built for that room is a completely different artifact from a paper, and building it as a summary of the paper is the standard mistake.

Structure follows the audience. In front of people who can authorize something, the professional convention is to state the request early rather than to build to it, because a group that hears the ask in the first two minutes spends the rest of the time evaluating it rather than waiting for the point. Then the evidence: the problem with its number, what was done, what happened, honestly. Then the decision you want, with the specific form it would take.

Timing is the constraint students most underestimate. Spoken delivery runs somewhere near 120 to 150 words per minute, which makes twelve minutes about 1,500 to 1,800 spoken words, and that is before questions. A deck that would take twenty-five minutes to present in twelve gets delivered at speed, which drops comprehension exactly where the argument matters. Building to the clock is a design activity, not a rehearsal problem. Where a section runs a discussion at this stage, it usually asks about your audience or your ask. Post it as final copy, since Canvas responses do not reopen.

Where the boundary sits in a presentation stage. The 168 clinical hours, the immersion, the relationships at the organization and the delivery of the presentation itself are yours and cannot be delegated. Nobody else presents for you, contacts anyone at your site, or speaks to your stakeholders. Hour logs, encounter counts, census entries, site paperwork, signatures and any evaluation completed about you are your own record, never drafted, reconstructed or estimated with help. What a manual supports is the written layer: how a deck is structured, how a slide is built, how speaker notes are written. Every slide is de-identified, which in a room full of colleagues matters more rather than less.

The NR-669 Week 7 method, step by step

Six moves for a presentation built to the room and the clock.

  1. Write the ask in one sentence before building a single slide

    Name what you want the group to decide: assign ownership, approve a template field, add a report to a standing agenda. A presentation without a request is an update, and updates get thanked and forgotten.

  2. Budget the minutes before the content

    Divide your allotted time into segments and assign each a purpose and a word count at roughly 130 words per minute. Reserve at least a quarter of the total for questions. Content then has to fit the budget rather than the budget stretching to fit content.

  3. Give each slide one idea and title it with that idea

    A slide title should be the sentence you want remembered, not a category label. Documented follow-up rose after the recall step went in beats Results as a heading, because the audience reads the title whether or not they hear the sentence.

  4. Build the results slide around one figure

    Pick the single display that carries the finding, size it to fill the slide, label the axes and the denominator, and mark when the change began. Then say the number out loud rather than making people read it.

  5. Write speaker notes as speech

    Short sentences, spoken rhythm, one idea per breath. Read them aloud and cut anything you stumble over. Notes written in manuscript prose produce a delivery that sounds like reading, and audiences disengage from reading within about ninety seconds.

  6. Prepare backup slides for the three likely challenges

    Cost in staff time, whether the change holds without you, and whether something else explains the result. One slide each, held behind the deck, ready when asked. Having the answer visually is the difference between handling a challenge and surviving it.

A minute budget and slide plan for a stakeholder talk

Our frame for a twelve to fifteen minute presentation with questions, sized at roughly 130 spoken words per minute. It is our own outline rather than anything the university issues, and your scoring guide and your host's agenda both outrank it.

SegmentWhat belongs in itMinutes and spoken words
Opening and the askWho you are in role terms, what the project addressed, and the decision you are requesting today.1.5 min, 180 to 220
Problem with a local numberThe gap as the audience experiences it, with the baseline count that made it concrete.2 min, 240 to 280
What was doneThe change at encounter level, who performs it, and what it costs in time, on one slide.2.5 min, 300 to 340
What happenedThe single figure, the counts spoken aloud, delivery reported beside effect, and the honest caveat.3 min, 360 to 400
What it would take to keep itOwnership, the monitoring step and its minutes, and what is still fragile.2 min, 240 to 280
The request and closeThe decision restated in the form the group would actually take, then stop talking.1 min, 120 to 150

Evidence craft for presenting improvement results

Say denominators out loud. A room hears thirty-one of fifty-two differently from sixty percent, and the first version protects you from the person who asks how many children that actually was. Spoken counts also make a modest result sound like what it is rather than like an overclaim.

Show one figure, not a dashboard. Slides carrying four charts communicate nothing in the seconds an audience has. Choose the display that carries the finding, and keep the rest as backup material for questions.

Let the honest caveat come from you. Naming the main limitation yourself, in one sentence, is far stronger than having it raised from the floor. Audiences read self-identified limits as command of the material and unnamed ones as either ignorance or concealment.

Credit the team explicitly and by role. Improvement is collective, the people who made it work are often in the room, and a presenter who names the contribution of the rooming staff or the front desk builds the goodwill the sustainability ask depends on.

Keep patient material off the slides entirely. No identifiers, no photographs, no case detail that could be recognized by colleagues who work in the same building. Where a scenario helps, compose it as a de-identified composite and say that it is one.

Five mistakes that cost points in this week's territory

  • The paper on slides. Dense text blocks in small type produce an audience reading rather than listening, and nobody finishes either.
  • No request. A talk that ends with thank you rather than with a decision wastes the only chance you get in front of people who can act.
  • Ignoring the clock. A deck that overruns gets cut from the back, which removes the sustainability ask and leaves the audience with results and no action.
  • Category slide titles. Background, Methods and Results waste the line the audience actually reads on every slide.
  • Defensive answers. Treating a challenge as an attack turns a question into a confrontation; a prepared backup slide turns it into a demonstration.

Before you submit

  • The ask appears in the first two minutes and again at the close
  • Each segment has an assigned minute count and a matching word budget
  • Every slide title states an idea rather than naming a category
  • The results slide carries one labeled figure with the denominator visible
  • Speaker notes read as speech and have been read aloud against a clock
  • Backup slides exist for cost, sustainability and the main rival explanation

Building the NR-669 presentation?

Send the scoring guide, your paper and the minutes you have out of Canvas. A premium original draft comes back in 24 to 48 hours as a deck timed to the clock, with speaker notes written to be spoken and backup slides for the three likely questions, and revisions run until the grade lands. You deliver it; your hours, site and logs stay entirely yours.

Questions students ask about this stage

How many slides for a twelve-minute talk?
Fewer than instinct suggests, and the count matters less than the pace. Something like eight to twelve content slides works for twelve minutes, which is roughly a minute each with a little more time on the results and the ask. What actually governs the number is how many ideas you have: one idea per slide, and a talk of this length carries about ten ideas. If you have twenty slides, you have either duplicated ideas or split single ones across multiple visuals, and the fix is to merge rather than to speak faster. Keep any additional material as backup behind the final slide, where it costs nothing and is available if a question calls for it. Rehearse with the deck and a timer at least twice, because the gap between how long a talk feels and how long it takes is consistently unpleasant.
What if someone challenges my numbers in front of the group?
Answer the question that was actually asked, from your data account, without defending. The people most likely to challenge a number work in the process and often know something real, such as that a visit type was included or excluded in a way that changes the denominator. If they are right, say so directly, state what it would change, and offer to check and follow up. That response builds credibility rather than costing it. If the challenge rests on a misunderstanding, restate your operational definition plainly and show the backup slide that carries the verification result. This is precisely why the data account written earlier is worth its effort: a presenter who can say that twenty-eight of thirty hand-checked records matched the extract has a factual answer available in one sentence, and factual answers end challenges much faster than confident ones.
My audience is mostly people who already know the project. Do I still explain it?
Briefly, and mostly for the two people in the room who do not. Even a familiar audience benefits from a compressed restatement, because their picture of the project is usually the version they encountered months ago rather than the one that actually ran. Two slides handle it: the problem with its number, and the intervention as adapted. Spend the recovered minutes on what they do not know, which is the result, the honest caveat and the sustainability ask. There is one more reason to include the restatement even when it feels redundant, which is that a senior person who joined the agenda item late will otherwise spend your results slide trying to work out what the project was, and that is the slide you most need them to follow.

Keep going

Online now