Thus far in the series, we’ve discovered the four camps of customers that exist in today’s HR landscape in part 1. Then in part 2, we covered what’s going on in the cloud. We then jumped over to the current state of SAP on-premise technologies in part 3, paying particular attention to UI5. Having covered a broad area of what’s out there today, the burning question for many people is: What’s going to happen next?
Given all we’ve covered in this series, here are my predictions for SAP and its customers in the HR landscape over the next few years:
Who is ready to play armchair CEO with me? If I was running SAP, here’s what my “silver-bullet” company strategy would entail:
If my theoretical plan was put into practice, customers who invested in UI5 on-premise in 2015 won’t feel like that investment was for nothing if they could transition to the cloud using the same technology to unite them. In the other camp, customers who invested in SuccessFactors don’t really mind what technology it is running on as long as it looks good and covers the same functionalities.
There is a growing need for a unified platform today. Look at the “Cloud Payroll” offering. This offering is essentially hosted SAP Payroll mashed-up with SuccessFactors. The two UIs don’t mesh completely right now. Aside from showing some basic info like a paystub in EC there’s not really any SAP functions surfaces in the SuccessFactors UI. What the marketing material doesn’t tell you is admins still have to run a lot off the backend with good old SAP GUI. It would be a lot more slick if everything was web-based in one look-and-feel. Then you wouldn’t even have to tell cloud customers what backend system any of it was running on.
It is also technically feasible for SuccessFactors to run on UI5. OData is pretty flexible and an API could be built while the open source UI5 library is expanded to accommodate on the front end. Once you’ve got that API piece worked out (oh wait, it exists already!) it is a matter of transitioning the existing SuccessFactors pages over to UI5 (which gives them the new power to run on any device!). In parallel, you continue to expand the SAP HCM features available on UI5 (oh wait, that’s already in progress with Fiori and HR Renewal!). Now you’ve got one platform that runs the world’s best payroll and world’s best talent management on a single slick unified user interface. You can take your time merging the backend systems however you want because the customers aren’t paying much attention anymore to this unexposed technology as they transition to the cloud. Now repeat for other modules/functional areas.
Sound like a good plan to you? I am available for the next board meeting if SAP needs a new member. Unfortunately for my wishful job prospects, SAP thought of this before me and I’m just piecing it together in this series. UI5 is taking off and partners are already coding in UI5 to make SuccessFactors extensions on the HANA Cloud Platform. In my opinion it is just a matter of time before SAP transitions all of SuccessFactors to the technology. In fact, they’ve even announced that Fiori is now the design basis for SuccessFactors going forward! I think it is then just a matter of time before the backend technologies merge or get covered up in the cloud to the point where we can no longer tell the difference between what is SuccessFactors and what is SAP. Then the question is, what module is next after HCM? Let’s keep our ears open at SAPPHIRE to see what else develops!
I hope you’ve enjoyed the blog series! What else is on your mind? Post some comments and let me know!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |