How to Write a Report Without Getting Lynched

You put forth your best effort to explain to the stupid sods exactly how and where they screwed up, then they have the temerity to not appreciate your fine efforts. Here's how to write a report that will cause change, instead of uproar.

Tognazzini, Bruce. Nielsen Norman Group (2001). Articles>Usability>Reports>Technical Writing

Review: Reporting Technical Information  

When I first picked up Reporting Technical Information, I thought from the title it was going to be a primer on writing technical reports. Instead, this book turned out to be a basic, though somewhat better than average, textbook on technical writing.

Coleman, Colleen. Technical Communication Online (2002). Articles>Reviews>Reports>Technical Writing

Some Advice on Writing a Technical Report

The Technical Report (TR) is a common written form through which computer scientist communicate their findings. Each TR should have a focused topic that is developed logically along some clearly identified perspective. The major components of a TR are title, author information, date, keywords, informative abstract, body, acknowledgments, references, and appendices. Typically, the body is organized into four sections: motivation, methods, results, and discussion. This document offers advice and specifications for writing TRs.

Sherman, Alan T. UMBC (1996). Articles>Writing>Reports>Technical Writing

Some Advice on Writing a Technical Report

The Technical Report (TR) is a common written form through which computer scientist communicate their findings. Each TR should have a focused topic that is developed logically along some clearly identified perspective. The major components of a TR are title, author information, date, keywords, informative abstract, body, acknowledgments, references, and appendices. Typically, the body is organized into four sections: motivation, methods, results, and discussion. This document offers advice and specifications for writing TRs.

Sherman, Alan T. UMBC (1996). Articles>Writing>Reports>Technical Writing

A Structured Process for Transforming Usability Data into Usability Information  

Much research has been devoted to developing usability evaluation methods that are used in evaluating interaction designs. More recently, however, research has shifted away from evaluation methods and comparisons of evaluation methods to issues of how to use the raw usability data generated by these methods. Associated with this focus is the assumption that the transformation of the raw usability data into usability information is relatively straightforward. We would argue that this assumption is incorrect, especially for novice usability practitioners. In this article, we present a structured process for transforming raw usability data into usability information that is based on a new way of thinking about usability problem data. The results of a study of this structured process indicate that it helps improve the effectiveness of novice usability practitioners.

Howarth, Jonathan, Terence S. Andre and Rex Hartson. Journal of Usability Studies (2007). Articles>Usability>Reports>Technical Writing

Technical Reports for Quick Reader Comprehension  

A technique to conserve the time of scientists and engineers in report preparation, assure prompt reporting, and provide reports that meet user needs.

DITA Users (1961). Articles>Writing>Technical Writing>Reports