Every few months, someone notices that AI can turn scattered work into a clean update: pull tasks from Jira, summarize Slack threads, compare commits, and write a neat paragraph for leadership. The obvious conclusion is that the status meeting should finally disappear. I understand the temptation. If the meeting existed only to move information from one place to another, it would already be a bad product. But that is the part of the story I do not fully buy.
The meeting is not the artifact
A status meeting is often a poor interface for a deeper social transaction. On the surface, people report progress. Underneath, they check whether somebody is still paying attention, whether a decision has silently changed, whether a risk is safe to name, whether a delay will be treated as information or as failure. None of this makes the meeting automatically valuable. Many status meetings are genuinely lazy. They repeat what should have been written, reward people who speak confidently, and punish people who need time to think. Still, calling them useless because an AI can produce the notes misses the mechanism. The meeting is not only the notes. It is a recurring moment where ambiguity is forced into contact with other people.
Automation removes the excuse, not the need
AI will remove a lot of the administrative theatre around status. That is good. It is hard to justify a team spending thirty minutes listening to updates that a system can assemble in thirty seconds. But once the update becomes cheap, the remaining question becomes less comfortable: what was the meeting really for? If the answer is only distribution of facts, cancellation is rational. If the answer is alignment, confidence, escalation, or permission to stop doing something, the team still needs a place where those things can happen. The mistake is to assume that because information became easier to move, judgment also became easier to share. It did not. Sometimes it became harder, because the clean summary makes disagreement look less necessary.
Status is often a proxy for permission
In many organizations, status is a polite word for permission. People do not only say, "this is where the work is." They are also asking, "is this still worth doing?", "am I allowed to slow down?", "will someone protect this decision if it becomes unpopular?", "does anyone above me understand the trade-off?" These questions rarely appear in the agenda, because naming them would make the social contract too visible. So they travel under safer labels: blockers, risks, dependencies, next steps. Again, this is not a moral criticism. It is a practical observation. People operate inside incentives. If a team has learned that bad news creates blame, it will not become honest because a dashboard is accurate. It will become more careful in how it hides the bad news.
The useful question is what the ritual protects
When a ritual survives after its stated function has been automated, it usually protects something else. Sometimes it protects leaders from the discomfort of trusting written updates. Sometimes it protects teams from unclear priorities. Sometimes it protects individuals from being alone with decisions they do not really own. And sometimes, less cynically, it protects coordination in a messy environment where too many things change too quickly for asynchronous updates to carry the whole load. The point is not that status meetings are secretly good. The point is that removing the visible waste without understanding the hidden function often moves the waste somewhere else. It becomes more Slack pings, more "quick syncs", more private clarification, more work performed around the system because the official system no longer has a place for the tension.
Better systems still need human nerve
The best use of AI here is not to generate more elegant summaries. It is to make the informational part boring enough that people can see what remains. If the facts are already available, a meeting can become shorter, sharper, and more honest. Or it can disappear. But that requires a kind of managerial nerve that is less common than tooling enthusiasm. Someone has to decide which conversations deserve synchronous time, which decisions need an owner, which risks should be visible before they become emergencies, and which updates are just performance. AI can expose that distinction. It cannot make the team comfortable with it.
This is why I am skeptical of the simple promise that AI will kill status meetings. It will kill some of them, and that will be useful. It will also reveal that a surprising number of meetings were never about status in the first place. They were about trust, permission, fear, accountability, and the small negotiations people use to survive uncertainty at work. That does not mean we should keep the ritual. It means we should be careful before confusing the disappearance of a calendar event with the disappearance of the problem.