Executive Analytics
Advanced 12 min read Executive Analytics

Executive Review Meetings

Pre-read decisions, meeting confirms

Exec reviews have a prep cadence: a data pack ahead of time, decisions pre-briefed, and the meeting itself answering only open questions — then committing actions with owners.

meetingsreviewQBRcadencepre-readdecisionsgovernance
Prerequisites: Decision Support Reporting Narrative and Storytelling
Before we start

What you will learn

  • Prepare a decision-first review pack
  • Run the meeting like a decision gate, not a chart walk
  • Trail actions with owners and dates
Introduction

What is this?

Executive review meetings turn analytics into decisions on a cadence — monthly exec review, QBR, risk board. The system: a data pack shipped early (read-only, decision-first), open questions pre-briefed, the meeting covering only what needs discussion, and every exchange leaving an owned action with a date. The analyst's job is the pack; the meeting confirms it and commits owners.

Motivation

Why do you need it?

  • Meetings that read charts burn executive time; decision gates don't.
  • Pre-reads convert the hour into a decision session.
  • Action trail with owners is what makes analytics consequential.
  • The cadence discipline is a senior BI analyst's signature.
Think about it

Mental model

Imagine

A doctor's chart before the consult

Think of

The pre-read

A physician reviews labs and charts before the patient sits down; the appointment then covers only what's new and decisions only the open ones. The alternative — reading labs aloud in the room — is the hour-long chart walk executives suffer. Pre-read, then consult, then commit.

Mechanics

How it works

  • Pack: data summary, decisions with positions, pre-read 48h prior.
  • Each decision pre-stated with a recommendation and its options.
  • Meeting = open questions + contested decisions only.
  • Scribe actions with owner + date; publish within a day.
  • Follow-up: actions roll into the next pack as the open column.

The review cadence loop.

Pre-read
Open decisions
Meeting
Actions
Roll-in
Hands-on

Examples

The QBR pack skeleton

The QBR pack skeleton
QBR PACK (ship Fri, meet Mon):
  1. OUTCOME one-pager (5 KPIs, deltas)
  2. DECISIONS on the table (3, each: position + options)
     D1 price US pilot   - position B (shift a week)
     D2 invest AP sales  - position A (2 SDRs now)
     D3 margin floor     - position C (hold 60%)
  3. OPEN QUESTIONS only — 2, researched
  4. RISKS & what's assumed
 
Meeting agenda = confirm pre-read,
resolve 2 opens, leave zero orphan actions.

The pack does the walk; the meeting does the deciding; actions leave the room owned.

Real world

In production

  • A monthly review runs 30 min on a 48h pre-read pack; actions tracked across the quarter.
  • A risk board reviews red KPIs with one owner/date per red flag.
  • A QBR recaps the quarter's decisions and counts their outcomes.
Guidelines

Best practices

  • Ship the pack 48h before; the meeting covers only opens.
  • Pre-state a recommendation per decision to force positions.
  • Timebox contested decisions; defer unresolved to owners by date.
  • Publish the action log within 24h; the next pack opens with it.
Watch out

Common mistakes

  • The meeting is a chart walk because the pack never shipped.
  • Decisions un-stated: the room 'discusses' without a position to reject.
  • Actions without owners or dates — 'somebody should' again.
  • No roll-in: QBRs reinvent the same open decisions each quarter.
When things break

Debugging tips

  • Reviews run long → pack is thin or late; enforce the 48h pre-read.
  • Same 'open' question every month → no action trail; escalate to an owned decision.
  • Nothing decided → no positions were pre-stated; draft them in the pack.
Interviews

Interview checkpoint

Test yourself

Quick quiz

0/2
1

The exec review pack should ship:

2

Every review action should leave with an owner and a date.

Go deeper

Official documentation

HBR - meetings that don't waste time
docs