confessional vs empathetic

Topic: Should we adopt async-first standups?
Axis varied: tone
A: Confessional B: Empathetic

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

I should have raised this six months ago, and I want to name that before I say anything else.

When we added the second India engineer in October, I noticed the standup time was going to be hard for them. I told myself it would settle. I told myself we would figure it out. What I actually did was nothing, for six months, while three engineers logged on at 9:30pm two or three nights a week and a fourth quietly stopped logging on at all. The 3.2/5 attendance number is not a discovery. It is a thing I could have seen any week if I had been looking.

I think I avoided this because the current standup is mine. I instituted it when the team was five people in Oakland, and I have always liked it. It made me feel like the team was a team. Changing it feels, honestly, like admitting that the team I built is not the team we have now, which is a thing I have known intellectually for a year and not really let myself feel.

The proposal in front of us - async updates with three fields, Thursday working session, thirty-day trial - is a good proposal, and it is mostly not mine. Other people on the team have been thinking about this more carefully than I have, and the reason it has not happened yet is that I have been slow.

So I want to say two things. First: I am for it, and I do not want to dress that up. Second: if anyone on the team, especially in India, has been carrying the cost of my slowness, I am sorry. The cost was real, and it was avoidable, and the person who could have avoided it was me.

Let us start the trial Monday.

B: empathetic

Team,

Before I propose a change, I want to name what the current schedule has been costing some of you, because I think we have been too quiet about it.

For our colleagues in Bengaluru, our 9am Pacific standup lands at 9:30pm IST. That is not a small inconvenience. That is dinner with your family, time with your kids before they sleep, the slow part of the evening that belongs to you. The attendance numbers reflect what any reasonable person would do: India averaged 3.2 of 5 standups last quarter, while US engineers averaged 4.6. I do not read that as a participation problem. I read it as people protecting the parts of their lives that should not be negotiable, and I think they have been right to do so.

I also want to acknowledge what missing standup actually costs the engineers who miss it. It is not the 14 minutes of meeting. It is the quiet drip of context you do not have the next morning - the decision that was half-made, the name of the person who picked up the migration, the thing someone mentioned in passing that turns out to matter. Catching up by reading scrollback is not the same, and I know it has sometimes felt like working with one hand behind your back.

And for those of you who have shown up at 9am Pacific every day, I want to acknowledge something too. The daily sync gave us a rhythm. Seeing each other, even briefly, is not nothing. If we move to async, we lose some of that, and I do not want to pretend the loss is zero.

Here is what I am proposing, with all of that in mind. For 30 days, we try an async format in #team-standup. Post by 10am your local time. Three fields: shipped, in progress, blocked. Blockers @mention an owner. The 9am Pacific slot becomes a Thursday working session - one hour, real collaboration, not status.

We can revert. We can adjust. What I do not want to keep doing is asking a third of the team to choose between their evening and their information.

Tell me what I am missing. I will listen carefully.