Protocol
Call out the critical fact and name its receiver
A fact shouted into a group chat can belong to everybody and therefore nobody.
When it fits
- Several people need the same urgent fact while one person must react to it.
When to avoid it
- Do not flood shared channels with low-priority call-outs; excessive broadcasting can hide the truly urgent signal.
Why it matters
State the critical fact briefly, direct it to the person who needs to act, and make the expected response visible. The call-out gives the whole team situational awareness while preserving a named receiver. Use it for fast-changing, consequential information—not as a substitute for normal task assignment.
Steps
- The group heard the same fact and one person knows they own the immediate response.
An example
'Marta, replication errors just crossed the stop threshold. Pause the next batch and confirm.'
Check your result
The group heard the same fact and one person knows they own the immediate response.
Keep this limit in mind
- Do not flood shared channels with low-priority call-outs; excessive broadcasting can hide the truly urgent signal.
Connected ideas
Useful withClose a critical instruction with a check-back
Evidence and sources
Supports
AHRQ TeamSTEPPS recommends call-outs for critical information that multiple team members need simultaneously and emphasizes directing information to a specific individual by name.
Broadcasting can overload attention; reserve it for information that truly requires shared immediate awareness.
Tool: Call-Out · Call-Out overview