Why not do a Computerization Project?

Search

You can do it, but are you sure that’s what you really want?

This morning, I arrived at an introductory meeting – the deciding group was sitting in the room: the CEO, CFO, COO and CIO.
The CEO began and asked – convince me why I should start a computerization project.

Poor guy… he chose the wrong person.

So I started with a long explanation of why not to do the project:
It’s expensive, difficult, undermines the stability of employees in the company, endangers the place of elected officials in the organization, there is a high risk of failure, high chance of resentment/resistance by some employees, it requires hard work, difficult management decisions, and in general – most of us hate change and much more.

“You’re confused”, the CEO said. “You’re telling me why I shouldn’t?!”
Exactly! If you are considering doing a computerization project, you must know why you’re doing it, fully understand the reason behind it and the goals of such project.

Entering this project is entering a difficult and expensive path, and if it is successful, the expenses will continue on and on, assuming that you will reach the point of understanding that every investment produces better automation, solutions and control.

So you want to do a project?
Convince me yourselves – why you should.

למה לא לעשות פרויקט מחשוב?
Skip to content