NR-705B Week 7 Write a Reflection That Analyzes: How to Write It

What NR-705B Week 7 asks for

Here is the difference in one comparison. A student writes that leading the screening rollout in the pediatric practice taught her a great deal about collaboration and made her a stronger leader. Another writes that she began the term assuming the practice manager's agreement was the decision that mattered, discovered in the second week that the rooming staff's ten-minute template was the actual constraint, and changed her approach from securing approval upward to negotiating capacity sideways - a shift she then applied when the same pattern appeared with the front desk. The first is a feeling. The second is an analyzed change in professional judgment, and it is what doctoral reflective rubrics are built to detect.

Competency-linked reflection has a shape. You take the domain the reflection is organized around - systems leadership, quality improvement methods, interprofessional collaboration, ethics, information systems - and for each one you provide a decision you made, the reasoning you used at the time, what happened, and what you would now do differently. Four elements per domain. Reflections that fail are usually reflections that supply the first and the last and skip the reasoning in between, which is exactly the part that demonstrates doctoral thinking.

Register matters here more than students expect. First person is normally permitted and often required in reflective writing, but permission to write I is not permission to stop supporting claims. If you assert that your project changed how the practice thinks about screening, the sentence still needs something behind it - an observed behaviour, a request that came to you unprompted, a decision someone else made differently. Reflection at this level is evidence-bearing prose that happens to be written in the first person.

Where the boundary sits. This is the page where the line has to be stated most plainly, because reflection sits closest to the practicum record. Your 192 clinical hours, the log that records them, activity and encounter counts, evaluations completed by a preceptor or site mentor, and every form a site or the university verifies are your own work and your own record. They are never drafted, reconstructed, summarized into a log, back-filled or estimated with help, and no honest service offers to touch them. What can be supported is the written reasoning: how to organize a reflection so it analyzes rather than narrates, how to evidence a claim about your own practice, how to write in scholarly first person. Every clinical detail must be de-identified - roles rather than names, no dates of service, no detail that would identify a family or a colleague. The experience is not shortcutable and no part of this suggests otherwise.

The NR-705B Week 7 method, step by step

Six moves for a reflection that reads as doctoral analysis.

1. Choose decisions, not events, as your raw material

   Scan your own project notes for moments where you chose between options: which barrier to address first, whether to accept an adaptation, whether to escalate a refusal. Decisions carry reasoning; events only carry chronology.

2. Reconstruct what you believed at the time

   Write the assumption you were operating under before the decision, honestly, including the ones that turned out wrong. A reflection with no superseded belief in it has not reflected on anything.

3. Anchor each reflection to one named competency domain

   Use the language of the doctoral competency framework your program works from and cite it. One decision serving one domain is cleaner than one decision claimed to demonstrate five.

4. Show the change with a second instance

   The strongest evidence that judgment changed is a later situation where you acted differently. Pair the decisions: the first time you handled it this way, the second time you handled it that way, and here is what accounted for the difference.

5. Name what you still cannot do

   A specific unresolved limitation - negotiating with a role whose incentives you still do not understand, reading a data extract without help - is more credible than a growth statement and sets up a defensible plan for the remaining program.

6. Write forward into practice, not into sentiment

   Close with what you will do differently in your role after the degree, stated concretely enough that someone could later check whether you did it. Inspirational closers are the most reliably penalized paragraph in reflective writing.

A layout and word budget for a competency-linked reflection

Our frame for a doctoral practicum reflection, sized for roughly 1,400 to 1,800 words across three or four domains. It is our own outline rather than anything the university issues, and your program's competency framework and your week's rubric outrank it wherever they disagree.

Evidence craft for reflective doctoral writing

Cite the competency framework you reflect against. Doctoral education standards and role competency documents are published and dated, and naming the source turns a personal essay into a piece of work assessed against an external standard. Quote a domain's language once and then use it consistently.

Evidence claims about yourself the way you would evidence any other claim. I became more comfortable with conflict is unsupported. In the second negotiation I opened by stating the constraint rather than the request, and the conversation reached a decision in one meeting rather than three is evidence, and it is the same sentence with the work done.

Use published thinking about reflection sparingly and correctly. If your program favours a reflective model, apply its stages to your material rather than describing it. One accurate paragraph applying a model beats three explaining it, and the explanation consumes space your analysis needs.

Do not turn colleagues into characters. Reflective writing tempts students into portraiture, and portraiture of identifiable people in a small practice is both an ethical problem and a professionalism marker on a rubric. Roles, not names; behaviour patterns, not personalities.

Keep the reflection about your practice, not about the project's results. There is a separate place for outcomes. A reflection that drifts into reporting numbers has abandoned the graded task, which is the change in you as a systems-level clinician.

Five mistakes that cost points in this week's territory

• Chronology instead of analysis. A week-by-week account of the term answers a question no reflective rubric asks. Three decisions examined beat eight weeks recounted.
• Growth without a superseded belief. If nothing you thought at the start turned out to be wrong, no reflection has occurred and the reader can see it.
• One anecdote claimed for every competency. Stretching a single decision across five domains signals a thin evidence base rather than a broad one.
• Sentimental closers. Passion, journey and privilege as a final paragraph are the most commonly flagged writing habit in doctoral reflective work.
• Confusing reflection with the practicum record. A reflection is scholarly prose. Hours, logs, counts and evaluations are a separate, verified record that belongs entirely to you and never mixes with writing support of any kind.

Before you submit

• A named, dated competency framework organizes the piece
• Each domain rests on one specific decision, not a general impression
• Every decision includes the belief you held before it
• At least one domain shows a later instance where you acted differently
• Claims about your own change carry observable evidence
• No colleague or family is identifiable anywhere in the text
• The closing paragraph names concrete future practice rather than sentiment

Questions students ask about this stage

Keep going