The Meeting That Decided Nothing

The standup starts on time. Same few people, same order, same slot that somehow always runs long.

Everyone gives an update. Blockers get named. Somebody promises to take one offline. The meeting ends roughly on schedule, and the room disperses feeling like something happened.

Now pull the notes from the last six weeks of that meeting and read them side by side. Count the items that show up more than once, in nearly the same words, still open. I have sat in rooms like this where the group was smart, the topics were real, and the meeting was still theater. Everyone left informed. No one left responsible for anything that wasn't already theirs.

Updates wearing a meeting's clothes

A meeting that only produces updates is a status broadcast wearing a meeting's clothes. The information could have traveled on its own, in a fraction of the time. The reason it didn't is that the meeting now exists for its own sake. A slot that recurs because it has always recurred.

This is the trap with a well-run ritual. It can hit every visible mark of a healthy operating rhythm and still produce nothing. Right people in the room. Right cadence. Right agenda. Structure is the easy part to get right, and it does not guarantee a decision. A status update is not a decision. A blocker named out loud is not a decision. "Let's take that offline" is very often where decisions go to be quietly forgotten by everyone who heard it.

It feels like alignment because everyone heard the same words at the same time. Alignment is what happens after the meeting.

Many teams now have an automated notetaker in the room and a perfect transcript of every meeting they run. For most of them, the number of decisions coming out of those meetings did not move. The record got dramatically better and the meeting did exactly what it did before. It produces beautifully documented status, and the same three items roll forward week after week, now searchable.

When the rhythm becomes a queue

There is a second cost, and it is harder to see from the inside. Most operating rhythms were inherited, not designed. The weekly staff meeting, the monthly business review, the quarterly planning cycle. Almost none of it was chosen.

Once a decision belongs to a meeting, it waits for that meeting. A call that could be made on Tuesday waits for Thursday, because Thursday is when we talk about that. A choice that needed a day gets a month, because the review that owns it runs monthly. Nobody experiences this as delay. The meeting happened on schedule. The rhythm looks healthy from the inside.

The tell is a particular complaint. People are in meetings all day and still waiting on decisions. High activity, low velocity.

Give every meeting a job

The fix most leaders reach for is fewer or shorter meetings. That treats the symptom and misses the cause. The cadence is not the enemy. The absence of design is.

A real operating rhythm gives each gathering a job. This one makes decisions. This one surfaces and clears blockers. This one reviews commitments against what was actually promised. If a meeting cannot name what it exists to produce, it should be an email.

Then it adds one unglamorous rule. Every item that surfaces gets a name and a date before the room moves to the next one. Not "we'll figure it out." A person, attached to a decision, attached to a deadline, in the room, out loud. A meeting that closes its own loops cannot quietly forget anything.

And it matches the tempo to the decisions. Some calls need a daily beat. Some can genuinely wait for the quarter. Running both at the same monthly tempo guarantees you are too slow for half of them.

The test is simple and a little brutal. At the end of the meeting, can everyone in the room name the decisions that were made and who now owns each one? If the most honest description is that the meeting "aligned" people, it produced the feeling of having met, and the plan is exactly where it was before anyone sat down.

Mike