When the group chat goes quiet

One week out from White Friday, the most honest dashboard I have is the campaign group chat.

Every peak I have run with a distributed team has one. The planner in one city, the designer in another, the developer in a time zone that is already asleep, the founder everywhere at once. The group exists to coordinate. What it actually does is measure.

Read it by volume, not by content.

A busy chat in the last week is a system failing in real time. Someone asks where the final creative is, which means there is no single place it lives. Someone asks whether the code has been tested, which means nobody owns testing. Someone pastes a screenshot of the landing page at midnight, which means a check that belonged on a test site is happening live, on a phone, by whoever is still awake.

Every message is a decision that had no home.

A quiet chat is the opposite, and it is easily misread. A founder who sees nothing for a day assumes nothing is happening. Usually the reverse is true. The creative was locked on the date it was meant to be. The offer sits in a document everyone can find. The person who owns the code has already tested it and has nothing to report, because nothing to report was the point.

The best-run peak I have watched produced almost no messages in its final week. A few confirmations. One question. Then the day itself, and a chat that stayed quiet through it, because everything that could break had been given an owner in October.

Nobody measures this. The post-peak report has revenue, spend, a return figure, a note on stock. It has no line for how many times someone asked, at eleven at night, where a file was. It cannot tell you whether the number was hit by a system or by people who did not sleep.

The chat can. Nobody files the chat.