Being in the human resource software industry for over 15 years, I like to really pay attention to one of the most important issues of doing business with a company, or when people do business with Aquire.
As software options grow from “integrated” solutions to “best of breed” solutions, so many considerations must be taken into account. The cost of an integrated talent management suite may or may not be worth the one-stop shopping and support. The succession planning feature in the last version of the HRMS really has to be worth the longer implementation cycle it requires. All of this, and so much more, requires a great deal of thought and due diligence.
Some members of the human resource technology market use organizations like IHRIM to seek advice from their peers online or at their conference. Some organizations attend tradeshows by vendors or the Human Resource Executive’s HR Technology Conference to do their shopping. Everybody asks a multitude of questions of their vendors and perspective vendors to support their decisions. I have created a list of the top 8 items I think companies should add to their consideration when evaluating a software company. I think these points are all powerful components of the customer experience you will have once you make a software selection.
1. What is the tenure of the developers on the development team, and has there been a lot of turn over?
The experience on the team should foster a depth of understanding of the code and the customer issues involved. This also speaks of the respect the company gives to their important assets and how hard they work to keep their people.
2. What is the tenure of the support team?
Depth of knowledge of the product can be taught more rapidly than some can imagine. The reason this is a good question is that it demonstrates the respect the company gives to their support people, to make them feel it is worth staying in a mentally stimulating but exhausting job. When you are handling support calls, you are always “on.” You are on the “stage” even if the stage you’re performing on is only through the phone.
3. What percentage of technical support calls are due to people wanting to know how to do something and what percentage is for bugs and software that will perform as advertised?
This gives an indication whether or not customers are always finding bugs and problems in the software.
4. How are features and products designed and enhancements considered, and how involved are the executives?
It’s imperative to find evidence of customer participation in this process. There should also be a mechanism for sales people to bring requests and ideas into the development team and have them taken seriously. Enhancements and features are often specifics gathered from many sources, and the better plugged into the market the employees are, the more ideas can be gathered for consideration. Sometimes products or new features need to be designed before the customers realize they need them. The visionaries within the company decide how that occurs.
5. Who has owned the software code; how many times has the executive leadership changed for a product or a company?
It’s important that at least some of the developers on the team now also wrote the product for earlier versions. Let me put it this way, have you ever heard of a Monet being finished by another painter? Other than a relay, can anybody else finish a race for you? It is not always possible, but I like some consistency on the teams, somewhere along the line.
6. Have there been any litigation issues with customers?
That can happen even within the best companies. But something must have changed to prevent it from happening again.
7. Is the company actively involved in their industry?
Companies should give back to the community that buys from them. Organizations have to learn from their market place by participating in conferences, committees, associations, etc. This shows a willingness to learn and a respect for the market place.
8. Can you try out the software before you buy it to test for usability and stability?
Maybe some software is functional within a pilot program, maybe some might need a lab environment for testing. Be creative to verify that things are not just smoke and mirrors. You can seldom expect to work with a fully functional implementation without an investment, but the company must ensure your comfort level with the tools you will be investing your time and money on.
There are so MANY additional elements of a software evaluation. These are just a few that I think need to be added to the mix.
Cheers,
Lois