narrative-case-study vs chronological-narrative

Topic: Should we adopt async-first standups?
Axis varied: style
A: Narrative Case Study B: Chronological Narrative

What to notice

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

A: narrative-case-study

The standup that ran at 9:30pm

The Platform team at Meridian had a daily standup at 9am Pacific. For eight of the eleven engineers, that was a normal morning meeting. For Priya, Arjun, and Devika in Bengaluru, it was 9:30pm on a Tuesday.

For most of 2025, this was treated as a fact of geography. Priya joined when she could. She missed about two standups a week, usually because her daughter had homework or her in-laws were visiting. Nobody held it against her. The Q1 attendance report eventually showed what everyone already knew: India averaged 3.2 of 5 standups; the US side averaged 4.6.

The turning point came in early March. On a Monday morning, Marcus in Austin pushed a fix for a 401 error on the auth service. He mentioned it in standup. Priya was not on the call.

On Tuesday at 2pm Pacific, Devika hit the same 401. She did not know Marcus had fixed it. She spent the next two hours retracing the diagnosis - reading logs, opening tickets, eventually pinging Marcus on Slack. Marcus replied: “Yeah, I shipped that fix yesterday. Sorry, I should have written it up.”

Devika did not say anything in standup the next day. But she sent her manager, Lina, a short message: “If we’re going to make me wake up to standups I cannot attend, I would like the standup to also write things down.”

Lina read that message twice. Then she opened the Q1 attendance numbers and looked at them with new eyes. She also opened the Zoom recording of Monday’s standup. It was 14 minutes long. The auth fix was mentioned at the 11-minute mark, between two unrelated updates. Even if Devika had watched the recording, she would have had to watch eleven minutes of unrelated work first.

Lina proposed a 30-day trial. Replace the sync standup with an async post in #team-standup. Three fields - Shipped, In progress, Blocked or at risk - posted by 10am local time. Blockers @mention the person who can unblock. The 9am Pacific slot becomes a 60-minute Thursday working session.

She framed it as reversible. She named the success criteria up front: blocker resolution time, posting consistency, and a team survey at day 30.

The first week was awkward. Two engineers forgot to post. Marcus over-shared and had to be gently told that “Shipped: nothing yet” was acceptable. By week two the rhythm was established.

By day 30, the survey came back with a sentence from Devika that Lina pinned in her notes file: “I no longer feel like I’m chasing the team. The team is on a page I can read.” Blocker resolution time during overlap windows had dropped from a median of just over 4 hours to 90 minutes. Nine of eleven engineers were posting at least four times a week.

The team kept the change. The Thursday working session became where the real arguments happened, which is what those meetings were always supposed to be.

Lina’s takeaway, written in her own retro notes: the schedule had been treated as fixed and the people as adaptable. The trial reversed the assumption. Once that flipped, the change was small.

B: chronological-narrative

How we got here

Eighteen months ago

The team was six engineers, all in Pacific time. The standup was created on a Tuesday afternoon over coffee. Sarah suggested 15 minutes at 9:30am. Nobody argued. For the first week it ran 8 minutes. By the second week it was 12. People liked it. It felt like a team.

Twelve months ago

We hired Daniel in New York. The 9:30am Pacific time meant 12:30pm for him, right after lunch. He came in cheerful and slightly over-caffeinated. Nobody noticed the time zone was now a constraint. The standup stayed at 9:30am Pacific.

Nine months ago

We hired Priya in Bangalore. The first week, she joined at 10pm her time, with a baby asleep in the next room. Her camera was off. She said “no blockers” and signed off. In the retro that quarter, someone mentioned the time was hard for her. We discussed rotating the slot. We did not rotate the slot. The conversation got buried under a release.

Six months ago

The team hit nine engineers. Standup ran 18 minutes, then 22, then we capped it at 15 by going faster, which meant going shallower. Updates became “working on the auth thing, no blockers.” A junior engineer asked Sarah after standup what “the auth thing” was. Sarah explained for ten minutes. That conversation was the most useful thing the standup produced that day.

Last quarter

We added Arjun in Bangalore and two more US engineers. Eleven people. The standup was now 14 minutes of taking turns. Priya stopped joining on Wednesdays. Arjun joined but his camera stayed off and he muted aggressively. In the quarterly retro, both said the time was difficult. They did not push hard. The team thanked them and moved on.

Three weeks ago

The team lead pulled the attendance data from the calendar. India-based engineers: 3.2 of 5 sessions on average. US-based engineers: 4.6 of 5. The gap had been growing for a quarter and nobody had named it.

Two weeks ago

Priya was supposed to hand off a deployment to the New York team. She missed standup that morning (it was 10:15pm her time and her kid had a fever). The handoff happened in Slack instead, 13 hours later, after the New York team had already started waiting for it. The deployment slipped a day. In the post-mortem, the standup absence got named as a contributing factor.

Last Friday

The team lead proposed async-first standups in a Slack thread. Three fields, posted by 10am local, @mention blockers. The thread got 23 replies in two hours. Most were cautious-positive. Two were actively opposed. One person said “I will miss the human contact.”

This Monday

A draft proposal went out. 30-day trial. Keep Friday sync for social and demos. Measure four signals at day 30: clarity, attendance burden, blocker resolution time, surprise moments in retros.

This morning

The team votes. Whatever happens next will be the next chapter, not this one.