Workday · Cross-functional
Workday is one system. Your organization is not.
Workday's promise is one unified platform across HR and Finance. That unification is exactly where the hardest, most political battles get fought. Here's where the seams strain, and the playbook to govern them.
The pitch is seductive: one system, one data model, HR and Finance finally speaking the same language. That unification drives the platform's real value. It is also the source of its hardest problems.
Put HR, Finance and IT on one shared foundation and you lose the ability to paper over the places those functions have quietly disagreed for years. The platform does not create cross-functional conflict. It exposes it, and hands you a deadline to resolve it.
Handoffs hide the conflict until testing
Seam 1
The foundation data model is the real negotiating table
At the center sits a model that forces a conversation most organizations have never had: how does HR's view of the organization reconcile with Finance's view of it?
HR
HR thinks in
Supervisory hierarchies, positions, jobs, worker records. The organization as a structure of people and reporting lines.
Finance
Finance thinks in
Cost centers, ledgers, worktags, allocations. The organization as a structure of money and accountability for it.
Design authority
The cost
If ownership of the worktag taxonomy is fuzzy, every downstream report, allocation and security rule inherits that fuzziness. Reconciling a misaligned model mid-project easily burns six unbudgeted weeks.
Design authority
The move
Treat the design as a cross-functional negotiation led by one named design authority. It is never a finance task with HR copied on the emails.
Seam 2
Competing calendars are a constraint
HR
HR's calendar
HR runs on open enrollment and performance cycles.
Finance
Finance's calendar
Finance runs on the close, quarter end and year end.
Design authority
Map the blackouts before you pick a date
Neither pauses for your project, and they rarely align with each other.
Dropping a go-live squarely on year-end close creates maximum cost, maximum stress and operational chaos. Map every functional calendar first, then schedule around the immovable objects.
Seam 3
One record, many masters
An employee, a worker and a resource are increasingly the same object seen through different lenses. When one change to a worker ripples simultaneously into payroll, budget and security, data ownership stops being a policy debate and becomes an operational necessity.
HR
What usually happens
The position versus job management call gets made inside the HCM workstream, in isolation, because it looks like an HR decision.
Finance
The cost
Months of retrofitting once Finance realizes it breaks their headcount-planning model, at exactly the point where the configuration is hardest to unpick.
Design authority
What it actually is
A decision that defines how headcount, budget and vacancy are modeled for the whole organization.
Design authority
The move
Decide cross-functional data rules together, in one session with both functions present, or pay to redo them later.
Seam 4
Security does not respect your org chart
A manager in HR and a cost center manager in Finance are often different people with different rights over overlapping data. The security model handles that nuance well, but only if the people designing the roles are looking across both functions at the same time.
HR
Roles designed in the HR silo
A manager in HR
Finance
Roles designed in the Finance silo
A cost center manager in Finance
Design authority
Where it surfaces
Designed in silos, security becomes the place cross-functional assumptions go to collide, usually loudly, during user acceptance testing. By then the roles are built, the test scripts are written, and the fix touches both.
Seam 5
Reporting is where the disagreement finally shows
Two functions can run happily on their own definitions until a single report has to satisfy both. Then headcount means two things, and the number on the page is wrong for somebody.
Headcount
What HR meansActive workers, including those on leave
What Finance meansFunded positions, whether or not anyone is in them
Manager
What HR meansThe supervisory relationship in the hierarchy
What Finance meansWhoever approves the spend against the cost center
Department
What HR meansThe supervisory organization
What Finance meansThe cost center carrying the budget
Start date
What HR meansThe date employment begins
What Finance meansThe date cost begins accruing, which may differ
Vacancy
What HR meansA position with no incumbent
What Finance meansBudget available and unspent
Design authority
The move
Agree the definitions before the reports are built, and write them down where both functions can see them. Every one of these disagreements is cheap to settle in design and expensive to settle in a board pack.
Across every seam
The governance that makes it work
Design authority
One design authority per seam
A named individual who can make the call across both functions, not a committee that reaches consensus slowly. Two opinions and no authority is the default failure.
HR, design authority and Finance together
Joint sessions, not serial reviews
Both functions in the room at the same time. Circulating a design for comment produces agreement in writing and disagreement in practice.
Design authority
Decisions logged with their reasoning
Why the call was made, not just what it was. These get re-litigated, and the reasoning is what ends it quickly.
Every one of these seams existed before the program started. What changed is that one shared data model now forces a single answer, on a date.
Put independent eyes on your program.
If you're betting tens of millions on an ERP program, a candid second opinion is the cheapest insurance you'll buy.