Nobody Remembered Who Started the Meeting

The weekly meeting had survived the project, its original agenda, and eventually the person who scheduled it.

Every Tuesday at 10:30, six people joined a meeting called Weekly Project Sync. The project had launched eight months earlier, and nobody was entirely sure whether this meant the meeting had succeeded or become impossible to kill.

The invitation offered few clues. Its description said the group would “stay aligned on priorities, risks, and next steps,” which covered nearly every workplace conversation short of ordering lunch. The person who created it had moved to another team. Ownership of the calendar series had passed to a manager who inherited it along with several documents and a spreadsheet whose first tab was named FINAL.

The meeting still had a routine. One analyst updated a tracker before the call. A developer checked whether anything had changed in a system the project once depended on. Everyone took a turn giving a status, including two people whose status was usually that they had no status. The manager asked whether there were any blockers. There rarely were.

Most weeks, the meeting ended seven minutes early. This was considered evidence that it was being run efficiently.

Then a new employee joined the team and asked an inconvenient question: “What are we deciding in this meeting?”

The manager started to answer, paused, and looked at the agenda. The agenda did not appear to have been burdened with this question before.

The original meeting had a clear job. During the launch, several teams were changing related pieces of the same system. A decision in one area could create work somewhere else, and waiting a week to discover that was expensive. The meeting gave everyone one place to raise conflicts while there was still time to do something about them.

After launch, most of those conflicts disappeared. One useful piece remained: the analyst and developer needed to compare a vendor update with the internal release schedule. That conversation took about ten minutes every other week. The other four people were attending because the invitation continued to arrive and nothing had happened that felt important enough to cancel it.

Recurring meetings have an administrative advantage over almost every other request. They do not need another yes. The calendar sends them back with the confidence of a decision that has already been made, even when the conditions behind that decision have changed.

This makes the cost easy to miss. The invitation says thirty minutes. Six calendars lose three combined hours before anyone prepares the tracker, reads the notes, or stops doing something else early enough to arrive. That may be a good trade when the meeting catches a conflict that would cost days. It is harder to defend when the primary result is six people confirming that Tuesday has happened again.

Canceling it can still feel strangely aggressive. A recurring meeting has participants, history, and occasionally a color-coded document. Removing it may sound like declaring the topic unimportant or announcing that nobody needs to speak to one another anymore. Keeping it asks for nothing except continuing to do what everyone did last week.

So the manager did not begin by deleting the series. She asked what people still used it for.

The analyst and developer needed their release check. Another participant liked hearing about vendor changes but did not need to discuss them live. The remaining three could not name anything they would lose, though one admitted the meeting had become a reliable time to finish coffee.

They replaced the weekly call with a short check between the two people doing the dependent work. The analyst added the result to an existing team update, where anyone interested could read it. The manager put a review date on the new arrangement so it would have to explain itself again in three months.

Nobody recovered an entire day. The change returned less than half an hour to each person most weeks, and some of that time probably disappeared into another meeting. Still, one recurring commitment had been asked to prove that it belonged on the calendar. It kept the part that served a purpose and released the people who were there because declining an invitation from the past felt more deliberate than accepting it.

Old commitments rarely announce that they have outlived their original shape. They continue arriving on schedule, so every so often, it is useful to ask them what they are still doing here.

I write about examining commitments before and after the yes in Default: No, available now for advance readers.