The inner life of failed IT projects

By | June 9, 2010, 10:42am PDT

Summary: This drawing illustrates the inner workings of failed IT projects. You’ve got to take a look!

Courtesy of Naomi Bloom’s HR strategy and technology blog, this drawing illustrates the inner workings of failed IT projects.

Study the picture closely, and you’ll see the following:

  • Complexity
  • Information silos
  • Poor communication
  • Complicated, although well-defined, process
  • Completely failed outcome

Do your company’s projects look like this?

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Michael Krigsman is a recognized authority on the causes and prevention of IT failures.

Disclosure

Michael Krigsman

Michael Krigsman writes and speaks about technology in a manner that most observers consider to be fair and balanced. Michael believes that writing about IT failures, which often have complex causes, creates a unique obligation to be reasonable and accurate in both reporting and analysis.

Michael maintains active personal and professional relationships with enterprise technology buyers, vendors, analyst firms (or individual analysts), consultants, and system integrators. As CEO of Asuret, Michael sells and delivers paid services to members of these same groups.

Vendors regularly reimburse Michael's out-of-pocket travel expenses to attend industry conferences and events. Conference organizers frequently waive entry fees when Michael attends industry events. Michael often speaks at industry conferences and events.

He is a member of the Enterprise Irregulars, a loose association of consultants, investors, industry representatives, analysts, and users of enterprise software.

For daily updates on Michael's activities, follow him on Twitter.

Biography

Michael Krigsman

Michael Krigsman is CEO of Asuret, Inc., a consulting company dedicated to reducing technology implementation failures. Asuret's suite of software tools improve the success rate of enterprise software deployments by quantifying and measuring governance issues that cause most project failures. Michael led the research effort underlying Asuret's model of collective intelligence and its practical application to reducing IT failures in consulting environments. He is a recognized authority on the causes and prevention of IT failures and is frequently quoted in the press on IT project and related CIO issues. He is considered an enterprise software industry "influencer" and provides advice to technology buyers, vendors, and services firms.

Previously, Michael served as CEO of Cambridge Publications, which develops tools and processes for software implementations and related business practice automation projects. Michael has been involved with hundreds of software development projects, for companies ranging from small startups to Fortune 500 organizations. Michael graduated with an M.B.A. from Boston University and a B.A. from Bard College. He is a Board member of the America's Cup Hall of Fame and the Herreshoff Marine Museum in Bristol, RI.

Talkback Most Recent of 11 Talkback(s)

  • None of this makes any sense.
    So yeah. Status quo.
    ZDNet Gravatar
    People
    9th Jun 2010
  • RE: The inner life of failed IT projects
    Yes agreed. but no solutions as people prefer life this way.

    On a recent development project for a proof of principle system to remotely personalise EMV paypass cards I did all the analysis, design and development myself. Partly due to customer budget but it was nice to see everything fall into place. But we can't do projects like this - white water raft risk.
    ZDNet Gravatar
    pauldavidgilligan
    9th Jun 2010
  • ZDNet Blogger

    RE: The inner life of failed IT projects
    Yeah, status quo in a situation that makes no sense. Indeed, that's it!
    ZDNet Gravatar
    mkrigsman@...
    9th Jun 2010
  • RE: The inner life of failed IT projects
    Where's Ben Shatley when you need him? :-p

    Unfortunately, this does look like the inner-workings of many projects I've been on. The Army says it best with their acronym SNAFU!
    ZDNet Gravatar
    Scott Priestley
    9th Jun 2010
  • RE: The inner life of failed IT projects
    @Scott Priestley
    No - the Navy does - FUBAR
    ZDNet Gravatar
    BitBanger_USA
    9th Jun 2010
  • RE: The inner life of failed IT projects
    @BitBanger_USA
    Navy fealty here!
    However: FUBAR=Result / SNAFU=SitRep :-p
    ZDNet Gravatar
    Scott Priestley
    9th Jun 2010
  • RE: The inner life of failed IT projects
    @BitBanger_USA I believe the medical profession is more forward looking: FUBAR BUNDY.
    ZDNet Gravatar
    ggriffin
    10th Jun 2010
  • RE: The inner life of failed IT projects
    @Scott Priestley

    By God's grace, I'm still around, Scott. Hope you are doing well.
    ZDNet Gravatar
    Ben_S
    15th Oct 2010
  • The view from inside is different...
    One of the real problems with a project (or even an organisation) is that the structure looks different from the inside, compared to outside or hindsight.

    Some of this is due to ego, some of it is due to the 'yes-man' syndrome, but there's also the problem that project / team / organisation members all have too much personal investment to allow themselves to see the faults and failings.
    ZDNet Gravatar
    martin.english
    9th Jun 2010
  • All have good points here
    But the majority of the projects that i've seen go the way of the dodo have a number of things in common.
    1. A great project mis-Manager
    2. lack of Key upper management buy in
    3. severe case of the scope creeps

    Projects that succeed do so by introducing components in phases not all for nothing v1 becoming v5 overnight. Managing client expectation as in it's ok to say we cannot do that in this version.
    ZDNet Gravatar
    DS-Solutions
    10th Jun 2010
  • RE: The inner life of failed IT projects
    The beauty of the diagram is that it is scalable. like projects doomed to fail.
    ZDNet Gravatar
    opcom
    24th Jun 2010

Talkback - Tell Us What You Think

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
Click Here

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources