Status, Decision or Discussion: A Rule for Every Recurring Meeting

Meeting reduction initiatives usually work for a quarter. Everyone agrees there are too many meetings, a few get cancelled, and by the following quarter the calendar is full again, often with the same meetings under new names.

The reason is that the meetings were doing something, and cancelling them removed the function along with the hour.

The three way rule

Take any recurring meeting and ask what it produces.

Type	Produces	Needs live time?
Status	Shared awareness of where things stand	No. This is a document read aloud.
Decision	A choice, with an owner	Only when people disagree
Discussion	A shared understanding that did not exist before	Yes. Keep these.

The test for discussion is whether the outcome was knowable in advance. If someone could have written the conclusion beforehand, it was not a discussion, it was a broadcast.

Audit your recurring meetings

List every recurring meeting and, for each, note the type and the honest cost in person hours per month. A weekly hour with eight people is over thirty person hours a month, which is most of a working week for someone.

Then find the mixed ones, because they are the majority. A typical weekly project meeting is forty minutes of status, ten minutes of one decision that could have been made by one person, and ten minutes of genuine discussion. It runs long, everyone leaves dissatisfied, and nothing was decided.

Split it. The status goes in writing. The decision gets an owner and a deadline. The discussion gets twenty minutes with only the people it concerns. You have removed most of the hour and improved all three functions.

Replacing a status meeting properly

The written replacement has to be better than the meeting, not merely cheaper, or people will go back.

• State, not activity. "Migration is at 60%, blocked on the DNS change, lands Thursday" beats a list of what was done.
• Named blockers. Every blocker with a person and a date. This is the field that makes the written version more useful than the meeting.
• One place, one format. Not four channels and three tools. The consistency is what makes it readable in ninety seconds.
• Nobody is required to read it all. It exists so anyone can find the state of anything, not so everyone is aware of everything.

That last point is where teams get it wrong. They replace a meeting where everyone hears everything with a document everyone is expected to read, which is the same cost in a worse format. The written version should be a reference, not a broadcast. See replacing the status meeting while keeping the status.

The version that holds up over time is one where the record is written by the work rather than as a chore. This is what StandIn is built for. At the end of the day each person spends about ninety seconds confirming a brief that is mostly already drafted: what moved, what is open, what is blocked, what is next. Then anyone can ask where something stands and get an answer from that brief, in the person's words, with a source under it. It never guesses, and when the answer is not there it says so and names who to ask. The status meeting is not replaced by a document nobody reads. It is replaced by the ability to ask. See how it works.

Moving decisions into writing

Most decisions do not need a meeting. They need a proposal with a deadline.

Write the recommendation, the alternatives, what happens if nobody responds, and a date. "We will move the export to nightly. Alternative was hourly, rejected because of load. Unless someone objects by Thursday, this is what we do." Silence becomes agreement, which it already was in the meeting, but now it costs nobody an hour.

Book the live slot only when someone objects. That converts most of your decision meetings into a five minute read and preserves live time for genuine disagreement. See making decisions in writing without reopening them.

Why cancelled meetings come back

Three failure modes, all avoidable.

The replacement was announced but never staffed, so after two weeks nobody was writing and the information stopped. Run the written version alongside the meeting for two weeks first, then cancel.

The meeting was also doing something nobody named, usually social contact or a manager's reassurance. Name that need and meet it separately rather than pretending it was not there.

And nothing replaced the escalation route. People used the weekly meeting to raise things, and with it gone they had nowhere, so it came back. Give blockers a named home first. See too many meetings usually means broken writing.

Common Questions

What about the all hands?

Keep it, make it short, and accept that its purpose is belonging rather than information. It is the one meeting where being together is the point.

Do we still need one to ones?

Yes, and they get better when status leaves them. The half hour becomes about what is hard and what is next rather than a verbal report.

How do we handle people who prefer meetings?

Often they prefer meetings because the written alternative is bad. Fix the written version first. If someone still prefers a call after four good weeks, that is a genuine working preference worth accommodating in their own team.

Will this feel colder?

It can if you remove every live contact. Keep the discussion meetings and the social one. What you are cutting is people reading updates aloud, and nobody has ever felt closer to a colleague because of that.