Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

A tsunami of IT project disasters is on the horizon

It is never the popular position to take in the organization to be the prognosticator of disaster and failure, so I write this missive with the full understanding the contents will fall on deaf ears and the potential benefits of my advice will be found on the pile of “I wish we would have….”   There is a tsunami of project disasters rapidly moving toward the enterprise shoreline and there is not much that can be done to stop it.  

The type of project disasters I am talking about are not those that are over budget and behind schedule, but rather the spectacular failures that disrupt supply chains, delay the reporting of financials, and blow up the careers of seemingly competent executives.  These are the types of failures that are created when enterprises “go-live” with an implementation that, in hindsight, will be deemed done in a reckless fashion.  

4 harbingers of doom

Why am I so convinced that many projects are on a collision course with failure?  Consider the following:

  • Double the volume.  There are twice the number of big projects in flight scheduled to go live between May and September of this year compared to a normal year.  When COVID shut things down in early 2020, many companies put their large IT-enabled transformation programs on hold.  In early 2021, the dam broke, and big programs scheduled to begin in 2020 got launched in 2021.  At the same time, companies that had originally planned on launching programs in 2021 did so.  Voila!  That means double the number of potential project disasters.  With initial deployment delivery timelines averaging 12-18 months for major initiatives, the table has been set.
  • Recency bias.  When was the last time you read about a major project go-live failure?   Projects like Select Comfort, National Grid, Cover Oregon, or Los Angeles Department of Water and Power (LADWP) have been off the radar for a few years—long enough for them to fade from the memory of the C-suite.  Organizational hubris is a powerful force that often counterbalances the reality of the real possibility of disasters.  When there is no news of disasters, the potential threat fades.  There is a reason we all drive more carefully after seeing a car accident.  
  • Talent voids.  Almost all major go-live disasters can be traced back to a lack of experience on the part of the senior project team members.  The ability to ascertain and communicate risks is obviously paramount to mitigating them.  With double the number of projects in play, the ability of the Systems Integrators (SIs) to bring highly qualified talent to all of the programs has been greatly diminished.  Couple this with the “great resignation” and attrition rates that have doubled over the last 6 months, and you’ll see that the level of situational awareness on these programs has been dramatically reduced.
  • Untested methods.  We have seen a lot of projects struggle in the areas of integrated systems testing during the pandemic.  The source of the productivity hit is often traced back to the lack of colocation of the project teams.  Without being together, team members are not as quick to learn from their neighbors and tips-and-tricks are not passed along as easily.  Now fast forward to after the deployment and consider the potential impact on thousands of users that may not have the super users in the next chair over to guide them through the startup.  There is no reason to believe that the same struggles we saw in testing would be miraculously cured following deployment.

How to avoid IT disasters

Are there ways to avoid the tsunami of disasters?  The answer in aggregate is, unfortunately, no.  The die has been cast.  Are there tactics that can be implemented on individual programs to prevent a disaster?  Fortunately, that answer is yes.   Here are some simple recommendations:

  • Make it real.  Ask your SI to put together a presentation on lessons learned from major program disasters.  There is no need for you to be the ‘messenger that gets shot on the beach.’  Get this presentation to the steering committee sooner rather than later to demonstrate that you are taking appropriate actions to protect the business.  
  • Establish go-live criteria early.  Too many programs make up the gate criteria 2-3 months before the targeted go-live.  When this is the case, the criteria then becomes, “What can we achieve before go-live” rather than, “Where should we be?”  This is particularly true for projects that are under budget stress.
  • Independent view.  ‘Go-live’ or ‘summit fever’ is real—just ask any of the families of those that perish trying to reach the peak of a mountain.  Good judgment is easily clouded by sunken cost assessments and unwarranted best-case scenario planning.  An independent view can be very sobering.

I realize that this post is likely a bit of a downer or it can be perceived as simply sensationalism, but if it sets the wheels in motion for even one project to avoid disaster, it was worth it!   


Read More from This Article: A tsunami of IT project disasters is on the horizon
Source: News

Category: NewsFebruary 4, 2022
Tags: art

Post navigation

PreviousPrevious post:Beyond the Cyber Buzzwords: What Executives Should Know About SASENextNext post:Key takeaways for CIOs from the Union Budget 2022

Related posts

Barb Wixom and MIT CISR on managing data like a product
May 30, 2025
Avery Dennison takes culture-first approach to AI transformation
May 30, 2025
The agentic AI assist Stanford University cancer care staff needed
May 30, 2025
Los desafíos de la era de la ‘IA en todas partes’, a fondo en Data & AI Summit 2025
May 30, 2025
“AI 비서가 팀 단위로 지원하는 효과”···퍼플렉시티, AI 프로젝트 10분 완성 도구 ‘랩스’ 출시
May 30, 2025
“ROI는 어디에?” AI 도입을 재고하게 만드는 실패 사례
May 30, 2025
Recent Posts
  • Barb Wixom and MIT CISR on managing data like a product
  • Avery Dennison takes culture-first approach to AI transformation
  • The agentic AI assist Stanford University cancer care staff needed
  • Los desafíos de la era de la ‘IA en todas partes’, a fondo en Data & AI Summit 2025
  • “AI 비서가 팀 단위로 지원하는 효과”···퍼플렉시티, AI 프로젝트 10분 완성 도구 ‘랩스’ 출시
Recent Comments
    Archives
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.