The "AI employee" title is a governance bug

On July 17, 2026, Emma Wiles and three BCG researchers put numbers behind something I had only been able to argue by instinct: what you call your agents changes how humans supervise them. Their working paper reports that 23% of 1,261 surveyed managers work at organisations that list AI agents on org charts. Read that again — nearly a quarter of these HR and finance managers already share an org chart with software.

The experiment is the interesting part. The researchers held the work product constant — the same flawed HR and finance documents — and randomised only one thing: whether the author was described as an AI tool, an AI employee, or a human employee. Among managers whose organisations already had agents on org charts, the "AI employee" label cut monitoring intensity by 16% and increased additional-review requests by 44%. The same framing shifted perceived accountability roughly 9 percentage points away from the manager and about 8 points toward the AI system itself.

Two honesty notes before the argument. The average effect across all managers was small; the oversight drop concentrated in the subgroup where AI employees were already institutionally credible through org-chart placement. And this is a July 17 working draft, not a peer-reviewed publication — whether the 23% prevalence or the subgroup effects generalise beyond these 1,261 managers is an open question. I am treating it as the best available evidence, not settled science.

The label does organisational work — in the wrong direction

The consensus read on "AI employee" branding is that it is harmless marketing that helps organisations make agents legible: give it a name, a title, a box on the chart, and everyone knows how to relate to it. The paper suggests the legibility is exactly the problem. Managers know how to relate to employees — you trust them, you monitor them lightly, you assume they own their mistakes. Port that relationship onto a system that cannot own anything, and you get less scrutiny on the work, more diffuse accountability, and no compensating improvement in the system itself.

Look at the two effects together, because they describe a specific dysfunction: monitoring down 16%, review requests up 44%. My reading — mine, not the paper's — is that the label converts supervision into escalation. Managers stop inspecting the work directly, the way they would stop hovering over a trusted colleague, and instead route doubt outward as requests for someone else to review. Accountability moves 9 points off the manager. That is a review queue growing while the person closest to the output looks at it less. In an agent deployment, that is the failure geometry: errors caught later, by people further from context, owned by no one.

I have watched the small version of this at work. A client deployment gave an internal agent a human name and a job title — it made the change management easier, everyone agreed. Six weeks in I asked three questions: who reviews its output, what is the escalation rule when it is wrong, and which human is accountable for its decisions? All three answers were implicit. Nobody had decided they should not be answered; the employee framing had simply made the questions feel already-answered. A tool gets an owner and a review gate by default. An "employee" gets assumed competence.

So here is the correction I now push in governance reviews: ban "AI employee" from org charts and role documents, full stop. Steal the replacement, it is one line per agent in the system inventory: agent name → accountable human owner → reviewer of output → escalation rule. If any cell is blank, the agent does not ship. Keep the friendly name for the demo if you like — but the org chart is a governance document, and governance documents should describe systems and owners, not colleagues.

Call it an employee and managers will supervise it like one — which is precisely the oversight level agent work has not yet earned.