The Standup the Model Quietly Replaced

The daily standup on a team I've spent a lot of time with this year still happens. Same time, same call, same three questions on the same shared doc. Attendance is fine. Nobody has complained. And it has been, for a few months now, almost entirely theatre — a ritual that used to carry real information and no longer does, because the information moved somewhere else without anyone deciding to move it.

What the standup used to do

The old version worked the way standups are supposed to work. Someone would say "I'm stuck on the reconciliation logic for the Meridian account," and someone else on the call would say "oh, I hit that exact thing last month, here's what fixed it," and a blocker that might have cost half a day got cleared in ninety seconds because two people happened to be on the same call at the same time. That's the actual value of a standup — not the status report, which nobody really needs read aloud, but the accidental collision of "I have this problem" and "I have solved this problem before," surfaced by simple proximity.

Where the collision moved

That collision doesn't happen on the call anymore, because it doesn't need to. The team now runs most first-pass troubleshooting through a shared AI assistant that has access to the team's own accumulated documentation, prior tickets, and a rolling summary of recent work. The analyst stuck on the Meridian reconciliation logic asks the assistant first, gets pointed at the fix from last month within seconds, and — this is the part that quietly hollowed out the standup — never has a reason to mention being stuck at all, because the blocker resolved itself before the next standup even happened.

"Nobody killed the standup. The problems it used to catch just stopped waiting around long enough to be mentioned."

The thing that got lost anyway

Here's what makes this a genuinely interesting problem rather than a simple efficiency win, and the reason I'm writing about a fifteen-minute meeting at all: the standup wasn't only clearing blockers. It was also the moment a manager heard, in passing, that two people were quietly working on overlapping pieces of the same problem, or that a junior analyst's "I'm stuck" was really a symptom of a much bigger structural issue nobody had named yet. The AI assistant is excellent at resolving the narrow, well-documented version of "I'm stuck." It has no mechanism at all for surfacing the pattern across five people's separately-resolved blockers that would have told a manager something was structurally wrong with how a project was scoped.

We noticed this the unglamorous way — a manager realised, about six weeks after standup attendance had quietly become a formality, that she had genuinely no idea two analysts had spent most of a sprint circling the same unresolved ambiguity in a client brief, each one resolving their immediate technical blocker with the assistant and never surfacing the underlying confusion, because neither blocker, on its own, looked worth mentioning out loud.

Why I think this generalises past standups

I've since gone looking for the same pattern on other teams, and it's not hard to find once you know what shape to look for. A weekly one-on-one that used to be the only place a manager heard a quiet complaint about workload, now bypassed because the assistant handles the logistical question that used to be the excuse for booking the one-on-one in the first place. A retro that used to surface process friction, now thinner because most of the friction it used to catch gets resolved inline, in the moment, by a tool, before it accumulates into something worth complaining about at the end of the sprint. In every case, the ritual's official purpose gets served better and faster by the tool. In every case, something the ritual was quietly also doing — surfacing patterns, catching structural problems, giving a manager an unscripted read on how people are actually doing — goes missing, and nobody notices until it's been missing long enough to cost something.

"Every ritual on a team is quietly doing at least two jobs. The tool usually only replaces one of them, and it's rarely the one anyone remembers to check for."

The practical habit I'd recommend, for any team leader watching a ritual's attendance stay steady while its energy visibly drains out of it, is to ask explicitly what the ritual's second job was — the one nobody wrote down because it was never the stated purpose — before deciding whether to kill it, shrink it, or replace it. Killing a ritual that's become theatre is usually the right call. Killing it without first asking what quiet, unscripted thing it was also doing is how a team loses a safety net it didn't know it had, and finds out only once something has already slipped through the gap where the net used to be.

What we do now instead

The team didn't bring the old standup back — that would have meant reintroducing the theatre along with the value. Instead, the manager added one deliberate five-minute segment, once a week rather than daily, with a single explicit question that the assistant can't answer for anyone: "what's something you resolved on your own this week that you suspect someone else on this team is also quietly dealing with?" It's a strange question to have to ask on purpose, because it used to be the standup's whole reason for existing without anyone naming it. Now it has to be named, because the accidental version of it disappeared the moment the accidental collisions stopped happening by default.