How CIO and CHRO share ownership
Shared governance
A joint CIO-CHRO steering committee co-owns decisions on vendor selection, data access, deployment, and risk — not just reviews them.
Joint metrics
Both functions anchor to the same outcomes — adoption rate, time-to-competence, and process completion — instead of measuring success separately.
Unified data strategy
Employee data quality becomes a joint responsibility, with both functions owning the standards, integrations, and access together.
CXO's take on the CIO-CHRO partnership
9 Leaders across conversational AI, eCommerce, insurance, tax law and more on how the partnership works in practice.
A bad hire was a real financial loss at Insurance Navy. So, we went so far as to stop thinking of recruiting technology as a CIO issue and retention as a CHRO issue. We made a collective outcome, a collective number.

CIO and CHRO should jointly manage results like retention and digital literacy. When both are responsible for engagement and training metrics, the CIO can ensure the tech stack reduces daily friction, and the CHRO can ensure adoption stays human-centered.

I depend on our CIO to vet AI tools and vendors. But where I need more from that partnership is the translation layer, turning what a tool can do into what it does for our people on the ground.

It was not the technology that was the issue; it was the sequencing. I would want to pull HR into vendor selection six months early. CIOs treat people issues as system issues. They look for the bug, install the fix, and move on. But people do not update like software.

The CIO can help connect the systems, but the CHRO helps define what the data is supposed to represent in the first place… Most successful workforce AI initiatives are the ones where both functions agree on the language, metrics, and outcomes before the AI enters the conversation.

Governance and bias discussions cannot be owned exclusively by IT. As AI increasingly influences workforce decisions, governance requires shared accountability between technology, HR, legal, compliance, and business leadership.

The common misconception is that deploying an AI agent is a one-and-done setup… We treat our AI assistants exactly like human employees. They are built into our formal workforce governance structure.

Our biggest challenge is data fragmentation. Information often lives in separate systems and was never designed to work together. We need a unified view that requires consistent definitions, data quality standards, and governance across multiple platforms.

Before you download
Why does AI adoption need a CIO-CHRO partnership specifically?
Because the CIO builds the system and the CHRO decides whether people actually use it. Most AI projects fail not on technology, but on the adoption side only the CHRO can influence.
We already have a CIO-led AI strategy. Why bring the CHRO in now?
Because the outcomes boards ask about — adoption, productivity, retention — all sit downstream of decisions the CHRO makes. A CIO-only strategy can hit every technical milestone and still fail on the business outcome.
Our CIO and CHRO already meet occasionally. Isn't that partnership enough?
Occasional check-ins usually mean the CIO still measures uptime and the CHRO still measures satisfaction, separately. The partnership only holds when both are accountable to the same shared metrics, not just aware of each other's work.
Ready to move your CIO and CHRO from talking points to a shared scorecard?
See how 9 industry leaders are building that partnership in practice.








