So … you're either in the market for your company's first human resources management system (HRMS), or you're ready to move up to a more sophisticated system, and you're struggling with whether to bring in the consultants or tackle the evaluation process by yourself. Can you do it yourself? The answer is yes, and maybe. It all depends on whether or not you can commit the time and resources to doing it right.
Be prepared for a fairly time-consuming process, ranging from at least three to nine months or more. You'll also need to recognize that it will require a considerable outlay of capital and staff resources to bring the project to fruition. Your company will have to live with your decision for the next eight to ten years or more, so you want to make sure that you do it right—the first time.
For starters, it will be extremely helpful to begin with a clean slate and an open mind. The less biased you are regarding a specific software vendor or application (either “for” or “against”), the easier it will be to make an objective evaluation and decision. In the last five years or so, vendors, software applications, and hosting options have undergone significant changes. Making a decision based solely on past experiences (good or bad) may be a disservice to your organization. Try to remain unbiased throughout the evaluation process. Whether you use a consulting firm to help you in your quest, or decide to strike out on your own, following a rock-solid methodology is the key to success.
User-Needs Assessment
The process begins with a user-needs assessment (UNA) to develop a wish list of features and functionality you expect the new system to deliver. In this phase, brainstorming sessions with each group of functional and technical users are scheduled to discover what they like about the current system, what they dislike about the current system, and what they are looking for in a new system.
There are various ways to build this information. Some people use questionnaires and surveys to collect this information, and some use the tools that software evaluation companies like Technology Evaluation Centers (TEC) offers to help organizations build their requirements. In addition to these tools, the interactive nature of face-to-face meetings with small groups of users allows useful information to be exchanged to help the decision process along. Some users may know exactly what they want out of a new system, while others may have difficulty envisioning their future needs. You'll have to facilitate the discussions and prod the users by asking such questions as “What are you doing manually today that would save you time if it were automated?”
While you're conducting these sessions, be sure to ask how new features and functionality will affect efficiency and productivity. This information will help you later when you prepare a cost-benefit analysis to justify the expense of the new software.
Next, take a look at some of the software vendors present in the marketplace. In the mid-market, there are no less than 20 vendors that could be considered “players” (prominent in the industry), and there are many more that are trying to enter this market. There is no way that you can evaluate all of them in depth, but there are some shortcuts that you can use to narrow down the choices.
One option available is to see what the analysts have to say about the major players in the HRMS software arena. Gartner's Magic Quadrant for HRMS, Forrester's Wave, or TEC's eBestMatch™ are all effective decision support systems offered by software evaluation organizations that can help you evaluate different vendors.
Another option is to attend conferences, such as those held by the Society for Human Resource Management (SHRM) and the International Association for Human Resource Information Management (IHRIM). These conferences usually have an exhibit hall, and the major HRMS vendors will each have a booth and product specialists on hand to discuss their offerings and to provide demos of their solutions. Often they will arrange a vendor shoot-out, where each vendor demos its solution to the assembled attendees, and the attendees decide for themselves which offers the best solution.
You can also use the Internet to research the vendors, but beware: this could turn out to be the equivalent of looking for a needle in a haystack. On the day I wrote this article, I did an Internet search on “HRMS software vendors,” and it returned 728,000 hits. You are going to either have to narrow your search, or be prepared to do a lot of surfing.
One other way is to do some sleuthing and try to find out what your competition is using. There are several vendors that have carved out a niche in the marketplace, and that have specialized solutions tailored to specific market verticals (such as health care, professional services, manufacturing, etc.)—a case of “birds of a feather …” This research should allow you to narrow your choices down to a handful of promising vendors. Call each one to request a copy of its company's current product information, and see if it has an online demo to provide a high-level familiarity of its products. This should help you come up with a shortlist of perhaps three or four prospective vendors.
Breaking with Tradition
Traditionally, the next phase of the project would involve issuing a request for proposal (RFP), in which you would draw up a list of high-level requirements and submit it to a large list of HRMS software vendors. After reviewing your requirements, interested vendors would notify you if they were interested in competing for your business.
This approach is time-consuming because you have to wait for vendors to complete their reviews of your requirements and contact you with their intentions. The next step would be to draft a request for information (RFI) to send to those vendors that chose to compete. The RFI should describe your requirements in more detail, list your project goals and objectives, provide a high-level project timeline, and request background on the vendor (including information about its proposed solution, the technical architecture employed, implementation approach and methodology, hosting options or partners, references, testimonials, and pricing strategies).
I recommend skipping the RFP, and start contacting the three or four short-listed vendors that you feel may have the best solution for your needs (based on your research). Your goal is to determine their willingness to conduct a scripted demonstration (versus a canned sales demo). This requires the vendor to “script” (prepare with detail) the demo according to your specific needs and scenarios.
Once you have the vendors' commitments, you can then send them a detailed RFI, and schedule the scripted demos. By skipping the RFP process, you can reduce the project timeline by as much as a month.
Be prepared for a fairly time-consuming process, ranging from at least three to nine months or more. You'll also need to recognize that it will require a considerable outlay of capital and staff resources to bring the project to fruition. Your company will have to live with your decision for the next eight to ten years or more, so you want to make sure that you do it right—the first time.
For starters, it will be extremely helpful to begin with a clean slate and an open mind. The less biased you are regarding a specific software vendor or application (either “for” or “against”), the easier it will be to make an objective evaluation and decision. In the last five years or so, vendors, software applications, and hosting options have undergone significant changes. Making a decision based solely on past experiences (good or bad) may be a disservice to your organization. Try to remain unbiased throughout the evaluation process. Whether you use a consulting firm to help you in your quest, or decide to strike out on your own, following a rock-solid methodology is the key to success.
User-Needs Assessment
The process begins with a user-needs assessment (UNA) to develop a wish list of features and functionality you expect the new system to deliver. In this phase, brainstorming sessions with each group of functional and technical users are scheduled to discover what they like about the current system, what they dislike about the current system, and what they are looking for in a new system.
There are various ways to build this information. Some people use questionnaires and surveys to collect this information, and some use the tools that software evaluation companies like Technology Evaluation Centers (TEC) offers to help organizations build their requirements. In addition to these tools, the interactive nature of face-to-face meetings with small groups of users allows useful information to be exchanged to help the decision process along. Some users may know exactly what they want out of a new system, while others may have difficulty envisioning their future needs. You'll have to facilitate the discussions and prod the users by asking such questions as “What are you doing manually today that would save you time if it were automated?”
While you're conducting these sessions, be sure to ask how new features and functionality will affect efficiency and productivity. This information will help you later when you prepare a cost-benefit analysis to justify the expense of the new software.
Next, take a look at some of the software vendors present in the marketplace. In the mid-market, there are no less than 20 vendors that could be considered “players” (prominent in the industry), and there are many more that are trying to enter this market. There is no way that you can evaluate all of them in depth, but there are some shortcuts that you can use to narrow down the choices.
One option available is to see what the analysts have to say about the major players in the HRMS software arena. Gartner's Magic Quadrant for HRMS, Forrester's Wave, or TEC's eBestMatch™ are all effective decision support systems offered by software evaluation organizations that can help you evaluate different vendors.
Another option is to attend conferences, such as those held by the Society for Human Resource Management (SHRM) and the International Association for Human Resource Information Management (IHRIM). These conferences usually have an exhibit hall, and the major HRMS vendors will each have a booth and product specialists on hand to discuss their offerings and to provide demos of their solutions. Often they will arrange a vendor shoot-out, where each vendor demos its solution to the assembled attendees, and the attendees decide for themselves which offers the best solution.
You can also use the Internet to research the vendors, but beware: this could turn out to be the equivalent of looking for a needle in a haystack. On the day I wrote this article, I did an Internet search on “HRMS software vendors,” and it returned 728,000 hits. You are going to either have to narrow your search, or be prepared to do a lot of surfing.
One other way is to do some sleuthing and try to find out what your competition is using. There are several vendors that have carved out a niche in the marketplace, and that have specialized solutions tailored to specific market verticals (such as health care, professional services, manufacturing, etc.)—a case of “birds of a feather …” This research should allow you to narrow your choices down to a handful of promising vendors. Call each one to request a copy of its company's current product information, and see if it has an online demo to provide a high-level familiarity of its products. This should help you come up with a shortlist of perhaps three or four prospective vendors.
Breaking with Tradition
Traditionally, the next phase of the project would involve issuing a request for proposal (RFP), in which you would draw up a list of high-level requirements and submit it to a large list of HRMS software vendors. After reviewing your requirements, interested vendors would notify you if they were interested in competing for your business.
This approach is time-consuming because you have to wait for vendors to complete their reviews of your requirements and contact you with their intentions. The next step would be to draft a request for information (RFI) to send to those vendors that chose to compete. The RFI should describe your requirements in more detail, list your project goals and objectives, provide a high-level project timeline, and request background on the vendor (including information about its proposed solution, the technical architecture employed, implementation approach and methodology, hosting options or partners, references, testimonials, and pricing strategies).
I recommend skipping the RFP, and start contacting the three or four short-listed vendors that you feel may have the best solution for your needs (based on your research). Your goal is to determine their willingness to conduct a scripted demonstration (versus a canned sales demo). This requires the vendor to “script” (prepare with detail) the demo according to your specific needs and scenarios.
Once you have the vendors' commitments, you can then send them a detailed RFI, and schedule the scripted demos. By skipping the RFP process, you can reduce the project timeline by as much as a month.
No comments:
Post a Comment