The Meeting That Outlived Its Purpose

https://hackernoon.imgix.net/images/2jqChkrv03exBUgkLrDzIbfM99q2-8a022sk.jpeg

Fourteen of my forty weekly hours belonged to one recurring status meeting with eleven people on the invite. Cutting it to four people and fifteen minutes did not slow anything down.

Forty hours in a week, and fourteen of them belonged to one recurring meeting. I counted, calendar block by calendar block, for the whole quarter, and the number held steady week after week. A Tuesday status sync with eleven people on the invite, most of whom sat through the full hour and said nothing.

That meeting existed for a reason once. Eighteen months earlier, a deployment slipped through three teams without anyone flagging a broken dependency until it hit production, and the postmortem's one durable output was a standing sync meant to catch exactly that kind of gap before it shipped.

It caught almost nothing after the first two months. The actual blockers surfaced in Slack threads and one-on-ones...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE