Presentation is loading. Please wait.

Presentation is loading. Please wait.

Technical Communication. Objectives  Show why engineers need to know how communicate  Identify how technical communication is different from high school.

Similar presentations


Presentation on theme: "Technical Communication. Objectives  Show why engineers need to know how communicate  Identify how technical communication is different from high school."— Presentation transcript:

1 Technical Communication

2 Objectives  Show why engineers need to know how communicate  Identify how technical communication is different from high school writing  Identify what makes a good technical report or presentation Rev: 20140827, NAO Technical Communication2

3 What is technical communication?  Laboratory reports and memos  Journal papers  Guides & Manuals  Proposals  Patents  Specifications  Progress and design reports ..and more! Technical Communication3 Rev: 20140827, NAO

4 Technical Communication is Different High School Writing  Expository  Double spaced  Essay format  Descriptive  Length requirement Technical Communication  Informative  Often single spaced  Professional format  Concise and precise  Short is preferred Technical Communication4 Rev: 20140827, NAO

5 Why do engineers need to communicate? Living in a “sound bite” world, engineers must learn to communicate effectively … If we place our trust solely in the primacy of logic and technical skills, we will lose the contest for the public’s attention—and in the end, both the public and the engineer will be the loser. -Norman Augustine, chair of the Human Space Flight Committee Technical Communication5 Rev: 20140827, NAO

6 Questions to ask while preparing  What is my goal?  Who is my audience?  What are the limitations of my medium?  How can I reduce the “noise”? Technical Communication6 Rev: 20140827, NAO

7 What is your goal?  Inform (Provide)  Request (Obtain)  Instruct (Give)  Propose (Suggest)  Recommend (Suggest)  Persuade (Convince)  Record (Document) Technical Communication7 Rev: 20140827, NAO

8 Who is your audience?  Am I delivering the information my audience wants? How much detail should I provide? What level of technical vocabulary is appropriate? Technical Communication8 Rev: 20140827, NAO

9 Limitations of your medium  Written vs. oral communication  Abstract/executive summary vs. memo vs. report  Specifications from audience Technical Communication9 Rev: 20140827, NAO

10 Reducing the “noise”  Write or speak clearly and concisely  Identify facts vs. opinions  Use the specified format If unspecified, choose a common format  Use appropriate spelling and grammar Technical Communication10 Rev: 20140827, NAO

11 Reducing Noise: Writing concisely  Using too many words Many have made the wise observation that when a stone is in motion rolling down a hill or incline that that moving stone is not as likely to be covered all over with the kind of thick green moss that grows on stationary unmoving things and becomes a nuisance and suggests that those things haven’t moved in a long time and probably won’t move any time soon. Technical Communication11 Rev: 20140827, NAO

12 Reducing Noise: Writing concisely  Using just enough words A rolling stone gathers no moss. Technical Communication12 Rev: 20140827, NAO

13 Reducing Noise: Writing concisely  Using showy words I am waiting for class to commence. I am waiting for class to start. It is essential that the gauge be cleaned at frequent intervals. Clean the gauge frequently. Technical Communication13 Rev: 20140827, NAO

14 Reducing Noise: Writing Clearly  Ambiguity  Good paragraph use  Sections and subsections  Bullets Technical Communication14 Rev: 20140827, NAO

15 Reducing Noise: Presenting Clearly  I can read this (32 pt.) I can read this, too (28 pt.)  We are getting small, but still readable (24 pt.)  This is getting too small to read (20 pt.)  Please be kind to your audience (16 pt.)  Don’t go below 20 point font (12 pt.) Technical Communication15 Rev: 20140827, NAO

16 Reducing Noise: Presenting Clearly  Don’t blind your audience. Technical Communication16 Bad Idea Good Idea Bad Idea Good Idea Rev: 20140827, NAO

17 Reducing Noise: Presenting Clearly  Watch size and complexity of figures and tables.  Use few words. Technical Communication17 Rev: 20140827, NAO

18 Reducing Noise: Presenting Clearly? Technical Communication18 Rev: 20140827, NAO X

19 Reducing Noise: Presenting Clearly? Technical Communication19 Rev: 20140827, NAO X

20 Reducing Noise: Presenting Clearly  Know your slides  Test the AV equipment beforehand  Speak to the audience  Be aware of your movement  Practice, practice, practice! Technical Communication20 Rev: 20140827, NAO

21 A Little Poem Regarding Computer Spell Checkers... Eye halve a spelling chequer It came with my pea sea It plainly marques four my revue Miss steaks eye kin knot sea. Eye strike a key and type a word And weight four it two say Weather eye am wrong oar write It shows me strait a weigh. As soon as a mist ache is maid It nose bee fore two long And eye can put the error rite Its rare lea ever wrong. Eye have run this poem threw it I am shore your pleased two no Its letter perfect awl the weigh My chequer tolled me sew. Technical Communication21 Rev: 20140827, NAO

22 Photos should…  Be clear with good contrast  Only include necessary equipment  Indicate scale Technical Communication22 Rev: 20140827, NAO

23 Cold Technical Communication23 Rev: 20140827, NAO

24 Getting warmer… Technical Communication24 Rev: 20140827, NAO

25 Warmer still… Technical Communication25 Rev: 20140827, NAO

26 Hot Technical Communication26 Rev: 20140827, NAO

27 Executive Summaries  Problem or objectives statement  Lab procedure  Results  Obstacles and solutions  Improvements  Attachments Technical Communication27 Rev: 20140827, NAO

28 Lab Memos  Heading  Introduction  Results  Conclusion and Recommendation  Appendix Technical Communication28 Rev: 20140827, NAO

29 Lab Reports  Title Page  Table of Contents  List of Figures and Tables  Executive Summary  Introduction  Results  Conclusion  References  Appendix Technical Communication27 Rev: 20140827, NAO

30 Report and Memo Resources  On Website See Technical Communication Guide  Instructional staff, especially GTAs Technical Communication30 Rev: 20140827, NAO

31 Rubrics: General Technical Communication31 https://eeiccourses.engineering.osu.edu/sites/eeiccourses.engineering.osu.edu/fil es/uploads/1182/AEVLab/AEVDocuments/LabGuidelines/AEV_Lab_Guidelines_R ev_2014-08-21.pdf Rev: 20140827, NAO  Check AEV Lab Guidelines at:

32 Questions?  Technical writing  Technical presentations  Lab reports and memos Technical Communication32 Rev: 20140827, NAO


Download ppt "Technical Communication. Objectives  Show why engineers need to know how communicate  Identify how technical communication is different from high school."

Similar presentations


Ads by Google