NR-730 Week 1 The Project Concept Brief: How to Write It

What NR-730 Week 1 asks for

A charge nurse on a 32-bed telemetry unit has watched the same failure for two years. Patients meeting the facility's own criteria for early escalation get escalated late, usually on the night shift, usually after a documented change that nobody acted on. She can name four patients. She has raised it at three staff meetings. What she has never done is write it down in the form a doctoral reader needs, which is a bounded setting, a current-state number, a standard with a source, and a change already supported by evidence that this unit is not doing. The first stage of a project design course exists to force that conversion.

What makes this course distinct from the practicum sequence around it is the navigator relationship. You are not writing into a void and waiting for a grade; you are producing material that a faculty member will interrogate, send back and eventually endorse. That changes how you should write. Concept briefs are read for whether they can be defended, so every sentence that will attract a question is better answered in advance. Where is your data coming from. Who at the site has agreed to anything. What happens if the unit's census pattern changes. Anticipating those questions in the document is the fastest route through a design course.

The scholarship framing matters as much as the content. A practice doctorate project translates existing evidence into a change at a real site. It does not generate new knowledge, it is not a dissertation, and the writing should not sound like either. We will investigate whether structured escalation reduces late transfers is research language. The evidence supports structured escalation, this unit does not use it consistently, and here is the size of that gap is translation language, and translation language is what a navigator is listening for in the first conversation.

Expect a short deliverable at this stage, possibly a concept form, a brief or a posted statement, and expect it to be revised more than once. That is the normal operation of a design course rather than a sign that something went wrong. If your section runs a discussion this week, write it as final copy, because posts do not reopen after submission in Canvas and an early post that describes a project you later abandon is awkward to live beside for seven more stages.

The boundary that governs every page in this manual. The project itself, any hours attached to it, site agreements, approvals, data access permissions and anything a preceptor, navigator or site verifies are your own record and your site's. They are never drafted, reconstructed or estimated with help from anyone. What a manual supports is the written layer: how to bound a problem, how to build an argument, how to structure a design document. Where your writing draws on a real encounter or a real unit, de-identify every patient detail, and describe the site by type and size rather than by name.

The NR-730 Week 1 method, step by step

Seven moves that turn a clinical frustration into a concept a navigator can work with.

1. Read the rubric for what a concept must contain

   Design courses grade completeness of elements more than elegance of prose. Copy each row into a blank file, mark which rows name a required element, and treat any element you cannot yet supply as the first task of the week rather than as something to write around.

2. Describe the setting by type, scale and workflow

   A 32-bed telemetry unit with a 1 to 5 ratio on days and 1 to 6 on nights, admitting primarily from the emergency department, is a setting a reader can reason about. The organization's name adds nothing and creates a confidentiality problem you do not need.

3. Write the problem as a shortfall, not a topic

   Alarm fatigue is a topic. Patients meeting the facility's escalation criteria are not escalated within the defined window on this unit is a shortfall, and only a shortfall can be measured, changed and re-measured.

4. Put a number beside it, or mark where the number will come from

   If you do not yet have the current-state figure, write the sentence with a blank and name the source you will use: an existing report, a chart review of a defined period, an existing quality dashboard. A concept with a known data route beats one with a confident guess.

5. Name the change and say where its evidence lives

   The proposed intervention should already be supported somewhere: in a guideline, a synthesis, a body of implementation reports. Say what it is in one sentence and where the support sits, without doing the full synthesis yet, because that arrives later in the arc.

6. Test the concept against feasibility before you fall in love with it

   Can you get the data, is anyone at the site willing to sponsor it, does it require a technology change, does it need budget approval, and can it be implemented and evaluated inside the timeline your program allows. Write the answers, including the uncomfortable ones.

7. Write the questions you expect your navigator to ask

   Then answer them in the brief. Doctoral design work moves at the speed of the weakest unanswered question, and a concept that pre-empts three of them will come back with a shorter revision list than one that leaves them open.

A layout and word budget for a concept brief

Our frame for an opening project concept, sized for roughly 800 to 1,100 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

Evidence craft for a project concept

Cite for the problem's significance, not only for the solution. A concept needs at least one source establishing that the problem matters beyond your unit, and one indicating that the change you propose has support. Two well-chosen citations at this stage do more work than fifteen assembled quickly.

Give the current-state number a base and a window. Nine of 61 escalations in the last quarter is evidence a reader can weigh. Fifteen percent is a figure whose denominator has been hidden, and a navigator will ask for it immediately.

Prefer guidelines and syntheses to single studies at this stage. Translation work rests on evidence that is already settled. A guideline or systematic review named with its issuing body and year is a stronger anchor for a concept than a promising trial, and it signals that you understand what kind of scholarship you are doing.

Do not promise an ethics determination. Whether a project is treated as quality improvement or as human subjects research is decided by the people who make that decision, not by you and not in advance. Write that a determination will be sought, describe the route, and leave the outcome open.

Keep the site anonymous and the patients invisible. Describe the unit by type and size, remove anything that identifies a person, and where an example comes from a real event, strip dates, room numbers, diagnoses in combination and anything else that would let a colleague recognize the patient.

Five mistakes that cost points in this week's territory

• A topic where a problem belongs. Sepsis, burnout, alarm fatigue. None of these can be measured, changed or evaluated until they are written as a shortfall in a bounded setting.
• Research framing. Investigating whether an intervention works is a different degree's work, and the vocabulary gives it away in the first paragraph.
• A project sized for a health system. Concepts that span nine units die in design. The ones that finish live in one workflow, one shift pattern or one handoff.
• No route to data. A project whose current-state number cannot be obtained is not feasible, and discovering that in a later stage costs weeks.
• Hiding the open questions. A brief that pretends everything is settled invites a navigator to find what is not, and that conversation is slower than volunteering it.

Before you submit

• The problem is written as a measurable shortfall, not a subject area
• The setting is described by type, size and workflow rather than by name
• The current-state number carries a base, a period and a stated data route
• The proposed change is named with the type of evidence that supports it
• Feasibility is addressed on data, sponsorship, dependencies and timeline
• No ethics outcome or site approval is claimed in advance

Questions students ask about this stage

Keep going