cdmandrews.github.io

ENGL 3301, Spring 2021

Project 2: Report on TPW

Below is my video overview for the project, but you must still read this page completely.

We started out this semester by asking the question, “What is technical and professional writing?” In your first project, you started to answer this question by surveying and examining the types of writing that actually happen in your prospective fields and professions. Put differently, project one was all about naming the various kinds of writing in your field. However, it’s important for us as writers to move beyond simply being aware of the kinds of writing we are likely to encounter as we continue to develop as professionals-who-write; we also need to understand how to produce technical documentation that is effective, and we need to have at least a working understanding of why some writing is effective and others are not. In other words, in order to become producers of effective technical documentation we need to be able to answer the following questions: What makes technical writing good in my field? And what do I, as a professional-who-writes, have to do in order to produce it? These two questions are the driving force behind writing project two.

Importantly, those two questions aren’t only relevant to the workplace. As we’ve talked about throughout the semester, technical communication is everywhere, and is sponsored by individuals and communities outside of official organizations just as much as it is sponsored by workplaces and institutions. With that in mind, you have **two directions you can choose from for this project:

  1. Do a “deep dive” on three professional genres that you feel are particularly pertinent for your field or professional goals.
  2. Do a “deep dive” on user-created technical communication related to a non-work activity you participate in or are interested in.

The end result for either option will be similar: you’ll write a report on your research findings, translating the primary and secondary research you’ll do into a coherent set of claims about what constitutes “good” technical writing. You’ll also need to address things that writers must do in order to produce effective technical documentation in the context you’ve identified, whether it’s a workplace, a profession, or a hobbyist subreddit.

You might think of your audience for this report in a couple of ways, and any one of these will be a good audience for your report:

Option 1: Deep Dive on three professional genres

This option picks up where we left off with project 1. Choose three (3) types of technical writing that you identified in your fact sheets and that you feel are particularly pertinent for your field or professional goals. There is no set criteria for which three documents you should choose; however, you must be able to provide a justification or rationale for why you selected the three genres you did. (e.g. You might argue that you selected the genres that you did because they are the most common in your field, or perhaps they are the genres that carry the most professional capital, etc).

After selecting three (3) genres that will provide the focus of your project two research, you will then need to locate actual examples of this type of writing from your field. These need to be real documents, not hypotheticals or template forms that you pull off the internet.

For obvious reasons, many workplace documents are protected or private. For example, patients are protected by HIPAA, which means their records and information are protected from disclosure. Recent police reports, PSIRs, or forensic reports may technically be part of the public record, but that doesn’t mean they’re easily findable on the internet. Engineering and scientific firms often keep proprietary information closely private and protected. While I would not simply say “give up looking,” if you’re not networked with a professional or have professional experience as an employee, volunteer, or intern, these kinds of private, confidential, or proprietary documents will be very difficult to get hold of. Thankfully, there are many other places you could look–if you’re stuck in this area, contact Dr. Andrews and he’ll help you out!

As well as locating three documents, you must also conduct research (both primary and secondary) into what makes these documents effective. You have many points of entry into your research here since, as part of project one, you’ve already started to identify the rhetorical aspects of professional writing in your field. Project 2 is an opportunity to go into more depth and detail and examine not just what these elements are but how they function to create effective documentation. Your research should reference our course readings. You should also rely on Chapter Five: “Writing in Genres” in Adam Pope’s Open Technical Writing textbook. In addition, you will need to conduct independent research (from academic and professional journals) to supplement and extend our course materials. Remember, you are researching what makes this piece of technical communication good and what technical writers have to do in order to produce it.

You will coalesce your research into a report that makes a series of claims about what constitutes “good” technical writing in your field and how writers produce it

Option 2: Deep Dive on three examples of tactical technical communication

In this option you will explore technical communication “as a broad human activity used to effect change in the world” (Kimball 2017, p 347), specifically technical communication created voluntarily by users (what Kimball calls tactical technical communication). Your goal here is to understand the ways people use and create technical communication in their everyday lives.

Think about the various activities you do, personal hobbies you have, or things that you’re just kind of nerdy about: cooking, fishing, gardening, parenting, woodworking, Skyrim, motorcycle repair, low-impact camping, or a whole host of activist and advocacy activities. After you’ve decided on the activity you’re going to explore, you will need to locate three (or more) user-created documents centered around that activity.

(For example, since I own a Shopsmith woodworking system, I might use the Shopsmith subreddit, an online discussion forum, and this user-written “Buying a used Shopsmith” manual, which are all user-generated technical discussions of the tool, or “tactical” technical communication. I would not use the official Shopsmith manual or offical Shopsmith Facebook page–these are examples of institutional, or strategic technical communication. Read more about tactical versus strategic technical communication.

As well as locating three documents, you must also conduct research (both primary and secondary) into what makes these documents effective. There is tons of research out there about user-generated technical communication, about the various technologies that are used in creating it, and the kinds of communities that use it. Your research should reference our course readings. You should also rely on Miles Kimball’s 2017 article “The Golden Age of Technical Communication” (JTWC 47.3) as a jumping-off point. *You’ll mostly want to focus on his discussions of tactical technical communication. In addition, you will need to conduct independent research (from academic and professional journals) to supplement and extend our course materials. Remember you are researching what makes these kinds of writing technical communication and what makes them good, useful, or interesting.

You will coalesce your research into a report that makes a series of claims about what makes this stuff technical communication, what interesting features typify it, and even what possibilities it presents for technical communicators inside and outside the workplace.

Requirements (same for both options)

When in doubt: Email your professor. He loves it. It gives him validation. It makes him feel needed and wanted, like a fuzzy puppy.

Writers of all abilities and experience levels can benefit from appointments with a Writing Consultant in the CASA Writing Center. Formatting, spelling, and grammatical errors can make your documents difficult to read and understand or can undermine your content.