Customer Reviews

Why New Systems Fail: An Insider's Guide to Successful IT Projects

5 star:		(24)
4 star:		(2)
3 star:		(0)
2 star:		(0)
1 star:		(0)

 

 

I came across this book while starting to plan an ERP implementation and purchased it based on the feedback on Amazon.

In my opinion this really is an outstanding book. It is one of the most useful I've come across in all my years in the business. It is written in a conversational style, not loaded with jargon for the sake of jargon and the author uses real-world examples to illustrate his points. It offers valuable insights, advice and tips.

I can't recommend it highly enough. Of course I may update this review based on how the implementation goes :)

This book offers sound, practical advice for anyone considering a system implementation or upgrade. It's writen in a manner that offers the reader real-life solutions to typical implementation challenges. Rarely does an IT book make you smile too. This one does.

The book takes a very practical approach to IT systems implementation by providing many examples from successes as well as failures. Many books concentrate on the development phases and neglect somehow the implementation phases, which are as important. This book concentrates on the implementation phase and this is what makes it unique. The examples are mainly from ERP implementations and specifically HR and Payroll modules, but you still can extrapolate from those examples to other type of modules an systems.

Having implemented several ERPs and financial packages Simon's "Why New Systems Fail" series is accurate and insightful. If only this was written 20 years ago I could have saved alot of time and done things right the first time.

The book uses a simple, true-to-life approach to educate the reader while keeping him entertained. Phil Simon provides valuable insight and explanations of practical solutions for Project Managers or CEOs. Simon's language communicates his knowledge with the reader in a clear and comprehensive manner.

The book is logically organized in five major parts, arranged into chapters that contain real world case studies and practical guides where mistakes leading to failure are clearly outline and explained. Simon has a unique ability to break down complex problems to adapt to the readers' needs.

Adaptability is key for CEOs and program managers, and the information in this book could be valuable if absorbed and implemented in the proper way. Simon maps a practical way to successfully implement your IT systems by providing examples of just that along with those implementations' successes and failures.

I wish I'd had this book ten years ago; I'd probably be better off financially and further along in my career.

Information systems projects frequently fail. Depending upon which study you read, the failure rate of large projects is reported as being between 50%-80%.
Due to the natural human tendency to hide bad news, the real statistic is most likely higher.
This is a catastrophic and as an industry we are failing at our jobs.

As defined by CIO.COM Projects fail when they do not meet the following criteria for success:
* On time delivery
* Delivery within the budget
* The product/system does what it was designed to do
Very few projects achieve all three.
Many more are delivered which fail on one or more of these criteria, and a substantial number are cancelled having totally imploded.
So what are the key factors for success?
Organizations and individuals have studied a number of projects that have both succeeded and failed and some common factors emerge.
A key finding is that there is no one overriding factor that causes project failure. A number of factors are involved in any particular project failure, some of which interact with each other.
In Phil Simons' Why New Systems Fail you will get an insider's look into the nuts and bolts of why systems tank, how budgets are blown clear out of sight and what could have been done to prevent such common pitfalls. As a consultant with well over 30 clients and 10 years in the corporate environment Phil has first-hand accounts of not only the top three project killers but a view from the trenches of political, emotional, logistical, and financial reasons that commonly contribute to system failures.
In just a few pages into Simon's book and I was able to quickly relate the scenarios to projects I have been involved with and draw parallel to the outcomes.
It is with confidence that I suggest Why New Systems Fail be required reading on the bookshelf of any project management professional.

Jay Etchings
Systems Storage Architect, IBM-TSM
Caesars Entertainment Corporation

Having worked on IT projects from both the client and vendor side, reading this book brought back chilling memories of past catastrophes. The insight and solutions contained in this book are very real and explained in practical ways that would have helped me save lots of time and the company lots of money. The content is delivered in a very tangible format with clearly written and supported business based case studies. The authors writing style enables the reader to experience real life scenarios that overlay concepts that most IT people are currently facing in their work environment. And although most IT books will put you to sleep, the author does a good job at infusing enough levity to keep the reader entertained. I highly recommend reading this book and doing as I have done....keep one by your desk.

Why New Systems Fail: An Insider's Guide to Successful IT Projects was a extremely informative book and a must read for all individuals making the important IT decisions. This book gives a great insight in the decision making when you are implementing a new system. Anyone that is interested in not duplicating bad decision should read this book. When bad decisions are bad it can cost companies a great amount of money and precious time. The lessons learned from "Why New Systems Fail: An Insider's Guide to Successful IT Projects " will be something that I will be used within my future decision making process. I have already purchased a copy of this book for several of my co-workers and friends.

Phil is right on the money. This book is a bargain to get such insight and experience. And Phil's pleasant style and humor make this a breeze to read.
This should be required reading for all CIO's (now I must get my CIO to read this!)

As a IT Consultant myself who has worked in large corporate environment down to solopreneurs; Why Systems Fail is a great primer for anyone looking for a macro understanding of system implementation. The scope of your system will of course scale with our organization, but such a key factor of this book is the online of steps along the way. I personally loved the rocker and movie references through the book and what made typically is a subject on the drier side more entertaining. If you are an IT Consultant and especially if your NOT, but want to be come a better manager, this is a must read.

The new edition brings a nice and needed update to the main title (existing systems fail too) as well at keeping up to date on growing trends in the industry; the biggest being SaaS.

Great update, great book!