daily-standup vs slack-message

Topic: Should we adopt async-first standups?
Axis varied: format
A: Daily Standup B: Slack Message

What to notice

Both live in Slack, and only one of them is a format.

A is the fixed three-part structure, filled in: shipped, in progress, blocked. It would keep its shape pasted into a doc, an email, or a wiki.

B is a channel message doing something else entirely, namely proposing the trial: “Proposal: try async standups for 30 days starting May 19.”

The tell: the container is not the format. B is Slack-shaped because of where it lives; A is standup-shaped because of what it is.

#team-standup - Devon Park - Tue May 27, 9:42am PT (day 9 of trial)

Shipped

In progress

Production rollout of rate-limiter, gated behind rl_v2 flag, 5% traffic by EOD
Pairing with Aditi 10am PT on the IST-hour metrics dashboard

Blocked / at risk

Waiting on @sara for sign-off on the rotation runbook before I close the parent ticket (not urgent, EOW is fine)
(meta) Async format participation was 9/11 yesterday - @oliver and @emma did not post. Oliver was on-call handoff, fine. Emma I will DM. Flagging so @maya has visibility before the day-15 pulse.

Proposal: try async standups for 30 days starting May 19

Our 9am standup is hard on the India team and the info disappears after each call. Want to run an experiment:

Each person posts to #team-standup by 10am local time (3 fields: shipped / in progress / blocked)
Blocked items @mention the person who can unblock
On-call reads the channel by 9am PT and responds to blocks within 30 min
We keep Thursday 3pm as a real working session for anything that needs live discussion

@priya @arjun @deepa - this gets you out of 9:30pm standups. Want to hear your reaction first.

:thread: Drop thoughts in thread by Friday and I will send a final plan Monday.