NR-720 · Week 8 of 8 · The synthesis brief for a senior audience

NR-720 Week 8 The Executive Synthesis Brief: How to Write It

The short answer

Closing work in a systems leadership course usually asks for synthesis: the environment read, the systems analysis, the cost build, the workforce position and the governance structure compressed into one argument aimed at people who will decide. Compression is the skill. Everything you have written this session has to survive being reduced to a few pages without losing the reasoning that makes it credible, and the parts that cannot survive that reduction were usually the parts that were not load-bearing. Your section may print this as NR 720 or NR720; 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-720 Week 8 grading scale at Chamberlain, the criterion levels this assessment is scored on, from Chamberlain Tutors
How Chamberlain grades NR-720 Week 8, visualized by Chamberlain Tutors.

What NR-720 Week 8 asks for

A first-year report on a telehealth follow-up service went to a board quality committee in two versions. The first ran fourteen pages and put the results in a table on page nine, under a heading about program activity. The second ran three pages and opened with a sentence saying that the service had seen a stated number of patients within seven days of discharge, that the medical service's early readmission pattern had moved in the direction expected while other explanations could not be excluded, that the cost had come in at the low end of the approved range, and that the committee was being asked to approve continuation with an expanded population. Both were accurate. Only one produced a decision, and it was not the one that contained more information.

The closing stage in this course tends to test exactly that. Deliverables at this point are often a final synthesis paper, an executive summary or brief, or a presentation of your leadership analysis to a senior audience. Whatever the form, the graded qualities are the same: does the argument hold together across all its parts, is it aimed at a decision, and can a busy reader act on it.

Synthesis has a technical meaning worth honouring. It is not a summary of your previous sections placed end to end. It is one argument in which the workforce constraint bears on the quality strategy, the payment environment bears on which option is viable, and the governance structure follows from the risk the recommendation creates. A grader looking for synthesis is looking for the sentences where two threads meet, and those sentences have to be written deliberately because they do not appear on their own.

Keep the practice-doctorate frame to the end. What you are producing is a scholarly product aimed at a practice audience: rigorous in its evidence, honest about uncertainty, and written to be used. It is not a dissertation, and describing your work as though it generated new knowledge misrepresents what a systems leadership analysis does.

The NR-720 Week 8 method, step by step

Six moves for compressing a session's work into a decision document.

  1. Write the decision paragraph first and let it govern the rest

    The recommendation, the scale, the cost, the source of funds and the review point. Everything that does not support those five things is a candidate for removal, and applying that test ruthlessly is what produces an executive document.

  2. Reduce each earlier analysis to its load-bearing finding

    One or two sentences per thread, carrying the conclusion and the evidence for it rather than the method that produced it. Method belongs in an appendix if it belongs anywhere.

  3. Write the junction sentences deliberately

    The sentence where the workforce position constrains the option choice; the sentence where the payment environment decides between two clinically equivalent alternatives. These are what the synthesis row is scoring and they must be explicit.

  4. Present the numbers in one place and in one format

    A single table with cost, benefit, timing and source beats figures scattered through prose. Executive readers look for the numbers first and judge the document partly by how easy they were to find.

  5. State the uncertainty and the strongest objection in your own words

    Name what could make the recommendation wrong and the best argument against it. Doing so pre-empts the challenge and reads as confidence; omitting it invites a reader to assume you have not thought of it.

  6. Close with the ask and the next step, not a conclusion

    What you want the body to approve, what happens in the following thirty days if they do, and who does it. Reflective closing paragraphs belong in academic papers; decision documents end with an action.

A layout and word budget for a synthesis brief

Our frame for the closing deliverable, sized for roughly 1,400 to 1,800 words with a consolidated numbers table. If your section asks for a presentation instead, the same order applies across slides. This outline is ours rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

SectionWhat belongs in itWord target
Decision paragraphRecommendation, scale, cost, funding source and review point, in five sentences or fewer.90 to 130
Why nowThe environmental forces and the local problem, compressed to their load-bearing findings with sources.250 to 300
What was consideredThe options and the criteria, with the reason the recommendation beat the closest alternative.250 to 300
The junctionsWorkforce against strategy, payment against option, risk against structure, written explicitly.250 to 300
Numbers and governanceThe consolidated table plus ownership, reporting and stop criteria in compressed form.280 to 340
Uncertainty and the askWhat could make this wrong, the strongest objection, and the specific approval requested with next steps.200 to 250

Evidence craft for a synthesis document

Keep citations in a compressed document rather than dropping them. Executive briefs in academic work still carry scholarly attribution, and the discipline is to cite the two or three sources that actually carry weight instead of the twenty that provided background.

Repeat the base with every retained number. Compression tempts writers to strip denominators and periods, which is exactly when a figure becomes unusable. If a number survives the edit, its base and its source survive with it.

Frame the results as improvement evidence with their limits. A local change evaluated over one period supports a statement about this setting, with alternative explanations acknowledged. Write it that way and the paper is both more honest and more credible than one claiming more.

Attribute anything you carried forward from earlier stages. If your workforce section rested on published staffing research, that citation travels into the brief with the finding. Conclusions that arrive unsupported in a final document look like assertions even when they were fully evidenced three papers ago.

Write for a reader who may act without reading further. Assume the decision paragraph is the only part that will be read by some members of the audience, and make sure nothing essential lives only in the appendix.

Five mistakes that cost points in this week's territory

  • Sections stacked instead of synthesized. A brief assembled from previous papers in sequence has compressed nothing and joined nothing.
  • The recommendation deferred. A closing document that builds to its ask on the last page is an academic essay handed to a decision-making body.
  • Numbers stripped of their bases. Compression that removes denominators produces figures nobody can use or defend.
  • Overclaiming the result. Describing a single-site improvement as evidence of effectiveness misstates what practice-doctorate work produces.
  • No objection acknowledged. Briefs that read as though no reasonable person could disagree are the ones a committee dismantles.

Before you submit

  • The decision paragraph appears first and contains the ask, cost, funding and review point
  • Each earlier thread is reduced to its load-bearing finding with its citation intact
  • At least two explicit junction sentences join separate threads
  • All numbers appear in one consolidated place with bases and sources
  • Governance is present in compressed form, including stop criteria
  • Uncertainty and the strongest objection are stated in your own words
  • The document closes with an approval request and a named next step

Finishing NR-720?

Send the rubric and your earlier work out of Canvas. A premium original draft comes back in 24 to 48 hours compressed to executive length with the junction sentences written deliberately and the numbers consolidated, and revisions run until the grade lands.

Questions students ask about this stage

How do I compress without losing the scholarly depth the rubric wants?
Cut method and keep conclusions with their sources, which is the trade every executive-facing scholarly document makes. A sentence saying that early follow-up after discharge is supported by published work in comparable populations, with two citations, carries the same scholarly weight in this format as three paragraphs describing how you appraised that literature, and it respects the reader's time. Where a rubric explicitly asks for depth of analysis, the usual answer is an appendix or a clearly marked section that carries the fuller treatment while the brief stays a brief. What does not work is splitting the difference by writing something that is too long to be executive and too shallow to be scholarly. Decide which document you are writing, then serve the other requirement through structure rather than by diluting the main text.
My results are not in yet. What do I put in the closing document?
Write it as a decision brief rather than a results report, which is a legitimate and common form of the document. The ask becomes approval to proceed, or approval to continue to the next stage, and the evidence section carries the published basis plus whatever local baseline you have established. State plainly what will be measured, when the first meaningful read will be available, and what the criteria for continuation are. A brief of that shape is exactly what real committees receive most of the time, since most decisions are made before results exist. What matters for the grade is that the argument is complete and the reasoning is visible, not that an outcome has landed. Where you have partial or process data, report it as process data with its limits, and resist the temptation to present an early signal as an outcome.
Does this document belong in a portfolio or a project defense later in the program?
Frequently yes, and writing it with that in mind costs nothing and saves work. Systems leadership analyses often become the organizational context section of later project work, the justification for a site and a problem, or a scholarly product aimed at a practice audience. Two habits make that reuse possible. Keep a full reference list even in a compressed document, since reconstructing citations months later is far harder than maintaining them now. And keep the local data with its provenance attached, including which report it came from and over which period, because a figure whose source you can no longer identify is a figure you cannot use in a later document. Also keep the version of the analysis you cut, since the fuller reasoning behind a compressed brief is exactly what a defense or a committee question will ask you to produce.

Keep going

Online now