A dashboard on a screen is not a meeting. A meeting is a decision-making event. Most operational reviews are dashboards on a screen with no decisions attached.

The meeting ends. Action items are captured. Nothing changes. Six weeks later, the same metrics are the same, and the same concerns are raised, and the same vague commitments are made. This is management theater.

The Structure of a High-Signal Operational Review

Before the meeting (pre-read, sent 24 hours ahead):

  • One page per metric area: where we are, why we're there, what we're doing
  • Exception list: what's off track and what's being done about it
  • Data notes: source of truth, freshness, definition changes, known disputes
  • Decisions needed: explicit, with context

During the meeting (60 minutes max for most teams):

`text

0-5 min Frame: exceptions, decisions needed, data-quality caveats

5-25 min Issue 1: interpretation, options, decision

25-45 min Issue 2: interpretation, options, decision

45-55 min Commitments: owners, dates, follow-up venue

55-60 min Decision log readback

`

Do not spend the first 20 minutes touring the dashboard. If the group has not read the pre-read, cancel the meeting or use the time as a reading block. Pretending everyone is prepared just rewards bad meeting hygiene.

After the meeting (same day):

  • Decision log: what was decided, who owns it, by when
  • Metric disputes: owner, resolution date, temporary source to use until resolved
  • Stale dashboard cleanup: anything nobody used, trusted, or acted on gets archived
  • Distributed to the same list as the pre-read

The Decision Log

A useful decision log is short:

| Date | Decision | Owner | Due date | Metric / evidence | Follow-up |

|---|---|---|---|---|---|

| May 8 | Roll back required setup fields for new accounts | Activation PM | May 10 | Activation 64% → 52%; support tickets +18% | Review cohort May 17 |

| May 8 | Use finance NRR model as source of truth until CRM dispute resolved | COO | May 15 | Finance and CRM differ by 2.4 pts | RevOps to reconcile |

The readback matters. The last five minutes should make ambiguity uncomfortable: what did we decide, who owns it, and where will it show up next?

The One Question to Ask at the End of Every Operational Review

"What is the one thing we're all leaving this room knowing that we didn't know when we walked in?"

If the answer is "nothing," the meeting failed — not because the information was bad, but because a meeting that only confirms what everyone already knew is a meeting that shouldn't have happened.