ENGL-2333RTechnical Writing I

Technical Communications - Ninth Edition

Lannon, John M.

Chapter 1 - Introduction to Technical Communications

1. Technical Communication Server Practical Needs
   1. Technical Documents Are User Oriented
      1. Technical documents do not focus on self-expression
         1. They do not focus on you personally
         2. They may focus on your knowledge
      2. Technical Documents focus on subjects, actions taken and actions required
   2. Technical Documents Strive for Efficiency
      1. Efficiency is measured as useful output to input (how much effort did you have to put in to getting the information out?)
      2. Reasons for inefficient documents are many:
         1. More (or less information that needed)
         2. Irrelevant or uninterrupted information
         3. Confusing organization
         4. Jargon or technical expressions people cannot understand
         5. More words than people need
         6. Uninviting appearance, confusing layout
         7. No visual aids when people need or expect them
      3. Efficient documents
         1. Content worth reading
         2. Organization that guides user
         3. Style the promotes fluid reading
         4. visuals that clarify concepts
         5. Acceptable format
         6. Supplements that allow users with needs to meet them.
2. Writing Is Part of Most Careers
   1. You may have to collaborate on a team
   2. You will write for the audience that will be reading your documents
3, Communication Has an Electronic and a Human Side
   1. Communication has been made quicker and easier by computers
   2. They still consist of written communications
4. Communication Reaches a Global Audience
   1. Writers must learn to respect language and cultural differences
   2. They must achieve efficiency without being offensive
5. In Brief: Transferable Skills for the Twenty-First Century
6. Exercises
7. Collaborative Project
8. Service-Learning Project