Thursday, August 28, 2008

Process as Well as Product 1-49

As I read this selection, I couldn't help but think about how some students associate intelligence and "good" writing with the use of long, convoluted words to make "deep" (ambiguous) points or compositions. However, technical writing is not about showcasing the writer's talent, brain capacity, or prowess using a thesaurus, but enabling the audience to accomplish a goal or simply react in some way. The more I read into the text, I even began to question my own work. How effective was my thesis proposal? If someone had to replicate my study, could he or she? Is the message of my document clear and significant?

I also realized that coming into the MAPC program, I was one of those people with "flowery" writing. Another name for this style is writer-based prose. I believe that I wrote this way as opposed to concentrating on the audience for two reasons: habit and too much worrying and not enough planning and revising. I also was never one to simply "put words on paper" because I'd always assumed that I would remember all my thoughts and would have to go back and erase all the bad ones.

On another note, I fully intend to utilize the PAFEO steps and the project worksheet in many of the projects I assume. I also noticed how effective headings and document format are in aiding clarity. Although these suggestions seem very obvious, these are the very mistakes that many people, including myself, carelessly make.

Tuesday, August 26, 2008

Project Brainstorming

I am considering working on a project for a travel agency in Greenville. Last year during the homecoming festivities, I met the owner of this company, and he suggested that I contact him about possibly writing a grant for him. Although I have neither seen nor spoken to him since last October, I would like to take him up on his offer. Moreover, he mentioned that he knew several people around Greenville who he could possibly introduce to me. I see this prospect as a great way to start on my project while also networking within the technical writing community.

Another idea I have considered is doing some volunteer writing/work for local non-profit organizations around Virginia. Since I plan to move back there after I graduate, it would be a great idea for me to start meeting people in that area and get experience to build my resume.

Lastly, I randomly met this older gentleman at my parents' church who said he may be interested in hiring me for some contract work. It would be wonderful if I could contact him about my project and get paid for working at the same time.

Monday, August 25, 2008

D.A. Winsor Response

Reading this selection enabled me to analyze the Challenger disaster from three different perspectives. Certainly, it emphasizes the need for and importance of professional communicators and clarity in writing. Yet, Winsor's text suggests that communication is more than merely word placement and crafting sentences; rather, it greatly entails arranging a message that carefully considers the speaker, audience, and text by employing ethos, logos, and pathos at the appropriate time. Specifically, when the engineers wrote the reports, they did not consider the fact that their superiors were not themselves engineers and did not understand the true meaning within the message. Hence, the upper management concluded that nothing in the reports was terribly out of the ordinary and made the unfortunate decision to proceed with the launch.

Secondly, the entire communication process, or lack thereof, exposes a major ethical problem within this scenario. Not only were the conversations and documents too technical, which obscured the message, but they were also misleading. In her article, "Communication Failures Contributing to the Challenger Accident: An Example for Technical Communicators", Winsor stresses that the messages that reached the upper management had an "optimistic view" of the problem (104). Compounded with fact that the reports did not make practical sense, the managers were deceived about the potential danger of the operation. Instead of being forthright and going against their better judgment, many people involved chose to simply ignore the problem or avoid confronting the managers and making themselves look badly.

Lastly, the only letter that portrayed any sense of urgency was Roger Boisjoly's. In comparison to Brian Russell's, Boisjoly's letter uses language indicative of the severity of the problem such as "mistakenly", "catastrophe", and "loss of human life"(104). One the other hand, Russell's letter is organized in a question and answer format. The immediate impressions from this format, and even the way that he numbered the letter, could have implied two false notions: 1) Any potential questions that had been raised must have had a logical answer that the engineers already resolved, and 2) there are only two questions pertaining to the problematic secondary seals, so the issue could not have been that dangerous. Obviously these possible responses to his message were not what Russell intended. Yet, without even reading the letter, the style of this letter alone could lead an unfamiliar audience to make these possible assumptions. Russell's letter uses terms such as "squeeze", "no reason...ever fail", and "guaranteed" (105). Although his letter tried to voice the same concerns as Boisjoly's, Russell used words that seemed to downplay the severity of the matter. Even the subject titles for these two letters signal two different meanings.

Although both letters were intended to articulate the same concern, Boisjoly's used rhetorical strategy to communicate a more effective message. The biggest mistake he made, however, was in labeling the correspondence as "COMPANY PRIVATE", which kept the letter from reaching the audience that needed it the most.