PARIS
If Workday is the belle of HR systems, Oracle is undoubtedly her ugly sister. Having implemented both, let me share some examples to prove my point. (The Oracle system here is the one that Oracle actively sells, Fusion HCM Cloud, having retired its shoddy predecessor, EBS, and putting PeopleSoft on life support.)
OVERALL SYSTEM USER FRIENDLINESS
In the 20 years I've known Oracle, one thing has not changed: its scant regard for customers and the most obvious consequence, poor user friendliness, reinforced by a technology that seems always a generation behind others. Key example: In most consumer-grade platforms you can get further details and actions from a given object you're looking at by clicking on the dots that can be found around that object, usually at the upper-right corner (just check any Google page) which in addition you can check by opening another tab.
As expected from a modern HR system like Workday, if you're looking at an org chart and wonder who a specific employee is, all you have to do is right click with the mouse on the dots and that employee record opens in a separate tab for you to peruse their data. Once your curiosity has been satisfied, just close that tab and go back to where you were, the org chart, to continue the work you were doing there.
No such luck if you're using Oracle Fusion. This supposedly latest-generation tool will display a pretty average org chart (see below) and should you want to see the details of a given employee there's no capability to open a tab with that employee's file. You'll have to go back to the landing page, search for that employee and then open their record. And then if you want to go back to where you were (that is, if you still remember what you were doing) you'll have to start all over again, go to the org chart, enter the team you're looking for and the system will display the page you were on eons ago.
As for the search bar, Oracle technology is still stuck in a time warp: it is case and accent sensitive. So if you have an employee called Pénélope (in French) or Penélope (Spanish), and you enter "Penelope" you'll get no results. Obviously, no Oracle developer has ever used Google and other similarly ubiquitous internet tools.
Menu jumbo-mambo
In Workday, action menus are organized alphabetically, which is the logical way to go about things on Planet Earth. The five most frequently used actions appear first, which is a great time saver. On Planet Oracle, actions appear randomly, making you waste quite some time going up and down and across the the screen in hot pursuit of the action you need. Nobody ever told Oracle that making life easier for the customer should be top priority.
SYNC ISSUE
We all know that "integrated" systems are rarely so, but what is amazing is that with Oracle even within a single module or feature thereof you still run into synchronization issues. Let's say that as a manager you perform an action in Workday (e.g., move an employee from your team to another) and this action requires an approval from another role (say, HR.) You log in as that HR person and here's the approval task awaiting you. Try and do the same in Oracle: you'll have a 3 to 5-minute time lag before the action travels from Manager to HR. In real life it doesn't really matter, but in project mode when you're constantly testing system setup and configuration it soon becomes bothersome and frustrating.
Language enablement is another area where Oracle's sync'ing prowess is, shall I say, sinking? If you need to turn on a certain number of languages to go with your global deployments, with Workday it can be done in a couple of clicks and you see the results instantly. If you are unfortunate to have selected Oracle Fusion, you need to request language activation with Oracle Support. If you happen to do this on Monday, too bad, since this is done over the weekend. And since it takes half a day per language, your global implementation may have to wait an additional couple of weeks before you can go in and start checking translations.
SECURITY AND WORKFLOW
Whereas Workday can handle complex security requirements via domain and business process security, Oracle is very limited, often offering only global roles with no possibility to restrict per country/company or other criteria. In addition, whereas Workday proposes role names that are meaningful (Compensation Partner, HR Partner etc.) Oracle suggests roles with inordinately long names to remind users what that role can do (HRWithCompensationNoNotification). Can't get uglier than that.
Managing role conflicts is always an issue the more complex system implementation is. Whereas Workday has its own challenges, business process conditions work pretty well. (Glossary: business conditions which allow you to decide how a specific role at a specific step in a given workflow should behave.) Oracle, on the other hand, doesn't manage role conflict satisfactorily. A user case I struggled with during an implementation of Fusion is the typical case of an HR user who is manager of an employee for whom he also plays the role of HR. If this manager initiates an action as manager and this action requires HR approval, you'd think since this manager is also this employee's HR they don't need to approve themselves. You'd be wrong! Oracle will make you do exactly that, which is absurd. You won't have this issue with Workday because its workflow configuration includes the possibility to exclude someone from approving a task if they are the initiator.
In summary, Oracle's workflow capability can't hold a candle to Workday's which is extremely rich and allows for a level of granularity and sophistication Oracle customers can only dream of.
HALF-BAKED SYSTEM
Both Workday and Oracle provide various seniority dates to be used where relevant depending on whether one is interested in a hire date, or a company date, or time in a position etc. The similarities end here: whereas Workday offers straight out of the box all these dates (as a user just go to an employee's record file and you'll see all the dates for that employee), Oracle will ask the user to launch a calculation for the dates they are interested in, otherwise they just remain empty not because some data is missing but because you haven't requested its calculation!!! Use case: You launch a promotion action on an employee and in order to help you make up your mind you need to know how long they have been in their current position.
In Workday, the data display effortlessly so you can continue with your promotion task.
In Oracle, you'll probably be met with an empty field, so you'll have to abort the task (remember you can't have two tabs or pages open at the same time in Oracle), go to the Seniority Dates screen in Quick Actions, request a calculation, and then start the promotion task all over again. Awful user experience. Got forbid that at that moment you need to check another piece of information (say, compensation). You'll have to exit the promotion task one more time, go to Compensation, view the data and, if you still have not slit your throat in despair, launch a THIRD time the promotion task. One of the nuttier design decisions I've ever seen in my quarter-century experience of HR systems.
 |
| Simple and available - the Workday way |
DATA LOAD/MIGRATION
I could rant for days on how complicated data management is with Oracle, but suffice it to give one example: data inactivation. Let's say that you created a contract type which is becoming obsolete. To inactivate it you will need two rows: Start and End Dates of the period when the contract was valid and another row with the Start and End Dates when it is no longer valid. Now, since the End Date of Inactive is till the end of time Oracle requires you to put something like 4532. Why this date and not 9999 the way they do it at SAP? And why do we even need to put an End Date? Because Oracle is still run by the same people who created the relational database and keep on thinking along the lines of this technology that harks back to the last millennium.
QUESTIONABLE DATA MODEL
Every vendor has their own data model which has been a perennial issue in system-to-system integration. None is worse than the manager data model as pursued by Oracle versus Workday. With Workday, a manager is appointed on an organization (or team) and any employee part of that team will share the same manager. Clear and straightforward - even if some first-time Workday users may be taken aback at the logical consequence of this choice: a manager will always sit in an organization above the one holding his/her team. An employee is hired into an organization. With Oracle, things are illogical and a source of endless confusion to users: a department with 3 employees can have 3 different managers since employees are linked directly to a manager, and in this case each can have a different manager. A department manager can be assigned (as a system admin task) but only employees without a directly assigned manager will inherit that departmental head as manager. You can easily see how ugly this can turn with different employees having different managers, some sharing the same or having none whatsoever.
Calculated Fields vs FastFormulas
In short, both are ways to write custom rules such as a calculation of a compensation element or a condition/eligibility rule to apply to who should get that compensation component. And that's where the resemblance between the two stops. Whereas Workday has innovated with an easy-to-use feature whereby you assemble your rules from different objects Lego-like, Oracle is still stuck in last millennium's technology -hardly surprising when you know that FastFormulas are a transplant from Oracle's much-hated EBS HR system which only a database nerd can make sense of. See below screenshot from the two to get a sense of how Workday has managed to become the default tool of HR users.
 |
| Today's tool vs yesterday's |
Custom Objects vs Flexfields
Here again, we have similar objects aiming at extending a system's capabilities beyond what was initially supplied by the vendor. But whereas Workday makes it easy to build, use and maintain such objects, Oracle's Flexfields have serious limitations. One of the most egregious being that on any screen it is linked to, a Flexfield appears systematically at the bottom. To give you an example, let's suppose that in a Hire screen in addition to the standard "Business Title" field, you want to add a related field called "Local Business Title". Since Oracle doesn't offer a second such field you'll have to create it via Flexields. So be it, except that being a Flexfield it appears all the way at the bottom of the screen, probably next to a data section on addresses or blood type which have nothing to do with it. Very confusing to the user. Worse, if the Flexfield is to be filled with a value depending on what you entered in the standard field, you'll have to scroll all the way up to remind yourself what you entered and, having duly taken note of it, scroll all the way back down to enter a value for the second, related, object. In terms of customer experience, it's simply awful, but on a par with Oracle's products.
DOCUMENTATION
The differences between the two vendors couldn't be starker: whereas Workday has a flourishing Community where you can find an easy answer to set-up documents, share best practice ideas with other customers, suggest enhancements to the tool (and track its status), Oracle is...well, Oracle. Its Help Center is anything but helpful. All you get is some marketing PowerPoint presentations, fluffy documents, links to attend Events and that's it. If men are from Mars and women from Venus, well Workday is clearly from Planet Customer and Oracle is still stuck in its Planet Larry Ellison - or Technology: the two are interchangeable.
So, why do some companies buy it?
I could go on for hours and inflict thousands of additional pixels on your retina, but I think you get my drift. Which prompts the following question: with Workday being manifestly so superior to Oracle in every way, why do some customers still buy Oracle for their HR needs?
First, you have to realize that only current customers (those who are using Oracle database or middleware or Financials or legacy EBS system) have any interest in envisioning the possibility of purchasing Oracle's Fusion system.
Second, a majority of Oracle customers (both PeopleSoft and EBS) moving their HR system to the cloud do it not with Oracle Fusion, but with...Workday, proof enough of what they really think of their current vendor.
Third, as for the minority who decides to stick with Oracle, you may still wonder that only masochists would spend good money on bad technology. And here you'd be more right than you may think. When I referred to these customers as buying Oracle Fusion HR, actually I wasn't being accurate because one of Oracle's (many) dirty little secrets is that these customers actually don't buy Oracle HR because ...they get it for free! Oracle just tells them that if they take Fusion Financials, they'll get HR for free. Most customers make the decision that sure it looks ugly but you don't look a gift horse in the mouth, do you? So, they decide to plod on and make the best out of a bad situation.
It's not dissimilar to those millions of consumers who have a regular meal at McDonald's knowing it's not good for their health (or their palate) but that consideration is outweighed by price and convenience.
So, my advice to Oracle customers as they head to Oracle CloudWorld is to remind them of that old phrase: you get what you pay for. And as you've seen it in this analysis, there's no denying it: Workday blows Oracle out of the water.
