diplomatic vs warm

Topic: Should we adopt async-first standups?
Axis varied: tone
A: Diplomatic B: Warm

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

I want to first acknowledge that our current standup was set up thoughtfully. The 9am Pacific slot was chosen when the team was smaller and largely co-located, and it has served a real purpose: it gave the team a shared daily moment and helped newer engineers feel connected. That value is not in question.

What has changed is the shape of the team. With three engineers now based in India, the 9:30pm slot has become a structural ask rather than an occasional one. The attendance pattern - 3.2 out of 5 for India versus 4.6 for the US - is not a reflection of engagement. It is, more accurately, a reflection of what we are asking people to give up at home. I think most of us would attend at the same rate in their position.

With that context in mind, I would like to propose - for the team’s consideration, and certainly open to refinement - that we trial an async-first format. The current sync slot would be reclaimed as a 60-minute Thursday working session, which preserves the value of synchronous time while moving daily status to a written channel that all timezones can participate in equally.

The proposed format is modest: three fields, posted by 10am local, with blockers @-mentioned for urgency. The intent is not to remove conversation but to relocate it - to a channel where the India team can contribute on the same footing as everyone else, and where status persists for the engineer who needs it three hours later.

It seems reasonable to treat this as a thirty-day trial, with a check-in at the midpoint. If the format does not serve the team well, we are not committed to it. I am also conscious that this change touches a meeting many of us care about, and I would welcome any concerns or adjustments before we proceed.

Whatever we land on, I am grateful for the care the team has put into this question.

B: warm

Hey team,

I want to share something I have been sitting with for a few weeks, and I want your honest reaction to it.

Our standup is not working well for everyone on this team. I know that. The people joining at 9:30pm their time - I see you, and I appreciate that you keep showing up. That should not be the ask. You should not have to choose between participating in the team rhythm and having a life after 9pm.

I have been looking at how other teams handle this, and I want to try something: moving to an async standup format for 30 days. Each person posts a short update to #team-standup by 10am their local time - what shipped, what is in progress, what is blocked. If you are blocked, you @mention the person who can help. I commit to reading the channel every morning and making sure blocked items get attention the same day.

What I hope this gives you is the ability to participate in a way that actually fits your day. A standup that requires me to see you all at the same moment was designed for a team that lived in the same building. We are not that team. I want our coordination practice to match the team we actually are.

I do not want to lose the sense of being in this together, so I want to keep a weekly sync on Thursdays - not for status, just for the work that needs real conversation. That is the standup I want to grow.

Can you each take five minutes this week to think about whether this would work for you? Drop your reactions in thread. If there are concerns I have not thought through, I want to hear them before we start.

Grateful to be building this with you.