One of the main points that Chapter 3: Readers and Context of Use stressed was the fact that different types of readers are looking for different things when reading. For example, the author states that the primary user is generally "raiding" the information for what they want. They are looking for the information required to make a decision or take action. Everything else just gets in the way. However if a manual is poorly written or written without consideration for readers other than the primary reader, the writer could get in trouble for writing something that is incorrect or not in line with what the supervisors want.
Determining who the reader is will be important when considering how to write something such as a help manual. By profiling what the reader's needs, wants and attitudes are a writer can better understand what their audience is looking for in a piece of writing. A writer targeting users looking for a simple how-to doesn't need to focus on high level theory. However if writing a scientific report targeted towards professionals with PhDs, the writer could assume the audience has some basic knowledge in regards to the content.
Chapter 3 also stresses the importance of considering the context of use of a piece of writing. Not only does the physical context of where the writing will be read need to be considered, but also the ethical, economical, and political context need to be considered as well. If for example a help manual only suggested an outrageously expensive solution the reader would be unlikely to try it. Instead they would go to another source looking for a cheaper solution.
Being aware of whom my readers are and the context my writing will be used in will be important in my future. I am currently planning on entering the Peace Corps. after college. In this occupation I might be called on to create how-to documents for people that have never used technology before. Therefore I would need to write differently than if I was writing a how-to document for a fellow colleague.
The concept of “raiding” a
The concept of “raiding” a document for information is an interesting way to consider how a reader may approach your documents. In thinking about it, I suppose that I also “raid” documents for the most important information and all the unnecessary fluff really just gets in my way. Writing for the primary reader and taking into consideration your other possible readers will most likely assist with making sure everyone is able to utilize a document to its full extent. The challenge, it would seem, is finding that balance between just enough fluff and just enough information to make everyone happy.
www.JFlitt.com
Response to "Raiding"
I thought the same thing about "raiding" documents. Reading that part of the chapter reminded me of how in a previous course I had to find a solution to a problem. My group spent a long time searching the Microsoft website for solutions. If you've ever had to do that before you know how some of the solutions come easy and others require an abundant amount of searching. We finally found our solution. It was buried deep in a document that was well over 80 pages. While this may be a little extreme I’m sure there are many other times where we have all been searching with Google for an answer and have had to weed through many pages of things that we didn’t want till we got to what we were looking for. Keeping in mind what a reader may be looking for and how you present your information will definitely help your readers.
-Chris
Response
In looking back at this chapter, I personally discovered that “Developing a Reader Profile” is a vital section. In asking about the Five-W, the guidelines the chapter drills you with are very useful. I agree that it’s important when writing a technical document to present the information at hand to the reader.
I can’t count the number of times where I have found myself “raiding” a technical document. Although this guideline is insightful, the other four guidelines have just as much importance as this one. I think guideline number two should be one of the first questions you should ask yourself when building a reader profile
Reply to Beachside32
Thank you Beachside32 for more fully bringing the second guideline to my attention. When reading the guidelines, I read and understood the first guideline, and then I became a "raider" myself and skimmed the rest of them. In my reading response I stated that I believe the first guideline is the most important also, but mainly because I didn't fully read the rest of them. After reading all of them, they seem to all go hand-in-hand with one another. All together, the five guidelines explain that readers like short, to-the-point text with assisting pictures and graphs. Then, when the reader is raiding, they will look at most or all of the imformation because there aren't lengthy paragraphs to scare the reader away.
Third Paragraph
I like the point you made on the third paragraph. You mention that not only should the physical context be considered when writing, but the ethical, economical, and political. This something in the chapter that I didn't respond to, but its important. You have to remember that people have different standards, whether it be manners, cost of living, etc. This is something that will be important for you especially. Good luck with the peace core!
Evan White