NR-662 Week 2 Microsystem Assessment and Stakeholders: How to Write It

What NR-662 Week 2 asks for

A two-provider family practice on the edge of a small city runs about sixty visits a day, roughly a third of them children. There is one medical assistant per provider, a shared front desk, a nurse who floats, and a scheduling template that puts well-child visits into the same twenty-minute slots as everything else. On Tuesdays a second nurse comes in and the whole rhythm of the building changes. None of that appears in a problem statement, and all of it determines whether a new step in the visit will survive. Describing it precisely is the work of this stage.

A microsystem assessment is an operational portrait, not a history of the organization. The elements that earn points are the ones that constrain change: who does what during the encounter, how information moves, where the record system helps and where it fights, what the volume and staffing pattern look like across a typical week, and what else the team is already being asked to absorb. Capstone readers are looking for a writer who can see a clinic as a system with capacity limits rather than as a group of people who should try harder.

The second half is the stakeholder map. Every improvement project has people who can authorize it, people who must perform it, people affected by it, and at least one person who can quietly stop it. The written version names each group in role terms, states what each one gains or loses if the change goes in, and says what you will do to earn or keep their cooperation. Sections that run a discussion at this stage often ask you to post the barrier you consider most serious. Write that post as final copy, because responses do not reopen once submitted in Canvas, and a barrier described casually in public becomes the thing peers keep asking about.

Where the boundary sits in an assessment stage. Your 144 hours, the observations you make inside the practice, the conversations with the person guiding your immersion and every relationship at the site belong to you alone and cannot be delegated. Hour logs, site paperwork, signatures and any evaluation completed about you are your own record, never drafted, reconstructed or estimated with help. This manual addresses the written layer: how to organize an operational description, how to argue about influence and capacity, how to keep a stakeholder analysis from becoming gossip on a page. Anything you observed reaches the document de-identified, with no patient, staff member or site identifiable from what you wrote.

The NR-662 Week 2 method, step by step

Six moves for writing a microsystem portrait that a reviewer can use.

1. Fix the unit of analysis before the first paragraph

   A microsystem is the smallest team that delivers the process end to end. For an action plan project it is the clinician, the medical assistant and the front desk on one clinic site, not the whole practice group. State the boundary in a sentence so a reader knows what your later results are results about.

2. Count what can be counted

   Visits per day, proportion pediatric, staff by role, exam rooms, average appointment length, number of providers on a typical Tuesday. Numbers make an operational description credible in a way that adjectives never do, and the same figures reappear later when you argue about feasibility and sample size.

3. Walk the process and write what actually happens

   Follow the sequence in real time rather than as it is described to you. Note where the step you care about is supposed to occur, who is holding the room at that moment, and what competes for the same thirty seconds. The distance between the official workflow and the observed one is usually where your intervention has to fit.

4. Map influence, not just job titles

   Sort people into who authorizes, who performs, who is affected and who can veto informally. In small practices the informal veto is often held by whoever controls the schedule or the rooming routine, and a project that ignores that person is planning around the wrong org chart.

5. State each group's interest in its own terms

   Write what the change costs and offers from where that person stands. For a medical assistant, an added step is seconds against a rooming target. For a parent, it is a clearer plan for a wheezing child. Interests written from the stakeholder's perspective produce realistic engagement strategies; interests written from yours produce a list of people who should agree with you.

6. Close with capacity, honestly

   Say what else the team is absorbing this quarter, what its slack looks like, and what that means for how much change your project can reasonably ask. A capstone that admits a limited appetite for change and designs to it outscores one that assumes unlimited goodwill.

A layout and word budget for a microsystem assessment

Our frame for an assessment and stakeholder document, sized for roughly 1,300 to 1,600 words. It is our own outline rather than anything the university issues, and your scoring guide outranks it wherever they disagree.

Evidence craft for an operational description

Anchor the framework you are using and name it. Structured approaches to assessing a clinical microsystem exist and are published; using a named one and following its categories lets a reviewer check your completeness against a standard rather than against your taste. Attribute it in the sentence where you first use its language, with a year.

Distinguish observed, reported and recorded. Three sources of fact appear in an assessment: what you watched, what staff told you, and what the record system shows. Label each as you use it. A paragraph saying the rooming process usually includes a device check, reported by two medical assistants, is honest evidence. The same claim written flatly reads as measurement and will not survive a careful grader.

Do not let the stakeholder map become character description. Write about roles, interests and authority, never about personalities. A sentence saying the scheduler is difficult is unprofessional and unusable. A sentence saying the scheduling role bears the cost of any change to visit length, and therefore needs to be consulted before the template is touched, is analysis that a director would act on.

Give the record system its own paragraph. Most ambulatory improvement projects live or die on whether the electronic record can prompt, capture and report the thing you care about. Say what exists now, what would need to be built, and who owns that build. A project that discovers in week five that no field captures the outcome has usually skipped this paragraph.

Keep the site unidentifiable. Describe the practice by type, size and population rather than by name, location or any detail that would narrow it to one building. This protects the site and is also better scholarly practice, because it forces you to write the features that generalize instead of the ones that identify.

Five mistakes that cost points in this week's territory

• An assessment made of history. When the practice was founded and how it grew tells a reviewer nothing about whether your change can fit into a twenty-minute visit.
• Stakeholders listed without interests. A roster of titles is not an analysis. Each entry needs what that role gains, loses and controls.
• The org chart mistaken for the influence map. Formal authority approves projects; informal authority decides whether they happen on a busy Tuesday.
• No numbers anywhere. Operational writing without volume, staffing or timing figures reads as impression, and impressions cannot support a feasibility claim.
• Capacity ignored. Projects designed as if the team had free attention are the ones that report low fidelity in week six and cannot explain why.

Before you submit

• The microsystem boundary is stated, with what lies outside it
• Volume, staffing and appointment structure appear as figures
• The current process is written as an observed sequence, not an official one
• Every stakeholder group carries authority, interest and a specific cost or gain
• The record system's current capability is described honestly
• Nothing in the document identifies a patient, a staff member or the site

Questions students ask about this stage

Keep going