The brief nobody wrote: how standup prep turns into ritual

Somewhere in your company's early history, a standup was invented on purpose. Somebody — probably tired of discovering on a Thursday that a teammate had been quietly stuck since Monday — said something like: "let's just check in every morning, fifteen minutes, what did you do, what are you doing, what's in your way." It worked. For a while, it was genuinely the highest-leverage fifteen minutes in the whole week.

You are almost certainly not in that meeting anymore. You are in its fossil.

The meeting that outlived its own reason

Here's a thought experiment. Picture your standup as a species, dropped into an environment it was well-adapted to survive in: a small team, a shared mental model, a genuine information gap between people that the meeting closed every morning. Now fast-forward eighteen months. The team is bigger. The codebase has tripled. Two of the original five people left and were replaced by people who never sat through the meeting's founding myth. The environment changed completely — and the standup didn't evolve. It just kept doing the thing that worked in the old environment, the way a species can go on performing a mating dance long after the conditions that made the dance adaptive have disappeared.

This isn't a metaphor reaching for effect. It's close to what researchers actually found when they went and watched it happen. Stray, Sjøberg and Dybå ran a grounded-theory study of the daily stand-up — interviewing 60 people and observing 79 real stand-up meetings across twelve teams in four countries — specifically to find out what the meeting becomes once it's been running for a while. Their finding, stripped of the academic hedging: standups routinely drift from peer-to-peer coordination into status reporting to whoever's perceived as being in charge. The format survives. The purpose quietly changes owners.

Three ways the ritual replaces the meeting

Watch a decayed standup closely enough and you can usually catch all three of these happening at once.

1. The audience shifts. The meeting was designed for fifteen peers correcting each other's mental models. It becomes fifteen people addressing one person, because that's who's evaluating them, and everyone else quietly stops listening — because they were never the audience to begin with.
2. The content shifts. "What I did yesterday" was supposed to surface coordination problems. It becomes a recitation of completed tickets, because tickets are what get read out loud in the retro, and nobody wants to be the person with nothing to report.
3. The prep shifts. This is the one this whole series is about. Preparing for the original meeting meant thinking: what does the team actually need to know from me today? Preparing for the fossil means: what do I say so this doesn't look bad? Those are opposite cognitive tasks, and only one of them takes any real thought.

None of the three shifts requires anyone to be lazy or political. They are the predictable result of running the same fifteen minutes, unmaintained, against a team and a codebase that keep changing underneath it. A format with no update mechanism degrades toward whatever's easiest to perform, and "recite what you did" is much easier to perform than "figure out what the team needs to hear."

What the research says actually predicts a good meeting

Here's the more useful half of the meeting-science literature, and it's almost never the half that gets quoted. The temptation is to focus on what happens during a meeting — better facilitation, tighter agendas, standing up so nobody gets too comfortable. The stronger finding runs the other direction. The Cambridge Handbook of Meeting Science, surveying the field Allen, Lehmann-Willenbrock and Rogelberg helped build, keeps landing on the same conclusion across dozens of studies: what happens before a meeting — whether there's a real agenda, whether it reflects what actually needs deciding, whether attendees walk in already knowing what's relevant to them — predicts meeting quality more reliably than almost anything that happens once people are in the room. Rogelberg, Scott and Kello made a related point in their own review of the field, in MIT Sloan Management Review: much of the dissatisfaction employees report with meetings traces to a mismatch between what the meeting is nominally for and what it's actually accomplishing — precisely the gap that opens once a meeting's original purpose quietly gets replaced by its performance.

Put those two findings together and the diagnosis for your standup writes itself: the ritual isn't a facilitation problem. It's a preparation problem. Nobody assembled a real brief, so the meeting had nothing real to run on, so it defaulted to the easiest available substitute — reciting yesterday.

A meeting doesn't decay because people stop caring. It decays because the thing it was supposed to run on — a fresh, specific, currently-true picture of what matters — stopped being assembled, and recitation is what fills the vacuum.

Why nobody keeps assembling it

Here's the part that should feel less like a scold and more like an indictment of the format itself. Suppose your team is disciplined. Suppose someone genuinely does sit down every morning and think hard about what the team needs to hear. That person is now doing unpaid, invisible cognitive labor, every single day, forever, with no artifact to show for it and no way to hand it off cleanly to whoever's on call this week. The moment that person goes on vacation, or changes teams, or simply has a bad morning, the brief stops happening and nobody notices for weeks — because the fossil format runs exactly the same whether or not a brief preceded it. Recitation doesn't need preparation. That's precisely why it's the attractor state.

A brief that depends on one conscientious human doing quiet, uncredited work every morning is a brief with a bus factor of one, propping up a fifteen-minute meeting that everyone else assumes runs on its own. It was never going to survive an org chart.

What a brief would have to be, to survive

Run the logic forward and the requirements aren't complicated, even if almost nobody meets them. A brief that survives has to exist independent of any one person's morning mood. It has to be current — reflecting what actually happened since the last standup, not what people remember happening, which per the rest of this series is a very different and much friendlier-sounding thing. And it has to answer the one question the fossil format quietly stopped asking: not "what did everyone do," but "what does this team need to know today that it doesn't already know" — open commitments coming due, anything the codebase itself has already contradicted, and the one question worth asking each person given what they've actually touched.

Notice that none of that requires better facilitation, a stricter timer, or a braver Scrum Master willing to interrupt the CEO. It requires an artifact that shows up whether or not anyone remembered to make it — which is exactly the kind of thing production systems are good at generating and humans are bad at sustaining by willpower. (This is the specific gap CodeNSM's pre-scrum brief is built to close: a page generated from the commit log and the telemetry before the meeting starts, so the fifteen minutes has something real to run against even on the week nobody had time to prepare.)

The test that actually matters

Here's a diagnostic you can run tomorrow morning, and it costs nothing: before your next standup, ask whether anyone in the room could describe, in one sentence, what today's meeting is for — not what it's called, what it's for. If four different people give you four different answers, you don't have a coordination meeting. You have a ritual that used to be one, still wearing its name tag.

Run the six-question check below and find out which regime your team is actually in.