In the first week of the project everyone reads the report. The sponsor replies with two questions, a director calls about one risk, someone asks for a date to be clarified.
In week three the sponsor replies “thanks”. In week six nobody replies. In week ten the report has the same structure, the same headings and half the same sentences as the week before, and the only person who reads it in full is the author.
Nobody decided to stop reading. The report simply stopped surprising anyone, and people quickly learn to skip what looks familiar.
What happens to a report nobody reads
The author is the first to notice. Since nobody asks, writing it takes less and less time. Sentences pass from week to week with a small change of date. “Work on the integration is ongoing” appears in the report for the fifth time running, and nobody has asked why it is taking so long.
There is no ill will in this. A report written for nobody turns into a ritual. Bad news put into such a report can sit there for three weeks, and formally everyone has been informed. This is how status reports stay “on track” for weeks right before a project turns red.
That is how a good tool becomes an alibi. The author can say they wrote it. The reader can say they received it.
Five minutes that give the report its meaning back
In my experience a report starts working again when at least one person reads it with three questions in mind. It takes five minutes.
What has changed since last week? I put the last two reports side by side. If they differ only in the date, then either nothing happened in the project or the report has stopped describing the project. Both cases are worth one question.
Which sentence is here for the third time? “In progress”, “work is ongoing”, “waiting for a reply”. Each of them is fine for a week. After three weeks it means something is stuck and nobody has called it that.
What isn’t here that used to be? A risk that vanished from the list without a word of explanation. A task there was a lot about three weeks ago and nothing today. Things rarely disappear from a report because they were solved. More often they disappear because they became uncomfortable.
One question in reply
After those five minutes it is enough to reply with one question. Not a list of remarks and not an assessment, just one specific question about one sentence in the report.
“The integration has been in progress for three weeks. What is holding it?”
The effect is bigger than one sentence would suggest. The author learns that someone is reading and writes the next report more carefully. After two or three such questions, sentences copied without thought disappear from the report, because any of them may come back with a question.
Tone matters. The question should sound like curiosity, not like catching someone out. An author who gets an interrogation in return for honesty will start writing more cautiously, which means less truthfully.
If you are the one writing the report
The same mechanism works the other way round. A PM who sees that nobody reads their reports can check that and change it.
The simplest way is to end the report with one question to the reader that needs an answer. If nobody answers for two weeks, the report isn’t getting through, and it is better to know that now than on the day there is something important in it.
The second way is to cut it in half. A one-page report in which most sentences change every week gets read. A four-page report in which one sentence changes does not. The four-part structure a sponsor update needs fits on that one page.
One question for this week
Take the last two reports from a project you oversee or run. Which sentence is identical in both, and what is really behind it?
All situations described in this article are based on real events, but contain no company names, no individual names, and no data from any specific project.
