<node id="57663">
  <nid>57663</nid>
  <type>news</type>
  <uid>
    <user id="27279"><![CDATA[27279]]></user>
  </uid>
  <created>1004576400</created>
  <changed>1475895995</changed>
  <title><![CDATA[Shop Talk 101: Integrating workplace communication into undergraduate engineering curricula]]></title>
  <body><![CDATA[<p><strong>Why are communication skills more important than ever for engineers?</strong> First, in today's workplace, engineers increasingly interact with non-engineers such as marketing and call center personnel, their CTOs and their CEOs. Second, technological communication tools have become central to engineering work. The new tools, which recent graduates are often assumed to know, include various e-mail systems, Microsoft Office, Microsoft Project and Access. Third, practicing engineers are increasingly responsible for their own communication, including wordsmithing and proofreading that was once done by secretaries. Fourth, practicing engineers interact with others person-to-person in meetings. The advent of office technology has not erased the need for personal communication as some once predicted. If anything, office technology has increased the need and opportunities for personal communication.
</p>
<p>Appearing in <a href="http://www.news-info.gatech.edu/" target="_blank">Georgia Tech's News &amp; Information website</a> online.
</p>
<p>By Judith Shaul Norback, Donna C. Llewellyn and Jill R. Hardin.<br />
<a href="http://www.lionhrtpub.com/orms/orms-8-01/norbackfr.html" target="_blank"><strong>Read the full article at the ORMS Today website.</strong></a>
</p>
<p class="ltgreen">Originally published in the August 2001 issue of <a href="http://www.lionhrtpub.com">ORMS Today</a>.  Copyright</p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2001-11-01T00:00:00-05:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[bchristopher@isye.gatech.edu]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[<strong>Barbara Christopher</strong><br />Industrial and Systems Engineering<br /><a href="http://www.gatech.edu/contact/index.html?id=bt3">Contact Barbara Christopher</a><br /><strong>404.385.3102</strong>]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>57458</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Engineering]]>
      </item>
          <item>
        <![CDATA[Research]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>145</tid>
        <value><![CDATA[Engineering]]></value>
      </item>
          <item>
        <tid>135</tid>
        <value><![CDATA[Research]]></value>
      </item>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>57458</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[ISyE External News]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
