Every so often, I am called upon to cast a critical eye over my colleagues’ work.
Admittedly, report-writing isn’t an easy skill to master, but as long as you keep things simple and factual, you should get your point across. Unfortunately, several of my co-workers appear to believe that a real technical report should be as bafflingly opaque as possible.
I suspect that this is a direct consequence of their own experience with poorly-written documents and their efforts are simply an attempt to copy the style. As a result, a kind of report-writing cargo cult has evolved and I am regularly exposed to impenetrable examples of WTF such as the following:
…this document is to cover and address the capacity, including primary and secondary short-comings, with over-all network functionality assessment from a capacity point of view, and take into the alternative upgrades on the bulk reticulation can only be commented on until we receive the report…
We’d be better off employing spambots.