Why should the technology lead take part in ERP selection?

Because they can assess an application’s robustness and performance beyond its advertised features, as well as its technology, maintainability and compatibility with existing systems.

Which advantage of open-source software does the chapter highlight?

It highlights transparency: the code can be examined and, when necessary, modified to adapt the software to specific needs.

What should the technology lead assess about customisations?

They should assess the amount of work the changes may require and their compatibility with existing tools, since they will also be involved in implementation and synchronisation.

What is the risk of ignoring the technology lead’s opinion?

The organisation may underestimate implementation effort, integration difficulties or required customisations, which can become very costly.

NaN-tic‎ㅤㅤㅤㅤㅤㅤ|‎‎ㅤㅤㅤㅤㅤㅤ‎ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤThe CTO’s Role in Choosing an ERP and Business Software

CHAPTER 7 - THE CTO OPINION

SUMMARY:

From the first day, those responsible for the technological infrastructure of the organization must be at your side. Only they will know how to properly assess the strongness and performance of the tools you are analyzing. In addition, they should end up installing and synchronizing the tool with the rest of corporate applications.

KEY IDEAS:

If you want to buy a car and you have a mechanic in the family, you will surely ask for advice. So the same with an ERP.
CTO managers understand how computer tools are built beyond the benefits they offer.
Surely modifications and adaptations of the program will be necessary. The CTO director will know how to evaluate the amount of work that will be required.

The CTO Manager

Imagine that you need to buy a car. If there was a mechanic in the family, it would probably be a good idea to ask him for advice. Plus, wouldn’t his point of view have some value when taking the final decision? You’d listen to his explanation about the pros and cons of different models, and you’d ask him about the future maintenance of each option. And it’s exactly the same when choosing a management tool for your company.

The CTO Manager, and even your IT engineers, must take part in the selection process from day one. In fact, they already know what the best tools are, and not because of the features offered, but because of how they are made. They know which ‘engines’ function better or worse, which are easier to repair, which use robust, modern technology and which are now outdated.

This is where, in general terms, open source software offers an undeniable competitive advantage: it is completely transparent. Anyone can analyse how the software has been made, right down to the finest detail, and where necessary, modify it to adapt it to their own specific needs. No tricks, no pitfalls, no false expectations.

What’s more, you may find that the rest of the company management staff are not able to calibrate the volume of work that adaptations or modifications needed will involve. Perhaps nobody understands the level of compatibility between the different tools that have already been installed. Therefore, the opinion of the Technology Manager, of the ‘Head of Mechanics’, for example, must be taken into serious consideration, as in the end, these are the people who will have to take part in the installation and implementation of the new program and they will have to harmonise it with your pre-existing software. Ignoring or undervaluing their criteria is an error that may be a highly expensive one.