Iris Holm: Long week — but I have something that reframes it. Ready?
Cyrus Reed: Yeah, what — oh, are we going straight in?
Iris Holm: Think about how a hospital staffs its OR. They don't say 'we have budget for twelve surgeons.' They say 'Tuesday's schedule needs a cardiothoracic specialist and two anesthesiologists with pediatric certification.' That's capability-based planning. Most companies aren't doing that. They're counting seats.
Cyrus Reed: Huh — okay, that's actually a clean way to see it. So the whole Heidrick and Struggles argument, Sunny Ackerman's argument, is that companies should plan like the OR, not like a headcount spreadsheet.
Iris Holm: Exactly. And the problem is ninety-one percent of HR leaders still cite headcount cost as their primary planning factor. So the narrative from Heidrick that leading organizations are making this shift — frankly, the data says the shift hasn't happened. Not at scale.
Cyrus Reed: So is this a real structural change or just — wait — is it just a better-sounding story layered on the same old machine?
Iris Holm: That's the real question — and the survey data makes it worse. Because these aren't two different populations. The ninety-one percent who say headcount cost dominates? That's the same group where eighty-five percent also call capability development critical. Same leaders. Same survey. Both things simultaneously.
Cyrus Reed: Wait — that's not tension, that's — okay, that's cognitive dissonance at scale. Like, how do those two answers coexist in the same budget meeting?
Iris Holm: They don't. One gets funded. One gets invoked when you need to sound strategic.
Cyrus Reed: So it's not that companies are running two planning models — they're bolting capability language onto the same headcount machine and calling it transformation. But then — wait, actually — if that's true, where does the Chief People Officer fit? Because Heidrick just published a twenty-twenty-six review, 'First-Time Chief People Officers in the UK,' and the framing is that the CPO role is 'absolutely center stage' now, seismic shifts in the business landscape, all of that — but first-time? In twenty-twenty-six? That's not a role that arrived at the board table.
Iris Holm: That's the tell. If capability-based planning were genuinely structural, the CPO elevation happens before you need to publish a guide for first-timers. The fact that Heidrick is writing that guide now means the infrastructure is still being built.
Cyrus Reed: So the second layer is getting installed while the first one is still running. Both operating systems, live, at the same time.
Iris Holm: And that dual-track problem gets sharpest when you look at where interim talent sits in all this — which is where Ackerman and Sandra Pinnavaia's argument either survives or breaks completely.
Cyrus Reed: And Ackerman and Pinnavaia are basically saying — okay, interim talent is the proof-of-concept for the whole capability argument. Like, if you can't even slot in three senior architects for six months, you don't actually have a capability planning system. You have a headcount system with better vocabulary.
Iris Holm: The number that breaks it is fifteen percent.
Cyrus Reed: Wait — only fifteen percent of HR leaders include interim talent in formal workforce planning? That's — how is that number so low when Business Talent Group and Heidrick have been making this case for years?
Iris Holm: Because the cost-optimization machinery doesn't have a category for it. Here's the actual scenario: a tech CFO reviews Q2, sees two hundred forty-seven approved headcount positions, fourteen percent under budget. HR submits a parallel request — three interim senior architects, six months, cost equivalent to one full-time hire, zero permanent headcount. CFO approves the headcount model. Denies the interim request.
Cyrus Reed: But wait — that's cheaper and more flexible and the CFO still says no? That's not a cost problem, that's a — okay, that's a model problem. The machine doesn't have a slot for it so it reads as noise.
Iris Holm: And that's what makes the fifteen percent so damning. Cloud infrastructure moved to on-demand in the early 2000s. Software teams normalized contractor-based architecture through the 2010s. But HR leadership? Still at fifteen. That's not an adoption lag.
Cyrus Reed: It's structural resistance — because those other shifts happened to technical resources, not to leadership itself. Moving leadership on-demand is the part nobody's actually tested at scale. And McKinsey's whole point about treating talent with the same rigor as financial capital — if that were real, the CFO in that scenario approves the interim request without blinking.
Iris Holm: And that's where the capacity-versus-capability line actually cuts. Capacity is 'do we have enough people for Tuesday?' Capability is 'do those people have what it takes for what comes next?' Those are different questions. They need different machines. The AI Pyramid framework — Khatri and Khanal, January 2026 — their whole argument is that capability formation has to become infrastructure. Not a training cycle. Not a quarterly initiative. Infrastructure. The same way you don't rebuild your cloud architecture from scratch every year.
Cyrus Reed: Right, but — wait, because if capability has to be infrastructure, then the question isn't whether organizations *want* to build it. It's whether they can actually run both systems at the same time without one quietly starving the other. And I don't — I mean, I don't think we have a clean answer to that. Like, what happens when budget pressure comes back hard and you can only feed one?
Iris Holm: The ninety-one percent knows.
Cyrus Reed: Yeah. That's — honestly, that's probably the right place to sit with it. Not a verdict. Just the number.
