The platform isn't the transformation — the hire-to-retire model is
HCM has stopped being a back-office system; it is now how employees experience the company. But a Workday or SuccessFactors implementation doesn't fix how talent demand enters, how approvals route, how onboarding hands off, or how performance is proven. It digitizes whatever flow already exists. Standardize a broken hire-to-retire model and you get a faster broken one — with adoption stalling because the software made the dysfunction visible, not gone.
Deloitte's framing is exact: people over platforms. The organizations that win don't buy their way to a better HR function; they read and fix the operating model first, then let the platform amplify it.
The platform lands. The adoption doesn't
HCM rollouts rarely fail on the software. They fail where the hire-to-retire model underneath was never fixed — and the number that exposes it is adoption.
organizations report their new HR-tech implementations fail to meet adoption expectations — a structural risk, not a marginal one.
organizations that deploy HCM effectively are 2.3× more likely to be high-performing — the upside of fixing the model, not just the module.
Workday and SuccessFactors both work. The split isn't the software — it is whether the hire-to-retire model beneath it was standardized. Adoption stalls where the flow was never fixed; performance compounds where it was. The platform amplifies whichever one it lands on.
Requisition
Approve & route
Onboard & enable
Perform & pay
Develop & retain
The employee lifecycle as one connected journey — adoption breaks worst at Onboard and Perform & pay, the handoffs a platform digitizes but a standardized model has to fix first.
Platform over people fails. People over platforms holds.
The instinct is to let the HCM rollout be the transformation — new system, new HR. But the platform inherits the hire-to-retire flow it lands on. Digitize an onboarding that drops handoffs and you get faster drops; automate approvals that run by exception and you scale the exceptions. The sequence decides whether adoption holds.
- Onboarding handoffs still drop — now on-screen
- Approvals still route by exception, faster
- Performance is reported, not proven
- Users revert to old flows; adoption decays
- The spend is committed either way
- One governed intake for talent demand
- Approvals set by rule, not exception
- Onboarding handoffs owned end to end
- Workforce metrics trace to governed work
- Adoption holds because the flow works
Standardize how a hire enters, is approved, onboarded, proven, and developed — then the platform earns its return. A fixed model is the prerequisite for adoption, and past that for any workforce AI that acts on the model without a human in every loop.
GSDPI, applied to hire-to-retire
The same five stages that read the value chain read the employee lifecycle. Here is the sequence — each a place a hire-to-retire model usually breaks, and what "governed" looks like instead.
-
G
Get Requisition & demand
Standardize how talent demand enters. Every requisition arrives through one governed intake with the role, level, and justification defined — not a mix of emails, side deals, and re-orgs the platform can't reconcile.
-
S
Sort Approve & route
Replace exception-based approvals with a governed rule — who approves a hire, at what level, on what threshold. Routing is consistent, so the platform's workflow reflects reality instead of fighting it.
-
D
Do Onboard & enable
Own the onboarding handoffs end to end — recruiting to IT to manager to payroll. The drops between those teams are where new hires stall and adoption first cracks; a governed handoff is the biggest single fix.
-
P
Prove Perform & pay
Performance and pay reconcile to governed work, not narrative. Workforce metrics become numbers held to a Traceability Ratio — so a headcount, a cost, or a rating traces to something real.
-
I
Improve Develop & retain
Give the development-and-retention loop an owner, and let the exit signal feed the next requisition. The model compounds workforce capability instead of re-hiring into the same broken flow.
New Insights, the day they publish.
The operating-model reads behind ERP, AI & services — a short note when one’s worth your time.
New posts & Insights only. Unsubscribe anytime.
Where the hire-to-retire flow breaks — point by point
The problems an HR leader feels as "low adoption" resolve, on inspection, into specific breaks in the model the platform was dropped onto. The six that carry the most weight:
Onboarding handoffs drop between teamsDo
A new hire passes from recruiting to IT to the manager to payroll — and each handoff is a place the baton drops. The platform shows a green onboarding task while the laptop hasn't shipped and access isn't provisioned. This is where day-one experience — and adoption — first cracks.
Performance is reported, not provenProve
The platform reports ratings, headcount, and cost — but the numbers trace to narrative, not governed work. A rating means different things to different managers; a headcount doesn't reconcile to who is actually delivering. Reported metrics a board can't defend.
Approvals route by exceptionSort
Who approves a hire — and on what threshold — is decided case by case rather than by rule. The platform's approval workflow then has to model the exceptions, so it's fought or bypassed. Governance that only exists on paper isn't governance.
Requisition intake is inconsistentGet
Talent demand enters through a mix of emails, re-orgs, and side deals — with role, level, and justification defined differently each time. The platform can only be as clean as the intake, so inconsistent demand becomes inconsistent data from day one.
Users revert to old flowsAdoption
When the model underneath didn't change, people keep their "real" process in spreadsheets and side channels — the platform becomes a system of record no one trusts. Migration is complete; adoption sits low. The tell that the flow, not the tool, was the problem.
The exit signal never feeds the next hireImprove
People leave and the reason leaves with them. Offboarding is a checklist, not a signal — so the same role is re-hired into the same broken flow. A closed loop would turn every exit into a correction; instead the model just repeats.
How ETEGY reads it
Adoption doesn't fail because Workday or SuccessFactors is bad. It fails because the hire-to-retire model underneath was never standardized. People over platforms: fix the model first, then let the platform amplify it.
A Zero-Based read of the hire-to-retire model across the GSDPI lifecycle — before the platform decision — ranking the pains, gains, and requirements, then holding workforce metrics to a Traceability Ratio. Fix the flow; then deploy the platform. See the ZBT Discovery →
The Hire-to-Retire Flow Map
The whole argument on a single page — the employee lifecycle mapped to GSDPI, where adoption breaks at each stage, and the question to ask before the platform decision. Built to circulate: take it into a board or operating review.