candid vs confident

Topic: Should we adopt async-first standups?
Axis varied: tone
A: Candid B: Confident

What to notice

Both examples address the same topic and (by default) share every axis other than tone. The only deliberate variable is which tone the writing was rendered through. Read both and ask: where does the framing change? Where does the vocabulary change? What does the reader take away from A that they would not take away from B, and vice versa? The tone swap is the entire cause of those differences.

A: candid

Team,

I want to be direct about something: our daily standup is not delivering what it is supposed to deliver, and we need to change it.

Here is the honest picture. We have three engineers who join at 9:30pm their local time on most days - and when they cannot make it, they miss information that affects their work. We have engineers who post “same as yesterday” most Tuesdays because nothing has actually changed since Monday’s standup. We have blockers that get mentioned in the meeting and then disappear because nobody wrote them down. The standup takes 14 minutes on average and the signal-to-noise ratio is not good.

I know this is not news to some of you. I have been aware of it for a while and I should have said something sooner.

Here is what I think we should do: replace the synchronous standup with an async format for 30 days. Three questions, answered in Slack by 10am local time: what shipped, what is in progress today, what is blocked or at risk. Blocked items require a @mention. I read the channel each morning and make sure blocks get resolved the same day.

This does not fix everything. If people do not post consistently, the format breaks. If I do not read the channel attentively, blocked items will pile up. I am asking for your participation and holding myself accountable to the same standard.

The synchronous meeting I want to preserve is Thursday working sessions - real collaboration, not status.

I would rather try this and learn than continue a format that is not working. We will review at 30 days and make a permanent call together.

Any questions, come find me.

B: confident

Async standups are the right call for this team. The math forces it.

We have eleven engineers across four timezones. Our standup at 9am Pacific lands at 9:30pm in India, and our India engineers attend 3.2 times out of 5 because they have families and lives and 9:30pm is not a fair ask. We have been doing this for months. The pattern is not going to change by itself.

The 14-minute standup with 4 minutes of signal is also not a coincidence. Sync standups optimize for the speaker’s convenience over the listener’s, and they convert status into a performance instead of a record. When status does not persist, every cross-timezone handoff costs us a second conversation. We pay that cost every day.

The proposal is well-shaped. Three fields - Shipped, In progress, Blocked-or-at-risk - is enough structure to make the updates scannable without turning them into paperwork. Posting by 10am local means each timezone writes during their own peak, which is when status is most accurate. Blockers @-mentioned means urgency still has a channel. And reclaiming the slot for a 60-minute Thursday working session gives us back something the current standup was pretending to be: a real coordination point.

There is one thing I want to be clear about. Async standups are not just a kinder version of what we have. They are a different operating mode. The team will lose some incidental conversation, and people who like meetings will feel that loss. That is a fair cost, and it is smaller than the cost of asking three engineers to log on at 9:30pm.

Thirty days is enough to learn whether the team adopts the rhythm. We do not need to debate it further. Let us run it.