The Meeting That Should Have Been a Playbook

There's a recurring meeting on your calendar right now that exists to move information from one person's head into five other heads, out loud, at a rate of maybe 200 words per minute. You know the one. Thursday, 10 a.m. Six people take turns reading updates they could have typed. Conventional wisdom says this is "alignment." It's actually a database with terrible latency.

Let me explain what I mean, because once you see it you can't stop seeing it.

The database with terrible latency

Every org needs somewhere to store state. What's shipped, what's blocked, who owns what, what we decided last time. That's just data. In a healthy system, you write it down once and anyone reads it when they need it. Random access. Cheap.

Most orgs never built that place. So they store state the only way they know how: by convening humans and having them say the data aloud on a schedule. The weekly status call is a query. The all-hands is a full table scan. The problem is the read speed. To find out one thing, you attend a 60-minute meeting and wait for your row to come up.

The mechanism that keeps this alive is almost sweet. Writing something down once feels slower than saying it. Saying it takes twelve seconds and you're already in the room. Writing it means opening a doc, thinking about structure, and admitting someone might read it later and hold you to it. So nobody writes it. So everyone re-says it. Forever. The synchronous meeting wins every individual cost-benefit calculation and loses the war.

A field guide to meetings that are secretly databases

The Status Readout. Six people, one at a time, narrating what's already true. Nobody asks a question. Nobody decides anything. At minute 43 someone says "I'll take that offline," which is the only honest sentence spoken, because "offline" means "in writing," which is where all of it belonged.

The Recurring Onboarding. A new person joins, so someone senior blocks an hour to explain how the thing works. Next month, new person, same hour, same explanation, delivered slightly worse because the senior person is now bored of their own tour. The knowledge lives in one skull and gets re-rendered on demand, like a webpage with no cache.

The Standing Sync That Nobody Remembers Scheduling. It recurs. It has for two years. The original reason left the company in 2024. It persists because deleting a meeting feels like a decision and nobody wants to own it, so forty people pay a weekly tax to a purpose that no longer exists.

The Decision Meeting That's Really a Readout. The sneaky one. It's framed as "let's decide," but forty of the forty-five minutes are spent getting everyone to the same set of facts. The actual decision takes ninety seconds at the end when everyone's tired. You spent an hour loading context and pocket change on judgment.

That last one is the whole game.

Playbooks as the place you never built

Here's the WISER version of somewhere to keep state. A Playbook is living documentation that holds the current state, the objectives, and the boundaries of a piece of work. Not a doc that dies in a wiki three folders deep. A working reference the team actually opens and updates, because it's the source of truth and not a chore performed for an audit.

The point isn't the document. The point is where the knowledge lives. In a Playbook, it lives in the system. In a status meeting, it lives in one person's head and gets broadcast on a schedule. One of those survives that person taking vacation.

When the state already lives somewhere everyone can read, the meeting changes shape. People walk in having read the row they cared about. You skip the 43 minutes of loading context. What's left is the part a document genuinely can't do.

A Playbook holds the facts. A meeting is for the arguments only humans can have.

Facts don't need a quorum. Judgment does. "Should we cut this feature" is a real conversation with tension and taste and people who disagree. "Here's what shipped last week" is a SELECT statement wearing a blazer.

The one question

You don't need a reorg. You need one filter. Walk your recurring calendar and ask each meeting a single question.

Is this a decision, or a readout?

• Readout? It's a Playbook. The state goes in writing, people read async, you get the hour back.
• Decision? Keep it. Shrink it. Send the context ahead in the Playbook so the meeting is only the argument.

Most standing meetings are readouts in a decision's clothing. That's not an indictment of your team. It's what happens when the only storage medium anyone gave you is other people's attention.

Cancel one this week. Move its contents into something people can read. See if anyone's actually less aligned, or just less scheduled.

My bet is you'll find the Thursday 10 a.m. was never storing anything you couldn't have written down. It was storing the feeling that something was being stored.