Most leaders don’t need a PSA to tell them that human capital management is becoming way more complicated. It’s hard to keep everything “running smoothly” when you’re juggling hybrid workers, AI/human teams, and an awkward combo of legacy and modern tech.
The biggest problem most businesses overlook, though, is misalignment between their staff. They still assume HCM is something that only HR teams need to worry about.
It’s no wonder so many teams end up frustrated. Deloitte has even warned us that up to 70% of HCM implementations don’t deliver the expected ROI, and a huge chunk of that traces back to ownership issues. Realistically, if your HCM team isn’t built like a cross-functional task force instead of a “tech upgrade committee,” you’re never going to get the outcomes you need.
Further reading:
Why do HCM Projects Need Cross-Functional Ownership?
It’s honestly far too easy to make everything related to employee experience “HR’s job”. Really, though, modern HCM systems connect with so much more than you’d expect. They deal with payroll, identity, compliance, workforce planning, analytics, benefits, scheduling, and even security.
That means one configuration tweak in HR can ripple through Finance’s cost centers, IT’s identity management, Legal’s privacy commitments, and even frontline operations.
We’ve already spoken a lot about how workplace and employee experience needs to be a “team sport” these days. When HR, IT, Finance, and Legal don’t show up as one unit, performance drops and innovation disappears. But cross-functional setups drive 60–70% higher effectiveness in large-scale transformations.
Honestly, the stakes are getting heavier. Hybrid work created this weird tug-of-war between digital access, security, and flexibility. Then the EU AI Act arrived, and suddenly Legal’s at the table asking pointed questions about model explainability and automated decisions. Finance is sweating over the HCM contract because payroll accuracy hits the P&L. IT wants cleaner data before they migrate anything. Everyone’s got skin in the game now.
Just look at BT Group: they unified HR, IT, Legal, and Data around one SAP SuccessFactors program and wound up saving 1 million productivity hours, just with proper ownership.
When no one owns the whole puzzle, nothing fits. When everyone owns their piece, the system finally starts to make a difference.
What Roles Are Essential For Successful HCM Programs?
When an HCM project doesn’t have clear ownership, it doesn’t implode dramatically. It just unravels. It starts with tiny delays: HR is waiting on IT, IT is waiting on Finance, Finance is waiting on Legal, and Legal is waiting on “more information.”
Meanwhile, the implementation partner keeps asking questions nobody feels authorized to answer. I’ve seen projects lose six to nine months to this strange limbo where everyone’s technically involved but nobody is accountable. It’s like organizational purgatory.
Data migration is usually the first real casualty. Without a dedicated owner, it becomes an endless game of “who knows where that lives?” Duplicate records, mismatched job codes, old cost centers that someone forgot to retire in 2018, they all come crawling out of the shadows. You can’t configure anything properly when the data’s a mess, so the delays compound.
Then integrations start failing because no one mapped them end-to-end. Or managers refuse to adopt workflows because nobody trained them early enough. The moment the system doesn’t meet expectations, employees go hunting for workarounds (hello, shadow AI again).
So let’s look at the teams that really do need to be involved.
HR: Process Owner, Experience Designer & Workforce Architect
Starting with probably the most obvious part of your HCM team: HR. These are the people often buried under unrealistic expectations. People assume HR will “own the system,” “manage the vendor,” “fix the data,” “rewrite the processes,” and somehow also “keep business-as-usual running.” It’s impossible. But HR does play the most foundational role: they shape the work itself.
- Redesigning every major people process, from onboarding to mobility to performance to pay cycles.
- Mapping employee journeys and removing friction (because employees notice every tiny snag).
- Defining people data standards: job architecture, competencies, fields, naming rules, lifecycle triggers.
- Interpreting EX signals like survey feedback, sentiment analysis, and ticket patterns.
- Setting the “human judgment” boundaries for AI-driven recommendations.
Patagonia proves what happens when HR actually leads the design side. After they rebuilt performance and mobility processes around real user behavior, managers finally had visibility they’d been begging for, and engagement lifted because workflows made sense again.
IT: Architecture, Integrations, Security & AI Governance
IT usually walks into an HCM project with both concerns and confidence. They know the tech side better than anyone, but they also know the system is going to touch 40 things nobody told them about yet. This is why IT isn’t a “supporting” function in an HCM team.
They’re a core owner, especially when it comes to architecture, identity, and security. They’re the ones building the integration blueprint from the ATS to Finance to UC platforms like Teams and Slack. Plus, they’re the ones doing the data cleansing nobody else wants to admit is necessary.
Then there’s the AI avenue they need to deal with. Every automated recommendation, every predictive model, and every workflow that leans on machine learning falls under IT’s guardrails. If IT doesn’t provide safe, sanctioned AI tools, employees will find their own.
Look at the City of Los Angeles. Their Workday + AI retention work only succeeded because HR and IT co-owned data governance from day one. Without that partnership, the models would’ve been unreliable noise.
Finance & Payroll: Accuracy, Cost Control, ROI
If HR carries the emotional weight in an HCM team, Finance deals with the operational risk. Then payroll carries everyone’s stress. It’s so easy to underestimate how many downstream calculations depend on the tiniest configuration choice.
Finance owns the money flows: comp, budgeting, GL integration, tax rules, so when they’re not involved early, the whole system feels like a house built on quicksand. Same with Payroll. They’re the ones who know the quirks: union rules, region-specific allowances, and statutory reporting weirdness that only makes sense to people who live inside payroll systems. Ignore that experience, and you’ll pay for it, literally, on go-live day.
Payroll accuracy isn’t a “nice to have.” It’s the bedrock of trust. Miss one cycle, and employees question everything else the system does. Workers will tolerate a lot, but not mistakes that hit their paychecks.
Finance also holds the ROI lens. They’re the ones modeling cost-per-hire reductions, turnover savings, process efficiency gains, and the ripple effects of better EX. When Finance is fully engaged, HCM optimization becomes measurable.
Legal & Compliance: Privacy, Contracts, Regulatory Alignment
We’ve said it already, but it’s worth repeating because people forget just how much lives inside an HCM system. You’re talking about pay details, performance notes, medical leave info, right-to-work checks, all the way down to how someone behaves at work if you’re using any kind of AI analytics. It’s basically the most sensitive drawer in the whole company.
Legal’s role is to keep the company out of the headlines. Between GDPR fines, pay transparency rules, biometric data restrictions, and now the EU AI Act tightening expectations around automated decisions, Legal’s involvement is more important than ever.
They’re the ones who review the vendor contract and spot the clause everyone else skipped. They ask, “Where is this data stored?” and “Who has access?” and “Can this model explain itself if an employee challenges a decision?” Plus, they’re the people who push for a formal risk register instead of the “we’ll deal with it later” approach that destroys so many projects.
When Legal isn’t at the table early, the HCM setup becomes a legal liability waiting to surface. When they are there, the HCM team builds something defensible, trustworthy, and future-proof.
Internal Communications & Change: Clarity, Adoption, Manager Enablement
This is one of the groups in the modern “HCM team” that often gets the least attention. People act like internal comms is just sending a few emails and recording a couple of how-to videos. Meanwhile, the entire success of the rollout depends on whether employees understand what’s happening, trust what’s happening, and actually use the system the way it was designed. None of that happens by accident.
Adoption isn’t a training problem. It’s often a clarity, timing, and communication problem. So Comms needs to be the connective tissue of the HCM team. They build the narrative that keeps everyone grounded when workflows get messy.
They translate legal-sounding updates into something normal people can digest. Plus, they prepare managers, who are absolutely the make-or-break audience, with talking points, Q&As, and reminders delivered where they actually work (like within Teams or Slack).
