Discussion Locked

How can IT Dept open CEO's eyes?

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have been working in my company for 7 years and have seen major changes in all senses.
The company had mainly acquired technology as the business grew. However, two years ago top-management decided to buy an IT project to a consulting company which would cost several million dollars to let the company have a solid IT platform. The decision was made without taking the company's CIO into account, mainly due to a transition in the position.
According to the documentation presented by the consultants to CEO, our company would have four different best of breed systems to cover all business needs integrated via EAI and published in a corporate portal.
At the beginning, the whole company believed this project would change our competitive position; however as time has passed by some of us who work in IT (including our current CIO), who were not taken into account in the top-mgmt decision, have come to the conclusion that the project will not meet its goals and it will even make our IT TCO and operational IT costs higher, without a tangible competitive advantage for the company.
We would like to show our CEO that the project has a minimal earned value and will not bring any of the benefits "sold" to the company. We would like to approach in a way that gives us as much objectivity as possible.
Has anyone been in a similar situation? Any advice would be greatly appreciated.
Regards,

1 reply

by timwalsh

1. The CIO needs to be the one to lead this effort. The CEO is more likely to listen to another executive.
2. How this is presented will depend greatly on how top-management perceives IT has reacted to this project (i.e. active involvement to try and make it work, ambivalent acceptance of the inevitable, outright hostility). If IT has been openly against this project from the start, any new argument will likely not be given a favorable reception ("You IT guys are just trying to sink this project!"). You are more likely to get a favorable reception if IT has been a willing participant in trying to get the project completed successfully.
3. Accurate numbers will be your most important weapon. Look for hidden costs that the consultantmay not have mentioned when selling the project. Look for flawed assumptions on the part of the consultant that would affect the TCO and ROI figures portrayed by the consultant at the start of the project.
4. How the CEO will likely react to ANY assault on this project will depend on whether he okayed the project based solely on advice from other top-management (i.e. he trusted them to know what they were talking about), or if he had a personal hand in defining the project and choosing the vendor (i.e. he personnally fell for the glossy pictures and fancy sales talk without really understanding what was being sold).
5. When it comes time for IT to lay out its case, it needs to be done unemotionally, and based on solid facts and reasonable projections (what was claimed by the vendor to sell the project vs. what was required by the contract vs. what is reality or likely to be reality at the completion of the project and during the lifecycle of the delivered systems).

This discussion is closed to new replies.