AOS Weekly Team Meeting Template

The AOS weekly team meeting is the heartbeat of the operating rhythm. Based on the Accelerate Operating System (AOS) model, it follows a fixed structure: a fast scan of the scorecard and priorities to find what is off track, then the bulk of the time spent solving the issues that surface.

When to use it

Run it the same day and time every week so it becomes a dependable ritual rather than a meeting people negotiate around. It keeps the quarter moving between monthly reviews and quarterly resets.

Who attends

Keep it to the team that shares a scorecard, three to ten people who own numbers and priorities. A tight room keeps the pace fast and the problem-solving honest. Stakeholders who only need updates can read the notes instead.

How to run it

Open with good news, then move fast through the scorecard, priorities, and action items, turning anything off track into an issue rather than debating it in the moment. Protect the largest block for the issues list: identify the real problem, discuss it, and solve it for good. 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 the reporting segments fast so the issues list gets the time.
• Move off-track items to issues instead of solving them mid-report.
• Solve issues at the root, not the symptom, even if it takes the whole block.
• Close every issue with an action, an owner, and a date.

Common mistakes

• Letting the reporting segments swell and starving the issues list.
• Reporting activity instead of movement on the actual numbers.
• Solving symptoms each week so the same issue returns.
• Ending without clear action items and owners.

Make the weekly meeting earn its slot. Run it in OrgTP and keep the scorecard, priorities, and issues live week to week, with OrgTP adapting to your cadence.