Showing posts with label hrms. Show all posts
Showing posts with label hrms. Show all posts

Sunday, October 19, 2014

Is HR Tech Overshooting HR Capabilities?

Human resources management is a hot area for new technology, at least based on the number of new vendor offerings. But why isn’t there greater adoption of among HR practitioners? In this post, I outline three reasons that interest is high but actual adoption is slow, and what business leaders should do about it.

But first, a quick summary about the leading conference on HR technology. 

HR Tech Conference, a Must-Attend Event

At the urging of several associates, I attended my first HR Technology® Conference (HR Tech) earlier this month in Las Vegas. If you are interested at all in HR technology, this annual event belongs on your calendar. Here's why:
  • Thought leadership. Anyone and everyone associated with HR technology  is at this conference--vendors, service providers, and HR professionals. This allows the conference organizers to select the best speakers and hold them to topics of high interest to attendees. Speakers go beyond traditional themes such as HR administration and compliance. Even cloud computing is old news to this crowd, as nearly all the leading HCM solutions these days are delivered as a service. This year, analytics was a hot topic, including predictive analytics, big data, machine learning, and employee sentiment analysis. Social business was another focus, as HR applications have turned out to be an excellent use case for social tools in recruiting, learning, and collaboration. The latest thinking around talent management was also on display.
     
  • Peer networking. HR Tech is an HR vendor expo as well as a conference for HR professionals, so of course there is a large exhibit hall and plenty of sponsor logos plastered everywhere. But end users form a high percentage of the attendees. This creates excellent opportunities for peer networking, more so than I see in most single vendor conferences. At many events, I have to work hard to arrange customer interviews. But at HR Tech, they came to me unsolicited, while queued up for receptions, sitting at meals, or before sessions.

  • Customer stories. Although vendors pay to exhibit, it doesn't buy them speaker slots, unlike many conferences. And, when they do speak, it has to be with a customer, never alone. As a result, many sessions are devoted to case studies, and there are lots of customer panels. This year there were presentations and panel discussions by HR practitioners from a diverse collection of organizations, from traditional companies such as ConAgra, Monsanto, Bristol-Myers Squibb, Unilever, Siemens, Lockheed Martin, and HP, to digital businesses such as Facebook, Google, LinkedIn, and Hootsuite. 
HR is fertile ground for new technologies, from social recruiting to sentiment analysis to wearables. But can HR organizations even begin to consume it all? This is where there is a gap between what is possible  and what is currently realized in practice. 

Workforce Analytics Illustrates the Problem

The adoption rate for workforce analytics is a good example. In one session, Brian Kelly, a former practice leader at Mercer, gave a presentation on strategic workforce planning. It is a hot topic, as it enables organizations to address the critical gaps between the current workforce characteristics and future workforce needs. In some industries, this is a critical process, as future workforce needs are changing with evolving business models and new products and services. High tech and healthcare are two sectors that come to mind. The good news, according to Kelly, is that most organizations already have the raw data needed to do strategic workforce planning, such as basic employee census data, high level job families and critical jobs, reporting hierarchy, rewards data, and employee demographics.

But as Bill Kutik, as the former HR Tech co-chair, points out in his excellent post-conference wrap up,  HR consultants, analysts, and marketers have been saying as far back as 2001 that workforce analytics will be the next big thing. “Certainly interest is very high now in workforce analytics, but still without widespread adoption,” Bill writes. “So I find it ironic (but typical) that vendors are so focused on predicting the future when their customers don’t yet have a firm handle on measuring the past.”

So, we have to ask, if technologies such as workforce analytics are critical to the mission of HR organizations, why is there not greater adoption?

From my consulting work with clients over 20 years, I see three basic problems.
  • HR viewed as a support role. Despite claims that “our people are our strategic advantage,” most companies do not view HR as a strategic function. In practice, it is a support role, focused around the basic day-to-day activities of hiring and on-boarding new employees, paying them, administering their benefits, maintaining accurate records, and keeping the organization in compliance with labor law and myriad other regulations. If the senior HR leader is in the room for strategic planning sessions, it is often as a token gesture, to keep him or her informed of corporate strategy, not as a co-equal partner with functions such as product development, marketing, operations, finance, or sales. In doing strategic planning over the past 15 years I've seen notable exceptions. But too often, HR in many organizations is like the typical IT function—it’s there to support the strategy, not to help formulate it.
     
  • Inadequate staff levels. Second, if HR is viewed as a support function, it is a ripe target for staff reductions. With the thinning of management ranks over the past twenty years, and especially since the 2008 recession, HR professional are spread thin. When there are not enough hours in the day to deliver both the strategic and the tactical, the tactical always win. Failing to think strategically is seldom a career-ending move, but falling out of compliance with labor law can give you a quick escort out the door. 
     
  • Lacking necessary skills. Finally, most HR professionals do not have the quantitative skills to make use of new technologies such as workforce analytics. As Kelly points out, simple tools such as Excel may be sufficient for planning headcount by job function and geography. But more sophisticated analytical tools are needed to correlate projections of workforce skills, attrition rates, pay growth, diversity analytics, and external labor market data. Unfortunately,  most HR professionals lack the skills to make use of these tools. HR has always been a career that is more attractive to liberal arts graduates, such as those majoring in psychology, sociology, and communications, rather than those with science and math degrees where they develop the quantitative analytical skills needed to make use of these tools.
I had a hallway conversion with my colleague Brian Sommer on this point, and Brian has now put his thoughts into a blog post, The Problem is HR, Not HR Technology. He writes, “
HR departments are chock full of great HR transaction folks. Likewise, they have great recruiters, compliance people and more in these groups. However, is there anyone who understands data analysis, external/Big Data, etc.?
Where are the quants in HR? Where are the statistics and math majors? Where are the social scientists who understand human behavior? Seriously, giving powerful analytic tools to many HR folks today (who lack awareness or skills in these technologies and disciplines) is like giving a chainsaw to a 4-year old. If they ever got it running, you’d have a bloody mess on your hands. If you don’t know the difference between causality and correlation, you have no business playing with analytics.
A rebalancing of the talent within HR organizations is needed today. New skills, capabilities and insights are needed to make HR more relevant and able to exploit today’s new HR technologies.
Ironically, then, HR has its own talent management problem.

HR Organizational Readiness Is the Key Need

If an organization’s people are indeed its strategic advantage, then HR technology should have a prominent position in any organization’s IT strategy. But, as we discussed, most HR groups are not ready to adopt the latest HR technologies. Business leaders, therefore, should focus on developing their HR organizations as well as implementing HR technology.

For some organizations, this means changing their view of HR, from a support function to a co-equal role in business strategy. It also means reversing some of the staff cutbacks that were put in place during the last recession. Finally, it means doing something about the skills gap in HR. In many cases this will mean reaching outside of the traditional candidate pool to find new talent with the quantitative skills needed to effectively use emerging solutions for workforce analytics and other new HR technologies.

Monday, September 23, 2013

Best Practices for SaaS Upgrades as Seen in Workday's Approach

If you're involved with enterprise software, you need to pay attention to what Workday is doing--even if you're not interested in HR or financial systems. Because Workday is one of the best examples of how enterprise applications can and should be delivered in the cloud.

This was one point I took away from Workday's annual user conference in San Francisco and from a day-long series of briefings for industry analysts earlier this month. 

The differences between Workday's practices and the approach of traditional enterprise software vendors are striking. There are several points of contrast, but in this post I'd like to focus on how Workday delivers software upgrades and some new twists in how it does this.

Traditional Approach to Software Upgrades

In the traditional enterprise software model, vendors develop new versions and provide them to their customers that are under maintenance agreements. The customer takes delivery of the new version, installs it on a test copy of the system, migrates data from the existing production version, retrofits any customizations or interfaces with other systems, revises its user procedures, performs system testing,  and migrates all of its users to the new version. In the process, if there is any time left in the schedule, the customer also may investigate how it would like to use any new functionality offered in the new version.

The bottom line is that in the traditional model, software upgrades are both a technical exercise as well as a business exercise. The technical challenges of data migration, retrofitting of customizations, and reworking system interfaces can be significant and can encourage customers to stay on older versions of a vendor's system for many years. When such a customer finally wants to get current on the latest version, the upgrade process can rival the time and expense of the original implementation. The technical aspect can be so much work that companies often retain outside service providers to manage or assist in the effort. The business aspects--accommodating changes to business processes or embracing new functionality--are often jettisoned for the sake of simply getting the new version installed from a technical perspective. As a result, customers often do not realize the benefits of the new functionality that the vendor offers.

The Workday Approach

Workday's approach to upgrades, from the beginning, is simple: it takes responsibility for all technical aspects of the software upgrade, allowing the customer to focus solely on the business aspects. There are at least three reasons that Workday can do this:
  • Workday's object model allows most customizations to be brought forward to new versions of the system with little or no retrofitting.
  • Likewise, Workday's Integration Cloud, based on technology it obtained through its acquisition of Cape Clear,  allow most custom integrations to continue to work with new versions of its system.
  • Since Workday operates the system on behalf of the customer, Workday takes all responsibility for migrating the customer's data to the new version. 
The impact of this last point should not be underestimated. Last year, Workday's CTO, Stan Swete, wrote about how important it is for the SaaS provider to take full responsibility for migrating customer data to new versions: 
[The] Software-as-a-Service (SaaS) model improves service delivery quality by letting the provider own the end-to-end process of development, conversion, and deployment. In the on-premise software world the vendor controls development (and associated QA), but there is a hand off for conversion and deployment. At Workday, the update process is not done until every customer is on the new version. The same team that project manages our development also project manages conversion and deployment.
When it comes to version upgrades, not all SaaS providers are created equal. Some are little more than single tenant hosting providers. Others are multi-tenant SaaS providers, but they deploy new versions as separate instances of the system and allow customers to stay on older versions for long periods of time. This makes version upgrades considerably more difficult if and when customers do decide to upgrade. Workday, as discussed, is at the other end of the spectrum, keeping all customers current on the latest version. Salesforce.com, NetSuite, and Plex, are similar to Workday in this regard, though they may differ in the details of how they do it.

    Further Improvements in Workday's Approach

    This year, Workday has further refined its approach to version upgrades in three ways:
    1. Single production instance for all versions. Previously, Workday would deploy a new version of Workday as a system instance that was separate from the previous version, and Workday would migrate customers in waves from the old version to the new version over a three week period. Workday's new approach is for the current version and the new version to exist simultaneously on the same system instance. Workday will now move customers to the new version by means of a set of "switches" that dictate which features of the system the customer will see. This new approach is possible because of Workday's object orientation discussed earlier.
    2. Continuous development and deployment of new functionality. Instead of holding all functionality enhancements for its periodic version upgrade, Workday is now introducing smaller changes on a weekly basis. This is especially important for small but high-priority changes or for tax and regulatory updates. Contrast this to the traditional vendors, who required many months or years between the time customers request changes and the time they actually see them in updated versions.
    3. Continuous conversion of customer data. As Workday develops new features that require changes to its data model, the single production instance now allows Workday to convert customer data in the background in advance of actually migrating customers to the new version. This reduces the amount of downtime required during the when the customer is moved to the new version. 
    4. Preview instance. Now that there is a single production instance and continuous conversion of customer data, Workday is now able to offer customers a preview instance of the new version, giving customers a longer time-frame in which to evaluate and plan for the new version. Under the traditional model, customers only get a hands-on look at the new version when they take delivery of the upgrade, install it, and convert their data to it in a prototype environment. Workday's approach gives customers much more time and encourages them to make use of the new functionality.
     Swete summarized these changes in a blog post during the user conference:
    Probably the best example of embracing continuous change is happening on the service delivery side of our business. Workday has moved to continuous deployment of new features to a single code line. This move, along with the continuous background conversion of data for new features, enables us to complete updates for our production customers with less scheduled downtime. Application of changes to a single code line reduces the expense of maintaining multiple code lines around each update we do. Moving to continuous deployment also gives us the flexibility to continue to respond to our customers’ requirements when it comes to the number of updates we do each year.
    As Swete indicates, the single production instance, continual development approach, and continuous conversion of customer data allow Workday to scale back from three new major versions a year to just two. The conference audience applauded when co-CEO Aneel Bhusri made this announcement, perhaps indicating that many companies have difficulty absorbing three major upgrades a year. At first blush, the reduction in the number of new versions a year would imply that Workday is slowing down the number of new features per year. But in an sidebar conversations with Workday executives the next day, it became clear that these most recent improvements actually mean that Workday will be introducing more new features each year. The difference is that the smaller changes will be trickled-in on a weekly basis, while major new features will be held for the twice-yearly updates.  As indicated earlier, this approach also allows Workday to accommodate regulatory or tax-law changes on short notice, which have become more common in recent years.

    Workday's core strategy of reducing or even eliminating the technical burden of version upgrades is a best practice for SaaS providers, allowing customers to focus exclusively on business improvement and maximizing the value of their system investment. More SaaS providers should follow this example.

    Postscript: Over at Diginomica, Phil Wainwright has two good posts covering some of these same points:
    Note: Workday covered my travel expenses for attending its user conference.

    Update, March 19, 2014: This Workday post by David Clarke provides a detailed explanation of Workday's single codeline development process.   

    Related Posts

    The Simplicity and Agility of Zero-Upgrades in Cloud ERP

    Monday, July 30, 2012

    2012 Technology Trends: Call for Survey Respondents

    Over at Computer Economics, we've now launched our 2012 Technology Trends survey, and we're looking for qualified IT executives to take a 15-minute survey about their technology investment plans.

    What's in it for you? If you complete the survey, we'll send you a complete copy of the final report (a $995 value).


    In this year's survey we're asking about your organization's adoption and experience with 13 technologies:
    • ERP
    • Customer Relationship Management (CRM)
    • Supply Chain Management
    • Human Resources Management Systems (HRMS)
    • Data Warehouse/BI
    • Social Business/Collaboration Systems
    • Legacy System Renewal
    • Software as a Service (SaaS)
    • Public Cloud Infrastructure (IaaS)
    • Platform as a Service (PaaS)
    • Unified Communications
    • Desktop Virtualization
    • Tablet Computers. 
    Want to know more? See a summary of the final report from last year.