Reflect on teamwork, then choose one useful next step
Harborlight Care Network is a fictional, 500+ employee care organization used for this example. This page helps multidisciplinary teams discuss how coordination worked after a challenging event, without turning the conversation into an investigation or a clinical review.
Keep the conversation within bounds
Discuss teamwork and coordination—not identifiable cases or clinical conclusions.
Use general, de-identified observations about how people shared information, understood roles, and coordinated work. Do not include patient-identifying details in the discussion or notes.
This debrief is distinct from clinical incident investigation, formal reporting, and approved safety procedures. If the conversation moves toward sensitive or patient-identifying details, anyone may pause it and redirect the group. If a matter requires a formal process or a trained role, use the organization’s existing approved route; this page does not define that route.
Questions and corrections: In this example, Clinical Operations and Support Services maintains the guidance. Ask the local facilitator or that function to clarify the appropriate help route when an issue falls outside this coordination discussion.
Illustrative 30-minute agenda
Example timings to help the facilitator pace the conversation; they are not a required workflow.
| Segment | Suggested time | Facilitator cue |
|---|---|---|
| Set the boundary | 3 min | State the de-identification and scope limits; agree that anyone can pause or redirect. |
| Recall the coordination | 7 min | Describe what the team needed to coordinate, without reconstructing a clinical case. |
| Explore teamwork | 10 min | Use the prompts below to surface what helped, what got in the way, and what remains unclear. |
| Name a learning theme | 5 min | Separate observable facts from interpretations; phrase an opportunity as a question or theme. |
| Agree one follow-up | 5 min | Name an accountable role and how the team will revisit the action through its existing local process. |
Prompts for a useful team reflection
Invite specific observations; participation is voluntary, and the group can pause or redirect at any point.
Which roles had relevant context, and when did they have an opportunity to contribute?
What information did the team expect to share? Where was the handoff or shared update easy—or difficult—to notice?
At which point was it clear who was coordinating the next step? Where did the group have to infer ownership?
Which team habit, shared cue, or coordination practice made it easier to stay aligned?
In Harborlight’s fictional example, two roles each believed another role had shared a routine coordination update. The team described the observable pattern—no agreed confirmation that the update had reached the group—rather than attributing it to one person. They framed the learning question as: “What shared cue would make receipt visible to the team?”
Turn discussion into learning themes
Capture de-identified coordination observations; do not record patient-identifying detail or clinical conclusions.
Separate observation from interpretation
Write what the group could observe before discussing why it may have happened.
- Observation: “The team did not have a shared confirmation that the update had been received.”
- Interpretation to keep separate: “Someone must have forgotten.”
Name what supported teamwork
Identify a coordination practice the group found useful, without implying it guarantees an outcome.
- Example: “A brief shared recap helped participants align on the next coordination step.”
- Note the context in which the practice helped.
Phrase an opportunity as a question
Keep learning themes open and focused on how the team works together.
- Example: “What shared cue would help the team notice that an update has been received?”
- Route clinical, safety-critical, or sensitive conclusions to the relevant trained role and approved process.
Assign one coordination-focused follow-up
A clear owner role and a real local review route make the handoff understandable.
The example below illustrates role-based ownership and is not a submitted task, approval, or record of completion.
-
1
Describe one observable action
Example: “The shift coordination role will test a brief shared recap at the team’s next existing handoff discussion.” This is a coordination example, not a clinical instruction.
-
2
Name the accountable role
For the example action, the shift coordination role owns arranging the discussion and bringing back what the team learns. Confirm who is covering that role and that they understand the agreed next step.
-
3
Agree how to revisit it
Use the team’s existing local process to review whether the action was tried and what was learned. This page is not a live work queue or system of record.
-
4
Hand off matters outside this scope
If a discussion raises a policy, safety-critical, clinical investigation, or sensitive matter, stop the debrief discussion of that matter and use the organization’s approved route and trained role.