A significance section has to work at three altitudes at once: the problem as a documented national or professional concern, the problem as a measurable condition inside your organization, and the problem as something happening to identifiable people in a specific workflow. Most drafts do one of the three well and gesture at the others. This stage of NR-730 is where a project earns the right to be taken seriously by connecting all three without leaving a gap. Your section may print this as NR 730 or NR730; 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-730 Week 2 asks for
Read enough project proposals and you learn to spot the seam. Two paragraphs of national statistics, a transition sentence beginning similarly, at the project site, and then a local claim with no number behind it. The reader is asked to accept that a documented national problem must also be a problem here, which is exactly the inference a doctoral reviewer refuses to make. The work of this stage is closing that seam: showing that the national concern has a local expression, that the local expression has been measured, and that the measurement was taken from something other than impression.
The three altitudes each need different evidence. At the highest altitude you need published sources establishing scale and consequence: prevalence, cost, harm, professional or regulatory attention. At the organizational altitude you need internal data or a defensible local proxy: quality dashboards, incident reporting, throughput or length-of-stay figures, audit results, existing reports. At the unit altitude you need workflow detail, which is often the part a doctoral clinician writes best, because it is the layer you have actually stood in. What is required is that each layer supports the next rather than merely sitting above it.
There is a second thing this stage does, and it is easy to underestimate. Significance writing is where your project acquires its stakeholders. A problem that costs the organization money interests a finance leader. A problem that produces a reportable event interests risk and quality. A problem that adds work to a night shift interests the manager who owns that schedule. Writing the significance at all three altitudes gives you the vocabulary you will need later to secure sponsorship, and projects with no sponsor do not get implemented no matter how well designed they are.
Expect the deliverable to be a written section rather than a form: a problem statement with significance, sometimes with a background of the problem heading, sometimes as part of a growing design document. Length in doctoral project courses is usually generous by the standards of earlier coursework, which makes the discipline harder rather than easier. If a discussion runs alongside, post the local number rather than the national one, and write it as final copy since posts do not reopen after submission in Canvas.
The NR-730 Week 2 method, step by step
Seven moves for building significance a reviewer cannot skip past.
-
Check the rubric for whether background and significance are separate rows
They frequently are, and they do different jobs. Background explains what is known about the problem. Significance argues why it must be addressed here, now, at this site. Merging them costs you the row that is easier to score well.
-
Write the national layer with figures that carry their base
Give rates with denominators and years, from named sources. A figure quoted without its base and its date is a decoration, and doctoral reviewers read it as a sign that the source was skimmed rather than used.
-
Find the organizational number before you write the transition
Search for what already exists: dashboards, quality reports, incident summaries, prior improvement projects, accreditation survey findings. Most sites hold more data than clinicians realize, and the retrieval work belongs before the drafting, not after.
-
If no local number exists, say so and describe the proxy
A defensible proxy, clearly labelled, is far stronger than an invented figure. A count of consults, a review of a defined sample of records, a stated period of manual tracking. Name the method, the period and the limits of what it can show.
-
Write the unit layer as workflow, not as anecdote
Describe where in the sequence the failure occurs: at handoff, at the point the vital sign posts, at the moment the covering clinician is paged. Workflow detail is what turns significance into a design brief for the intervention you will propose later.
-
Convert the gap into people and, where you can, into cost
Fourteen percentage points below the standard is abstract. Roughly 130 patients a year on this unit who did not receive an intervention the evidence supports is not. Where cost data is available and defensible, one sentence of it changes which leaders read your document.
-
End with the consequence of doing nothing
Significance sections that stop at description leave the reader to supply the urgency. Write the trajectory: what continues, at what rate, with what accumulating consequence, if the current state persists through the next year.
A layout and word budget for a significance section
Our frame for problem significance inside a project design document, sized for roughly 1,200 to 1,600 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 |
|---|---|---|
| Problem statement | The shortfall in one or two sentences, with the population and the bounded setting named. | 80 to 110 |
| National and professional layer | Scale, consequence and any regulatory or professional attention, with figures carrying bases and years. | 280 to 350 |
| Organizational layer | The internal data or labelled proxy, its period, its source and what it shows about this site. | 250 to 320 |
| Unit and workflow layer | Where in the sequence the failure happens, and what conditions make it more likely. | 250 to 320 |
| Gap in human terms | The shortfall converted into affected patients per period, with cost where defensible data exists. | 150 to 200 |
| Consequence of inaction | What continues at what rate if nothing changes, and who carries that consequence. | 130 to 180 |
Evidence craft for significance writing
Use recent sources for scale and let older ones carry concepts. A prevalence figure from a decade ago invites a question about whether the problem still exists at that size. Foundational conceptual work ages differently and can be cited without apology, but every number should be as current as you can defend.
Label internal data precisely. Say what system it came from, what period it covers, who pulled it and what it excludes. Data from the unit's quality dashboard for the first two quarters, excluding transfers, is a defensible sentence. Our data shows is not.
Never present an estimate as a measurement. If you counted 22 cases yourself over six weeks, say that. If a colleague believes it happens weekly, that is a report of a belief and should be written as one, or left out. In project design, a single invented number contaminates everything built on top of it.
Keep cost claims conservative and show the arithmetic. If you use a published cost per event, name the source and the year, state the number of events, and show the multiplication. Finance readers check arithmetic, and a cost claim that survives checking earns more attention than a larger one that does not.
De-identify the workflow examples. Where you illustrate the failure with a real sequence of events, strip dates, unit identifiers in combination, unusual diagnoses and anything else that could identify a patient or a colleague. Describe roles rather than people throughout.
Five mistakes that cost points in this week's territory
- The unsupported transition. Similarly, at the project site, followed by no number, is the single most common weakness in DNP significance writing.
- National statistics as the whole argument. A well-cited page about a problem's importance nationally does not establish that it exists here at a size worth a project.
- Percentages with no denominators. Reviewers cannot judge a rate without knowing whether it came from 40 cases or 4,000.
- Beliefs presented as data. Staff report that this happens frequently is perception, and dressing it as evidence undermines the sections that follow.
- No consequence of inaction. Without it, the section describes a problem rather than arguing for a project, and the urgency row scores in the middle.
Before you submit
- All three altitudes appear and each supports the next
- Every rate carries its base, its period and its named source
- The organizational number is identified by system, period and exclusions, or the proxy is labelled as one
- The workflow layer names where in the sequence the failure occurs
- The gap is converted into affected people per period
- The section closes with the consequence of maintaining the current state
Writing the significance section for NR-730?
Send the rubric and whatever local data you have out of Canvas. A premium original draft comes back in 24 to 48 hours with the three altitudes connected and every figure carrying its base, and revisions run until the grade lands.