<node id="675191">
  <nid>675191</nid>
  <type>news</type>
  <uid>
    <user id="27164"><![CDATA[27164]]></user>
  </uid>
  <created>1719242934</created>
  <changed>1719323478</changed>
  <title><![CDATA[Leo Howell Named Vice President for Information Technology and Chief Information Officer]]></title>
  <body><![CDATA[<div><p>Following a national search, the Georgia Institute of Technology has selected Leo Howell as its new vice president for Information Technology and chief information officer. Howell has served as interim vice president for Information Technology and chief information officer since Jan. 1.&nbsp;&nbsp;</p></div><div><p>He will transition to his new permanent role on July 1 and will report directly to Shantay N. Bolton, executive vice president for Administration and Finance.&nbsp;</p></div><div><p>“We are very pleased that Leo will be leading Georgia Tech’s information technology efforts during this transformative time,” said Bolton. “His years of experience in information technology, including leading solutions for addressing cybersecurity risk at the Institute and his proven record as a collaborator and change agent, will help to bring a superior technology experience to students, faculty, staff, and other constituents.”&nbsp;</p></div><div><p><a href="https://oit.gatech.edu/node/197" rel="noreferrer noopener" target="_blank"><strong>Howell joined Georgia Tech in October 2021</strong></a> as Tech’s chief information security officer. In this role, he led the development and implementation of an Institute-wide information security and risk management program. As a member of the senior leadership team in OIT, he was responsible for creating and maintaining a cybersecurity program and leading the cybersecurity team, which manages the confidentiality, integrity, and availability of Institute information assets and cybersecurity-related compliance. In his most recent interim leadership role, Howell has been responsible for guiding the strategic course of the Institute’s IT resources and identifying opportunities for the integration of information systems, platforms, and services across all business units.&nbsp;</p></div><div><p>With more than 20 years in higher education, he has extensive experience in risk management, data governance, operational change management, and strategic leadership. Before joining Georgia Tech, he held IT leadership roles at the University of Oregon and North Carolina State University.&nbsp;</p></div><div><p>In his new permanent role, Howell will provide vision, leadership, and oversight in the development and implementation of information technology. He will be responsible for establishing the strategic direction of information technology resources, including a governance strategy, as well as supporting information users by determining trends and technologies needed to advance the Institute’s academic and research mission.&nbsp;&nbsp;</p></div><div><p>“I am very excited for this opportunity to be in an environment that is committed to being innovative and data-driven,” Howell said. “I look forward to continuing to work closely with the Georgia Tech community to develop an inclusive information technology strategy that will further the Institute’s continued commitment to administrative excellence through collaboration and innovation.”&nbsp;</p></div>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2024-06-25T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Leo Howell will begin his new role on July 1. ]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>Following a national search, the Georgia Institute of Technology has selected Leo Howell as its new vice president for Information Technology and chief information officer. Howell has served as interim vice president for Information Technology and chief information officer since Jan. 1.&nbsp;</p>]]></value>
    </item>
  </field_summary>
  <field_media>
          <item>
        <nid>
          <node id="672542">
            <nid>672542</nid>
            <type>image</type>
            <title><![CDATA[Georgia Tech VP of IT and CIO Leo Howell]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>255795</fid>
                  <filename><![CDATA[Leo Howell_Georgia Tech CISO_2_0.png]]></filename>
                  <filepath><![CDATA[/sites/default/files/2023/12/11/Leo%20Howell_Georgia%20Tech%20CISO_2_0.png]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/2023/12/11/Leo%20Howell_Georgia%20Tech%20CISO_2_0.png]]></file_full_path>
                  <filemime>image/png</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[Georgia Tech VP of IT and CIO Leo Howell]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[rpocklington@gatech.edu]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[<p>Rachael Pocklington<br>Institute Communications</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>64319</item>
          <item>1214</item>
          <item>174291</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
          <item>
        <tid>71871</tid>
        <value><![CDATA[Campus and Community]]></value>
      </item>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>64319</item>
          <item>1214</item>
          <item>174291</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Administration and Finance]]></item>
          <item><![CDATA[News Room]]></item>
          <item><![CDATA[OIT]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
