Leave the debrief with one useful change

What we found in the news

AHRQ’s TeamSTEPPS guidance on debriefs, created in May 2023 and reviewed that December, offers a question teams can use:

“What did not go well that we can improve?”

The guidance describes reviewing events, recognizing useful actions, and incorporating lessons into future plans. It emphasizes an environment where mistakes can be discussed as opportunities to learn. This is a teamwork resource, not proof that a particular meeting format will improve outcomes in every setting. Read AHRQ’s debrief guidance (opens in a new tab).

Why this matters to us

After a difficult day, a team may have plenty to say and very little time left. The same coordination problem can return tomorrow if nobody has a place to examine it.

A debrief can offer that place, provided it is more than a round of general frustrations. People need to understand what happened, what helped, and what can realistically change. They also need to know that raising a problem will not automatically be treated as admitting personal failure.

There is room for appreciation here too. A colleague who clarified an uncertain handover or noticed a missing contact detail has contributed something worth understanding and repeating.

Keep the discussion close to the event

Consider an illustrative day-program team reviewing a confusing transport handover. Two people had different versions of the pickup arrangement. Staff resolved it, but only after several calls.

A useful discussion can reconstruct the sequence without inventing motives. Which information was available? Who received the change? Where did the two versions diverge? What made the eventual clarification possible?

The aim is to learn from the work as it actually happened. A manager who begins with a preferred explanation may miss the detail that would improve the process.

Staff should follow the organization’s confidentiality and recordkeeping requirements. A debrief is not a reason to copy unnecessary personal information into meeting notes.

Choose an improvement small enough to carry out

The team might decide that one role should confirm transport changes with the receiving service, and that the confirmation needs a clear place in the agreed workflow. That is more useful than a general instruction to communicate better.

The action needs an owner and a review point. If it requires another organization’s agreement, record that dependency rather than treating it as already solved. If the problem comes from staffing or a contract limitation, leaders need to address that level of responsibility.

A small action is not necessarily a small issue. It is simply a change the team can describe, try appropriately, and check.

Leave room for other accounts

The staff debrief will not capture everything the person receiving care or their supporter experienced. Where appropriate, the organization should seek their account through a suitable route and explain how feedback will be used.

Perhaps the person received no update while staff were making calls. Perhaps the arrangement was resolved but the uncertainty changed their plans. Those details can alter what the team chooses to improve.

A brief learning conversation also has limits. It does not replace formal incident reporting, safeguarding, professional review, or staff support after a distressing event. Teams need to know which issues require those additional processes and who will initiate them.

At the next review, ask what happened to the agreed action. Repeatedly collecting concerns without responding can make the invitation to speak feel hollow.

The genus connection

Today, genus can support agreed tasks and authorized communication in a configured care community. These functions can help a team carry an operational follow-up from a conversation into visible action, with the right people involved.

That is not a claim that genus provides a formal incident investigation or substitutes for an organization’s learning and accountability processes. The team still needs judgment, appropriate records, and leadership that responds.

We are interested in the modest but valuable connection between noticing a problem together and doing something specific about it.

One question to take away

What is one change from your last team debrief that someone owns and the team will return to check?