The CIO is not the enemy

Whenever I describe the Chief Workforce Officer to a technology leader, the first reaction is defensive, and it is fair. It sounds like a new executive being created to second-guess the people who build the systems. It is not, and the relationship between the two roles deserves to be set out before anyone is appointed.

Start with what the CIO is accountable for and should remain accountable for: that the systems work. Availability, security, data integrity, vendor management, integration, cost of the platform. These are hard, and they are getting harder as agents multiply and talk to each other. Nothing in the CWO's charter touches them. A CWO who tried to choose models or negotiate with vendors would be doing the CIO's job badly.

Now consider what nobody is accountable for in most organisations: what the systems do. Not whether the agent is up, but whether its answers are right; not whether it is secure, but whether anyone would notice if it quietly started screening out a class of applicants; not whether it was delivered on budget, but whether the humans around it are spending eight hours a week checking it for a saving of ten. These are workforce questions. They concern the division of work between people and systems and the supervision of that work, and they are the CWO's.

The two roles meet at a specific point: the decision to deploy. The CIO can say the system is ready. The CWO can say the organisation is not, because no one has been named to answer for the output, or the verification cost is too high for the task, or the entry-level roles it would displace are the ones the organisation needs for its own future. Either can block; neither can decide alone. That is the design. It will produce arguments, and the arguments are the point, because they are the only mechanism by which the organisation hears both the capability and the consequence before it commits.

This is why the reporting line matters more than the title. If the CWO reports to the CIO, the argument never reaches the chief executive; it is settled inside the technology function, which has every incentive to settle it in favour of deployment. If the two functions are merged, as Moderna has done, the argument is settled inside one head. Only when the two are peers, each reporting to the chief executive, does the disagreement survive long enough to be heard.

There is a precedent that technology leaders will recognise. Security was once a sub-function of IT, and it was systematically overruled by delivery pressure until organisations learned to give it an independent line. The chief information security officer who can halt a launch is not the enemy of the CIO; the two are a system of checks that lets the organisation move fast without moving blind. The CWO stands in the same relation to the CIO on the question of work, and the same objections that were raised against independent security will be raised against it, for the same reasons, with the same outcome.

So the pitch to a CIO is not "someone will now review your decisions." It is "someone will now own the part of this that was never yours, and that you have been blamed for anyway." Most technology leaders I have spoken to, once they hear it that way, want the role to exist. They are tired of being the only person in the room when the agent fails.