Protocol

Huddle when reality invalidates the plan

Do not keep executing the old plan while privately admitting it is obsolete.

About 1 min read

Before you use it

Use when
  • Conditions, workload, team availability or evidence change enough that the existing plan is no longer reliable.

Keep this limit in mind

  • A huddle is a replanning tool, not a recurring status meeting with no changed decision or action.

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

Pause briefly, state what changed, identify which part of the plan is now invalid, redistribute work or alter the sequence, and restate the updated plan. Any team member should be able to call the huddle when they see a material change. End when the new shared plan is clear.

Steps

  1. The team leaves with an updated plan that explicitly responds to the changed condition.

An example

A key expert becomes unavailable during a cutover; the team huddles to reduce scope and reassign the validation role.

Check your result

The team leaves with an updated plan that explicitly responds to the changed 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 readingHuddle when reality invalidates the plan

Evidence and sources
Supports

AHRQ TeamSTEPPS recommends a huddle when conditions, membership or plan effectiveness change enough to require replanning.

A huddle should change the plan or shared state; recurring updates without a decision need are a different meeting.

Monitoring and Modifying the Plan: Huddle · Monitoring and Modifying the Plan

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