NR-718 Week 6 Leading Without Authority: How to Write It

What NR-718 Week 6 asks for

A workgroup convened to redesign a discharge process produced thirty-one pages of minutes across nine months and one implemented change. Reading the minutes in sequence explained why. Every meeting recorded a discussion, several recorded a decision, and almost none recorded an owner. The action column, where it existed at all, contained entries like the team will explore and pharmacy to review. Fourteen of the seventeen recorded actions had no name and no date attached. The three that did were completed. The workgroup was not lazy, unmotivated or badly attended; it was ungoverned, and its own documentation showed exactly where the accountability leaked. Nobody had ever declined a task. Tasks had simply never been assigned to a person in writing.

That is the territory of this stage. The written work usually asks you to analyze or design interprofessional collaboration around a practice change, sometimes through a named team or collaboration framework, sometimes through a leadership self-assessment applied to a real team situation. Whatever the framing, the analytic core is the same: how influence works when authority is absent, and how written structure substitutes for hierarchy.

Doctoral students often approach this stage as a soft topic and write it in a soft register, which is where the marks go. Interprofessional collaboration has a substantial literature with measurable outcomes, published competency frameworks, and well-documented failure modes including diffusion of responsibility, professional hierarchy effects on speaking up, unclear decision rights and role ambiguity. Writing about it in terms of respect and communication, without engaging that literature or naming a mechanism, produces a page that could have been written before the degree started.

The practice-doctorate contribution is structural. You are not being assessed on whether you get along with colleagues; you are being assessed on whether you can design the conditions under which a group of people from different professions, with different accountabilities and different training in what counts as evidence, will reliably do a thing. Those conditions are largely made of documents: a charter that states scope and decision rights, an agenda that forces decisions rather than updates, minutes that assign owners and dates, and a measure that everyone can see.

The NR-718 Week 6 method, step by step

Six moves for writing interprofessional leadership as structure rather than sentiment.

1. Map the professions by what each is accountable for

   Pharmacy, therapy, social work, medicine, nursing, informatics and administration each answer to different standards, different regulators and different metrics. Write those accountabilities before you write about collaboration, because most friction that looks interpersonal is two people being correctly loyal to different obligations.

2. Name the decision rights explicitly

   Who decides, who must be consulted, who is informed, and who can stop the change. Most collaborative failures trace to this never having been written down. Putting it in a charter, in plain language, is the single highest-yield leadership document in this territory.

3. Choose one collaboration or team framework and apply it

   Published interprofessional competency sets and team effectiveness models give you named domains and a language other professions recognize. Cite the source with its year, use its actual domains, and apply at least one of them to your real situation rather than describing all of them abstractly.

4. Design the meeting artifacts, not just the meeting

   An agenda that lists decisions rather than topics, a minute template with an owner and date column, a one-page measure summary that opens every session. Write these as designed objects with reasons. They are the mechanism by which shared accountability actually occurs.

5. Write the influence strategy for the party you cannot direct

   Pick the profession or department whose cooperation you most need and least control. State what they are measured on, what your change costs them in time or risk, and what version of your proposal serves their accountability as well as yours. Influence in this setting is mostly redesign, not persuasion.

6. Say how you would handle open disagreement

   Name the escalation path, the forum where a stalemate gets resolved, and the standard of evidence that would settle a factual dispute. Groups without an agreed route through disagreement do not avoid conflict; they route it underground, where it becomes non-participation.

A layout and word budget for an interprofessional leadership analysis

Our frame for this stage, sized for roughly 1,400 to 1,700 words. If your section requires a charter or similar artifact as an appendix, budget that separately. This outline is ours rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

Evidence craft for leadership writing

Cite the collaboration literature rather than asserting its conclusions. Claims about team communication and outcomes, hierarchy effects on speaking up, or role clarity and error rates are all empirical claims with sources. A leadership paper that runs entirely on assertion forfeits the support rows even when its content is sound.

Write about colleagues at the level of role and accountability. Never name individuals or characterize their motives in a document you do not control. The chief of a service resisting a change becomes the service accountable for throughput on the affected unit, which is both more accurate and more useful, since it points at what would have to be true for them to agree.

Keep any team scene de-identified and fair. If you illustrate with a real situation, remove identifiers and enough contextual detail that no participant could be recognized, and write the other party's position in a form they would accept as fair. A scene that exists to make somebody look bad reads as grievance and is marked as such.

Attach a measure to a collaboration claim wherever one exists. Meeting attendance, action closure rate, time from decision to implementation, protocol adherence by discipline: these turn a soft assertion about teamwork into something a reader can check, and they are usually available in documents the group already produces.

Five mistakes that cost points in this week's territory

• Sentiment in place of structure. Mutual respect and open communication describe a desired outcome, not a mechanism that produces it.
• No decision rights. A collaboration plan that never says who decides has designed a discussion group.
• Other professions written as obstacles. Treating resistance as a character trait rather than as a rational response to a different accountability produces strategies that do not work.
• A framework named and never applied. Listing a competency set's domains without working one through your situation is a citation, not an analysis.
• No route through disagreement. Plans that assume consensus fail the first time somebody dissents, and the paper should say what happens then.

Before you submit

• Each profession appears with its own accountability and metrics
• Decision rights are stated explicitly in charter language
• A named collaboration framework is cited with its year and one domain is applied
• Meeting artifacts are designed with owners, dates and a visible measure
• The influence strategy addresses the least controllable party in their own terms
• An escalation route and an evidence standard for factual disputes are named
• No individual is identified or characterized by motive

Questions students ask about this stage

Keep going