Protocol

Call out the critical fact and name its receiver

A fact shouted into a group chat can belong to everybody and therefore nobody.

About 1 min read

Before you use it

Use when
  • Several people need the same urgent fact while one person must react to it.

Keep this limit in mind

  • Do not flood shared channels with low-priority call-outs; excessive broadcasting can hide the truly urgent signal.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

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

  1. 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.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingCall out the critical fact and name its receiver

More from this collection

Close the communication loop when ambiguity can become an error

Use SBAR when the issue needs a decision now
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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details