Status meetings are one of the easiest rituals for a team to justify and one of the hardest to defend honestly. Everyone can explain what they are for. Very few people can explain why they still need this many of them.
Why the status meeting is dying
Because it is a low-bandwidth way to communicate information that should already be available. If the team needs a meeting just to learn what moved, the system is weak. If the updates have to be spoken aloud to become real, the process is compensating for missing visibility.
That is why status meetings increasingly feel performative. They exist because the organization does not trust the written signal, not because the meeting itself adds much insight.
What async patterns actually work
Written updates in one shared place work. Threaded questions work. Weekly review notes work. Daily personal triage works. The common trait is simple: the information is available when needed, and it stays attached to the work instead of evaporating after the call.
Async does not mean silent. It means people communicate in a way that respects concentration and creates a durable record.
What to keep synchronous
Disagreement. Decisions with tradeoffs. Sensitive conversations. Complex debugging. Those are great reasons to meet. “Tell me what you did yesterday” is not.
The status meeting is dying because teams are learning the difference between communication and ritual. The more visible the work becomes, the less reason there is to keep reporting it live.