Before building out the plan for a bi solution project, I always like to think about what other projects that I have done or know about that are similar to the one I am going to embark on. I always ask myself what issues or obstacles did I encounter in those projects? There are so many reasons why projects get dragged out or just do not succeed, either from the start or they dwindle out if the project exceeds its expected delivery date. Lets just review some and see how many you came across in your professional career on why a project has failed.
- No Executive sponsorship. There is no real buy in from the senior management team, which can lead to many different problems for the success of the project. You have to be persistent here and spend time presenting and socializing how important this project is to them and the company.
- Battle between departments. Believe it or not I have run into this issue so many times when I have investigated why so many companies have failed in implementing a business intelligence solution. So what I mean here is that each department is acting like a ten year old child that does not want to share their data or their process because they believe it is their own secret sauce or they have something to hide.
- No real project plan in place. This is were a company decides they would like to shoot from the hip on this project. They have no real kick off, no steps, no definition of what success is for the project, no anything. They fail to realize that this is a company wide project and the need for a project plan not only holds everyone accountable but ensures the right steps are completed before the next step are taken. It is this mentality that will kill any project almost from the start,
- The IT department wants to build everything from scratch. This can be a problem in a lot of companies were the IT department wants to build everything custom. This can be not only very time extensive but also very costly. I always tell my clients to take the build, buy, or align approach when looking at the different areas of a project. There are several reasons when you should consider building a custom application over buying or aligning: Off the shelf products cannot meet every need, off the shelf products are to rigid, off the shelf products may not be compatible with your existing applications. Now let me give you several reason when you should be thinking of buying an off the shelf product: budget is limited, lack of time, lack of technical proficiency, and technology would not give you a competitive edge.
Above are just a few examples why your project could take longer than expected to be completed or just fail. I am sure that you can think of many more or even have experienced many more. I know in my long career as an IT professional I have come across reasons why projects have failed that would make people laugh and then some other reason that would make people cry. I will save those stories maybe for another blog. I think the main reason why I wanted to get you thinking about project failure is so that history doesn’t repeat itself and I am a firm believer that if you can learn from all failures, you will have a more successful future.