NR-720 opens a systems leadership sequence, and the first thing that changes is the reader. Executive readers do not read to learn; they read to decide, and they decide from the first paragraph. Opening work in this course typically asks you to identify a systems-level issue and write about it the way a senior leader writes: the decision named early, the analysis compressed behind it, and every claim written for someone who will act on it. 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.
What NR-720 Week 1 asks for
A system running virtual nursing on four medical-surgical units had to decide whether to extend it to eleven more. The proposal that went up first ran nineteen pages and opened with a literature review on virtual care models. The chief nursing officer read two pages, asked what she was being asked to approve, and sent it back. The version that succeeded opened with four sentences: extend the virtual nursing model to eleven units over two fiscal quarters, at a stated capital and staffing cost, funded from the travel labor line it is expected to displace, with a go or no-go review after the first three units. Everything else in the document served those four sentences. The content had barely changed. The altitude had.
That altitude is what this stage installs. The written work in an opening systems leadership stage often asks you to define a systems-level problem in your organization, introduce a leadership issue you will carry through the session, or write a short analysis positioning yourself as a senior-level leader. Whatever the framing, the first thing being scored is whether you can write above the unit.
Above the unit means something concrete. A systems issue touches more than one service, involves at least two of capital, workforce and payment, and cannot be solved by any single manager acting well. Length of stay on one medical-surgical floor is a unit problem. Length of stay across a medical service, driven by imaging turnaround, a discharge pharmacy queue, transport capacity and a post-acute network that will not take patients on Fridays, is a systems problem, and it looks completely different on paper.
The doctoral requirement runs underneath all of it. This is a practice doctorate, so your contribution is translating what is already known into a decision at a real organization, not generating new knowledge about whether the intervention works. Write the systems argument the way a chief operating officer would need it, and cite the evidence the way a scholar would require. Doing both at once is the actual skill this course is built to develop.
The NR-720 Week 1 method, step by step
Six moves for writing at executive altitude from the first line.
-
Identify the decision, not the topic
Write the sentence that begins with a verb an executive can act on: approve, fund, extend, consolidate, discontinue, redesign. If your opening sentence names a subject rather than a choice, you have written a report and the reader has to find the decision themselves.
-
Establish altitude by naming what crosses boundaries
Say which services, which budgets and which workforces are involved. A problem that lives entirely inside one department, one cost center and one manager's authority is not the subject of this course, and the fastest way to fail the altitude row is not to notice.
-
Size the problem in the organization's own currency
Bed days, avoidable transfers, vacancy rate, contribution margin, throughput, readmissions, agency spend. Use the measures your organization already reports, because a systems argument built on a number nobody tracks cannot be acted on.
-
State the recommendation before the analysis
Executive writing inverts the academic order. Recommendation, then the two or three reasons, then the supporting material. Readers who agree by paragraph two read the rest as confirmation; readers who disagree know immediately what they are arguing with.
-
Name the trade-off in the opening section
Every systems recommendation consumes capital, attention or workforce that is currently going somewhere else. Saying what will not get done is the single clearest marker of executive-level writing and the one students most often omit.
-
Attach a decision point and a measure
When the decision has to be made, what would be reviewed afterwards, and what result would trigger a reversal. A recommendation without a review point asks a senior leader to make a permanent bet, which is why so many of them come back unapproved.
A layout and word budget for an opening systems analysis
Our frame for an opening piece in this course, sized for roughly 1,200 to 1,500 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| The decision | What is being recommended, to whom, at what scale and by when, in four sentences or fewer. | 80 to 110 |
| Why it is a systems issue | The services, budgets and workforces it crosses, and why no single manager can resolve it. | 200 to 250 |
| The problem sized | The measures the organization already reports, with bases, periods and sources named. | 230 to 280 |
| What is already known | The established evidence for the direction you propose, cited, framed as translation rather than discovery. | 220 to 270 |
| Trade-off and constraint | What the recommendation consumes and what will not happen if it proceeds. | 180 to 230 |
| Decision point and review | The timing, the measure that would be reviewed, and the result that would reverse the decision. | 150 to 190 |
Evidence craft for executive systems writing
Use the organization's reported measures, and say where they come from. A figure taken from the monthly operating review or the quality dashboard carries authority in this genre because the reader recognizes it. Name the report and the period rather than presenting a number as though it were self-evident.
Keep the base with every proportion. Eleven of the 214 medical-surgical discharges in one month is checkable; five percent is not. Executive readers challenge numbers first, and a proportion without a denominator is the easiest challenge in the room.
Cite scholarly and industry sources for different jobs. Peer-reviewed literature establishes that an intervention works; industry, regulatory and professional sources establish what the operating environment requires. Doctoral writing uses both and never confuses which is doing which.
Attribute leadership and systems concepts. Complexity in health systems, high reliability, value-based care and transformational leadership all have literatures with names and years attached. Using the vocabulary without the citations reads as fluency without grounding, and it costs support rows.
Do not invent institutional facts to make the argument clean. If you do not know the capital cost, write that it requires a costing and name who would produce it. Fabricated precision is worse than acknowledged uncertainty, and any reader inside a health system will spot an invented number immediately.
Five mistakes that cost points in this week's territory
- Unit-level writing in a systems course. An excellent analysis of one floor's problem answers a question this course did not ask, and no amount of polish repairs the altitude.
- Literature review first. Opening with background delays the decision past the point where an executive reader is still deciding rather than skimming.
- A topic instead of a recommendation. Writing about staffing challenges gives the reader nothing to approve or refuse.
- No trade-off named. Recommendations presented as free are the ones senior leaders trust least, because they know nothing is.
- Numbers without provenance. A systems argument stands on figures the reader can trace, and untraceable ones discredit the paragraphs around them.
Before you submit
- The opening states a decision with an actionable verb
- The services, budgets and workforces crossed are named
- Every figure carries a source, a base and a period
- The evidence section is framed as translation rather than as discovery
- The trade-off is stated explicitly, including what will not get done
- Leadership and systems concepts are cited with authors and years
- A decision point, a review measure and a reversal condition all appear
Starting NR-720 this week?
Send the instructions and the rubric out of Canvas. A premium original draft comes back in 24 to 48 hours written at executive altitude with the decision in the opening lines, and revisions run until the grade lands.