Written Updates Over Standups: Six Weeks Without a Morning Call

Nine people had spent 14 minutes a morning in a call that produced, on average, one decision a week. The maths was not subtle. Moving the update to a written form was supposed to return 63 minutes a week to each person, and it returned something more useful than time.

The team built a scheduling product for clinics, working across three countries. The morning call had existed since the company had five people, and nobody had asked what it was for after the sixth joined.

The standup that had stopped standing up

The format was the usual one: what I did, what I will do, what is blocking me. It ran for 14 minutes because everyone spoke in turn and two people always had a story. Four attendees had no work in progress at any given moment, so their turn was a formality.

The blocking question was the only part with a function, and it was answered twice in five weeks.

The replacement

The team replaced the call with a message posted before 10:00 local time in a single channel, using three fixed lines: what moved yesterday, what moves today, and what is stuck. Two rules made it work. The message had to name a ticket, and nobody was allowed to reply inside the thread unless a ticket was blocked.

The first rule killed the narrative. The second rule killed the conversation.

The first two weeks

Messages were long. Three or four people wrote six or seven lines instead of three, which took twelve minutes and produced no more information than the call. One person stopped posting entirely, which nobody noticed for four days.

The channel also accumulated replies that should have been tickets, because a written channel feels like a place to discuss.

Cutting the message back

The team imposed a length limit of 40 words per section and a hard rule that a stuck item must carry a name and a date. The length limit was arbitrary and worked. The stuck-item rule converted complaints into requests, which changed who responded.

By week three the median message was 31 words and took about two minutes to write. Reading all nine took four minutes.

What the written form exposed

Two people had been doing work that nobody knew about, because in a call they had learned to describe it in a way that sounded like part of a larger effort. Written against a ticket number, the work stood alone and looked exactly as small as it was.

One of those two raised it directly in week four, which would not have happened on a call where the social cost of speaking is higher.

What was lost

The call had carried tone. A short answer in writing reads as curt, and two exchanges in week two were read as irritation when neither was. The team added an explicit convention: a plain answer means agreement, not annoyance.

The other loss was speed on genuinely tangled problems. Three times in six weeks someone said they missed the call, and all three times the problem was solved faster by two people writing for ten minutes than by nine people talking for fourteen.

Six weeks on

The meeting was not reinstated. Decisions made per week rose from roughly one to four, measured by counting tickets that changed scope after an update. Blocked items were resolved in a median of six hours rather than overnight.

The reading habit nobody planned

Reading nine updates takes four minutes, and within a month most of the team was reading them at a fixed time rather than as they arrived. That single change removed the last reason to check a channel continuously in the morning, which was where the interruption cost had actually lived.

The updates also became the record. When a piece of work was questioned three weeks later, the answer was in the channel with a date attached, which the call had never provided.

Nine people once spent 14 minutes a morning to produce one decision a week. The same nine now spend two minutes writing and four minutes reading, and the week produces four decisions instead of one.