I decided to go for the topic of common mistakes in technical writing. For these sources, I've mostly found solutions but I plan to dive deeper into finding problems from peer reviewed sources rather than random lists found on google to get a starting point.
Annett, C. H. (1982). An Editor’s View: Ten Common Errors in Technical Writing. Journal of Technical Writing and Communication, 12(3), 185-190. https://doi-org.libproxy.utahtech.edu/10.2190/W558-WV3D-F1P6-HXMD
Campbell, K. S., Naidoo, J. S., & Smith, J. (2021). When Your Boss Says, “You Need to Sound More Professional”: Writing Style and Writer Attributions. International Journal of Business Communication, 60(4), 1071-1094. https://doi-org.libproxy.utahtech.edu/10.1177/23294884211025735
Edens, B. (1980). Readability and Creativity in Technical Writing. Journal of Technical Writing and Communication, 10(4), 329-336. https://doi-org.libproxy.utahtech.edu/10.2190/FDXC-J28W-GLC1-CCUN
NOTE: CANNOT FIND FULL ACCESS THROUGH SAGE. ASK PROF ABOUT IT.
Fallahi, C. R., Wood, R. M., Austad, C. S., & Fallahi, H. (2006). A Program for Improving Undergraduate Psychology Students’ Basic Writing Skills. Teaching of Psychology, 33(3), 171-175. https://doi-org.libproxy.utahtech.edu/10.1207/s15328023top3303_3
Garwood, K. (2013). Metonymy and Plain Language. Journal of Technical Writing and Communication, 43(2), 165-180. https://doi-org.libproxy.utahtech.edu/10.2190/TW.43.2.d
MacKiewicz, J. (2004). What Technical Writing Students Should Know about Typeface Personality. Journal of Technical Writing and Communication, 34(1), 113-131. https://doi-org.libproxy.utahtech.edu/10.2190/NMDQ-XBVH-Q79J-M749
Sharon, A. J., & Baram-Tsabari, A. (2013). Measuring mumbo jumbo: A preliminary quantification of the use of jargon in science communication. Public Understanding of Science, 23(5), 528-546. https://doi-org.libproxy.utahtech.edu/10.1177/0963662512469916
This is such an interesting topic, and not at all the direction I thought you were going. I like the idea of being able to find common mistakes while providing the solution. I think you could take this to the next level by l looking at doing a case study where you can use students work (a sample) and find what mistakes they are making. Maybe one or two classes, multiple assignments and/or emails, editing, and coding the most common mistakes. If you ask, you will get generic answers, and it wouldn’t benefit the research, but I totally understand that’s a large undertaking. Your sources are strong which will make for a great lit review that tells a story while giving you the cut and dry answers you are looking for in making a guide. I am interested to see what comes of this!
ReplyDeleteBrief revision plan: The biggest thing I think I should improve is the applicability of the sources. I know that I could potentially make all of them suit my needs based on the information I read, but I just know there's better sources out there. I think that the biggest detrimental factor was that I mainly stayed within one journal. I think that looking more into business geared technical writing journals (Journal of Business and Technical Communication and Business and Professional Communication Quarterly, for example) will give me more sources on what NOT to do rather than what is good to remember, like what I have here. From there, I can build a proposal for this basic guide to common mistakes and how to avoid them by using official, peer-reviewed sources to point out both common mistakes and offer some solutions.
ReplyDeleteI also think I should shift focus just a little bit. This basic list really only covers things that are good to do and remember. There is only one source that highlights common mistakes, and that source is from 1982. There's got to be more relevant articles out there, maybe talking about common mistakes in technical writing research? I plan to look deeper and go beyond just one journal in the next week or so to add more credibility to my future claims.
Hi Frances,
ReplyDeleteLooks like you had a good start on your sources! I am very pleased to know that your topic interest is a bit more distilled at this point and, as you plow through and annotate these sources, I suspect you'll gain an even tighter focus leading toward your proposal.
It's always our goal as scholars to make a study more beneficial and applicable to practitioners within our field. Your blog post so far is very interesting and Merika's suggestion about designing a case study for your proposal regarding this topic seems rife with possibilities. :)
I like that you plan on expanding your search to our TWDR journals -- keep it up! BTW, if you found a good journal article and our Utah Tech does not have an e-copy for download, our library's Interlibrary Loan is your friend. =))
Please don't hesistate to set a quick Zoom appt. with me to go over your plans, ok? This way, I can help you up and running with your focus to be on the right track... am here. :)
Keep up the good work!
Best,
Dr. B