NR-721 Week 2 Collaborative Practice Competencies: How to Write It

What NR-721 Week 2 asks for

Why do good people on a good team still miss each other? A community health center that had recently added a nurse practitioner to a walk-in schedule started seeing something odd at the front. Patients arriving with a wound check were being roomed by whoever was free, assessed by whoever was closest, and sent home by whoever signed the note, and about once a week two clinicians documented the same encounter from different assumptions about who was doing the follow-up call. Nobody was careless. Every person could describe their own job accurately. What no one could describe was the same job in the same words as the person beside them, which is the definition of a missing shared mental model rather than the definition of a bad team.

That distinction is the territory of this stage. Collaborative practice is a set of competencies, not a personality trait, and competency frameworks in interprofessional education exist precisely so that a leader can say what is missing in language other professions recognize. The written work here is typically an application piece: you take a team or a service you know, you assess it against a named competency framework, and you write a judgment supported by observable evidence rather than by how the team feels to work in.

Expect the format to reward a specific kind of restraint. Doctoral graders in leadership courses look for whether you can hold a construct steady. A student who writes that the team lacks communication has said nothing scoreable. A student who writes that the team has no structured method for transferring responsibility at shift change, that two of four professional groups were unable to name who closes an outstanding referral, and that this pattern maps to the role clarity domain of a published framework has produced a finding, a source of evidence, and a defensible category.

Note what this stage is not. It is not a place to conduct research on your colleagues. If your paper draws on conversations or observations at work, treat them as professional experience described in general terms rather than as data collected under a protocol, keep every person unidentifiable, and do not present informal impressions as survey findings. Doctoral programs are strict about this distinction and it is easy to violate accidentally with a sentence like I surveyed the staff.

The other habit worth installing now is comparative reasoning. A competency assessment gains most of its value when you say which domains are strong as well as which are weak. A team with a genuinely strong mutual support culture and genuinely weak information transfer needs a different intervention from a team that is weak in both, and week five will ask you to design that intervention. A one-sided assessment forces you into a generic plan later.

The NR-721 Week 2 method, step by step

Six moves for assessing a team against a competency framework in writing.

1. Choose one framework and stay inside it

   Interprofessional competency sets and team performance models each carry their own domains. Pick the one that fits your setting, name it with its year, and use its domain names as your headings rather than inventing a hybrid nobody can check.

2. Define each domain in the source's words before you judge it

   One sentence of definition, cited, then your assessment. Graders can only score whether your evidence fits the domain if you have shown what the domain means, and this also stops the drift where role clarity slowly becomes anything you did not like.

3. Attach observable evidence to every judgment

   Behaviors, artifacts and outcomes: what someone could see, what documents exist or do not, what the operational data shows. An assessment that rests on the phrase in my experience across five domains has no evidentiary layer at all.

4. Rate the strong domains as carefully as the weak ones

   Strength is diagnostic. A team that already trusts one another but has no structure is a design problem, while a team with structure and no trust is a very different one, and naming which you have determines every later stage.

5. Explain each gap by mechanism, not by attitude

   Ask what feature of the work produces the behavior: a schedule that never overlaps two professions, a record system that hides one group's notes, an incentive that pays for volume in one department and for continuity in another.

6. Close with the one domain you would move first, and why

   Rank by leverage rather than by severity. The domain whose improvement makes other domains easier is usually the right first target, and saying so explicitly is the leadership judgment the rubric is actually reading for.

A layout and word budget for a competency assessment

Our frame for assessing one team against a named framework, sized for roughly 1,400 to 1,700 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.

Evidence craft for team competency writing

Frameworks are dated documents and must be cited as such. Competency sets get revised, and a domain list from one edition does not always match the next. Name the issuing body and the edition or year inside the sentence, so a reader can check that the four domains you used are the four that document contains.

Keep experience as illustration and literature as proof. The order that scores is claim, cited support, then the scene from your setting showing the construct operating. Reversed, the paragraph reads as an anecdote with a reference stapled to it, and leadership graders mark that ordering consistently.

Prefer artifacts to impressions. A huddle that has no written agenda, a referral form with no field for the receiving clinician, a schedule showing two professions never on site at the same hour: these are checkable, they survive a grader's skepticism, and they point directly at a fixable design feature.

Say what you could not observe. Every honest assessment has a blind side, usually the perspective of a group you are not part of. One paragraph naming that limit strengthens the paper rather than weakening it, and its absence is the most common reason a confident assessment reads as overreach.

Five mistakes that cost points in this week's territory

• Framework shopping. Borrowing one domain from each of three models produces a list nobody can validate your reasoning against.
• Communication as the finding. Almost every team problem can be labelled communication, which is why the label carries no analytic weight on its own.
• Informal impressions presented as data. Writing that you surveyed or interviewed staff describes a study, and describing a study you did not conduct under a protocol is a serious error in a doctoral course.
• All weaknesses and no strengths. An assessment with nothing positive in it reads as a grievance and gives your later intervention nothing to build on.
• Judgments with no observable behind them. Five domains rated on personal feeling is an opinion piece wearing a framework's headings.

Before you submit

• One framework is named with its issuing body and year
• Each domain carries a sourced definition before any judgment
• Every judgment has at least one observable behavior, artifact or figure attached
• Strong domains are assessed with the same care as weak ones
• The two weakest domains have a structural mechanism explaining them
• A closing paragraph states what the assessment could not see

Questions students ask about this stage

Keep going