Operating Cadence: Weekly, Monthly and Quarterly Meeting Agendas

Each level answers a different question, which is why they shouldn't be merged:

• Weekly: Are we on track, and what's blocked? This is about the next seven days.
• Monthly: Did we hit our numbers, and why or why not? This is about the last thirty days and any correction needed.
• Quarterly: Are we working on the right things for the next three months? This is about priorities and resources.
• Yearly: Where are we going, and what has to be true to get there? This is about direction and budget.

When a weekly meeting turns into a strategy debate or a quarterly session turns into a status update, the layers have collapsed. Keep each meeting to its own question, and park anything else on a list for the right forum.

Keep it to 60 minutes with the same agenda every week:

1. Numbers glance (10 minutes). Review five to ten key numbers on one page, flagging anything off track. No discussion of causes yet.
2. Priorities check (10 minutes). Each leader states whether their top one to three priorities are on or off track.
3. Issues list (35 minutes). Pick the most important problems, and for each one discuss it, decide, and assign an owner and date.
4. Recap (5 minutes). Read back each decision and action item, and confirm what customers or staff need to hear.

The output is a short written list of decisions and owners, sent within an hour. The most common failure is spending the whole meeting on reports that could have been read in advance. Ask people to update the numbers page before the meeting, so the time goes to decisions. The executive dashboard cadence covers how to build that page.

The monthly review looks back and asks what to change. Allow 90 to 120 minutes, and include department heads as well as the leadership team.

• Inputs: closed financials, a KPI pack by function, a list of last month's commitments, and any customer or people issues that surfaced.
• Agenda: results against plan, three to five explanations of the biggest variances, cross-team problems that a weekly meeting couldn't fix, and decisions on what to start, stop or change.
• Outputs: a one-page summary of variances and decisions, and any changes to next month's priorities.

Insist that variance explanations name a cause and an owner. "Sales were down" is a fact. "Sales were down because two proposals slipped, and the owner will re-engage both by the 15th" is something you can act on. Reuse your weekly status report format for project updates, so the monthly meeting doesn't need new reporting.

The quarterly session resets the company's focus. Plan half a day, ideally away from daily interruptions.

1. Review the last quarter's priorities: what was finished, what wasn't, and why.
2. Look at the current state of the business: results, customer feedback, team capacity and risks.
3. Choose the three to five company priorities for the next quarter, and no more.
4. Assign one owner to each priority, with a measurable definition of done.
5. Check capacity. Say your team has time for four priorities and you've listed seven; cut three now, or you'll decide by neglect later.
6. Agree how progress will show up in the weekly and monthly meetings.

Write the priorities on a single page that everyone can see. If people can't recite them, they're too many or too vague.

Every cadence collects meetings over time. Once a quarter, audit yours with these questions:

• Does this meeting have a written purpose and a decision or output every time?
• Are the right people in the room, and would anyone lose anything if they skipped it?
• Could a written update replace it?
• Is it more frequent than the decisions it supports?

Do the math on cost, too. In this example, a one-hour weekly meeting with ten people is ten person-hours every week, or more than five hundred person-hours a year. If it doesn't produce decisions worth that time, shrink the attendee list or shorten the meeting.

A related point is to avoid stacking cadences. If every function runs its own weekly, monthly and quarterly, leaders spend their whole week in reviews. Ask functions to feed the company cadence, not duplicate it.

Put the cadence itself in your work management system so it isn't dependent on one person's calendar. A project tool such as Asana can hold recurring agenda tasks, the priorities list and the action items, with each owned by a named person. A workflow tool such as Monday.com suits teams that want boards and dashboards for numbers and status in one place. Setup details are in the guide on setting up Asana for a small team, and a comparison is in the project tool comparison.

If the cadence assigns decisions to specific people, back it with a RACI chart so nobody is unsure who owns what. Professional-services firms with billable work should also read project tools for professional services.