THE GAUGEPLAYBOOK

The meeting that should be a gauge

Most recurring meetings are instruments. Badly built, expensively operated instruments, but instruments — their actual function is to move information from the people who have it to the people who need it, on a schedule.

Which means they're competing with a gauge, and they usually lose.

The test

For each recurring meeting, ask: what information moves here that couldn't move as a number?

Sort what happens into three buckets.

Status transfer — "here's where things stand." This is a gauge wearing a costume. It's slower than a number, less accurate (it's assembled from memory under mild social pressure), it requires everyone's simultaneous attention, and it produces no record anyone will read afterward. Delete it and publish the number.

Decisions — several people with different information converging on a choice. This genuinely needs a meeting, or at least a synchronous exchange. Keep it. But notice that a decision meeting takes twenty minutes when the status is already known, and ninety when it isn't — which is why deleting the status transfer makes the decisions better rather than just cheaper.

Alignment and relationship — building shared context, disagreeing productively, the human stuff. Real and irreplaceable. Also, in most companies, about 10% of the calendar time allocated to meetings that claim it as their purpose.

Run this on a real calendar and the typical result is that half to two-thirds of recurring meeting time is status transfer.

What has to exist first

Here's the part people skip, and skipping it is why "we cancelled our status meetings" so often gets quietly reversed a month later.

You cannot delete a status meeting until the gauge exists. Otherwise you haven't removed an instrument, you've gone dark — and the meeting will come back, correctly, because a bad instrument beats no instrument.

The replacement needs three properties:

  1. Automatic. Nobody assembles it. If a person compiles the update, you've kept the meeting and removed the part where people could ask questions.
  2. Pushed. It arrives, in a channel people already read. A dashboard someone must remember to visit will be visited for two weeks and then never.
  3. Owned. Each number has a name attached. The meeting provided accountability through the discomfort of reporting bad news to a room; the gauge has to provide it some other way, and a name is the cheapest way.

Get those three right and the status meeting can go. Miss any one and it'll be back by the end of the quarter.

What improves

The information gets better. A number computed automatically doesn't round off the inconvenient parts. A status update delivered verbally by the person responsible is, inevitably and without any dishonesty, the most reasonable available version of events.

It arrives sooner. A weekly meeting means bad news waits up to seven days for its slot. A gauge moves when the thing moves. Most operational problems are cheap to fix on day one and expensive on day six.

Everyone gets it at once. In a meeting, the room learns. Everyone else learns through retelling, degraded and delayed. A published gauge reaches the whole company simultaneously, including the people who'd never have been invited but are affected anyway.

The meetings you keep get better. A decision meeting where everyone already knows the numbers starts at the actual question. That's the biggest win and it's the one nobody predicts — deleting meetings improves the remaining ones more than it saves time.

The residual

One caveat, and it's real. Meetings do something gauges don't: they create a moment where someone can say "that number is up but I'm worried anyway."

Intuition arriving ahead of the data is genuinely valuable, and a pure-gauge culture can lose it — because there's no forum for a concern that isn't yet a number, and unspoken concerns don't route themselves.

So keep a short, low-frequency forum whose only agenda is "what are you worried about that the gauges don't show?" Fifteen minutes. No status. It's the highest-value meeting most companies don't have, and it's affordable precisely because you deleted the other ones.

  • playbook
  • operations
  • meetings

Building something that should flow through this system? hello@theclearpipe.com · Subscribe by RSS