The message that survives a change of shift

The afternoon team at a coordination office used to receive a long email at the end of every morning shift. It contained useful information, but completed tasks, unresolved questions and background comments appeared in the order the writer remembered them. A colleague reading quickly could easily mistake the latest comment for the current status. The office therefore tried a different structure for two weeks, asking writers to separate completed work from actions that still required an owner or a reply.

During the trial, one entry concerned a replacement radio. The morning team had checked the faulty item and submitted a request, but the replacement had not yet been approved. An early draft described the matter as “dealt with”. The outgoing officer meant that the request had been sent; the incoming officer understood that a working radio would be available. Neither person had deliberately withheld information. The phrase simply compressed two distinct stages into an apparently reassuring conclusion.

The team rewrote the entry to identify what had happened, what remained open and who would follow it up. It also included a time for the next update, rather than inventing a delivery time that nobody could confirm. This last distinction mattered: an update can be promised by the person responsible for sending it, while an external delivery may depend on decisions outside that person’s control. The revised message was slightly longer, but required fewer clarification calls.

At the end of the trial, staff chose to keep the new headings while allowing short background notes where a decision needed context. They did not introduce a rigid word limit. Their test was whether a colleague arriving without the morning conversation could identify the next action. If the answer was unclear, the writer revised the message before leaving. Concision remained a goal, but saving a few words was no longer treated as success when those words carried essential responsibility.