<node id="193411">
  <nid>193411</nid>
  <type>news</type>
  <uid>
    <user id="27445"><![CDATA[27445]]></user>
  </uid>
  <created>1361282578</created>
  <changed>1475896420</changed>
  <title><![CDATA[Researchers Learn Communication Best Practices]]></title>
  <body><![CDATA[<p>Tell the truth. Be brief. Speak in common language.</p><p>These are just a few of the tips that a panel of experts shared during a Jan. 11 seminar,&nbsp; “Communicating Technical Research to Policymakers and Media.” The event was part of the Georgia Tech Research Institute’s (GTRI) monthly Technical Seminar Series. </p><p>Those providing tips for communicating with policymakers included GTRI’s Doug Britton, senior research engineer, Danielle Ayan, senior research scientist and Jud Ready, principal research engineer; Warren Matthews, a research scientist in the Office of Technology; and Danny Boston, a School of Economics professor.</p><p>Britton, who regularly appears before the Georgia Legislature to talk about his state-funded food processing and technology program, recommended rehearsing sound bites ahead of time, as if you were being interviewed by the media.</p><p>“Figure out the three to five words you want to communicate, even if your presentation is much longer,” Britton said. “Repeat them often.”</p><p>Fatimot Ladipo, assistant director of federal relations in the Office of Government and Community Relations, offered the following tips when dealing with policymakers:</p><ul><li>Speak in “common folks’ language.”</li><li>Do your research on the group or individual you are speaking with.</li><li>Notify Government and Community Relations when you’re contacted by a policymaker.</li></ul><p>The panelists providing tips for communicating with the media included GTRI researchers who ranged in experience from first-timer to veteran including Andrew Howard, Leanne West, Jason Nadler and Sheila Isbell.</p><p>“Be prepared for contacts when a story goes out from communications,” Nadler said. “If they release a story on your work, you will know it immediately because your email inbox and voice mail will fill up in a hurry.”</p><p>The panelists also suggested these tips:</p><ul><li>Treat every conversation as “on the record.”</li><li>Notify the communications office in your department or college.</li><li>Rehearse sound bites ahead of time.</li></ul><p>For personalized media training, contact <a href="mailto:nagel@gatech.edu">Matt Nagel</a>, director of media relations.</p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2013-02-18T00:00:00-05:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Tell the truth. Be brief. Speak in common language. These are just a few of the tips that a panel of experts shared during a Jan. 11 seminar,  “Communicating Technical Research to Policymakers and Media.”]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>Tell the truth. Be brief. Speak in common language. These are just a few of the tips that a panel of experts shared during a Jan. 11 seminar,&nbsp; “Communicating Technical Research to Policymakers and Media.”</p>]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[<p><a href="mailto:lance.wallace@gtri.gatech.edu">Lance Wallace</a><br />Georgia Tech Research Institute</p>]]></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>1259</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Institute and Campus]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>129</tid>
        <value><![CDATA[Institute and Campus]]></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>1259</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Whistle]]></item>
      </og_groups_both>
  <field_keywords>
          <item>
        <tid>58891</tid>
        <value><![CDATA[communicating]]></value>
      </item>
          <item>
        <tid>58901</tid>
        <value><![CDATA[communicating best practices]]></value>
      </item>
          <item>
        <tid>58871</tid>
        <value><![CDATA[Communicating Technical Research to Policymakers and Media]]></value>
      </item>
          <item>
        <tid>1976</tid>
        <value><![CDATA[Media]]></value>
      </item>
          <item>
        <tid>58881</tid>
        <value><![CDATA[policymakers]]></value>
      </item>
          <item>
        <tid>56181</tid>
        <value><![CDATA[researchers]]></value>
      </item>
      </field_keywords>
  <field_userdata>
      <![CDATA[]]>
  </field_userdata>
</node>
