IDEAS home Printed from https://ideas.repec.org/h/spr/mgmchp/978-3-319-95273-4_22.html
   My bibliography  Save this book chapter

How the US Federal Communications Commission Managed the Process of IT Modernization

In: Digitalization Cases

Author

Listed:
  • Kevin C. Desouza

    (Queensland University of Technology)

  • James S. Denford

    (Royal Military College of Canada)

  • Rashmi Krishnamurthy

    (Queen’s University)

Abstract

(a) Situation faced: This case examines how the U.S. Federal Communications Commission (FCC) executed its information technology (IT) modernization effort. In 2013, the FCC was spending about 80% of its IT budget on maintaining its legacy systems. Further, the FCC had experienced constant changes in top leadership that resulted in several fragmented IT modernization efforts. The outdated IT systems were not only costly to maintain but were prone to cyber-attacks and verge of major failure. And, the employee morale was lower, and they feared IT modernization and transformation. Overall, the FCC faced several technical and human challenges with IT modernization. (b) Action taken: Acknowledging the eight previous years of fragmented implementation, the new CIO conducted inventory of both IT and human infrastructure. The CIO commissioned an IT tech team to conduct an inventory of the existing IT infrastructure in the organization with a focus to understand vulnerabilities and level of exposure to cyber security. Further, the CIO also took steps to understand the sentiments of employees, customers, and top leadership about IT modernization efforts. Public agencies often promote silo functioning and employees are fearful about change. Thus, the CIO designed several initiatives to solicit feedback from diverse stakeholders and regularly engage them in the process of IT modernization. (c) Results achieved: The FCC moved 207 on premise IT systems to either public cloud environments or with a commercial service provider. In the process of this successful transformation, the Commission reduced the amount spent on operating and maintaining systems from over 85% to less than 50%. The FCC achieved this with a flat budget, thereby increasing the percentage of funds available for new development even. The FCC also reduced the time it took to prototype new systems from approximately 7 months to less than 48 h to produce a prototype. (d) Lessons learned: The FCC’s IT modernization efforts offer following lessons to C-suite leaders: (1) develop a IT modernization strategy that includes both IT systems and the people supporting it; (2) plan a phased approach that achieves ‘quick wins’ in cloud implementation to increases momentum; (3) take time to align both top leadership and employees’ expectations with the IT modernization effort during planning; (4) adopt an open innovation approach that encourages and empower ‘change agents’ within the agency to creatively address in a cloud environment the longstanding challenges associated with the agency’s legacy endeavors, IT systems, and roles; and (5) effectively engage and communicate openly with internal and external stakeholders.

Suggested Citation

  • Kevin C. Desouza & James S. Denford & Rashmi Krishnamurthy, 2019. "How the US Federal Communications Commission Managed the Process of IT Modernization," Management for Professionals, in: Nils Urbach & Maximilian Röglinger (ed.), Digitalization Cases, pages 411-428, Springer.
  • Handle: RePEc:spr:mgmchp:978-3-319-95273-4_22
    DOI: 10.1007/978-3-319-95273-4_22
    as

    Download full text from publisher

    To our knowledge, this item is not available for download. To find whether it is available, there are three options:
    1. Check below whether another version of this item is available online.
    2. Check on the provider's web page whether it is in fact available.
    3. Perform a search for a similarly titled item that would be available.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:mgmchp:978-3-319-95273-4_22. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.