Async standups that don’t lose the blocker.

01 · The problem

A digest is a bulletin. It owns nothing.

Getting nine people to type three lines async, across timezones — a standup bot does that fine. That was never where standup broke. It broke at the blocker nobody actioned, because posting a wall of answers and owning what's in them are different jobs.

line 3where the blocker was, under forty replies 2ndsprint running for the same expired credentials

02 · What you need

The blocker becomes something owned.

Reading "blocked — staging creds expired" shouldn't end in printing it in bold. It opens as a tracked item with a named owner and a give-up date — the day it stops waiting and re-plans — and carries forward until it's actually resolved. Pick what happens next and watch it run.

03 · How it runs

Collect, then own what's in it.

Set where the standup happens and what a "done" gets checked against. Every step rewrites itself to match — she asks each person individually so nobody copies the answer above theirs, and where a surface can't do something, it says so.

04 · What it's worth

If you only need the answers collected, keep the bot.

Collecting is genuinely solved, and a standup bot is free or close to it. Go and use one if that's the job. The difference is what happens to line 3 between Monday and Friday.