How to Run a Successful Quarterly Business Review
A practical guide to designing and facilitating QBRs that drive accountability, surface real insights, and produce commitments that move the business forward.
The Purpose of the QBR: Accountability, Not Theater
The Quarterly Business Review has become a standard operating ritual in most growth-stage and enterprise organizations, and it is, in most of them, deeply underperforming its potential. The archetypal QBR is a two-hour (or two-day) parade of decks in which function leaders deliver carefully curated presentations that emphasize progress against goals while minimizing visibility into underperformance, blockers, and risks. Executives leave the review with a positive feeling but without the information they needed to make better allocation and priority decisions. The purpose of a genuinely effective QBR is fundamentally different from this archetype. It is to create the conditions under which the leadership team can make the best possible decisions for the next quarter by ensuring shared understanding of what happened in the last quarter, why it happened, and what it implies for the plan going forward. That purpose requires a QBR design that prioritizes candor over comfort, analysis over narrative, and forward-looking commitment over backward-looking reporting. COOs who own the QBR process design face an organizational change management challenge: shifting from a culture where QBRs are performance reviews (in which function leaders are defending their record) to a culture where QBRs are operational planning sessions (in which the leadership team is collectively solving the most important problems). This shift requires changes to the format of the QBR, the content standards, and—most importantly—the behavioral signals from senior leadership about what is valued in the room.
QBR Structure: What to Cover and in What Order
The structure of an effective QBR should reflect the questions the leadership team most needs to answer at the end of each quarter: Did we perform against plan, and why? What is the honest assessment of our current position? What are the most important priorities for the next quarter? What decisions need to be made at this level of the organization? A well-designed two-hour QBR agenda allocates approximately 30% of time to backward review (Q3 performance vs. plan, root cause of key variances), 40% of time to forward planning (Q4 priorities, resource allocation decisions, risk identification), and 30% to cross-functional discussion and decision-making. The distribution matters: QBRs that spend 80% of their time on backward review generate historical context without producing actionable decisions; QBRs that skip backward review miss the organizational learning that comes from honest analysis of what worked and what did not. The backward review section should be organized around the company's most important operational metrics, presented in a format that makes performance trends visible and variance explanations explicit. A simple red/yellow/green status framework for each metric, with a brief explanation of the most significant variances from plan, is more decision-useful than elaborate slide presentations that bury the key findings in narrative. The discipline of a simple status framework forces presenters to take a clear position on performance—something that elaborate presentations are often designed to avoid.
Preparation: The Work That Makes QBRs Productive
The quality of a QBR is determined primarily by the quality of the preparation that precedes it, not by the skill of the facilitation during the session. Preparation failures—incomplete analysis, metrics not available at required granularity, pre-reads distributed too close to the session for meaningful review—produce QBRs that spend meeting time on information gathering rather than decision-making. The preparation standard for a well-run QBR includes: a QBR planning document distributed two weeks before the session that specifies the agenda, the content standards for each section, and the decisions the leadership team needs to make; a pre-read package distributed 48–72 hours before the session that includes all quantitative performance data, key analysis, and materials requiring decision; and a pre-session read of the pre-read by all attendees (enforced by a facilitation design that begins the session assuming the pre-read has been completed, rather than re-presenting its content). For function leaders preparing QBR presentations, the most common gap is the transition from data reporting to analysis. Data tells the leadership team what happened; analysis tells them why it happened and what it implies for decisions. A function leader who presents "customer churn increased 2 percentage points versus plan" has shared a data point. A function leader who presents "churn increased 2 points versus plan, driven primarily by the February cohort where we had onboarding delays due to the implementation timeline—we expect this to normalize in Q4 as those accounts complete the delayed onboarding steps" has provided the context the leadership team needs to assess the severity of the issue and the likelihood that Q4 will self-correct.
Decision Quality: The Standard QBRs Should Set
The defining output of a QBR is not a presentation deck or a performance report—it is a set of decisions and commitments that will shape the organization's priorities and resource allocation for the next quarter. QBRs that end without explicit decisions and clear accountability for next steps have consumed significant management time without producing the organizational value that the time investment warrants. Decision quality in QBRs is elevated by three practices. The first is pre-framing decisions before the meeting: for each decision the leadership team needs to make, the QBR preparation materials should include a decision memo that states the question, the options under consideration, the analysis that informs the choice, and the recommendation. This format accelerates decision-making in the room by ensuring that the relevant information has been reviewed in advance and that the in-session time can be used for discussion and resolution rather than information transfer. The second practice is explicit decision documentation during the session: a designated note-taker who records decisions in real time, with the decision owner and timeline for implementation. This documentation should be distributed within 24 hours of the QBR close, creating the accountability infrastructure for follow-through. The third practice is opening the following QBR by reviewing the commitments made in the prior QBR—a mechanism that creates consistent accountability for decision follow-through and signals that QBR commitments are organizational obligations rather than aspirational statements.
Frequently Asked Questions
How long should a QBR be?
The right duration depends on the complexity of the business and the scope of the review. For most growth-stage companies reviewing performance across 4–6 functional areas, a half-day session (4 hours) with appropriate breaks provides enough time for genuine analysis discussion and decision-making. Full-day or multi-day QBRs are appropriate when the review includes strategic planning for the following year or when significant organizational changes require extended discussion. QBRs that run longer than necessary typically do so because pre-reads were not reviewed and because the format allows information re-presentation rather than analysis discussion.
Who should attend a QBR?
The core QBR should include the CEO, the COO, and all C-suite function leaders who own the metrics being reviewed. Extended leadership (VP-level leaders, key individual contributors in areas under specific discussion) can be included for portions of the agenda relevant to their domain. The principle of minimum necessary attendance applies: adding attendees to signal inclusion or prestige value adds overhead without adding decision quality, and large QBR rooms inhibit the candid, analytical conversations that produce valuable outcomes.
How do you handle a QBR when performance has been significantly below plan?
This is the most important QBR design question because it is when the behavioral norms of the organization are most visibly tested. The CEO and COO must model the behavior they want to see: engaging in honest diagnostic analysis of underperformance without creating an environment of blame or defensiveness. The agenda design should allocate more time to root cause analysis and forward planning in underperformance quarters, not less. Organizations that use QBRs to create accountability through embarrassment or punishment consistently produce cultures where function leaders manage information to avoid bad QBR experiences rather than managing their functions to produce good business outcomes.
Related Articles
Supply Chain Optimization: A COO's Playbook
A comprehensive framework for COOs to diagnose inefficiencies, redesign supply networks, and build resilience across procurement, logistics, and fulfillment.
Read →
How to Build a Scalable Operations Team
A practical guide to designing, hiring, and structuring an operations function that can scale with the business without breaking under growth pressure.
Read →
Lean Operations for Manufacturing Companies
How manufacturing COOs can apply lean principles—waste elimination, value stream mapping, and continuous improvement culture—to drive cost efficiency and quality gains.
Read →
The Crimson Bench · Est. 2002 · Founded in New York City
Deploy an Executive in 48 Hours
Verified corporate accounts only. Ivy League-educated. Flat-rate pricing. 14-day no-cause cancellation.
25,000+ Ivy League Executives · 150,000+ Global Consultants · 48-Hour Deployment