Quarterly Business Review Template: An Agenda That Ends in Decisions

The meeting that ran an hour late and decided nothing

Michael Mankins tells the story of a hypothetical company he calls AnyCo. A few days before the top team's meeting, the CEO's assistant collects agenda items and lists them in the order they arrived. On the day, the team spends a long time debating the look of an advertising campaign. A compliance update turns into a gripe session about IT. A major factory-automation investment gets a cursory green light, to the CFO's discomfort. A worrying shift in European competition is put off to a future meeting. The meeting ends an hour late, and people leave complaining about another waste of time ².

Mankins's point was that this is normal. In a survey of top management teams at 187 large companies, executives spent an average of 21 hours a month together in leadership meetings, and less than three hours a month on strategy ².

A quarterly business review (QBR), in the internal sense used here, is a scheduled meeting where a leadership team checks progress on its strategy and decides what to change: which initiatives get more money or people, which stop, which assumptions have broken. (Sales and customer-success teams use “QBR” for a review held with a customer; the Strategy Studio guide to the quarterly business review covers the components in general.)

The thesis of this page: a QBR earns its half-day only if it ends in written decisions that move money, people or priorities. A review that only reports status is a meeting about a dashboard, and the dashboard could have been sent by email.

If nothing was decided, it was a briefing with lunch.

Why reviews drift into status theater

Status is easy to present, and safe. Decisions are hard, and somebody loses. Left alone, every review slides toward the first.

Mankins's survey put numbers on the slide. More than 65% of leadership team meetings were not even called to make a decision; they were held for information sharing, group input or discussion. Only 12% of executives believed their top management meetings consistently produced decisions on important strategic or organizational issues. Less than 5% said their company had a rigorous process for focusing top management's time on the most important issues ². As much as 80% of top management's time, Mankins found, went to issues accounting for less than 20% of long-term value ².

Two forces drive the slide. The first is urgency: operational problems arrive with deadlines and owners, strategy has neither, so put them on one agenda and operations win. The strategy execution page covers that mechanism and the case for separate meetings. The second is agenda-setting by default: items in the order they were submitted, each presenter given equal time, the crisis of the moment at the top ². Neither is anyone's fault. Both are design problems, which means a template can fix them.

Be clear what the QBR is for. Robert Kaplan and David Norton describe strategy reviews as meetings that ask whether execution is on track, where and why problems are occurring, what will correct them and who is responsible; they “take the strategy as a given,” leaving the testing and adapting of the strategy itself to a separate process ¹. That is the default here, with one exception covered in the advanced section.

Part 1: the pre-read

Decisions get made in the room only when the explaining happened before it. At Cadbury Schweppes, Mankins reports, all reading materials for the chief executive committee went out at least five days before each session, and every item carried a standard cover sheet saying why it was being sent: for information only, for discussion and debate, or for a decision ². Kaplan and Norton make the same demand: managers should arrive already familiar with the data and ready to propose solutions, not sit through presentations ¹.

The pre-read below goes out five working days ahead. It has a one-page summary and one page per strategic priority.

The full scorecard lives in a standing dashboard; the KPI dashboard template covers how to build one. The pre-read lifts out the exceptions, and the exceptions set the agenda.

Part 2: the agenda

Kaplan and Norton observed that most companies hold a monthly strategy review of two to three hours, and that companies meeting only quarterly will probably need at least a full day to discuss all their strategic objectives and themes ¹. Their fix for limited time is to spend most of the meeting on a deep dive into one or two strategic themes rather than skimming everything ¹. The half-day agenda below follows that logic and rotates the deep dives across the year.

Two design choices carry the agenda.

Rank decisions by value at stake. Mankins describes Roche's “decision agenda”: the ten most important opportunities and problems facing the company, each with its value at stake quantified, together taking up more than half of the chief executive committee's time each year ². Rank the requests the same way, so the factory automation is not approved in the last five minutes while the ad campaign got forty.

Read the decisions back. Mankins found that teams often leave with different interpretations of what they agreed, and that a dissenter can exercise a “silent veto” simply by relaying nothing to their own teams ². Fifteen minutes at the end, restating each decision with an owner and a date, is the cheapest defense there is.

Part 3: the decision log

The log is the meeting's only output that matters. Keep it in one place, visible to the leadership team, and open each QBR with it. See decision log for the general practice.

The last field is optional and valuable. Writing down the strongest objection keeps it from becoming a silent veto, and gives the next review something specific to check.

A filled-in example

The company is invented. The three entries show what a decision looks like when it is written to be carried out.

None of those three would have appeared on a status slide. The Germany sellers looked fully staffed in the org chart, and the hosting problem lived in three separate lost-deal notes. The deep dive and the assumption check surfaced both.

How to set it up

1. Separate it from the operating reviewDifferent day, or at least a different agenda. Operational issues come in only if they are significant and cross-functional, as Kaplan and Norton recommend ¹.
2. Name an owner of the agendaUsually the head of strategy. Mankins found that in many companies nobody is explicitly responsible for managing the leadership team's agenda ².
3. Plan the deep-dive rotation for the yearAssign each strategic priority a quarter, so every priority gets at least one full examination a year and owners know when theirs is coming.
4. Send the pre-read five working days aheadWith a cover sheet marking each item Information, Discussion or Decision.
5. Run the agenda to timeThe CEO or unit head chairs; the strategy lead keeps time and the log.
6. Publish the decision log within 24 hoursTo everyone who attended and to the owners named in it.
7. Open the next review with the logEvery decision either done, or explained.

When the quarterly review should question the strategy

Kaplan and Norton keep strategy reviews about execution, and leave strategy testing to the annual offsite unless a major disruption or opportunity forces it earlier ¹. That is a sound default, but it has a cost: a strategy can be wrong for eleven months before anyone is allowed to say so.

Mankins and Richard Steele found that the timing of strategy work affects how many decisions get made. In their survey of 156 large companies, those with an annual, business-unit-by-business-unit planning process reached an average of 2.5 major strategic decisions a year; those with continuous reviews organized around issues reached 6.1 ³. That is a correlation from a survey, not proof that the format causes the decisions, but the direction is consistent with everything above. Textron, in their account, reviews two or three units' strategies each quarter instead of all units at once, and resolves each strategic issue in two sessions: one to agree the facts and generate alternatives, a second to choose ³.

The practical compromise: keep the QBR focused on execution, but build in two doors to the strategy itself. The assumptions-and-signposts slot is the first; if a core assumption is marked broken, or a scenario signpost crosses its trigger, the decision on the table is to convene a strategy test meeting within the month. The second door is one strategic issue per quarter, taken through facts and alternatives in this review and decided in the next.

Two second-order problems appear when QBRs run across many units:

• Resource tracking lags. The org chart says the team exists; the calendar says it is working on something else. Mankins and Steele describe Cisco monitoring each unit's actual resource deployments monthly against its plan ⁴. Ask for deployed people, not budgeted headcount, in every priority page.
• The review becomes a performance trial. If owners expect blame for gaps, the pre-read gets vaguer. Make the first question in every deep dive “what did we learn?” rather than “whose fault is it?”, and treat an assumption flagged early as good work.

The case for a lighter touch

The strongest objection is cost. A half-day for the whole leadership team, four times a year, plus a pre-read that takes days to prepare, is a lot of senior time. Fast-moving businesses might argue that a quarterly rhythm is too slow anyway, and that decisions should happen when issues arise, not when the calendar says.

Both points cut toward the same design. The time is usually already being spent, just badly: Mankins's executives were in meetings 21 hours a month ². ABN AMRO, in his account, cut its managing board's meeting time slightly, from 24 to 22 hours a month, while raising the time on strategy from as little as one hour a month to as much as ten, by splitting a weekly operations meeting from a monthly full-day strategy session ². And nothing in this template forbids deciding between reviews. The QBR is the backstop that guarantees the big reallocation questions get asked at least four times a year, whatever else is happening.

Before the next review

• The review is separate from the operating review, or has a distinct agenda.
• One person owns the agenda.
• The pre-read went out five working days ahead, with a cover sheet.
• Only exceptions are presented; on-target measures stay in the appendix.
• Most of the time goes to one or two deep dives.
• Assumptions and signposts are checked every quarter.
• Decision requests are ranked by value at stake and come with options.
• Every decision is read back, logged and owned.
• The next review opens with the log.

Monday morning: pull the minutes of your last three quarterly reviews and count the decisions that moved money or people. If the count is near zero, the fix is not a better dashboard. It is a different agenda.

The scorecard tells you where you are. The review exists to change where you are going. Judge each one by a single number: how many lines did it add to the decision log, and how many of last quarter's were actually done.

Questions

What is a quarterly business review?

Internally, a quarterly business review is a scheduled meeting where a leadership team checks progress on its strategy and decides what to change: where money and people move, which initiatives stop, which assumptions have broken. In sales and customer success, the same term describes a review held with a customer. This template covers the internal strategy version.

What should be on a quarterly business review agenda?

A good internal QBR agenda opens with last quarter's decisions, moves quickly through scorecard exceptions, spends most of its time on a deep dive into one or two priorities, checks the strategy's assumptions and signposts, decides ranked requests, confirms the resource moves that follow, and ends by reading back every decision with an owner and a date.

How long should a quarterly strategy review be?

A half-day works if the meeting deep-dives into one or two priorities and rotates the rest across the year. Kaplan and Norton observed that companies reviewing strategy only quarterly probably need at least a full day to discuss all strategic objectives. Many companies instead hold a shorter monthly strategy review and use the quarterly one for larger reallocation decisions.

What is the difference between a strategy review and an operating review?

An operating review solves short-term performance problems, often weekly or monthly. A strategy review checks whether strategic priorities are on track and decides what to change in resources and initiatives. Kaplan and Norton recommend keeping them separate, or at least giving them distinct agendas, because urgent operational issues otherwise crowd out the strategic discussion.

Where to go next

• Strategy Execution: Where It Breaks Between the Offsite and Monday
• KPI Dashboard Template
• Decision Log
• Balanced Scorecard: Framework & How to Apply It