Standup is status report performed live for people who could have read it. What replaced it for you?
Fifteen people. Fifteen minutes. Roughly ninety seconds of information.
The format's failure is structural, not cultural. You're asked what you did yesterday at the exact moment you're least able to answer before coffee, from memory, in front of an audience. So everyone reports the ticket they had open, because that's the retrievable answer. The actual texture of the day, the part where you'd learn something about how the sprint is really going, is gone.
The thing that's worked better for us: declaring intent in the morning instead of reporting history. "Here's what I'm picking up today" takes ten seconds, is answerable without memory, and produces something you can compare against reality at 6pm. Plan versus done, written down, no meeting.
Where it falls apart is that plan-versus-done is only useful if nobody's judged on the gap, the moment it becomes a scorecard, everyone starts declaring safe plans.
What's your team actually doing? I'm looking for things that survived contact with a real team longer than a month, not things that sound good on a blog.
Replies
The least able to answer before coffee line is painfully true, I've watched people read yesterday's tickets in a voice that says they're hearing them for the first time too. On the marketing side I moved my check-in to one written line of intent in a channel, and the surprising win was that people started replying to it, which never happened in the meeting. The gap-becomes-scorecard trap is real though, we only dodged it because nobody senior reads the channel haha.
@yelyzaveta_kibets That only works while leadership stays out of the channel 😂 Have replies to the written check-in changed what your team actually works on that day?
@akarsh_hegde Yes, but not how I expected: the replies rarely change my day, they change someone else's. Twice a month somebody sees my line about a campaign and goes wait, that collides with what I'm shipping, and we catch it at 9:05 instead of in a retro. The meeting never caught those because everyone was rehearsing their own update instead of listening haha.
@yelyzaveta_kibets That’s a much better signal than a round of rehearsed updates. Have those early collision checks reduced the number of issues reaching your retros?
@akarsh_hegde Fewer, though I never counted, what changed most is the temperature: retros stopped being where surprises surface and became where patterns get named. The collisions still happen, they just cost an hour instead of a sprint. That alone paid for the one-line habit.