The Expert Chief of Staff's Guide to Running a Quarterly Business Review That Drives Decisions Instead of Reporting History Using ChatGPT

You are an expert chief of staff and executive operations strategist with 16 years of experience designing high-stakes business review processes for C-suite teams at growth-stage and enterprise companies. Help me generate a priority matrix so I can reclaim five hours per week currently lost to QBR preparation, presentation, and follow-up that generates no meaningful decision output. My situation: - Company stage and leadership team size: [e.g., "Series D SaaS company, 8-person executive team, 14 department heads presenting at each QBR"] - Current QBR format and duration: [e.g., "two full days, 45-minute slots per department, slide deck format, ends with an action items list that is never tracked"] - Primary dysfunction I am trying to fix: [e.g., "QBR is a reporting theater — executives sit through 12 hours of backward-looking data and leave without committing to a single new decision"] - Decision types that should come out of each QBR but do not: [e.g., "resource reallocation, initiative kill decisions, cross-functional priority conflicts resolved"] - Preparation time currently required per department: [e.g., "12–15 hours per department head building slides — 168 hours of company time per QBR cycle"] - Executive attention span and feedback on current format: [e.g., "CEO has said twice that the QBR format needs to change — no one has taken ownership of the redesign"] - Next QBR date and available redesign window: [e.g., "QBR is in 11 weeks — 6 weeks available for design, 5 weeks for preparation under the new format"] Deliver: 1. A priority matrix that classifies every QBR agenda item across two axes — strategic impact (high or low) and decision urgency (must decide this quarter or can defer) — producing four quadrants that determine which items get airtime, which get pre-read treatment, and which get cut entirely 2. A redesigned QBR format compressed to one day — a timed agenda with five sections, the role of each section, who runs it, and the specific output required before the session can close 3. A pre-read standard template replacing live slide presentations — a one-page format each department head completes covering three metrics, one risk, one cross-functional dependency, and one decision request with two options and a recommendation 4. A decision log protocol — a running document maintained by the chief of staff that records every decision made in the QBR with the owner, the rationale, the deadline, and the 30-day check-in trigger 5. A department preparation brief reducing per-department prep time from 12 hours to 3 hours — specifies exactly what data to pull, what to exclude, and how to frame the decision request in a format executives can respond to in 90 seconds 6. A QBR facilitation script for the chief of staff — covers how to open each agenda section, how to force a decision when executives are circling, and how to close a discussion and document the outcome without losing momentum 7. A 30-day post-QBR accountability review template — a 45-minute meeting structure held four weeks after the QBR that checks decision implementation status, identifies stalled commitments, and applies consequences or resets timelines 8. A QBR redesign change management plan — a five-step communication sequence for introducing the new format to the executive team and department heads six weeks before the next cycle, addressing the three predictable objections in order **Write every output from the perspective of someone who has run this process before and knows where it breaks — include the failure modes alongside the frameworks, not as a separate section but embedded in the instruction.**