System Failures Don't Have to Happen, Author Argues

Patrick Avery

Implementing a new computer system is likely to cause some speed bumps, author Phil Simon says in his book "Why New Systems Fail: Theory and Practice Collide." But, he argues, that doesn't have to be the case.


According to his research, Simon says more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems. The reason, he says, is that organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations.


Simon has allowed us to post Chapter 1 of his book in the Knowledge Network (click on the link above to access this excerpt). The first chapter delves specifically into the types of system failures and the consequences that result. The rest of the book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are also presented.

Add Comment      Leave a comment on this blog post

Post a comment





(Maximum characters: 1200). You have 1200 characters left.




Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.