celebratory vs playful
Topic: Should we adopt async-first standups?
Axis varied: tone
A: Celebratory B: Playful
What to notice
Section titled “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: celebratory
Team,
30 days ago we started the async standup trial. Today I want to tell you what we accomplished, because the numbers are real and the people behind them are the reason.
Participation across timezones, finally even. For the first time since we became a four-timezone team, our India engineers participated in daily coordination at the same rate as everyone else. Bengaluru posted on 96% of working days this month. Last quarter they made 3.2 of 5 sync standups. This month they were present in the conversation every single day. Priya, Rajiv, Anjali - thank you. You showed up the moment the format let you.
Blocker response time, cut in half. Median time from blocker posted to blocker owned dropped from 19 hours to 7. Median time to resolution dropped from 2.4 days to 1.1. Every blocker this month was claimed by a named owner within the workday it was raised. That happened because all of you took the @mention discipline seriously, and because Marcus and Lin made a habit of scanning the channel before lunch and picking up unowned items. That habit is the system. Thank you both.
Zero handoff incidents. Last quarter we had three production issues that root-caused to “the person who knew was offline and nobody else had the context.” This month: zero. The written record is doing the work the meeting could not.
The Thursday working session has become the best hour of our week. I have heard this from at least six of you unprompted. We are using it for real coordination - architecture decisions, cross-team dependencies, the messy middle of hard problems. The agenda fills itself now. That is what coordination time is supposed to feel like.
A specific call-out: Sam built the blocker-tracking dashboard in week two, on their own initiative, because they noticed we were losing track of resolved-vs-open items in scrollback. That dashboard is now how we run the channel. Quiet, useful, exactly the kind of work that compounds.
We are making this permanent.
A trial only succeeds because people decide to make it succeed. You did that. I am genuinely proud of this team, and grateful that we get to keep doing work this way.
B: playful
Friends, colleagues, fellow connoisseurs of the 14-minute meeting in which 10 minutes are spent waiting for Zoom to admit Rajiv:
I have a modest proposal.
Our daily standup is, by the numbers, a beverage service. It runs 14 minutes. Roughly 4 of those minutes produce anything an engineer can act on. The remaining 10 minutes are, generously, vibes. We are paying for vibes in the currency of three engineers’ evenings, because 9am Pacific is 9:30pm in Bengaluru, which is the time when normal humans are eating dinner and abnormal humans are watching us nod sympathetically at a screen.
So here is the pitch. For 30 days, we replace the daily sync with three lines of text in #team-standup, posted by 10am local time:
- Shipped: something
- In progress: something
- Blocked: ideally nothing, but if something, @ the person who can unblock it
Three lines. Local time. The end. If you want to add a gif, I will not stop you, but I will judge you, and so will history.
The 9am Pacific slot does not disappear into the void. It becomes a 60-minute Thursday working session, which is a beautiful phrase that means “an hour where we actually do the coordination work that standup pretends to do but doesn’t.” Bring problems. Bring decisions. Do not bring status updates - status updates have their own channel now and they are happy there.
I want to be clear: this is not me being precious about meetings. The sync standup has done its job. It got us through the first year of being a team across four timezones. We have outgrown it the way you outgrow a pair of jeans you really liked. There is no shame in this. We simply need pants that fit.
30 days. If it stinks, we revert. If it works, the India team eats dinner with their families and the US team gets 14 minutes of their morning back to do literally anything else, including, if they insist, scheduling another meeting.
Reply with a thumbs up if you are in, a thumbs down if you are not, and a thumbs sideways if you have feedback. I am reading all of them.