12: Engineering Communication
- Page ID
- 142335
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)- 12.1: Communication Is Part of the Deliverable
- This page discusses the critical role of effective communication in engineering, emphasizing the necessity of thorough documentation for project completion and future verification. It highlights that clear documentation is vital for others to understand, build, or maintain the project, adhering to standards that require another competent engineer to evaluate the work based solely on the provided materials.
- 12.2: Three Modes of Communication
- This page discusses three key modes of engineering communication: technical memos, technical presentations, and professional emails/briefts. It highlights the use of technical memos for documenting analyses, technical presentations for conveying decisions to non-technical audiences, and professional emails for improving interactions in the course. Examples include the Cable Car memo and the TEGO case study, which illustrate these communication methods in action.
- 12.3: The Technical Memo
- This page provides a detailed overview of the structure and standards for a professional engineering memo, which consists of six essential sections: Purpose, Background, Methodology, Results, Analysis, and Conclusion. It emphasizes the need for clear writing and outlines common pitfalls and errors, such as vague statements and unlabeled graphs, while providing examples of both weak and strong writing to enhance communication of technical information effectively.
- 12.4: Complete Memo Example
- This page provides an annotated memo assessing the safety of a 330 Ω, 0.25 W resistor used in a 12 V DC circuit. It details the evaluation purpose, methodology, and findings, revealing that the calculated power dissipation (0.436 W) surpasses the resistor’s rating by 74%, posing overheating risks. The memo advises against using this resistor, recommending a minimum of 0.5 W rating or higher resistance for safety, and acknowledges the limitations of a steady-state analysis.
- 12.5: Quantitative Precision
- This page highlights the necessity of quantitative precision in engineering writing, emphasizing that claims should be verifiable with numerical evidence and appropriate units. It contrasts weak and strong assertions based on data support, underscores the correct use of significant figures, and warns against presenting numbers without units, labeling them as errors.
- 12.6: Graphs and Tables
- This page explains the appropriate use of tables and graphs for data presentation, favoring tables for exact values and graphs for trends. It emphasizes prioritizing patterns over precision in graphs and advises against using both formats for the same data unless justified. Further, it highlights the importance of adhering to specific requirements for graph presentations.
- 12.7: Technical Presentations
- This page emphasizes the significance of technical presentations in engineering, especially for assignments like the TEGO case study and PowerPoint Project. It outlines the differences between presentations and memos, highlighting the necessity of real-time delivery. The Five Core Rules for Engineering Presentations are introduced: utilize visuals, structure arguments first, tailor vocabulary to the audience, cite sources, and practice narration.
- 12.8: TEGO Case Study
- This page discusses the TEGO case study, which highlights the communication challenges engineers encounter when presenting solutions to non-technical decision-makers. It details how an engineer from a toy company responds to complaints about missing pieces in a toy set by creating a clear five-slide presentation.
- 12.9: Professional Email
- This page outlines conventions for professional emails in engineering, emphasizing their role as permanent records. It includes a sample email format that highlights the importance of specificity in subject lines and salutations, contextual information, and explicitly stated questions. The page advocates for detailing attempts and uncertainties instead of vague confusion, aiming to enhance communication effectiveness rather than restrict it.
- 12.10: Communicating Uncertainty and Limitations
- This page emphasizes the importance of communicating limitations in engineering analyses as essential for professional integrity and informed decision-making. It provides a standard format for limitation statements, examples of common limitations, and discusses the ethical implications of omitting such information. Clear communication is reinforced as vital throughout the engineering workflow, ensuring that all claims made are quantifiable and verifiable by others.
- 12.11: Summary
- This page emphasizes the critical role of communication in engineering, stating that undocumented work is incomplete. It details three communication modes: technical memos, presentations, and professional writing. A technical memo must have six sections and include accurate quantitative data. Effective presentation skills, including visual aids and suitable language, are essential.
- 12.12: End-of-Chapter Applied Exercises
- This page emphasizes applied exercises aimed at improving precision in technical writing and analysis. It includes tasks like clarifying vague statements, drafting memos on safety, effectively introducing graphs, revising conclusions, and email communication with instructors. The content encourages professionalism and enhances analytical thinking within engineering contexts.
Engineering Communication
Undocumented engineering is unfinished engineering. Communication is not the final step that can be abbreviated — it is part of the deliverable.
Learning Objectives
- Explain why communication is an integral part of the engineering deliverable, not a step that can be abbreviated.
- Structure a technical engineering memo using the standard six-section format.
- Write with quantitative precision: correct units, appropriate significant figures, and objective rather than vague language.
- Select between graphs and tables appropriately and explain the purpose of each.
- Construct a technical presentation for a non-technical audience.
- Apply the communication framework to the TEGO case study.
- Identify the five most common errors that undermine an engineering document's credibility.
- 12.1: Communication Is Part of the Deliverable
- This page discusses the critical role of effective communication in engineering, emphasizing the necessity of thorough documentation for project completion and future verification. It highlights that clear documentation is vital for others to understand, build, or maintain the project, adhering to standards that require another competent engineer to evaluate the work based solely on the provided materials.
- 12.2: Three Modes of Communication
- This page discusses three key modes of engineering communication: technical memos, technical presentations, and professional emails/briefts. It highlights the use of technical memos for documenting analyses, technical presentations for conveying decisions to non-technical audiences, and professional emails for improving interactions in the course. Examples include the Cable Car memo and the TEGO case study, which illustrate these communication methods in action.
- 12.3: The Technical Memo
- This page provides a detailed overview of the structure and standards for a professional engineering memo, which consists of six essential sections: Purpose, Background, Methodology, Results, Analysis, and Conclusion. It emphasizes the need for clear writing and outlines common pitfalls and errors, such as vague statements and unlabeled graphs, while providing examples of both weak and strong writing to enhance communication of technical information effectively.
- 12.4: Complete Memo Example
- This page provides an annotated memo assessing the safety of a 330 Ω, 0.25 W resistor used in a 12 V DC circuit. It details the evaluation purpose, methodology, and findings, revealing that the calculated power dissipation (0.436 W) surpasses the resistor’s rating by 74%, posing overheating risks. The memo advises against using this resistor, recommending a minimum of 0.5 W rating or higher resistance for safety, and acknowledges the limitations of a steady-state analysis.
- 12.5: Quantitative Precision
- This page highlights the necessity of quantitative precision in engineering writing, emphasizing that claims should be verifiable with numerical evidence and appropriate units. It contrasts weak and strong assertions based on data support, underscores the correct use of significant figures, and warns against presenting numbers without units, labeling them as errors.
- 12.6: Graphs and Tables
- This page explains the appropriate use of tables and graphs for data presentation, favoring tables for exact values and graphs for trends. It emphasizes prioritizing patterns over precision in graphs and advises against using both formats for the same data unless justified. Further, it highlights the importance of adhering to specific requirements for graph presentations.
- 12.7: Technical Presentations
- This page emphasizes the significance of technical presentations in engineering, especially for assignments like the TEGO case study and PowerPoint Project. It outlines the differences between presentations and memos, highlighting the necessity of real-time delivery. The Five Core Rules for Engineering Presentations are introduced: utilize visuals, structure arguments first, tailor vocabulary to the audience, cite sources, and practice narration.
- 12.8: TEGO Case Study
- This page discusses the TEGO case study, which highlights the communication challenges engineers encounter when presenting solutions to non-technical decision-makers. It details how an engineer from a toy company responds to complaints about missing pieces in a toy set by creating a clear five-slide presentation.
- 12.9: Professional Email
- This page outlines conventions for professional emails in engineering, emphasizing their role as permanent records. It includes a sample email format that highlights the importance of specificity in subject lines and salutations, contextual information, and explicitly stated questions. The page advocates for detailing attempts and uncertainties instead of vague confusion, aiming to enhance communication effectiveness rather than restrict it.
- 12.10: Communicating Uncertainty and Limitations
- This page emphasizes the importance of communicating limitations in engineering analyses as essential for professional integrity and informed decision-making. It provides a standard format for limitation statements, examples of common limitations, and discusses the ethical implications of omitting such information. Clear communication is reinforced as vital throughout the engineering workflow, ensuring that all claims made are quantifiable and verifiable by others.
- 12.11: Summary
- This page emphasizes the critical role of communication in engineering, stating that undocumented work is incomplete. It details three communication modes: technical memos, presentations, and professional writing. A technical memo must have six sections and include accurate quantitative data. Effective presentation skills, including visual aids and suitable language, are essential.
- 12.12: End-of-Chapter Applied Exercises
- This page emphasizes applied exercises aimed at improving precision in technical writing and analysis. It includes tasks like clarifying vague statements, drafting memos on safety, effectively introducing graphs, revising conclusions, and email communication with instructors. The content encourages professionalism and enhances analytical thinking within engineering contexts.