Definitions, Ownership, Trust: The Non-Negotiables of AI-Ready Workforce Data
AI makes data problems louder and more expensive to fix. Leaders from AbbVie, Corning, UW Health, T. Rowe Price, and ABM Industries share how they're aligning definitions, rebuilding trust, and assigning ownership to get workforce data truly AI-ready.

Picture this: Your finance team logs a hire the day an offer is signed. Your IT team logs it the day system access goes live. Your HR team logs it the day that person shows up for their first shift.
Same person, same event, three different dates. And once each version rolls into a report… three different numbers. What happens when you expand it to thousands of workforce data points? That mismatch becomes the problem sitting underneath every conversation about workforce data and whether or not it's ready for AI.
I recently sat in on a panel of leading data practitioners from Corning, AbbVie, UW Health, T. Rowe Price, and ABM Industries to discuss AI implementation in their organizations. Data integrity was a central talking point, and the conversation kept coming back to four core factors: definitions, trust, compliance, and ownership
Here's what I learned:
Key Takeaways
Definitions come first. HR counts who reports to whom while Finance counts who gets paid by whom, and until those categories are settled—FTEs, employees on leave, contractors, interns—every metric built on top of them inherits the mismatch.
Trust is structured, not requested. Corning wrote a formal spec for every metric, and AbbVie tiers its data gold, silver, and bronze. These systems ensure leaders know exactly which numbers are safe to act on before the debate starts.
AI turns a data problem into a legal one. A dashboard with conflicting trend lines invites questions, but an AI assistant delivers one confident answer—but is that answer right? The EU AI Act (among others) now puts privacy and legal in conversations that used to sit between HR and Finance.
Every number needs a name on it. ABM Industries holds each HR metric to four standards: clear owners, standard definitions, regular quality checks, and transparent calculations. It’s ownership that makes the other three enforceable.

Definitions: HR and finance still aren't speaking the same language
The hire-versus-start gap is by no means unique. Headcount figures run into the same wall. HR usually counts who reports to whom, while Finance usually counts who gets paid by whom. Both are technically right, but they don’t match up.
Imran Hashmi, senior director of data and digital strategy at AbbVie, has watched this trip up more people analytics teams than any other technical problem has:
“You have to agree on the definitions. Do you look at full-time equivalents versus individual counts? Do you look at people on leave? Interns, students, co-ops and contractors versus full-time? There’s no shortcut through those conversations; you have to work through them category by category.”
At Corning, these challenges showed up in the org chart itself. Li Tao, HR director of people analytics, described two valid hierarchies built on different logic. One was a "paid by" structure reflecting Finance's cost-center view. The other was a “responsible for” structure reflecting who actually manages a team. Because these didn’t match up, it led to manual reconciliation and competing answers to the same question.
Rather than choosing one hierarchy over the other, Corning invested in building out the “responsible for” hierarchy properly, then aligned with Finance on exactly when each view applies. That gave them two clear structures that finally work together instead of against each other.
Trust: When trust breaks, decisions stall
Misaligned numbers create extra work and inaccuracies, but costs compound in the meetings where nothing gets decided because everyone is still debating what data to use, and if it's even accurate.
As Li Tao explained: “Once leaders stop trusting the data, action slows down. And instead of deciding what to do next, people spend time debating whose number is right.”
The same pattern shows up in metrics that look clean and rigorous on paper. Revenue per FTE and profit per FTE read like standardized numbers, until an FTE definition, a cost allocation method, or a segmentation choice shifts underneath. Suddenly two teams land on two different answers to a question that everyone assumed was settled.
The team at Corning responded by writing the logic down and giving every metric a formal spec around why it's measured, what data feeds it, and what business question it answers. This offered leaders a shared reference that everyone could point to if the numbers stopped matching.
To bridge this trust gap without spending years custom-building logic from scratch, we've been working on how to handle the heavy lifting upfront here at Visier. We know our customers are going through these same issues in maintaining trustworthy data.
Our Workforce Context Engine comes pre-loaded with 15+ years of workforce domain expertise and over 2,000 standardized HR metrics. It automatically reconciles timeline discrepancies—like the difference between when an action happened and when it was logged—so both HR and Finance operate from the same reality.
When every metric has a clear, automated logic layer behind it, leaders stop debating whose spreadsheet is right and start acting on the insights.
Compliance: AI turns a data problem into a legal one
AI raises the stakes further by making bad data sound confident, even if it's highly debatable. A dashboard with conflicting trend lines invites questions, but an AI chatbot will deliver a confident answer that seemingly closes the conversation—whether or not anyone's agreed on what the numbers mean.
That's what turns this into a legal problem. For example, what happens when AI tools name specific employees as flight risks, based on their own, invisible reasoning? That immediately pulls privacy and legal partners into conversations that used to sit between HR and finance alone. And the governance implications are only getting more pressing.
Illinois has already introduced clear guardrails on using AI in employment decisions, while in Europe the EU AI Act covers similar ground around recruitment, candidate screening, pay decisions, promotions, and terminations.
At AbbVie, Imran Hashmi is candid that the instinct to keep AI out of hiring and firing decisions is easier said than done. Even with a firm rule in place, he's seen the line blur in practice and creep in over time, and that risk is part of why his team has widened who's in the room. HR, finance, business, and IT already worked on analytics together. Now privacy and legal teams are permanent additions too.

Ownership: Trust demands a name attached to every number
Every data framework here traces back to the question of ownership.
Christy Cole, SVP of HR shared services at ABM Industries, outlined four qualities every HR metric needs to be trustworthy:
Clear owner(s)
Standard definitions
Regular quality checks
Transparent calculations
Say a turnover rate comes in at 9.7%. On its own, that invites debate around whether it’s good, bad, or even worth worrying about. But if you were to tie that same rate to a $2 million cost in one specific business unit, it turns the debate into business-critical insight, and it gives leaders much more context for more immediate action.
AbbVie has built this type of discipline into its data architecture with a medallion system of gold, silver, and bronze layers. Only gold-layer data reaches business leaders and AI tools. Silver and bronze stay with analysts working with rougher material. This classification system draws a hard line around what's safe to act on.
At UW Health, Christine Wittleder spoke about how her team was rebuilding governance from the ground up. It begins with an executive sponsor, followed by a cross-functional council, then the subject matter experts who understand how their numbers get used. She also brought in “strong champions” and “thoughtful skeptics.” Champions carry momentum, while skeptics catch problems early enough to fix.
Fix the foundation before you fix the dashboard

We took away many important lessons from this candid conversation between leaders who are doing the hard, oftentimes unglamorous work preparing workforce data for AI.
The first is that definitions have to come before anything else gets built. Corning fixed its headcount confusion by sitting down with Finance and working out when specific hierarchies apply.
We also came away convinced that trust is something you structure rather than something you ask for during a heated debate in a meeting. AbbVie's gold-silver-bronze tiers and Corning's metric specs work because they draw a hard line around what's safe to act on.
And underneath both of those sits ownership: UW Health's governance rebuild started with names attached to the work, from an executive sponsor down to the people accountable for how each metric gets used.
AI didn't create any of these problems, but it has made them louder and more costly to ignore. What this conversation made clear is that the organizations pulling ahead aren't the ones with the most AI tools in their stack, but they're the ones who solved the trust problem first, with one timeline, one org chart, and one shared definition no matter who is asking.
Clean data gets you partway there, and connected data takes you further, but context is what turns a number into an answer you can act on and defend when someone asks how you got there.
Time to prepare your workforce data for AI.
Most enterprise AI underperforms because the workforce data it's fed lacks context. Get the four-part framework to diagnose the context gap in order to build an AI-ready foundation.



