Breaking silos: why HR, IT, and Finance must own Workforce Intelligence together

Most organizations talk about workforce intelligence as a destination, but few have built the foundation it depends on: reliable workforce capability data. Skills initiatives that were supposed to transform internal mobility are falling short. AI transformation programs, including efforts built around tools like Cornerstone Workforce AI, struggle to sustain themselves because basic skills questions about workforce readiness go unanswered. Our research “The board's new mandate to CIOs and CHROs”, found this pattern repeating across organizations: contractor spend increases quarter after quarter while the HR team tries to understand why internal capacity never seems to match demand.

Each problem gets analyzed in isolation. HR sees change management issues and reaches for better communication or stronger executive sponsorship. Finance treats it as a cost control problem and pushes for tighter procurement processes. For IT, it looks like just another integration request, so the technical requirements get scoped and the ticket moves forward.

What almost nobody sees is the common thread running through all of it: workforce capability data that doesn't exist, can't be trusted, or sits fragmented across systems where no one can actually use it. Workforce capability data has a specific meaning here, covering what skills people in the organization actually have, how strong those skills are, and how recently they've been demonstrated or verified. It's the raw material that, once reliable and governed, becomes workforce intelligence organizations can actually act on. It's a problem that sits at the intersection of three functions, and the organizational design gives no one both the authority and the incentive to solve it. Until that changes, the gap persists. People rarely disagree with the logic once they see it; the real obstacle is that nobody owns pulling the right people into the room.

CHROs, CIOs, CFOs: same problem, different views

The three functions affected by poor workforce data quality get measured on completely different outcomes, which means the problem manifests differently in each domain and never surfaces as shared accountability.

None of these three leaders is measured on workforce capability data quality as a shared outcome, which is why the partnership never forms. Misaligned incentives combined with unclear ownership create conditions that persist because no one has the organizational mandate to change them unilaterally.

The CHRO's View

CHROs get measured on talent acquisition speed, retention rates, employee engagement, and learning program delivery, none of which directly surface data quality as a cause when they go wrong. When an internal mobility program underperforms, it looks like a change management failure. When a skills initiative loses momentum, it looks like poor adoption. The data underneath remains invisible because the measurement framework was never designed to make it visible. It shows up in the numbers too: 73% of employees are already change fatigued, and 74% of managers aren't equipped to lead transitions. (Gartner, 2024)

The CFO's View

CFOs get measured on cost efficiency, ROI, and financial performance of business units. When contractor spend runs over budget or an AI initiative fails to deliver expected returns, those appear as line items requiring course correction rather than symptoms of a deeper data quality problem. The connection between a fragmented HRIS architecture and a £4 million overspend on external hiring requires someone to draw a line that standard financial reporting never draws, because workforce data quality isn't a category in the chart of accounts. At a macro level, the number is stark: skills gaps are projected to cost businesses $8.5 trillion in unrealized revenue annually by 2030. (World Assessment Council, 2025)

The CIO's View

CIOs get measured on systems reliability, security, and successful delivery of technology initiatives within scope and budget. Workforce data quality sits in an uncomfortable middle ground, technically in HR's domain but architecturally requiring IT's deep involvement, which means it falls through the gap rather than landing clearly in either function. IT gets pulled in to support HR initiatives but is rarely accountable for the data quality outcomes those initiatives depend on, while HR owns the outcomes but lacks the architectural capability to ensure the data foundation can support them. 55% of HR leaders already say their current technology doesn't meet future business needs, and 46% say it actively hinders the employee experience. (Gartner, 2024)

How to govern workforce intelligence

The organizations that have made this work treated workforce capability data as shared infrastructure with joint governance, rather than as an HR initiative with IT support and CFO sign-off. In practice, that means a few specific structural changes:

Cross-Functional Steering. The steering committee spans all three functions from the start, as a decision-making body with the authority to allocate budget, set priorities, and resolve conflicts.

Budget Outside HR. Budget ownership sits with the CFO or COO rather than with HR, because infrastructure investments belong on the enterprise balance sheet rather than the people function's operating budget.

Named Accountability. There's explicit accountability for data quality that cuts across functional boundaries, typically a senior leader who operates at the boundary between functions, someone who can turn HR's requirements into specifications IT can build against, and just as easily explain IT's constraints in terms HR can weigh.

Joint Success Metrics. Success metrics are defined jointly before the first investment, and they're business metrics rather than HR metrics: what percentage of strategic roles were filled internally, time-to-fill reduction for critical positions, how much contractor spend decreased, and success rate for AI initiatives using workforce capability data.

Why workforce intelligence belongs on the enterprise balance sheet

The goal is enterprise infrastructure that happens to live in HR's domain, built and governed as infrastructure rather than as a better HR system. Think of it in the same category as ERP for finance, CRM for sales, or supply chain management for operations. That distinction changes everything about how it gets funded, governed, and measured.

Who owns workforce capability data?

Every program that depends on skills data shares the same underlying condition: someone has to own the data quality question with the authority and accountability to actually answer it, and that ownership has to be recognized and resourced by the organization as a permanent operational responsibility rather than a project deliverable.

That condition doesn't exist in most organizations today. The technology is available and the ROI is demonstrable; what's missing is that the first conversation has never happened. The CHRO, the CFO, and the CIO have never sat in a room together and asked: Who owns workforce capability data as operational infrastructure? What does that ownership require from each of us? How do we measure whether we're succeeding?

How do you start the workforce intelligence conversation across functions?

That conversation doesn't require a consultant, a transformation program, or a new organizational structure. It requires one person, probably the CHRO, to bring the other two into a room with a specific business problem, a specific cost, and a specific question about what it would take to solve it together.

The business problem should be real and current, for example:

• A transformation program that keeps overrunning because capability gaps are invisible.

• Contractor spend that climbs every quarter.

• AI initiatives that fail because no one can verify workforce capabilities.

The cost should be quantified, even if it is roughly. The question should be simple: "If we could actually see what capabilities exist in this organization right now, how confident people are in those capabilities, and how recently they've been demonstrated, what would change about how we make decisions?"

Why workforce intelligence can't wait: AI, talent competition, and budget pressure

AI transformation is accelerating, but the results are uneven. In the US, 88% of organizations use AI in at least one function, yet only 39% can report a measurable impact on EBIT. (McKinsey & Company, 2025)

Talent competition is intensifying while organizations sit on internal capability they can't see, can't find, and can't deploy, paying premium rates for external talent while internal people remain underutilized. Budget scrutiny is tightening, and every pound spent on contractors or transformation program that goes nowhere has become a question about whether the organization has the foundational intelligence to operate efficiently.

When workforce capability data becomes reliable operational infrastructure, strategic workforce planning stops being guesswork, AI transformation becomes feasible, internal mobility becomes practical, learning investment becomes targeted, and resource deployment becomes dynamic. This is a fundamentally different operating model where workforce capability is as visible and actionable as financial data or customer data, but it only works if all three functions, HR, IT, and Finance, own it together.

The organizations that build this partnership now will be able to see what they have, deploy it strategically, and make investment decisions based on actual capability rather than assumption. The organizations that wait will keep paying the cost of invisibility.

What happens next

What happens next depends entirely on whether someone calls the meeting.

The logic is clear, the ROI is demonstrable, and the technology exists. What's missing, in most organizations, is the cross-functional partnership required to turn insight into infrastructure. Three executives need to understand the same problem in their own terms: the CHRO sees a data failure dressed up as a talent strategy failure. The CFO sees a measurable cost with a clear ROI case. For the CIO, it's an architectural gap with a defined technical fix. When all three understand that they're looking at the same problem from different angles, the partnership becomes obvious.

Conclusion

Here's the question that matters: If you could actually see what capabilities exist in your organization right now, how confident people are in those capabilities, and how recently they've been demonstrated, what would change about how you make decisions?

If the answer is "not much," workforce intelligence probably sits lower on your priority list. But if the answer is "a great deal," if it would change decisions like these, then the remaining question is who is responsible for making that data exist, and what they need to make it reliable enough to run the business on?

• Hiring decisions

• Deployment decisions

• Learning investments

• AI readiness assessments

• Strategic planning

• Budget allocation

That's the conversation that unlocks everything else, and it starts with someone calling the meeting.