friendly-mentor vs storyteller

Topic: Should we adopt async-first standups?
Axis varied: voice
A: Friendly Mentor B: Storyteller

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: friendly-mentor

You have probably been in that standup. Twelve people on a Zoom call. Someone shares their screen to demo a bug they hit. Three people are clearly doing something else. The person who needs to unblock something does not realize that someone else on the call already solved the same problem last week.

That is not a standup problem. That is a coordination problem wearing a standup costume.

Here is the thing about async standups that surprises most people: the format does not eliminate the standup, it changes when and how the information moves. Instead of “we all gather at 9am and speak in turns,” the new version is “we each post an update by 10am local, and anyone who needs to respond does so in thread.”

The part that trips most people up is this: they think async means slower. It often means faster. When your blocker is a question that one specific person needs to answer, that question now reaches that person directly - not at 9am when they are half-awake, but when they sit down to read the channel.

What you do need to think through is structure. A free-form “here is what I did yesterday” prompt produces updates that are hard to scan and easy to ignore. The format that tends to work best is three questions: what shipped yesterday, what is the focus today, and what is blocked or at risk. Short answers, not essays. The discipline is in the brevity.

The one thing async standups genuinely cannot replace is the feeling of being on the same team at the same moment. If your team has low cohesion, adding a daily async ritual will not fix it. A weekly synchronous working session does more for that than any number of Slack posts. Use async for status. Use synchronous time for actual collaboration.

Start with a two-week trial. You will know pretty quickly whether it is working.

B: storyteller

The Slack channel had forty-seven new messages when Priya opened her laptop. It was 9:47pm in Bengaluru. The standup had ended without her, again. Outside her window, an autorickshaw passed. Inside, her son turned over in his sleep and made the small sound he sometimes made.

She scrolled.

Marco had shipped the cache invalidation fix. Good. There was a thread about the migration she had been waiting on for two weeks, and it ended with a shrug emoji from someone in London. She did not know what the shrug meant. Above the shrug, Dev had written, “I’ll pick this up tomorrow.” Below the shrug, nobody had replied. Priya read the thread twice. She still did not know what the shrug meant.

She typed, “Hey - is the migration unblocked or not?” Then she deleted it. Then she typed it again. Then she closed the laptop.

In San Francisco, Marco had just gotten back from lunch. He saw Priya’s question come in, then disappear, then come in again. He thought about answering. He thought about how the standup had ended forty minutes ago and how he had explained the migration status during it. He thought about how Priya had not been there. He thought about how Priya had not been there last Tuesday, either, or the Tuesday before. He thought about what time it was in Bengaluru.

He typed, “Yes - unblocked. I’ll write it up properly in a doc tonight your time so it’s there when you start.”

In Bengaluru, Priya had already gone to make tea. When she came back, the message was waiting.

She read it twice. Then she opened a new document and started writing down everything she had figured out about the migration over the last two weeks, the parts that had only ever lived in her head, the parts she had been planning to say in standup but had never quite gotten to. The document grew. The autorickshaw came back the other way.

At her standup the next morning - the proposed new one, the asynchronous one, posted by 10am local - she would paste the link.