It was 30 years ago October that I took my first job at Unisys supporting payroll for K-12 school districts. I’ve seen and heard it all, and I know for a fact just how hard it is to integrate disparate systems with legacy data models, processes and frameworks. One of the reasons I found the move to Ceridian so exciting was to be liberated of that headache. It takes guts to start over, and with Dayforce HCM, we’ve done exactly that—built a unified system with no need for integration (or interfacing) between modules. It makes product development infinitely easier. Combine that with deployment in the cloud, and you have the kind of story that has customers choosing Dayforce HCM in large numbers. I’m not going back, and you’ll have to decide for yourself when it’s time to make the journey. In the meantime, here’s a little more on what I mean about modern HCM technology in 2013….
Integrated Technology: Complicated, Certainly Not Elegant
HCM used to be straightforward—at least compared to today. The complexity of regulations surrounding employee pay, shift scheduling and benefits administration—the list goes on—has become mind-boggling. Today, everything moves faster and faster. Change is never-ending. Plus, employees want choice in their schedules and in the ways they receive pay. They want their benefits to be there when they need them, and they want control over the basics of their employment. Managers and HR, too, want flexible technology to deal with these realities.
Tackling all that in an effective, efficient way just hasn’t been truly possible with the way technology has evolved in our industry. As you’ve heard me say here and here, dependence on technology integration is the culprit. It’s complicated and certainly not elegant. Applications in silos just can’t communicate in the ways they must. When you really think about it, the complexities of overly integrated HCM technology actually amplify the complexities that are already a part of modern HCM. You just have to accept that when you choose integration, you accelerate the level of complexity inherited as a result.
Presenting a Unified Front in the Back—Eliminating Complexity
Now it’s time for me to take a biased position: Dayforce HCM has eliminated the need for integration. It’s a unified system for HCM. That’s a major leap forward, a huge departure from everything that has been available in this marketplace. Giving users a friendly, single point of entry is one of Dayforce HCM’s strong suits. But it’s the unified front in the back—the back-end, that is—that really sets Dayforce HCM apart and solves so many of the problems I just described. It’s just one application for payroll, time and attendance—a first in our industry. And it’s operating under just one rule engine and depending on zero interfaces. One set of data represents everything, making it possible to offer the first real-time, single system for time and pay.
Integration: A Thing of the Past?
Listen, I’m not going to make gigantic “pie-in-the-sky” claims about integrated vs. unified HCM applications. But this I am going to say with resolve: Unified systems are less complex than integrated ones. It changes the game with respect to how they operate, and the benefits are demonstrated in user experience and real-time interactions. Ultimately, the market will decide.