Institute for Human and Artificial Work‹ Essays
The Chief Workforce Officer · Essay 17 of 23

A Chief Workforce Officer in a two-hundred-person company

The title is for large organisations. The job exists at any size where an agent does work that used to be someone's.

Iman Abrishamchi··5 min read

An objection I hear often: this is a problem for multinationals. A two-hundred-person company cannot afford another executive, and does not need one. The first half is true. The second is not, and the difference is between a title and a job.

Consider the two-hundred-person company as it actually is in 2026. It uses an agent to handle first-line customer questions, another to screen job applications, a third to draft proposals, and several more that individual teams signed up for without telling anyone. Nobody in the company knows the full list. The operations lead knows about the customer agent, the office manager set up the recruitment one, and the proposals agent was a founder's experiment that stuck. If the customer agent starts giving wrong answers on a Friday evening, the person who notices will be a customer.

That company has every element of the problem a multinational has, at a scale where it can be solved in an afternoon. What it needs is not an executive but a decision: one named person holds the workforce question for both people and agents. In a company of that size it is usually the chief operating officer or the head of people, and the addition to their job is specific.

They keep the register: every agent, what it does, who set it up, what it may decide, when it was last checked. In a two-hundred-person company this is a single page, and the act of writing it usually reveals two agents nobody remembered.

They assign the name: for each agent, one person who signs for its output, who knows the work well enough to spot a wrong answer, and who can switch it off without asking. In a small company this is often the person who was doing the task before the agent arrived, which is exactly right, because they have the expertise.

They watch the two numbers that matter: how much time the agent's output is costing people to check, set against the time it saves, and how many people in the company could still do the task by hand. The first prevents the quiet overload that small teams are especially prone to; the second prevents the small company's version of the missing junior loop, which arrives faster because there are fewer people to begin with.

And they make the composition decision on purpose, once a year: for the handful of task families where agents do real work, what share should be human, what share agent, and what is the plan if the vendor doubles the price or changes the model. Small companies are more exposed to vendor dependency than large ones, because they cannot build their own, and the composition decision is where that exposure is managed.

None of this requires a new hire. All of it requires that someone is named, and that the naming is taken seriously by the founder or chief executive, which in a small company is the whole of governance. The Chief Workforce Officer in a two-hundred-person company is a Tuesday-afternoon addition to an existing role, and it is more important there than in a large company, because the small company has no slack to absorb the day the agent fails. The title can wait indefinitely. The job cannot wait until Monday.

The question this series asks. Should organisations create a Chief Workforce Officer, accountable for people and AI agents together, and what must be thought through before they do? Every essay takes one angle on it. Write to the Institute; every message is read and answered.