I'm going to try using this style in status reports.
"Notice the almost reverse order of these points in comparison with the common reporting style in which team members start with a long explanation of why things went wrong." [permalink]