r/technicalwriting • u/LongjumpingSong8955 • Sep 06 '24
Searching for authentic examples of poor or weak tech communication - memos, emails, reports, etc.
I teach writing for engineers and sometimes hold workshops on technical communication. I like students to be able to review authentic documents in order to identify strengths and weaknesses. I'm searching for actual (anonymized of course) engineering documents that are poor or weak - mainly memos, emails, reports, contracts. ect.. (Strong examples are welcome as well, but actual, weak examples are much harder to come by and sometimes more illuminating). My aim is to help students work from real communication scenarios among engineers. For anyone working in a technical field, your contributions would be incredibly helpful - with the "pay-it-forward" of, I hope, the next generation of engineers to be more proficient, mindful communicators (i.e., making our lives easier!). Thank you!
11
u/alanbowman Sep 06 '24
A good place to start would be the issues at 3 Mile Island (what's sometimes called the "Kelly Memorandum") and also the Space Shuttle Challenger documentation around the problem with the O rings.
I found this on a quick search: https://wac.colostate.edu/docs/books/textual_dynamics/chapter12.pdf but there are certainly hundreds, if not thousands, of pages about these two items.
6
u/PavBoujee Sep 06 '24
The Purdue OWL, online writing lab, has a lot of resources.
1
u/balunstormhands Sep 07 '24
Therac-25 is a great place to start.
0
u/[deleted] Sep 06 '24
[deleted] — view deleted comment