Software for the finest computer – The Mind

  • Tim’s YouTube Channel

  • Enter your email address to follow this blog and receive notifications of new posts by email.

    Join 999 other followers

  • Categories

  • Fan Page

  • Since 1971:
    "Software for the finest computer - The Mind"

    Follow me on Twitter: @timbryce

  • Subscribe


Posted by Tim Bryce on June 12, 2011

For more than 30 years I have had the pleasure of watching the development of some rather large and complex information systems, particularly for manufacturing, banking, insurance, and government. I have also had an opportunity to observe some rather massive system disasters in both the corporate and government sectors. It’s rather unsettling to see companies shoot themselves in the foot on such projects, but it seems to have become somewhat routine in the last decade where I have seen banking systems fail, transportation systems collapse, and medical systems die a slow agonizing death, at considerable expense, usually in the millions of dollars.

Recently, I was watching an episode of “60 Minutes” (The Espionage Act: Why Tom Drake was indicted – May 22) which discussed the prosecution of a whistle blower at the National Security Agency (NSA) regarding the development of a major system to be used in the War on Terror, code named “Trailblazer.” This system represented a massive effort to modernize the NSA and was started shortly after 9-11. Although the intentions of the developers may have been good, the project started to spiral out of control almost from the beginning.

Instead of using internal resources, Trailblazer was developed by major DoD contractors with some rather well known names and reputations. As it was a classified project, I obviously was not made privy to the details of the project. However, having read what is publicly available, and seen many other mega-snafus, I think I have a good idea what happened.

First, a rudimentary management infrastructure was created, where vendors vied for control over the project thereby leading to disagreement over the methodology to follow in developing the system. This is quite common even within a single company, but to have multiple companies involved, each jockeying for position, there was probably no agreement in terms of Who, was going to do What, When, Where, Why, or How. In all likelihood, there was no consensus as to what deliverables would be produced, the criteria for their acceptance, or review points before proceeding to the next step or stage of development. Without a defined road map to follow in such a colossal effort, developers undoubtedly began to lose their direction early on. Further, it is highly likely there was no consensus in terms of defining the requirements for the system and, instead, developers focused on technology issues. Without a proper set of requirements, the project was easily sidetracked. Inevitably, a technical solution was sought before truly understanding the problem. In other words, they tried to program their way to success without knowing what they were supposed to produce. This scenario is typical of all of the system snafus I’ve seen over the years. It’s a “Fire-Aim-Ready” approach to development as opposed to “Ready-Aim-Fire.”

Trailblazer eventually died a slow and painful death; even the NSA dubbed it “an expensive failure.” Unlike the other system snafus I’ve seen, ranging upwards to $100 million in costs, the project cost more than $1 billion to the taxpayers, the largest mega-system disaster I have ever known. The point is, it did not have to be such a tremendous waste of money, time and effort. Had the people in charge at NSA had a defined road map for the project, it could have easily been brought under control and they would not have had to leap before they looked, but because of their blind-faith in technology they pressed forward without properly doing their homework.

Again, Trailblazer was not unique in its failure. In fact, it typifies how major systems are botched in this country today, and why companies are skeptical of tackling such efforts. Instead, they are content to tackle minuscule programming assignments which they hope will be able to integrate into their systems. However, without a blueprint in place, the chances for success are slim to none. Yet, it is this “cut and fit” approach to systems development which is now the prevalent mode of operation in most companies today and, as a taxpayer, I am concerned Trailblazer will not be the last billion dollar systems disaster the government will produce.

Keep the Faith!

Note: All trademarks both marked and unmarked belong to their respective companies.

Tim Bryce is a writer and the Managing Director of M. Bryce & Associates (MBA) of Palm Harbor, Florida and has over 30 years of experience in the management consulting field. He can be reached at

For Tim’s columns, see:

Like the article? TELL A FRIEND.

Tune into Tim’s THE BRYCE IS RIGHT! podcast Mondays-Fridays, 7:30am (Eastern).

Copyright © 2011 by Tim Bryce. All rights reserved.


  1. Simon Crosby said

    We probably won’t know what happened on this project for a long time, but it sounds like it has at least some superficial similarities with the FBI’s Virtual Case File project. They were similar in that the goal in both projects to allow sharing of secret information.

    There was a good article in IEEE Spectrum a while ago:

    Also, a podcast where some experts discuss why the project failed:


  2. […] written about such snafus, such as at the United States Department of Agriculture (USDA) and the National Security Agency (NSA). Another that comes to mind is the Obamacare health system which was delivered late and horribly […]



Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: