The CHRO Counterpart Question: Workforce Strategy or Technology Strategy?

The Counterpart Model is being framed in most enterprises as a technology decision. It is not. It is the largest workforce architecture change in a generation, and the CHRO who is excluded from authoring it is the CHRO who later has to repair it.

The conversation about AI in 2026 has been almost entirely a conversation between CEOs and CIOs. Boards are asking the CEO. The CIO is presenting the architecture. The CFO is approving the budget. The COO is sponsoring the deployments. The CHRO is, in most enterprises I observe, on the periphery of the conversation — invited to talk about change management once the architecture has been chosen, asked to handle communications once the deployments are scheduled, looped in for upskilling programmes once the gaps have been identified by other functions.

This positioning is wrong, and the wrongness is going to become visible in 2027 in ways that will be expensive to fix. The Counterpart Model is not an IT deployment with HR implications. It is a workforce architecture decision with technology dependencies. The reversal of those two clauses is the entire argument of this essay. Every consequence flows from getting the framing right — or from getting it wrong.

For the categorical context of what a Counterpart actually is — why it sits in the workforce category rather than the software category — see Post 7 of this series. This essay assumes that ground and asks what follows for the CHRO specifically.

Why This Is a Workforce Architecture Decision

The simplest test of whether something is a workforce decision is whether it changes the design of roles. The Counterpart Model passes that test in every direction. Roles paired with Counterparts shift in composition. The Finance Director paired with their Counterpart spends less time on close mechanics and more on business partnership. The COO paired with theirs spends less time on operational orchestration and more on strategy and people. The Sales Director with theirs spends less time on CRM hygiene and more on customer relationships. None of these role shifts happen passively. They have to be designed.

Role design is HR's domain. So is career path design — what happens to the people who used to do the work the Counterpart now handles? Are their roles eliminated, restructured, expanded? What is the progression for someone now operating at the higher altitude the Counterpart enables? What does the next analyst hire into Finance look like, given that the Counterpart now handles much of what an entry-level analyst used to do? Performance management is HR's domain — how do you measure a Finance Director whose primary work is now strategic partnership rather than process execution? Total rewards is HR's domain — does compensation philosophy shift when individual contributors paired with Counterparts produce two or three times the output they did before?

Each of these questions has technology dependencies but is fundamentally a workforce question. They cannot be answered by IT. They can only be answered correctly with HR leadership at the centre of the design conversation, not at the receiving end of decisions made elsewhere.

The CHRO Blind Spot

Why are CHROs being left out of the conversation? Three reasons, in roughly the order they show up.

1. The Framing Problem

The technology vendors selling AI capability — and there are many, with substantial marketing budgets — frame their offerings as efficiency tools, productivity copilots, automation platforms. None of these framings naturally invite the CHRO into the room. A productivity tool is a CIO conversation. An automation platform is a COO conversation. The CHRO joins these conversations after the fact, to handle the people implications. The framing of what is being deployed determines who is in the room when the design happens, and the dominant framing in 2026 is one that places the CHRO downstream of the design.

2. The Speed Problem

Counterpart deployments are moving faster than most enterprises' organisational design cycles. A finance team can pair with a Counterpart in four to six weeks. A redesign of the Finance Director role typically takes six to nine months in most enterprises' HR processes. By the time HR is engaged through the standard organisational design channel, the deployment is already producing new working patterns and the role has begun to shift in practice. HR is then trying to design a role that has already been emerging in the field for six months. This is not a failure of HR competence. It is a process speed mismatch, and the mismatch is structural.

3. The Confidence Problem

Many CHROs I speak with describe a confidence gap on the technical content of AI deployments. They are asked to opine on architectures they do not fully understand, in vocabulary that is unfamiliar, alongside CIOs and CTOs whose entire role is to be fluent in this material. The natural response is to defer on the technical decisions and focus on the people implications afterwards. This is exactly the wrong instinct for the Counterpart Model, because the technical decisions and the workforce decisions are not separable. The architecture choices made on day one determine the role structures that emerge by month twelve. Deferring on the architecture means deferring on the workforce.

What Gets Built Without the CHRO at the Table

Picture a typical Counterpart deployment that proceeds without HR at the design level. The CIO and COO scope the deployment. The technology vendor implements. The pilot runs successfully. The deployment scales to additional functions. Six months in, the CHRO is asked to address the resulting issues. What are those issues? The pattern is consistent across the deployments I have observed.

Issue 1: Role Drift Without Role Design

The roles paired with Counterparts have shifted in composition, but the formal role descriptions have not. The Finance Director's job description still describes the close, the reconciliation oversight, the consolidation responsibility — none of which they actually do anymore. New hires read the job description and arrive expecting one job; they discover a different job once they start. The interview process is calibrated for the old role; the people being hired do not match the new role's actual demands. The performance framework still measures the old work. The compensation benchmarks still anchor on the old responsibilities. None of these are catastrophic individually. Together, they produce a six-to-twelve-month period of organisational confusion that genuinely could have been avoided with role design happening alongside the deployment rather than after it.

Issue 2: Career Paths That Stop Making Sense

The progression that used to lead from Analyst to Senior Analyst to Manager to Finance Director was built on accumulating mastery of the work the Counterpart now handles. With the Counterpart in place, what does a Senior Analyst do that an Analyst paired with their own Counterpart does not? What is the progression that builds toward a Finance Director role that is now substantially about strategic partnership? The career path question does not answer itself. If HR is not designing the new path, the answer the workforce gets by default is "the old path with the old work removed" — which is a path that does not lead anywhere meaningful and produces talent flight to enterprises that have answered the question.

Issue 3: Performance Conversations That Have Lost Their Anchor

Performance management is built on observable behaviours and outcomes. When the Counterpart handles much of the observable execution work, what gets measured? The strategic contribution of the Finance Director paired with a Counterpart is real but harder to evidence than the close cycle they used to run. Without a redesigned performance framework, managers default to measuring what is easy to measure, which is no longer what matters. The performance conversation becomes vague. Top performers are not being recognised for their actual contribution; underperformers are not being identified clearly. The consequences compound across review cycles. By year two of the Counterpart deployment, the performance management system is functionally broken in the paired functions.

Issue 4: A Workforce That Does Not Know What Story It Is In

The most consequential issue is also the least visible early on. The workforce does not understand what is happening to it. Are Counterparts going to lead to layoffs? Are they here to stay or are they a passing experiment? Should I be learning to work with mine or should I be looking for a job at a company that has not deployed them? These are the questions every employee in a paired function is asking themselves, and in the absence of a coherent story from leadership — which means in the absence of the CHRO authoring the narrative — they answer the questions privately, often pessimistically, and the workforce engagement metrics drift quietly downward. The deployment can be technically successful and culturally toxic at the same time, and the cultural toxicity is the harder problem to fix.

Five Things the CHRO Owns in a Counterpart Deployment

The argument so far has been a problem statement. The constructive form of it is a list of specific decision rights the CHRO must hold during a Counterpart deployment. These are the decisions that, made well, produce a coherent workforce architecture; made poorly or not at all, produce the four issues described above.

1. Role Architecture for Paired Roles

For every role being paired with a Counterpart, the CHRO leads the redesign. What does this role do now that the Counterpart handles its execution work? What is the new altitude? What capabilities does the redesigned role require? How is the redesigned role described, recruited for, and onboarded? This work happens in parallel with the deployment, not after it. The CHRO partners with the function leader (CFO for Finance, COO for Operations, etc.) to author the new role design and the transition path from the existing description.

2. Career Path and Progression Design

The new progression model — what a career looks like in a function paired with Counterparts. The CHRO designs how junior talent enters the function, what their development looks like over the first three years, what middle-management progression looks like, and what the senior contributor track is. The progression is meaningfully different from the pre-Counterpart progression, and getting it right is what determines whether the function is a place top talent wants to build a career.

3. Performance Management Framework

What gets measured in roles paired with Counterparts? The CHRO redesigns the performance framework for paired roles — including the criteria, the cadence, the calibration process, and the link to compensation. This is hard work because the new performance criteria are inherently more qualitative — strategic contribution, business partnership impact, judgment quality — and the calibration discipline has to compensate for the loss of the cleaner quantitative measures the old work provided.

4. Capability Development and Upskilling

What capabilities does the workforce need to operate effectively with Counterparts? This is broader than "AI literacy" and more specific than "future of work." It is the concrete capability building that lets a Finance Director use their Counterpart well, lets a Procurement Manager pair effectively, lets an individual contributor develop the judgment that the Counterpart's escalation requires of them. The CHRO designs the curriculum, the development pathways, and the capability assessment framework.

5. The Workforce Narrative

The story the enterprise tells its workforce about why the Counterpart Model is being deployed, what it means for them, and what their role in the future enterprise looks like. This is the most consequential of the five and the most CHRO-specific — no one else in the enterprise can author this credibly. Done well, it is the difference between a workforce that engages with the deployment as participants and a workforce that experiences it as something happening to them. The narrative is not communications work to be assigned to the comms team. It is strategic work that the CHRO authors and the comms team helps deliver.

How the CHRO Enters the Architecture Conversation

For the CHRO who reads this and recognises their enterprise is building a Counterpart Model deployment without them at the design level, the practical question is how to enter the conversation now without it feeling like territorial overreach. The framing matters here — claiming the territory has to be done in a way that strengthens the deployment rather than slowing it down, or else the architecture team will route around HR even more thoroughly. Three moves work, in roughly the order they should be made.

Move one. Bring the workforce architecture frame to the CEO directly, not to the deployment programme. The CEO is the person who can authoritatively reposition the Counterpart deployment from "technology programme with HR support" to "workforce transformation with technology dependencies." This is a single conversation, ideally fifteen minutes, in which the CHRO presents the four issues described above as predictable outcomes of the current framing and proposes the five decision rights as the corrective. Most CEOs, presented this way, will accept the reframing immediately — they just have not been led to think about it in those terms.

Move two. Partner with the function leader of the most advanced Counterpart deployment, not with the deployment team. If Finance is the furthest along, the partnership is with the CFO. The CHRO and the CFO together design the role architecture, career paths, and performance framework for the Finance function under the Counterpart Model. This produces a working example that other functions can replicate, and it positions HR as a strategic partner in the deployment rather than a downstream consumer of its outputs.

Move three. Author the workforce narrative early and publicly. Before the workforce hears stories about the Counterpart from anyone else — vendors, the press, social media, internal speculation — the CHRO publishes the enterprise's narrative through the standard internal channels. The narrative is strategic, honest, and specific to this enterprise. This early authoring sets the frame for every subsequent conversation about the deployment, and the frame is the thing that determines whether the workforce experiences the change as something they are part of or something being done to them.

The Strategic Implication for the Whole Executive Team

The CHRO's positioning on the Counterpart deployment is not just a CHRO question. It is an executive team question with consequences for the deployment's overall success. A Counterpart deployment that has the CHRO at the architecture table from day one moves slower in the early phases — there are more design conversations, more workforce considerations, more careful sequencing — but produces durable organisational change by month twelve. A deployment that proceeds without HR at the design level moves faster initially and runs into the four issues described above somewhere between month nine and month eighteen, requiring substantial remediation effort that more than erases the early speed advantage.

The CEO who recognises this trade-off — and who positions the CHRO as a peer in the architecture decision rather than a downstream beneficiary — produces a measurably better deployment outcome. This is one of the underrated CEO judgment calls in the Counterpart era. It will distinguish the enterprises that arrive at 2030 with workforces that scaled gracefully from the enterprises that arrived with workforces that have been organisationally damaged by deployments their HR functions never got to author. See Post 1 of this series for the broader CEO framing of the Counterpart Model decision.

The Counterpart Series

A ten-part series on the AI Agent Counterpart Model — strategic case for executives, operational reality across functions, and the conceptual ground that defines what a counterpart is and what it is not.