AOS Daily Huddle Template

The AOS daily huddle is a short standing meeting that keeps a team in sync without eating the day. Based on the Accelerate Operating System (AOS) model, it shares a couple of quick metrics, names today priorities, and surfaces blockers so help arrives the same morning rather than days later.

When to use it

Run it every working day at the same time, ideally early, so the team aligns before the day fills up. It works best for teams moving fast on shared work where small misalignments would otherwise compound over a week.

Who attends

Keep it to the working team, three to twelve people, standing if you can so the meeting stays brief. Anyone with a clear, repeating reason to align belongs; everyone else can read the notes.

How to run it

Share the quick metrics, then go around for one-line priorities and any stuck points. The huddle is for surfacing blockers, not solving them: decide who helps, then take the detail offline so the meeting ends on time. Note: this agenda is an independent interpretation of the AOS quarterly-rhythm model and is not affiliated with or endorsed by any provider.

Facilitator tips

• Keep it standing and time-boxed so it never creeps past fifteen minutes.
• Limit each person to one priority and one blocker.
• Surface blockers in the huddle, solve them after it.
• Hold the same time every day so it becomes automatic.

Common mistakes

• Letting the huddle balloon into a full status meeting.
• Solving blockers in the room and dragging everyone in.
• Turning quick updates into long narratives.
• Skipping days so the rhythm never sets.

Keep the team aligned without the meeting tax. Run it in OrgTP and keep daily metrics and blockers visible, with OrgTP adapting to your cadence.