Protocol
Brief the team before consequential work starts
Five minutes of shared plan can be cheaper than five different plans.
When it fits
- Several people will act in parallel on a task where role confusion or resource gaps can create failure.
When to avoid it
- Do not add a formal brief to low-risk work that one person can perform safely without coordination.
Why it matters
Before execution, align on the goal, roles, sequence, known risks, available resources and the signal that would require replanning. Keep the brief short enough to preserve momentum. Its output is a shared plan, not meeting minutes.
Steps
- The goal and success condition are explicit.
- Each critical role has an owner.
- Dependencies and sequence are understood.
- Important constraints and resources are visible.
- A trigger for huddling or stopping is named.
- Open disagreements are resolved or escalated before execution.
An example
Before a production mass update, identify who runs it, who watches locks, who validates results and who can stop the batch.
Check your result
Team members can independently state the same goal, their role and the main stop condition.
Keep this limit in mind
- Do not add a formal brief to low-risk work that one person can perform safely without coordination.
Connected ideas
Use beforeHuddle when reality invalidates the plan
Evidence and sources
Supports
AHRQ TeamSTEPPS brief guidance asks teams to align on goals, roles, responsibilities, plan, workload and resources before work.
The brief should be proportional to the task; low-risk individual work does not need a team ceremony.
Sharing the Care Plan: Brief · Brief checklist