In Full Bloom

Reprise — HRM #EnSW Vendor Consolidation Fairy Tales

Fairy Tales Can Come True, It Can Happen To You...

 2-12-2012 I just couldn’t help myself on this one.  After another week of non-stop M&A fall-out from Oracle/Taleo, I was reminded of the post below, written just over a year ago, and thought it was not only worth a reread but also an update.  Some of it reads like I really did have a crystal ball, but most of what’s been happening was VERY easy to predict.  Now I’ve gone back, using blue for visibility, and brought this old post up-to-date, at least as of this moment.  G-d only knows what tomorrow will bring.  And as before, in the interests of full disclosure, so many of the vendors/providers mentioned below have been, are or will be Bloom & Wallace clients that it’s best to assume that I’m ecumenically biased.  Also nothing learned under NDA — and I need a tracking system to track all that I’ve signed — has been used in this creation or update of this post, nor have any delightful fairies been harmed.

There was a ton of consolidation in the HRM software and services market during 2010, and 2011 is off to a roaring start with SumTotal’s acquisition of GeoLearning. There’s a lot more to come (and it came in spades in 2011 and the start of 2012), and speculation is already rampant about:

But this post isn’t about all the possible M&A/IPO/etc. events that may occur in 2011 and beyond.  It’s about the fairy tales that surround such liquidity events from the perspective of their impact on customers and what not to believe.  With examples I’m making up and which don’t represent any specific HRM software companies, living or dead, here’s my view of the fairy tales that are launched with the press releases surrounding these deals along with their true meanings:

    1. We (the acquirer) will continue to support all product lines fully— Almost no acquirer ever says, in their first press release, that all investments in major architectural overhauls [not to mention the agility, innovation, etc.] will now stop for one or more of the combined product lines, but that’s exactly what does happen. No vendor can afford to advance equally a series of wildly different product architectures.  What they can do, and what the most sincere and capable actually do, is continue to add features/functions within the framework of each product’s existing architecture and object model, while they figure out how to sunset and/or converge them, choosing one of the product lines as having the winning future state architecture and object model (the desired outcome when the deal was done), realizing that they must create a new architecture and object model onto which to build the full range of covered functionality in order to create their future state product line, or simply to mine the acquired customer base via upsell, price increases, and taking out costs.  Where historical data isn’t important, where configurations (gasp! or customizations) are limited, and where other elements of implementation complexity are modest, migrating to a new and/or converged platform need not be life-threatening, but it’s certainly not a non-event.  But in most cases where the software in question provided broad HRM functionality, there’s a fair amount of time and effort (translate: cost) to the customer for that migration even if the vendor doesn’t add to that cost.  I could name names here, but there’s no need as most of my readers know of whom I speak.  [What’s really important to understand when your favored vendor gets a new landlord, is that it matters tremendously why your favored vendor was bought.  Does the new owner really want/need the software they’ve acquired as part of their own development plans or were they buying a revenue stream/customer base for upsell/gap filler/competitor killer/defensive play/etc.?]
    2. We (the acquirer) are delighted with our new colleagues and expect to retain all of them – Almost no acquirer is ever able to retain all the best talent that comes with the acquired vendor.  Some of the leadership wanted to cash out or just wanted out, either of which could have been the impetus for the deal.  Or that leadership has been sufficiently unsuccessful that the acquiring company’s leadership isn’t likely to want to perpetuate the source of those business/personal failings.  Great software people quickly notice if their products aren’t going to be the next generation platform for the consolidated company, and they pick up their marbles and leave.  And there are many more good reasons, for staff of both the acquiring or acquired company, to decide it’s time for a change, to include being immediately courted by other firms which assume that may be the case.  IPOs can produce the same effect, with some folks taking their money, after years of forced death march schedules, and just kicking back for a while.  But whatever the myriad reasons for staff changes, to include the natural effects of consolidation in eliminating duplicate roles, count on these events to cause a fair amount of churn in the new organization’s design and staffing.  Does that matter to customers?  Have you ever been forced to change hairdressers or barbers and dreaded that first haircut?  Even when the new haircut is noticeably better than you’d ever had before, we creatures of habit and inertia rarely switch hairdressers unless the old one about cut off an ear.  How else would you explain the many companies still running my Snowdons of Yesteryear (and clinging to the next generation of Snowdons) under cover of darkness?
    3. Our customers can expect to see only improvements in their support, product roadmaps, and overall happiness as a result of this event– this may well be true if you were the customer of a dying vendor which has been picked up by a thriving one once you and they are over the hump of needed changes, which can include your migration to a different software platform, agreement on a different contract/SLA/etc., working with a new support team, and more.  And it could also be true if your vendor has been acquired for an amazing set of assets that they just hadn’t exploited well but which will now be given the love and support they need to blossom by a new owner who is more passionate about HRM and whatever your acquired vendor’s product does than they are about getting the costs out quickly.  But HRM #EnSw vendors rarely become acquisition targets unless they’ve got a problem — aging architecture, lack of market momentum, exhausted or inadequate leadership, lack of profitability, inability to scale product/sales/support/etc., lack of capital to challenge market leaders, etc. – unless the acquirer is trying to take out a major threat competitor.  But even then, that threat competitor might well have been able to fight off the acquirer if they were gunning on all cylinders.  So even under the best of circumstances, all customers of the combined companies need to keep a careful eye on what’s happening there and invest more than they had been investing in their vendor relationship governance as well as competitive landscape assessment while the combined companies sort out their organizational design and staffing changes, separate and/or converged product roadmaps, product architecture convergence or refresh, rationalization of contracts across all customers, etc.  There’s no rest for the weary here as change, even change for the better, always brings extra work.

So what should I have offered in my earlier post as advice and a bottom line for buyers?  What do I wish I had said then but am determined to say now?  STOP!  Don’t make another investment (except what’s needed just to keep the lights on) into products that have new landlords — or are likely to have such at any minute — until you’ve got a great and freshly updated HRM/HRM delivery system strategy in place.  And don’t make another investment into products whose owners have them on life support, have declared them legacy, or are otherwise focused heavily on a different future for their products than the ones you’re using now — until you’ve got a great and freshly updated HR/HRM delivery system strategy in place.  You should always keep your HRM/HRM delivery system strategy in good shape so that you can use it against which to test new business needs, make further investments, continue roll-outs, emphasize what’s important to your customers, and help ensure that HRM drives business outcomes.  But if you’ve been a little lax, if you’ve never had a clear enough strategy to guide you through M&A-land, now’s the time to get your act together.  And here’s where you start https://infullbloom.us/?p=2857.

Change is change, and it’s never without extra effort on everyone’s part even when it’s change for the good.  When we went from S/V Mar-Lin Nights to M/V SmartyPants, a change for which we had long prepared and one anticipated with great enthusiasm, it was nevertheless daunting to take the controls of our new trawler for the first time.  So when ownership/leadership changes happen suddenly, and without your advice and consent, to the vendor of one or more of the HRM delivery system platform components upon which you rely, it’s little wonder that you feel some whiplash.  [And these last few months have brought more whiplash than ever because of the sheer size and reach of Taleo and SuccessFactors.]  Therefore, it shouldn’t surprise anyone that the “new”company’s leadership puts out soothing messages all around.  But despite the best intentions of everyone concerned, prepare for the possibility of some disruption when you hear that your vendor has just been acquired.  If you’re faced with a rocky ride, you’ll at least be prepared.  And if you’re pleasantly surprised, shout that acquirer’s praises to the heavens or via a comment right here.  [For more coverage of M&A on my blog, here’s a selection of posts that may be of interest https://infullbloom.us/?cat=32]

With many thanks to the publishers of Golden Books for their book cover used here and to lyricists Carolyn Leigh and Johnny Richards for the song ”Young at Heart” popularized by Frank Sinatra.

 

Exit mobile version