The review packet is not meeting prep. It is where the company writes down its operating logic.
This matters because the packet forces thinking before performance. A weak packet produces a weak meeting even if the room is full of smart people. A strong packet makes the meeting harder to fake.
A useful packet names the last cycle's commitments and the current state against them. It highlights material variance instead of dumping every metric. It explains what changed, what the team believes caused it, and what is still unknown. It identifies the decisions needed. It records follow-up conditions: what we will watch next and when we will reopen the issue.
The packet should make absence expensive. If someone misses the meeting, they should still understand the operating picture. If the company needs to reconstruct a decision three months later, the packet should carry the trail.
This is why slide decks often make poor review packets. They are optimized for presentation, not auditability. They hide the logic in speaker notes and conversation. A memo-style packet is usually better: concise, explicit, scannable, and easy to quote in the decision log.
The meeting then tests the packet. Is the diagnosis credible? Is the evidence enough? Is the decision framed correctly? Are we treating a metric movement as a system problem? Are we hiding a tradeoff behind an action item?
Packet quality is an operating standard. If a leader repeatedly brings metric dumps, unclear asks, or narratives that do not explain variance, the fix is not “better slides.” The fix is a higher standard for operating thinking.
The packet is the company thinking in public. Treat it that way.
