Quality Improvement Zone

A team huddle is a short, focused discussion that helps teams review current information, share learning and agree on next steps. Huddles are usually held regularly and follow a simple, consistent structure that supports communication, problem-solving and improvement.

Team huddles create a dedicated opportunity to review progress, discuss learning, identify barriers and coordinate actions. They are commonly used to support improvement work, but can also be used to discuss quality, safety, operational issues and service performance.

While many teams find a 15-minute weekly huddle effective, the frequency, format and content should reflect the needs of the team and the purpose of the huddle. The structure should be consistent enough to feel familiar, but flexible enough to remain useful.

Improvement work generates learning, data and actions that need regular review. Team huddles create a structured opportunity for teams to reflect on progress, make decisions and maintain momentum.

Team huddles can help you:

• review data and performance regularly
• share learning from PDSA cycles and improvement activity
• identify issues, barriers and risks early
• coordinate actions across the team
• improve communication and collaboration
• support shared ownership of improvement work
• maintain momentum between formal meetings

The most effective huddles focus on learning, action and decision-making rather than simply providing updates.

1. Agree the purpose and format

Decide:

• the purpose of the huddle
• who should attend
• how often it will take place
• how long it will last

Some teams use daily huddles to review operational issues, while others use weekly huddles to review improvement activity. Choose a format that supports the needs of the team.

2. Prepare visual information

Use a visual display to support discussion and shared understanding.

This may include:

• visual management boards
• run charts
• SPC charts
• dashboards
• project boards

shared screens for virtual meetings

The aim is to review information together rather than rely on verbal updates alone.

3. Review data and variation

Review the measures that are most relevant to the work and discuss what they are telling you.

Useful questions include:

• What is the data telling us?
• What variation can we see?
• Are we seeing improvement?
• Is there anything unexpected?

Focus on understanding the system rather than simply reporting numbers.

4. Share testing and learning

Discuss recent improvement activity, including:

• PDSA cycles
• tests of change
• stakeholder feedback
• implementation activity

Questions may include:

• What did we expect to happen?
• What actually happened?
• What did we learn?
• What should we do next?

5. Identify barriers and support needed

Explore any issues affecting progress.

Consider:

• What barriers are we facing?
• What support is needed?
• Are there any risks or dependencies?
• Is anything preventing progress?

Where barriers cannot be resolved by the team, agree how they will be escalated.

6. Agree and record next steps

Every huddle should conclude with clear outputs.

Agree:

• actions
• owners
• timescales
• decisions made
• issues requiring escalation

Capture these visibly and review them at the next huddle.

7. Review and adapt the huddle

Periodically review whether the huddle remains useful.

Consider:

• Are we learning from the discussion?
• Are decisions being made?
• Are actions progressing?
• Does the current format still meet our needs?

Adapt the agenda, structure or frequency if the huddle is becoming a routine reporting meeting rather than a useful improvement tool.