When My Vendor Gets Acquired

March 27, 2012


I recently facilitated a panel discussion on what to do when your vendor is acquired by another vendor.   The panel consisted of a practitioner, a consultant, and a vendor.  It was a very interesting discussion, but one of the most interesting discussions were on the various reasons why a vendor may purchase another vendor.

The first reason is to control competition.  This occurs when vendors feel that competing vendor systems are similar in functionality and there could be limited need for similar offerings.  Usually the vendor does not purchase this product to eliminate the other system, but the usual process of assimilating an acquisition may be a bit faster than in other types of acquisitions.  Oftentimes, various features from the acquired project are incorporated into the next release.  Most vendors will not “kill” a product, but will have one offering which begins to become the stronger of the two.  While the vendor will usually support both systems, at some time the vendor may announce that they will be discontinuing support; however, this is usually done with ample time to move your system and data over to the newer version.

The second is to add functionality.  A vendor may see a competitor of having some features and functionality that is not currently offered in their product, so they acquire the software with the intention of incorporating features and functionality that is missing from their  current offering.  Many vendors will begin to incorporate the features immediately, but usually the addition of the features may take up to 6 months.  The vendor may continue to support both versions of the software, but usually there is a push to move all users to one platform which simplifies the support of the software.

Finally, the third reason to acquire a vendor product is to move into new delivery areas.  We saw this recently with SAP purchasing SuccessFactors.  Both projects will continue to be offered, but the acquisition of SuccessFactors also brings to SAP the access into cloud computing and SaaS delivery, which SAP was just beginning to began to expand into.  At this time both products should continue to be developed, oftentimes, with this type of acquisition the long-term outlook of the product could change as the relationship matures.  This type of acquisition must be continually monitored to see if there will be product changes in the future.

The one thing everyone on which the panel agreed was that the best thing is not to panic when your vendor is purchased.  There is normally no material change to your system or the delivery for at least 6 to 9 months.  The best thing you can do if you vendor is acquired, is to begin to plan.  You may want to reassess how you are using the software to see if it is still meeting you needs.  Should you be coming to the end of your contract, you may want to evaluate other products to assure yourself that the one you are using is still the best fit.  To accomplish this after your vendor has been acquired may be a bit more work than the typical HCM technology staff had bandwidth, and you may want to look to outside resources to assist in your efforts.  Planning for the merger of your vendor into another should always be a risk on your risk mitigation plan.


John Hinojos
HRchitect


Understanding the Vendor Demo Process

March 16, 2012

After assisting multiple clients with the system selection process I always get a bit surprised when the process seems to bog down the closer we get to the demo.  Historically, we spend a lot of time in Discovery, interviewing staff and collecting requirements.  Then we create a RFI or RFP so we can evaluate the vendors in order to invite the strongest three (3) vendors to demo.

Once the RFP is completed, we usually begin working on the demo script.  Often I do get queries from a client as to why we need the script and just don’t schedule the vendor in to “show us the system.”  After some discussion, everyone usually begins to understand that you would not take a trip without a good map or plan, and that is exactly what the demo script will provide.  It assures that those attending the demo will see the same functionality from each vendor and be able to better compare each vendors system performance.

The demo script for any system should be created in a life cycle flow.  For an PR/HR system, as an example, you would start with recruiting, then to employment, to benefits, compensation, Payroll and on through the termination process.  Then you can look at reporting and system set-up.  I usually suggest that there be an agenda for each section of the demo so various members of staff can come into the demo on features which will impact their area of responsibility.  The one thing I normally stress with a client is that everyone be in the same sections for all demos.

Usually I recommend that items on the demo script also be weighted with a priority.  This allows you to weight the scoring after the demo is done and put more focus on the items which are critical to the running of the company.  It does help in creating a Vendor Comparison Report which will show in one page the major areas of the demo and how well each vendor did to the requirements.  The Vendor Comparison Report and the Decisions Drivers are usually the key elements used to select the vendor of choice.

There is a lot of activity going on during the development of the demo script and coordinating the actual demo. I recommend that companies look at using an outside resource from HRchitect to assist with these tasks.  This resource will allow the full client team to be focused on the demo and not on the administration.  If you have any questions about the demo, be sure to ask your HRchitect representative on how they can help make the demo a smooth process.


An Ever-Changing Landscape

February 14, 2012

It has been a very active couple of weeks in the acquisition market for HR systems.  This has sparked many discussions and conjecture within the HR systems industry on how these acquisitions will effect the future of the HR systems market.  While much has been discussed, it is still too early to fully know the impact to the final look and feel of the product.  What appears is that the major ERP players are moving into Software as a Service (SaaS) and, as predicted, there will continue to be consolidation in the HR systems market.

Every time there is a major merger or acquisition announcement, I continue to get calls and emails from HR professionals asking about how these changes will impact their system.  Even if you are not a client of the acquired vendor, the acquisition can impact your currently used technology.  The acquisition could have a profound change in the direction of the specific genre of software or it could result in an entirely new product being developed which will scientifically change the way HR technology is used.  The one thing that is certain, the changes we have seen will continue to occur.

To better prepare yourself for changes in the market, it is very important you have a full understanding of the technology you are using and what are the plans to interconnect the technology.  If you have not created a HCM technology strategy, now is the time to consider the undertaking.  If you do have a strategy, you may want to revisit your original assumptions during the creation to assure that your plan is still viable.  I realize that undertaking such an exercise in a time of smaller staffs can be difficult, but the payback with a solid strategy can help avoid any costly mistakes.

When updating any strategy it is best to get input from system experts.  This can come from organizations such as IHRIM or from reliable consulting firms such as HRchitect.  The knowledge you can obtain from outside resources can eliminate hours of research for you.  When updating your plans to address changes in the HCM technology future, consider using outside resources.  You will save time and update your plan to include the impacts of the recent software mergers and acquisitions.


2012 HCM Budget Observations

January 27, 2012

I recently served as a panelist on a webinar which discussed the 2012 HCM budgets.  The survey was done by IHRIM (International Association for Human Resource Information Management), and some interesting results appeared on the survey which caused me to do additional research on how the past few years of a difficult economy has impacted HR and HR systems budgets.

The good news is that 82% of those surveyed had their 2011 budget kept at the 2010 level or increased.  For 2012 that number is going up to 85%.  While we are still struggling with the economy, it shows that corporate leaders are realizing that they need to begin to invest in their technology infrastructure.  As companies have tried to hold down their expenses, their systems have continued to age and may not be taking full advantage of the technologies being used by  newer groups of employees.

Use of the 2012 budgets appear to be in the Talent Management areas (Recruiting, Performance Management and On-Boarding).  One interesting area of increase is with Business Intelligence, which corporations have realized can help them make better decisions about running the business.  32% of all respondents said they would be looking at some sort of Business Intelligence this year.

Spending on HR technology continues to grow in 2012 as organizations begin to see the economy moving.  There are still many areas which could impact the economy and corporate spending, but if you have allowed your technology and HR systems to become out dated, this needs to be rectified sooner instead of waiting for a full economic recovery.  If you haven’t already done so, you should begin to create an HCM technology strategy roadmap to best use your budgeted funding.


Follow

Get every new post delivered to your Inbox.