In response to When will HR catch on the wave?

Michael’s post here made me reread what I’d written a couple of weeks ago. Perhaps I should have been clearer.

I meant the current niche players being more threatened by web 2.0 than the big guys.  I think the recruiting space will be hit first, as the social networking side of web 2.0 has a direct impact on recruiting. Someone who has a neat recruiting app with basic job board integration and applicant tracking and 50-100 customers and not really profitable is going to find it hard to move to SOA, re-architect to support RSS feeds etc. Unlike the SAP’s and Oracle’s they probably can’t finance the shift.

I think we will see a new wave of players addressing HR related topics using the Netweaver and other enterprise frameworks.   These will be more nimble, yet more integrated than their stand alone predecessors. They will need to be as it is becoming easier for customers to use tools like visual composer to build add ons to SAP. Mashup type developments will impact niche applications more than it will the key ERP backbone. I’m unlikely to Mashup a payroll, but if the ERP succession management doesn’t offer what you need exactly, I reckon customers will be more likely to build something using the new tools on top of an open ERP than head out and buy a third party product and spend a fortune integrating it. 

Very few vendors managed the switch from mainfrance to C/S, or from ditto with C/S-windows to web based. The same will happen with the move to SOA.  As always comments welcome.

I’m interested in what you think the impact of RSS and extensions will be on things like manager and employee self service. I think they will be significant. Jeremiah, are you reading this, dude? 

14 thoughts on “In response to When will HR catch on the wave?”

  1. Agree with you Thomas that the current niche players probably will not be able to finance the shift and recruiting is the first to be hit.

    Mashup Payroll, not what I was thinking but that is an idea 🙂

    Customers will only build on an ERP framework if the framework is open enough to enable it. (IMO SAP is moving down the right path here.) In part this will mean moving some parts of the framework from the IT geeks into the hands of BAs, however not into the hands of end users. This move will probably be harder for IT departments than for vendors to facilitate.

    If we look back 5 years when we were portal-ising everything (aka ), ESS/MSS for many organisations was the main course of their portal deployment, corporate communication and other services provided the starters and desert. But ESS/MSS (not just HR from any department) was king to providing the stickiness and return patronage that portal’s required. (On a side note workflow turned your meal into a banquet.)

    RSS, SSE, OPML, HR-XML and other XML based formats are going to require ESS/MSS tools to be completely re-written. There are two scenarios I see here. One a form for an employee to change their address should be based on HR-XML’s Postal Address schema, a benefit’s enrolment the same. Or two, they are based on augmented-RSS. The first provides interoperability like we have never seen before, while the second is probably easier for a single vendor but not good for the industry overall. Take this further. For example the R/3 Workflow Inbox should produce an RSS feed to inform users when new tasks require their attention, secure of course. Overlay presence awareness from an IM platform and the application can then begin to make intelligent decisions as to how to contact the user based on the importance of the task.

    Thomas we need to get to a point where integration is not such a big deal, I know Holy Grail stuff but we need to try. Common data exchange formats, like HR-XML will help. This way you can deploy a point solution for your succession management process but still integrate it back into your ERP, which is where payroll should remain.

    Great discussion!

  2. Thomas I am not 100% up on all that Mendocino will do and how it will be implemented, having said that if it delivers half of what it claims to do it will be a great addition. It is a bit of a paradox that it will be delivered via a thick client when so much is going to the browser, but given it will be implemented in Outlook I can understand the thick client approach. I have been wondering if it will replace Business Workplace or be an option for low volume GUI users.

    Yes I have read that it is using XAML as well.

  3. Pingback: Omaha Hi Lo Tips

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s