New graphic. First step in touching up my collection of pages on writing short technical reports.
A business memo, a lab report, or a professional e-mail are all variations on the basic report structure described in this document. Feel free to modify these guidelines in order to meet your reader’s needs.
- Think of Your Reader First
Your busy reader has a problem, and has turned to your report for help. What, exactly, does your reader want? Deliver it as efficiently as possible. - Begin with Your Conclusions
A technical document is not a mystery novel. Don’t save your best points for the end, because most readers are too impatient to wait. - Organize with Appropriate Headings
For any document longer than a page or two, break the content into sections (like introduction, background, discussion, and conclusion).
Similar:
Dr. David von Schlichten honors the spectrum of motivations (not always financial) feature...
Journalist flexes in story about Trump Media accountant who has spelled his own name 14 di...
NASA reconnects with Voyager 1 (after months of confusion)
Collegewide game encourages small interactions around campus
Surprise sidewalk encounter with my man Hopkins outside the Admin shuttle stop this mornin...
Shakespeare-themed Math Puzzles