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:
So I’m starting a thing. Wish me luck. #blender3d #medieval #york #mysteryplay #corpuschr...
How to Disagree Academically: Using Graham's "Disagreement Hierarchy" to organize a colleg...
A.I. 'Completes' Keith Haring's Intentionally Unfinished Painting
Seton Hill students Emily Vohs, Elizabeth Burns, Jake Carnahan-Curcio and Carolyn Jerz in ...
“The Cowherd Who Became a Poet,” by James Baldwin. (Read by Dennis Jerz)
Dr. David von Schlichten honors the spectrum of motivations (not always financial) feature...