NR-702A Week 1 Bounding the Practice Problem: How to Write It

What NR-702A Week 1 asks for

What changes when a nurse who has run a unit for a decade starts writing at doctoral level? Mostly the direction of the argument. A federally qualified health center in a county with two pediatricians has a lead screening rate that sits well under the rate its own protocol calls for, and every clinician in the building can tell you why in conversation. Doctoral writing asks you to stop telling it and start bounding it: which site, which population, which number, over which period, compared with what standard. The opening stage of a project practicum is where that bounding happens on paper, and it is harder than it sounds because clinicians are trained to describe a problem in the language of causes rather than in the language of magnitude.

The second thing this stage asks is that you understand what kind of scholarship you are doing. A practice doctorate project translates evidence that already exists into a change at a site. It is not a study that generates new knowledge, it is not a dissertation, and describing it as one is the fastest way to signal that the distinction has not landed yet. The literature you will assemble later is not there to reveal something unknown; it is there to establish that the intervention you intend to put in front of real patients has already earned its place. Writing that says we will investigate whether X works is research language. Writing that says the evidence supports X, and this site does not do X, and here is the size of that gap, is translation language, and translation language is what a doctoral reader is scoring.

Third, this stage asks for scope discipline that matches your hour load. A 2-credit practicum block gives you 128 hours across an eight-week session, which is roughly sixteen hours a week for a clinician who is probably also working. That reality should be visible in what you propose. A problem that requires changing referral behavior across nine clinics is not a 128-hour problem. A problem that lives in one clinic session, one intake workflow or one discharge handoff is. Faculty read early scoping work largely for feasibility, because the most common way a doctoral project stalls is that it was sized for an organization when it should have been sized for a service.

The boundary that governs every page in this manual. Practicum hours, hour logs, encounter counts, site documentation, preceptor evaluations and signatures are your own record and your site's. They are never drafted, reconstructed, estimated or filled in with help from anyone, including us, and no tutor should ever perform, observe or document clinical activity on your behalf. What a manual can support is the written layer that surrounds real work you genuinely did: how to bound a problem, how to structure an argument, how to write a reflection that analyzes instead of narrates. Where your writing draws on a real encounter or a real site, every patient detail must be de-identified before it reaches a page, and the site itself is normally described by type and size rather than by name.

The NR-702A Week 1 method, step by step

Seven moves that turn a clinical frustration into a bounded practice problem a committee can accept.

1. Open your week's rubric and split it into hours and paper

   Practicum rubrics mix administrative rows about hours, site agreements and supervision with scholarly rows about the written deliverable. Copy the rows into a blank file and separate them. The administrative half is yours to satisfy directly. The scholarly half is what your word budget applies to, and it is usually smaller than students assume.

2. Write the setting in one sentence, sized rather than named

   A community health center serving roughly 4,800 patients a year across two exam pods, with three prescribing clinicians and one care coordinator, is a setting a reader can picture and scale against. The name of the organization adds nothing and creates a confidentiality problem you do not need.

3. State the current number with its numerator and denominator

   Not performance is low. Instead: 61 of 402 eligible visits over the last quarter, which is what the number is and what it is out of. If you cannot retrieve those two figures yet, write the sentence with blanks in it and treat filling the blanks as the first real task of your practicum time.

4. Attach a benchmark that came from somewhere

   The desired number needs a source: a national quality measure, a professional society recommendation, a payer or accreditation threshold, or your own organization's written standard. A target you chose because it sounded ambitious is an opinion, and opinions do not survive committee questions.

5. Subtract, and write the gap as a sentence

   The gap is the project. Say it plainly: the site performs at fifteen percent where the standard is fifty, which is 141 patients a year who did not receive something the evidence supports. Converting a percentage into people is the single move that most improves how a problem statement reads to a doctoral audience.

6. Test the problem against your hour reality before you commit

   Ask what would have to happen at the site for this change to be attempted and measured inside your sequence. If the honest answer involves a new hire, a purchase, or a decision by a board that meets twice a year, narrow the problem now rather than discovering the constraint in a later practicum course.

7. Say what already works elsewhere, in one hedged sentence

   You are not proving the intervention this week. You are signalling that one exists. A single sentence saying that structured outreach protocols have been reported to raise screening completion in similar outpatient settings, with a source, tells the reader this is a translation problem and not a research question.

A layout and word budget for an opening problem paper

Our frame for a first practicum written deliverable, 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. Scale the targets proportionally if your assigned length differs, and cut from background first.

Evidence craft for a doctoral problem statement

Local data outranks national data in this genre. A page of statistics about a condition across the country establishes that the topic is important; it does not establish that your site has a problem. Doctoral readers want the local figure first and the national context second, in that order, and reversing the order is the most common structural weakness in opening practicum papers. National numbers earn one paragraph as scale, not four as introduction.

Every number arrives with its retrieval path. Beside each figure you plan to use, note in a working document where it would come from: a report someone runs monthly, a registry extract, a scheduling system query, a chart audit you would have to conduct yourself. Numbers with no retrieval path collapse later, and discovering that in week two of a 128-hour block costs you far less than discovering it during implementation.

Cite the standard, not the impression of the standard. When you write that a benchmark is fifty percent, the sentence should carry the organization that set it and the year of the version you read. Quality measures are revised, specifications change, and a threshold quoted from memory is a claim about the present made from an unknown date.

Keep intervention language conditional this early. You have not appraised anything yet, so write that a body of work reports benefit rather than that an approach works. Overcommitting to a solution in the opening stage tends to produce a later synthesis written to defend a decision already made, which readers notice and score down.

De-identify by default and describe by type. If a real encounter motivated the problem, it can appear as illustration, but stripped: no name, no date, no room number, no detail combination that would identify a person in a small community. The same discipline applies to the site, which is normally described as a rural community health center or a county clinic rather than by its actual name.

Five mistakes that cost points in this week's territory

• Writing a topic instead of a problem. Medication adherence in diabetes is a subject heading. A named rate at a named type of site, measured and compared, is a problem.
• Research framing on a translation project. Language about investigating whether an intervention works signals that the practice-doctorate distinction has not been absorbed, and it colors how every later section is read.
• A benchmark with no parent. Targets that appear without an issuing body read as preference, and a reader who cannot check the standard cannot score the gap.
• Scope sized for a system. Proposals that reach across facilities are not deliverable inside a 128-hour block, and feasibility is graded even when no row says so explicitly.
• Background swallowing the paper. Six hundred words on national prevalence and ninety on the site is the inversion that most reliably lands an otherwise competent draft mid-range.

Before you submit

• The gap appears in the first paragraph with both numbers attached
• The setting is described by size, staffing and population rather than by name
• Your baseline carries a numerator, a denominator and a time window
• The benchmark names its issuing body and the year of the version you used
• The consequence is expressed as patients affected, not as a percentage alone
• At least one sentence establishes that an intervention family already has published support
• The feasibility paragraph is honest about what 128 hours can carry
• No clinical detail in the paper could identify a patient, a colleague or the site

Questions students ask about this stage

Keep going