reverent vs warm

Topic: Should we adopt async-first standups?
Axis varied: tone
A: Reverent 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: reverent

There is something worth pausing over in the daily standup, before we decide whether to change it.

The practice, at its origin, was not really about status. It was about something older and harder to name: the daily act of accounting for yourself to the people who are depending on you. What am I carrying? Where am I stuck? What do I need, and what do I have to offer? To speak these things aloud, in front of your team, is a small act of trust. It assumes that your colleagues are paying attention, that your progress matters to them, that your blockers are their concern too.

This is not nothing. And it should not be discarded lightly.

The question before us is whether the specific form - the synchronous daily meeting, the verbal report, the shared calendar slot - is the only way to sustain that accountability, or whether the accountability itself can survive in a different vessel.

There are teams separated by oceans who have found that a well-kept async channel carries more genuine weight than a hurried meeting where half the participants are elsewhere in mind if not in body. The words posted to a Slack thread at 8am, carefully chosen, read carefully by the people who need to know them - there is a kind of presence in that, different from the meeting but not lesser.

What would be lost, and what would need to be tended deliberately, is the sense of shared time. The meeting, for all its inefficiency, puts everyone in the same moment. That shared moment is not nothing either.

Whatever we decide, let us not decide quickly. The question is not only whether async standups work. The question is what we owe one another in the daily rhythm of work, and what form that obligation should take.

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.