Business reviews
Key takeaways
- review charter
- evidence register
- question ledger
Operating data
Playbook
A distributed QBR fails when leaders spend the meeting discovering what numbers mean. Six weeks out, issue a charter naming business questions, decision authorities, reporting period, data cutoff, contributors, time-zone rules, pre-read date, and required outcomes. “Share an update” is not a decision.
Create an evidence register before slides. Each measure needs definition, unit, source, period, comparison basis, owner, and limitation. Label regional variants instead of normalizing without authority. Collect variance, explanation, action, risk, dependency, and requested decision from each owner.
Publish the pre-read for asynchronous challenge and keep an asker, claim, respondent, deadline, and disposition ledger. The weekly dashboard guide provides disputed-input controls. Reserve live overlap for unresolved assumptions and tradeoffs.
Rotate inconvenient hours and offer asynchronous contribution. GitLab asynchronous guidance explains why documented context matters. Capture authority, owner, local due date, dependencies, and review evidence, then route actions through operations follow-through.
At the next kickoff, compare promised outcomes with completion evidence, identify inputs that repeatedly arrived late, and revise the charter before contributors produce another set of regional materials.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.