candid vs skeptical

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

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: skeptical

The case for switching to async is real. India is at 3.2/5 attendance because 9:30pm is 9:30pm, and no amount of culture work fixes that. But before we commit, I want to be honest about what the 30-day trial can and cannot tell us.

What is established: the current standup hurts our India engineers. The 14-minute meeting with 4 minutes of signal is documented. Status not persisting is documented. These are the things I am sure of.

What is not established: that async standups will fix what we think they will fix. Thirty days is two sprint cycles. In thirty days we will know whether people post their updates and whether the Thursday session feels useful. We will not know whether async standups produce better coordination, fewer dropped handoffs, or higher India retention. Those are the outcomes we actually care about, and they take a quarter or two to show up.

I would also push on what “trial success” means. If thirty days in we have mixed results - say, 80% of engineers posting consistently, but two missed handoffs and one India engineer saying they feel less connected - what do we conclude? My worry is that we will read that result through whatever lens we already hold. The people who wanted async will see the 80%. The people who wanted sync will see the handoffs.

I am not arguing against the change. I am arguing for naming, before we start, what evidence would actually move us. What posting rate is the floor? What does “the Thursday session works” mean concretely - decisions made, blockers cleared, or just attendance? And what would make us roll it back?

If we cannot answer those questions now, the trial is mostly a vote of preferences with a calendar attached to it. Let us decide what we are measuring before we measure it.