This week, we’re continuing our general introduction to TPW by taking a broad view and considering rhetoric as a foundational set of concepts for our work this semester. Again, like last week, these concepts are important, and we’ll come back to them again and again for the entire semester. Starting next week, we will begin exploring some particular strategies that technical writers use to make documents rhetorical, accessible, and readable for their audiences. Some of the stuff below gets a little heady, so as Downs notes in the chapter I’ve assigned to read, “buckle up!” Obviously we can’t understand everything we need to know about rhetoric in one week, but we can do just enough to be dangerous, and that’s okay with me for now.
Assigned to read this week:
First of all, what IS rhetoric?
Downs posits that “[r]hetoric refers both to such principles of meaning-making, and to the use of those principles in a given interaction” (p. 459). This broadly constructed definition suggests that rhetoric:
I was originally planning to wax really (really (really)) long and introduce the foundations of rhetoric in 5th century BC Greece, but decided that would get us pretty far away from what we are doing. Instead, I want to start with the idea that technical and professional writing is rhetorical. One traditional model of communication you may have learned about is the “conduit” or “linear” model. (See Figure 1).
In this model, the sender simply packages their content and sends it via some channel to a reciever, no muss or fuss unless a little noise, or interference, gets in the way. (Maybe that’s literal background noise, like radio chatter while you’re trying to talk to someone on that channel, or maybe it’s email problems on one or the other person’s end, etc.) That’s a gross oversimplification of communication and the model has a number of limitations. Messages aren’t just passed from sender to receiver; we must interpret and decode information at the very least. The model also doesn’t take into account senders’ and receivers’ different backgrounds and contexts. Finally, as anyone on Instagram should know, communication doesn’t go in only one direction; it’s a dynamic, multidirectional process. It changes all the time, and people talk back-and-forth with one another, interrupt, overhear, and so on.
A more dynamic model of communication is captured with the “transactional” model. (Lucky you, I’ve skipped a bunch of models in the middle!). Transactional models, though still an oversimplification, account for many of the weaknesses I just pointed out (see Figure 2). Most importantly, unlike the one-way transmission of information from an active sender to a passive receiver in the conduit model, communication from a transactional perspective is a cooperative. Communicators interact to create meanings and share knowledge; meaning is shared, and the various backgrounds, contexts, and environments of each communicator in the situation need to be accounted for as major factors impinging on understanding.
Also important is the role of a shared environment or context (some communication scholars would refer to this as a “field of experience”). Downs’s sections about motivation, knowledge-making, and identification will help you think about the ways relationships between all the various rhetorical agents (human and nonhuman) are part of a rhetorical conception of communication.
Okay, let’s bring this back to TPW. Because it’s the lifeblood of groups and organizations from large to small, technical and professional writing plays an important role in the construction of knowledge and meaning. (If you haven't read the Downs chapter yet, best go do that now before I lose you!)
Since knowledge is constructed, “knowing” and with it “passing along information” are trickier business than we might otherwise presume. Often people think about professional writing along the lines of that conduit model of communication. Writers can create knowledge in readers simply by exposing their audience to an idea. I simply write it down, send it out, and people read and then know it. Right? Right? Wrong.
This is a poor model of communication primarily because it presumes audience members are just passive recipients of information. Sharing evidence does not simply translate to shared knowledge. For examples, we only have to look around at our widespread problems with disinformation and conspiracy theories in 2021. With conspiracy theorists in particular, the very nature of evidence and fact are brought into question, and if people have different ideas about the very basis of any argument: what counts as evidence of a phenomenon, well then there’s really little chance for shared knowledge (that is, persuasion) to occur.
Data and evidence are not simply valid because they exist–they are perceived as valid by an audience. Or they are perceived as invalid, or limited, or problematic, etc. Because audiences vary in their assumptions, evidence that is valid for one group is invalid for another. Or, if you present valid data the wrong way or in a way that the audience won’t recognize, you might as well have presented invalid data. The fact of social construction theory is that the people with power in any group decide what gets to count as knowledge, as effective data presentation, and as validity and rigor.
We therefore cannot simply think of technical and professional writing as an objective transportation device for information, as something that gives “just the facts” without any interference from style or attention or delivery. It’s always an angle, a perspective, a snapshot, and the audiences always have their own angle, their own perspective, their own snapshot, their own agenda. Rhetoric and persuasion are at the very heart of what we’re doing. Good technical writing, in the words of Carolyn Miller, “becomes, rather than the revelation of absolute reality, a persuasive version of experience” (1979, p 616).
Complete the "1.5: Rhetoric, ecology, and other conceptual foundations" discussion thread in your group before 5:00 pm on Tuesday. You do not need to post or link to an external document for this assignment–just post replies directly to the discussion thread.
Collaborate with your group to collect and post definitions of key terms from the reading, listed below. These are definitions you’ll be able to return to and throughout the semester, so it’s important we’re on the same page with them! You may copy and paste definitions from the text, but must also paraphrase them and put them in your own words.
This is a collaborative activity—work with the people in your group to divide and conquer the assignment. Assign each person in the group a different term or pair of terms. It’s okay if you double up some, but each person should have something different to post.
The terms and concepts your group needs to define:
You should also include with your definition a short reaction to Downs’ chapter. What was interesting, confusing, or enlightening? How do you understand rhetoric differently now than you did before?
Complete the "1.6: Yet more Rhetorical Foundations" discussion thread in your group before 5:00 pm on Thursday.
Look back at those six qualities of rhetoric again (Downs, p. 480). If something is rhetorical, it is:
For this post, go back to any two of your examples of TPW you’ve looked at over the previous three weeks, something from any of the assignments you already posted. Use these six qualities and any other relevant terms from the reading you’re interested in to explain how those texts are rhetorical. What does it mean that the document is rhetorical–and how does looking at it through this lens change how you think about it now versus when you might have looked at it before?
Then go in and respond to your peers’ posts. Discuss, compare notes, and share ideas.