The candid report

Most organisational reports are written to be survivable rather than true. This is not because the authors are dishonest. It is because a candid report has a predictable set of consequences and a vague one does not.

The mechanics are easy to trace. A report that says the project is behind invites questions about who is responsible. A report that says the project faces some challenges invites nothing. Both authors know the project is behind. Only one of them has to spend the following week in meetings.

Over time this produces a documented record that is systematically more optimistic than reality, and the gap grows with the number of layers the report passes through. Each layer softens slightly, reasonably, and the softening compounds. By the time the account reaches whoever decides, a serious problem can read as a minor delay. No single person lied.

Organisations that avoid this do a small number of specific things. They separate the report of facts from the judgement about blame, often by writing them at different times. They ask for a number rather than an adjective, because 'behind' can be softened and 'eleven days behind' cannot. And they make a habit of rewarding the first person to report bad news, which sounds sentimental and is the only mechanism that reliably works, because the alternative is that the first reporter is punished and the second learns from watching.

The test of whether an organisation has managed this is not whether its reports are positive. It is how quickly bad news travels upward compared with good.