Protocol

Brief the team before consequential work starts

Five minutes of shared plan can be cheaper than five different plans.

About 1 min read

Before you use it

Use when
  • Several people will act in parallel on a task where role confusion or resource gaps can create failure.

Keep this limit in mind

  • Do not add a formal brief to low-risk work that one person can perform safely without coordination.

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

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

  1. The goal and success condition are explicit.
  2. Each critical role has an owner.
  3. Dependencies and sequence are understood.
  4. Important constraints and resources are visible.
  5. A trigger for huddling or stopping is named.
  6. 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.

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 readingBrief the team before consequential work starts

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

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