The challenge of choosing software:
Choosing the right software for your company can be challenging: it starts with a facial expression. The fact is that all the demons look the same and all the cars look good in the dealer’s room.
When choosing the wrong software:
The business requirements of a company not addressed in the demo can result in a costly exchange.
If the software is too focused on end users it may lead to a long, expensive implementation. In extreme cases, the project is canceled and the company returns to its old software.
Software is selected by decision makers based on their past experience without regard to the ability of their users.
One of our former clients hired a new president to run the company.
The president came from a large company that used very sophisticated software. Shortly after assuming his new position, the president decided to buy the software he used in his previous job. Department heads who viewed the software in the demo did not consider it to be the right choice for their company, fearing that users who have been running the home-grown program for 15 years may find it difficult to read.
Without their advice, the president has decided to buy the software. The consulting firm that sold the software confirmed the cost would not exceed $ 750,000. Two years and $ 2.5 million later, the software was eventually used and the company went “live.” The main reason for the cost elimination was because the software had to be modified to meet the needs of the company’s business, as well as users of the longest learning curve encountered when trying to manage the system.
This has resulted in the expulsion of the president, a company whose software has many of its functions and functions, and it needs a large computer department to support the operation of the software.
The right way to choose software:
Before you are given a demo, make a list of your current and future business needs.
Provide a copy of these requirements to the person who will provide the demo and copies to users who can mark what needs are being considered.
Make sure the person giving this demo learns as much as you can about the needs of your company’s business.
Some requirements may be missed during the demo because questions and answers are asked. This is a great way to follow all the requirements listed.
After the demo, another required list should be developed based on the new software skills learned.
Hire software vendors before making a final decision:
Make sure the Software Source Code stays on your server. Having software on “escrow” is not a good solution.
Not having a Software Source Code on your Server binds you to a vendor and if there is something wrong with the relationship, you cannot choose other services.
Ask your software vendor to refer three clients. Talk to the CEO, CFO, and Director of IT. You will find three different ideas on how software works.
The most important question to ask: how is a hotline supported? Unresponsive hotline support will create business interruptions.
Going “live” with the new program:
After a decision is made to purchase a new software, prioritization must be made.
Priority for “A”: must be done before program and operation.
Important “B”: it can wait until the system is complete and running.
Most important “C”: it would be nice to have it.
Usually after using a new system, users find that most of the “B” key elements are not needed as the new system deals with them.
The most important “C” doesn’t have to be time-consuming because the new system caters to all business needs.
Detailed program research should be done before the software vendor gives you the final suggestion, to find out what needs to be written that is not needed for the business.
The research will prevent it from being surprised to appear