NR-705C · Week 7 of 8 · Reflection on leading a project team

NR-705C Week 7 Reflect on Leading the Project Team: How to Write It

The short answer

Late in a practicum block most programs ask for reflective writing tied to doctoral competencies, and in a term this size the material is largely about leading other people through a change you do not have formal authority over. A doctoral reflection is an argument about how your judgment shifted, evidenced by decisions you can name, not an account of how the term felt. It is written from hours you personally worked, and the hours themselves stay entirely yours. Your section may print this as NR 705C or NR705C; 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.

NR 705C Week 7 grading scale at Chamberlain, the criterion levels this assessment is scored on, from Chamberlain Tutors
How Chamberlain grades NR 705C Week 7, visualized by Chamberlain Tutors.

What NR-705C Week 7 asks for

Compare two sentences a student might write about running a change across two pediatric locations. The first says the experience taught her the importance of communication and collaboration across sites. The second says she scheduled a single combined briefing to save time, discovered that the second location's staff had questions they would not ask in front of the first location's manager, and thereafter ran site-specific sessions - a decision she then applied again when the practice added a third location's staff to the project's mailing list. The first is a sentiment. The second is a documented change in professional judgment with a second instance attached, which is exactly what doctoral reflective rubrics are constructed to detect.

Multi-site or larger-scope work generates a particular kind of reflective material worth mining. Influence without authority. Managing a project across managers who do not report to each other. Deciding what to standardize and what to let vary locally. Discovering that the same protocol produces different behaviour in different staffing models. Holding the line on the mechanism while conceding on packaging. Those are systems-leadership problems, and they belong in a reflection at doctoral altitude far more than a general statement about teamwork.

Register deserves attention. First person is usually permitted and often required in reflective writing, but the permission does not suspend the requirement to support claims. If you assert that your approach to a manager changed the pace of decisions, show it: three meetings before, one after, or a request that came to you unprompted rather than through your chair. Reflection at this level is evidence-bearing prose that happens to be written in the first person.

Where the boundary sits. This is where the line most needs stating, because reflection sits closest to the practicum record. Your 256 clinical hours, the log recording them, encounter and activity counts, evaluations completed by preceptors or site mentors, and every form the site or 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 from anyone, and no honest service offers to touch them. What can be supported is the written reasoning: organizing a reflection so it analyzes rather than narrates, evidencing a claim about your own practice, writing in scholarly first person. De-identify every clinical and staff detail - roles rather than names, no service dates, nothing that places a family or a colleague. The experience cannot be shortcut.

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

Six moves for a reflection built on leadership decisions.

  1. Mine your own project record for decision points

    Go through your event notes and mark every place you chose between options: which site to start, whether to standardize a step, whether to escalate a refusal, whether to accept an adaptation. Decisions carry reasoning; events carry only sequence.

  2. Write the assumption you held before each decision

    Including the ones that proved wrong, stated without defensiveness. A reflection containing no superseded belief has not reflected, and readers can tell within a paragraph.

  3. Tie each decision to one named competency domain

    Systems leadership, quality improvement methods, interprofessional collaboration, information systems, ethics. Cite the framework your program works from. One decision serving one domain reads far better than one stretched across five.

  4. Show the change with a later instance

    The strongest evidence that judgment shifted is a second situation where you acted differently. Pair them explicitly and name what accounted for the difference.

  5. Analyze one moment where influence failed

    A request that was declined, a site that would not move, a meeting that produced nothing. What you tried, what you now think was wrong about the approach, and what you would try instead. Failure analyzed is worth more than three successes narrated.

  6. Close on concrete forward practice

    What changes in your role after this term, stated specifically enough that someone could check whether you did it. Inspirational closers are the most reliably penalized paragraph in doctoral reflective writing.

A layout and word budget for a leadership-focused reflection

Our frame for a doctoral practicum reflection at this stage, sized for roughly 1,500 to 1,900 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.

SectionWhat belongs in itWord target
Framework and domainsThe competency framework you reflect against, named and dated, and the domains this piece will cover.110 to 150
Domain one: influence without authorityA decision about how to move someone who does not report to you, the belief behind it, and what happened.320 to 380
Domain two: standardize or localizeA decision about what had to be identical across settings and what could vary, with the mechanism reasoning behind it.320 to 380
Domain three: your choiceA third domain the first two did not touch - data stewardship, ethics, interprofessional practice - with the same four-part structure.320 to 380
A failure of influenceOne attempt that did not work, analyzed for what the approach assumed and what you would do instead.230 to 290
Capabilities still missingOne or two specific things you cannot yet do, described concretely, with what would build them.170 to 220
Forward practice statementWhat changes in your practice after this block, written so it could be checked later.140 to 180

Evidence craft for reflective doctoral writing

Cite the competency framework and use its language. Doctoral education standards and role competency documents are published and dated. Naming the source converts a personal essay into work assessed against an external standard, and quoting a domain once anchors the vocabulary for the rest of the piece.

Evidence claims about yourself as rigorously as any other claim. I became better at negotiation is unsupported. In the second conversation I opened with the constraint rather than the request, and the decision came in one meeting rather than three is the same claim with the work done.

Keep the reflection about your practice, not your results. Your data section exists elsewhere. A reflection that drifts into reporting numbers has abandoned the task the rubric is actually scoring, which is the change in you as a systems-level clinician.

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

Apply a reflective model rather than describing one. If your program favours a particular model, walk your material through its stages in a paragraph. Three paragraphs explaining the model consume the space your analysis needs and demonstrate nothing.

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 with no superseded belief. If nothing you assumed turned out to be wrong, no reflection has taken place and the absence is obvious.
  • One anecdote claimed for every domain. Stretching a single decision across five competencies signals a thin evidence base rather than a broad one.
  • Only successes. A reflection with no failed attempt in it reads as curated, and the failed attempt is usually where the transferable learning sits.
  • Confusing reflection with the practicum record. A reflection is scholarly prose. Hours, logs, counts and evaluations are a verified record belonging entirely to you and never mixing with writing support of any kind.

Before you submit

  • A named, dated competency framework organizes the piece
  • Each domain rests on one specific decision rather than a general impression
  • Every decision includes the belief you held beforehand
  • At least one domain shows a later instance where you acted differently
  • One failed attempt at influence is analyzed honestly
  • 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, not sentiment

Writing the NR-705C reflection?

Send the rubric and the competency framework out of Canvas along with your own notes on the decisions you made. A premium original draft comes back in 24 to 48 hours organized by domain with every claim evidenced, revised free until it lands. Hours, logs and preceptor evaluations are yours alone and never part of the work.

Questions students ask about this stage

Is it acceptable to get writing help with a reflection about my own practicum?
Help with the writing, yes; help with the record, never, and the difference is worth stating precisely. Your hour log, activity or encounter counts, your site evaluations and anything a preceptor or the university signs are verified records of what you personally did. Nobody else can compose, reconstruct or estimate them, and no legitimate service will offer to. The reflection is a different object: scholarly prose about decisions you made during work you genuinely performed, and shaping that prose, tightening the argument and fixing the register is ordinary academic writing support of the kind a university writing centre provides. The practical test is where the substance comes from. If you can describe the decisions, the assumptions and the outcomes, the writing can be organized and sharpened. If the underlying experience is not there, no amount of writing help creates it, and a reflection resting on experience that did not occur is an integrity problem rather than a stylistic one.
How do I write about leading people who are senior to me?
Write about the mechanics of influence rather than about the hierarchy, and be honest about what worked. Most DNP students run projects without formal authority over anyone involved, and the reflective material there is genuinely rich: what you offered a senior colleague in exchange for their time, whether you led with the evidence or with the operational problem, when you used your chair or a site champion as a channel rather than approaching directly, and how you handled a decision that went against you. Avoid two traps. The first is writing yourself as powerless, which is both inaccurate - you had evidence, a plan and institutional backing - and unimpressive on a leadership competency. The second is overstating your influence, which anyone who has worked in a practice will read as inexperience. The register that works is the one a consultant uses: here was the constraint, here is what I tried, here is what moved and what did not, here is what I now understand about how decisions actually travel in this organization.
Can I write about conflict between sites or between staff?
Yes, carefully, and with the focus on the system rather than the people. Differences between locations about how a step should run are ordinary organizational facts and often illuminate something real about local constraints, so they belong in doctoral reflection. What does not belong is anything that reads as a complaint about identifiable colleagues or that reproduces a disagreement in a way a participant would recognize and resent. Describe the positions rather than the personalities: one location wanted the step at check-in because their rooming stage is compressed, the other wanted it at rooming for privacy, and the mechanism required only that it happen before the provider entered the room. Then write what you decided and why. That version is analytic, professional, and safe to circulate, which matters because reflective work occasionally travels further than students expect. If in doubt, write the paragraph and then reread it as though the practice manager were the reader.

Keep going

Online now