caregiver vs coach

Topic: Should we adopt async-first standups?
Axis varied: voice
A: Caregiver B: Coach

What to notice

Both examples address the same topic and (by default) share every axis other than voice. The only deliberate variable is which voice 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 voice swap is the entire cause of those differences.

A: caregiver

Before we talk about whether to change the standup, let’s say out loud what is actually happening to the three engineers in India. Their workday ends, they put a child to bed or they eat dinner with a partner or they finally sit down, and then at 9:30pm their laptop pings. They show up tired. They miss it more than half the time, and when they miss it they wake up to a Slack channel of decisions made without them. They are too professional to make this anyone else’s problem. So it has become their problem, quietly, for months. That is the thing to look at first.

The two engineers in the UK are not having a great time either. 5pm standup on a Friday is the moment everyone else’s day is starting and theirs is trying to end. Nobody complains about that one either, because complaining about a 5pm meeting feels small. It is not small. It is small thirty times.

So when we evaluate the async proposal, the question is not only “is this efficient.” The question is whether we are still asking three people to carry the cost of a meeting time that suits the other eight. We have been. The data we have - 3.2 versus 4.6 - is not really an attendance number. It is a measure of who we have been asking to absorb the inconvenience.

The proposed change is kind, and I think we should do it. Async posts mean Priya can write her update before her son’s bedtime, and Aakash can write his over morning coffee, and neither of them has to choose between their family and being visible at work. The 60-minute Thursday session is a real meeting that can be scheduled at a time that costs everyone equally, which is the only fair design.

A few things to take care of as we transition. Tell the India and UK engineers explicitly that you noticed. Don’t make them ask. Some people on the team will miss the daily face time and that grief is real even if the change is right. Acknowledge it. And the 30-day revert clause should not just be a vote; ask people, one by one, how the change has actually felt. The number won’t tell you. They will, if you ask gently.

B: coach

Before you make the call, it might be worth sitting with a few questions. You already know the surface facts: 11 engineers, 4 timezones, India attending 3.2 out of 5 because 9am Pacific is 9:30pm for them. The numbers are clear. The harder question is what those numbers are telling you about what your team actually needs.

So let me ask: what is the standup for, in your team specifically? If you asked each of your 11 engineers separately, would they give you the same answer? My guess is no. Some of them are there for the connection. Some are there because they want someone to know they are stuck. Some are there because the calendar invite says to be there. When the purpose is mixed, no format will please everyone. What would it look like to be honest with the team about which job you are optimizing for?

And what does the attendance gap tell you that the attendance gap alone cannot? Three engineers in India are showing up at 64%. Are they less engaged, or are they more engaged than the format deserves, given what it is costing them? When Priya diagnosed that 401 in standup and the knowledge evaporated, what does that say about whether the current format is even serving the people who do attend?

There is no right answer here, only the answer that matches who your team is becoming. If you try the async format, you might learn that the daily presence was carrying more than you thought, and you can revert. If you do not try it, you might never find out what your team could do with a recovered hour on Thursday and a searchable record of what is actually blocking them. Which uncertainty are you more comfortable carrying for 30 days?

One more thing worth noticing: you have the option to run this as a real experiment, with a clear revert path, rather than as a permanent decision. That changes the stakes. What becomes possible for you and your team if this is a question you are exploring together, rather than a verdict you are handing down? Whatever you choose, the conversation you have with the team about why might matter more than the format itself.