AOS Annual Strategy Meeting Template

The AOS annual strategy meeting sets the destination for the year and the first leg of the route. Based on the Accelerate Operating System (AOS) model, it sits at the top of a quarterly operating rhythm, turning a long-term vision into a short list of annual priorities, a refreshed scorecard, and the quarterly work that delivers them.

When to use it

Run this once a year, late in the current year or at the very start of the new one, so the team enters the year aligned. It anchors the rest of the rhythm: the annual session sets direction, and each quarter executes a leg of it.

Who attends

Include the leadership team and the key contributors who will own annual priorities, usually six to fifteen people. The group should be wide enough to commit the organization yet small enough to make real decisions. Cascade the detail to teams afterward rather than crowding the room.

How to run it

Begin with an honest year in review against last year priorities and the scorecard. Reconnect with vision, assess market and capabilities, then set a focused set of annual priorities and the numbers that will track them. Cascade those into a concrete first quarter with named owners before anyone leaves. 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

• Ground the year in an honest review before looking ahead.
• Keep annual priorities few enough that the team can name them.
• Tie every annual priority to a measurable scorecard number.
• Cascade to quarterly priorities so the plan becomes executable.

Common mistakes

• Setting lofty annual goals with no quarterly execution path.
• Skipping the honest review and repeating last year mistakes.
• Producing a plan that lives in a deck and never in the work.
• Defining no scorecard, so progress cannot be measured through the year.

Turn the year ahead into a plan you can run. Run it in OrgTP and connect annual priorities to quarterly and weekly execution, with OrgTP adapting to whatever cadence your team keeps.