← Back to blog

Planning

How to Run Your Best Quarterly Planning Meeting

Jeremy Chatelaine · Jul 6, 2026 · 13 min read

You get four quarterly planning meetings a year. That's it. Each one sets the direction for the next 90 days.

Introduction

You get four quarterly planning meetings a year. That's it.

Each one sets the direction for the next 90 days. Get it right and the whole company pulls in the same direction for a quarter. Get it wrong and you spend three months fixing the confusion you created in a single day.

Most leadership teams treat the quarterly planning meeting as a calendar event. Something to survive. But it's the highest-leverage day on your calendar. One good day of decisions steers thousands of hours of work.

This practical guide covers how to prepare, how to run the day, what to do after, and the traps that ruin it.

Know your team's dynamic first

Every leadership team has a personality. Before you can run a good quarterly planning meeting, you need to know which one you're dealing with. The meeting fails in a different way for each type.

The Silo Squad. Each leader runs their own department well. Sales does sales. Support does support. But nobody looks across. The quarterly planning meeting turns into five separate status reports stapled together. Everyone waits for their turn to talk and checks out during everyone else's.

The Debate Club. Smart people who love to discuss. Every topic gets picked apart from six angles. The meeting is lively, everyone feels heard, and at 5 PM nothing has been decided. They mistake talking for deciding.

The One-Voice Team. The founder or CEO talks. Everyone else nods. Priorities get set fast because there's no real discussion. Then those priorities quietly die over the quarter, because the people who nodded never believed in them.

The Peacekeepers. Nobody disagrees out loud. The room feels warm. Patrick Lencioni calls this out in The Five Dysfunctions of a Team: fear of conflict looks like harmony but it's the opposite. Real disagreements go underground and get settled in hallway conversations after the meeting.

The Firefighters. Everything is urgent. The quarterly planning meeting gets hijacked by whatever broke this week. The team leaves with a list of fires to fight and no plan for the quarter, again.

What misalignment looks like

You don't need a survey to spot a misaligned leadership team. The symptoms show up in daily work:

Ask three leaders what the top priority is and you get three answers.

Two departments build the same thing without knowing it.

Decisions made in the last meeting get re-argued in the next one.

Middle managers guess what matters (or ignore it), because the message from the top keeps changing.

You spend your week chasing updates instead of doing the real job.

That last one deserves attention. When priorities aren't clear and owned, someone has to hold everything together by hand. That someone is usually the operations leader. They become the manual override for a system that should run on its own.

What misalignment costs

The consequences compound quickly. A misaligned quarter means wasted salary on work that didn't matter. It means slower progress on the right goals. It means your best people, the ones who want to win, get frustrated and start looking around. And it means the next quarterly planning meeting starts from a worse position than the last one.

When goals aren't shared and visible, effort scatters. The fix isn't more effort; it's alignment on fewer things.

What to prepare before the meeting

A quarterly planning meeting is only as good as what walks in the door with you. If you build the inputs during the meeting, you burn half the day on homework. Prepare these six things ahead of time.

1. Last quarter's results

Pull the numbers on every priority you set 90 days ago. Done or not done. Not "80% done." A priority that's 80% done is not done. You'll review these honestly in the meeting, so have the facts ready, not memories.

If your priorities, metrics, and to-dos live in one system (like with MonsterOps), this step can take 10 minutes (less actually, if you ask MonsterAI™).

If the information live in spreadsheets, decks, and chat threads, it will take some time, and you'll still miss things. Try running your next quarter in a tool like MonsterOps to see the difference.

2. The long-term issues list

All quarter, issues come up that are too big to solve in a weekly meeting. A pricing question. A hire channel that isn't working. A market shift. These are usually parked on a running list, not forgotten. In MonsterOps, you will typically use the long-term issue. The quarterly planning meeting is where that list gets opened.

If you don't keep this list during the quarter, you'll spend the first hour of the meeting trying to remember what the big issues were (and run the risk of missing some). Keep it in one place, make sure everyone knows, and pull that list before the meeting.

3. Company goals and the longer view

Your quarterly priorities should ladder up to something. Before the meeting, make sure the one-year goals and the long view (e.g. three-year picture) are written down and current. The quarter exists to serve them. If the longer view is fuzzy, fix that first, or the quarterly priorities will be guesses.

4. An accountability chart

A simple chart showing who owns what. Every major function has exactly one name next to it. Not a job title. A name. You'll use this in the meeting to assign ownership of each new priority. If two people share a seat on this chart, sort that out before the meeting, because shared ownership is where priorities go to die.

Strengths, weaknesses, opportunities, threats. It's an old tool, but it works. Have each leader fill one out alone before the meeting. Doing it alone matters: you want each person's honest read before the room shapes it. Compare them in the meeting. The gaps between answers are often the most useful part.

6. Scorecard data

Bring the weekly numbers for the whole quarter, not just the last week (simply change view to Quarterly in your MonsterOps account and you'll have your numbers). Trends tell you more than snapshots. A metric that's been sliding for eight weeks is a quarterly issue even if this week looked fine.

One note on volume: you don't need to review every number in the meeting. Keep the human review to a short list of metrics that matter most. Let software watch the rest.

MonsterOps tracks the full set in the background and flags a metric only when it breaks its target, so the meeting stays focused without anything going unwatched.

7. The right people, and only them

The quarterly planning meeting is for the leadership team. That usually means five to eight people, each owning a major function. Fewer than that and you're missing perspectives. More than ten and honest debate dies, because people perform for a crowd instead of talking to peers.

Resist the urge to invite observers, note-takers, or "high potentials who should see how this works." Every extra person in the room raises the cost of saying something uncomfortable. If someone's presence would make a leader soften their words about a struggling department, that person shouldn't be there.

One exception worth considering: a facilitator who isn't the CEO. When the CEO runs the meeting, the room reads their reactions and steers toward them. A neutral facilitator, whether an outside coach or a leader who's good at it, keeps the CEO in the debate instead of above it.

Best practices: before, during, and after

The meeting itself usually takes a day, but there are more things to consider.

Before the meeting

Block a full day, out of the office. Half-day quarterly planning meetings produce half-decisions. Book eight hours somewhere that isn't your office. The change of room matters more than it sounds. In your own conference room, people drift back to their desks at breaks and return with their heads in today's problems.

Send a prep packet one week ahead. It contains last quarter's results, the issues list, the current goals, the scorecard trends, and the agenda. Every leader reads it before the day. The rule is simple: the meeting is for deciding, not for reading.

Have each leader self-score. Before the meeting, each person marks their own priorities from last quarter as done or not done, and writes one sentence on why. This removes the awkward live grading and gets honesty on the table early.

Set the agenda and a timekeeper. A quarterly planning meeting without a clock becomes a debate club. Assign someone to own the schedule and give them permission to cut discussions off.

A working agenda that fits in a day:

Check-in and wins (30 min)

Review last quarter's priorities and numbers (60 min)

Revisit the one-year goals and three-year picture (60 min)

SWOT comparison (45 min)

Set 3 to 5 priorities for the new quarter (90 min)

Work the issues list (120 min)

Confirm owners, measures, review communication, and next steps (30 min)

During the meeting

Open with wins. Thirty minutes on what went right, business and personal. This isn't fluff. It sets a tone where people talk like humans, which you'll need when the hard topics come.

Review last quarter without softening it. Done or not done. When a priority wasn't done, ask why without blame. The goal is to find the pattern: was it too big, wrongly owned, or just deprioritized? Teams that can't say "we failed at this" out loud will fail at it again.

Farm for dissent. Reed Hastings describes this practice in No Rules Rules: before locking a big decision, ask the room to argue against it. Make disagreement a job, not a risk. If your team is the Peacekeeper type, this is the single most useful habit you can install. A priority that survives open disagreement is one the team will defend all quarter.

Pick 3 to 5 priorities. No more. This is the hardest discipline in the room. Every leader has ten things they want. The company can do about four well. Doerr's rule from Measure What Matters applies here: if everything is a priority, nothing is. Write the candidates on a board, then cut until five remain. The cutting is the meeting.

One owner per priority. A name, not a team. The owner isn't the one who does all the work. They're the one who answers for it. Check each name against the accountability chart. If a priority has no natural owner, that's a signal it either isn't ready or your chart has a gap.

Make each priority measurable. "Improve onboarding" is a wish. "New customers reach their first live meeting within 14 days" is a priority. If you can't tell whether it's done in December, rewrite it in the room now.

Use a parking lot. Good discussions spawn side topics. Don't chase them and don't kill them. Write each one on a visible list and keep moving. At the end of the day, sort the parking lot (or backlogs in MonsterOps): some items become to-dos, some go on the issues list for next quarter, some get dropped. This one habit protects the agenda more than any amount of timekeeping.

Work the issues list with a decision rule. For each issue: name the real problem, discuss it, decide. The decision can be "solve it," "assign someone to solve it," or "drop it." What's not allowed is "discuss it again next quarter." An issue touched three quarters in a row without a decision is a leadership problem, not a business problem.

End with a round-the-table close. Each leader states the quarter's priorities in their own words and says what they'll tell their team. If someone can't state the priorities, you're not done. This ten-minute close catches the misalignment that would otherwise surface in week six.

After the meeting

This is where most quarterly planning meetings actually fail. The day goes fine. Then nothing happens.

Publish within 24 hours. Priorities, owners, measures, decisions, and to-dos. One page. Everyone in the company should be able to read it. Speed matters: the longer the gap between the meeting and the write-up, the more each leader's memory drifts.

Every leader runs a team version. Within one week, each leader sits with their own team, shares the company priorities, and sets the team's supporting priorities. This is how a quarterly planning meeting becomes a company plan instead of a leadership secret.

Track weekly, in the open. Each priority gets a status every week: on track or off track. Not a paragraph. A status. When priorities live where everyone can see them, the follow-up chases itself. This is the mechanical reason to run the quarter in a system like MonsterOps rather than a slide deck: the priorities you set in the meeting become the same items your weekly meetings review, with owners and status visible to everyone. The deck version gets opened twice: once to write it, once to feel bad about it in 90 days.

Feed the issues list all quarter. When something too big for a weekly meeting comes up, park it on the list and move on. Your next quarterly planning meeting is already being prepared, every week, with almost no effort.

What failing this meeting actually costs

You get four of these a year. That framing changes the math.

A wasted quarterly planning meeting doesn't cost you a day. It costs you 90 days, because there's no mechanism to reset direction until the next one. Fail one and a quarter of your planning year is gone. Fail two in a row and you've run half a year on drift.

Here's what a failed quarter looks like in practice. Priorities were vague, so each department interpreted them their own way. By week four, the interpretations have diverged. By week eight, two teams are in quiet conflict about direction and the COO is spending their days untangling it by hand. By week twelve, the honest summary is "we were busy," and nobody can say what moved.

There's a second cost that compounds: the team stops believing in the meeting. When quarterly priorities don't survive contact with the quarter, leaders learn to treat the meeting as a show. They nod, they leave, they go back to their own plans. Lencioni's fifth dysfunction, inattention to results, is caused by a planning process that taught them results were optional.

The point of a well-run quarter isn't just that the work gets done. It's that the leadership team stops spending its hours holding the operation together and starts spending them on the harder problems: the next product, the next market, the next stage of the company. That work is what a leadership team is for.

Pitfalls to avoid

Setting too many priorities. It may be tempting, but seven priorities is really like having zero priorities. If the team can't recite the list from memory, it's too long. Cut to five or fewer, every time, no exceptions for a "special" quarter.

Shared ownership. "Sales and marketing will own this together" means nobody owns it. One name per priority. The owner can pull in whoever they need, but one person answers for the result.

Status updates disguised as planning. If each leader presents slides about their department, you're holding a review, not a quarterly planning meeting. Reviews look backward. This meeting exists to decide what happens next. Keep the backward look to the first 90 minutes only.

Skipping the honest review of last quarter. Teams that jump straight to new priorities repeat their mistakes. The pattern in your failures (too big, wrong owner, no measure) is the most useful data in the room. Spend the hour.

Letting the loudest voice set the priorities. If the priorities are whatever the CEO walked in wanting, you didn't need a meeting. Use silent writing first: each leader writes their top three candidates before anyone speaks. Then compare. You'll be surprised how often the quiet leaders were holding the best answer.

No follow-up system. The most common failure, by a wide margin. The meeting was great, the write-up was clean, and then the priorities lived in a document nobody opened. Decide, before you leave the room, exactly where the priorities will live, who reviews them, and in which weekly meeting. If the answer involves a spreadsheet someone updates by hand, it will stop being updated by week five. Put the priorities where the weekly work already happens. Ideally, in a system like MonsterOps.

Devices open in the room. Laptops closed except for the person running the shared screen. A quarterly planning meeting with everyone half-answering email produces half-commitments. If it can't wait eight hours, it belongs to whoever you left in charge back at the office.

No breaks, no food plan. Small thing, real effect. Decision quality drops when people are tired and hungry. Break every 90 minutes. Feed people. Day-long meetings are physical events.

The payoff

Run the quarterly planning meeting well four times in a row, and things change. Priorities move without you pushing them. Commitments turn into action because everyone can see who owns what and where it stands. The weekly meetings get shorter because the direction was settled in one good day.

A leadership team that's aligned on the same short list, an operation that stays on track between meetings, and leaders who get their best hours back for the work that grows the company.

Four days a year is a big investment. So make sure you prepare them and follow through on them. Everything else in your operating rhythm gets easier when these four days are right.

“We’ve been using EOS in our business for a number of years but had struggled to find a reliable, cost effective, and user friendly EOS implementation tool online. I stumbled across MonsterOps and couldn’t be happier that I did! Its functionality is equal or better than some of the other software we’ve used but at a fraction of the cost.”

BradenBradenCEO at Scissors & Scotch Ventures

Try MonsterOps for a Quarter

Plug your metrics, rocks, and meetings into one simple tool that won't require your team to take additional training.

Start free setup