The Meeting That Became a Document: A Weekly Review Test
A weekly review meeting consumed 75 minutes of eight people’s time and generated 3 action items, of which 1.2 on average were completed. Replacing the meeting with a document produced 7 actions and a 4.1 completion rate over six weeks.
The team ran marketing for a software company: campaigns, content and events. The review covered progress, blockers and approvals, and it had been running weekly for two years.
How the 75 minutes were spent
A timed sample of three meetings showed 22 minutes of reporting, 31 minutes of discussion about two items, 14 minutes of approvals and 8 minutes of finding a document someone had mentioned.
The approvals were the only part that required more than one person at once, and they took 14 minutes for four decisions.
The document format
The replacement was a single document published on Friday morning with four sections: what shipped, what slipped and why, what needs a decision, and what needs approval. Decisions were written as options with a recommendation, and comment threads closed on Monday at noon.
The document was capped at two pages, which forced the writing to be selective rather than exhaustive.
The first fortnight
Writing the document took the owner about 55 minutes, which was more than expected and less than the 75 minutes she used to spend in the room. Comments arrived unevenly: six people commented, two did not, and one of the silent two was responsible for a third of the approvals.
Silence became the first problem to solve, because an approval that never arrives blocks a week.
The approval rule
The team introduced a default: an approval not refused by Monday noon is granted, and the person who was asked is named in the document. This inverted the burden and made silence productive.
It was used 11 times in six weeks. Twice someone objected after the deadline and the work was adjusted rather than reversed.
What the document did to quality
Writing an option set forces the writer to state a recommendation, and stating a recommendation invites disagreement that a verbal update never triggers. The number of comments that changed an outcome rose from about one a week to four.
The document also created a record. Three decisions from the first month were cited in the sixth week, which had never happened with verbal reviews.
What was lost
Two people said they missed hearing how others reacted to a number, which is information a comment thread carries poorly. One campaign was approved in the document that would probably have been questioned in the room, and it underperformed.
That is a real cost and the team recorded it without changing the format, because the counterfactual cannot be tested.
The effort shift
Total time spent fell from 600 minutes a week across eight people to 160 minutes of reading and writing, plus 55 minutes of authorship. The saving is real but the distribution changed: the document owner now carries more of the load than she did before.
The team recognised this and rotated authorship, which spread the work and reduced the quality of the document, since not everyone writes an option set well.
Six weeks on
Actions per cycle rose from 3 to 7 and completion from 1.2 to 4.1. The meeting has been reinstated once, for a quarterly planning session that genuinely required everyone at once.
What the document replaced
The meeting had also carried a social function that the document does not: eight people hearing the same number in the same minute, which produced a shared sense of the week’s shape. Two of them said they now read the document at different times and arrive at different impressions of how the week went.
The team judged that acceptable, because the impressions were rarely acted on and the decisions now arrive faster.
Seventy-five minutes once produced three actions and one and a bit completions. A two-page document now produces seven and four, and the week no longer contains an hour where eight people wait for four approvals.
