A client wants to implement a new software system that was recommended by a different division of the same company. How do you evaluate it to ensure it's the right choice?
It's not uncommon for many corporations with multiple locations or divisions to have different computer systems and networks that don't necessarily talk to each other. They may share a few common systems that allow them to communicate with other locations or business units to conduct business as usual. Since companies that are decentralized have systems, networks, and/or software that could differ from other locations, hiring managers will ask how you will gather information, who you will talk to, the method you will use to evaluate the new software, and how you will arrive at a decision to recommend or not recommend the software. Giving an example or short checklist of what you will cover in the evaluation process will be important.
"I've been in similar situations like this before, and have consulted clients on what needs to be considered before a new software implementation can take place. In a consulting engagement, a proper discovery and background must be conducted on the business. This step is absolutely critical. If you don't understand why the customer is asking you to evaluate new software for their business, you'll miss the most important part of why you are evaluating the software. My experience has shown that if you find the compelling event or pain point that's prompting them to look at a new system, you'll know if it's the right choice for them."
