AI Teammates Quietly Erase Human Roles
A scheduling agent moves a meeting because two calendars conflict. It does not know that the move erases the only hour a junior employee had to ask a senior colleague for help. The system logs success: no double-booking. What it cannot log is the mentorship that quietly stopped happening.
A Role That Dissolves Without Anyone Deciding
A new paper by Rida Qadri and fifteen co-authors, “Working with Agentic ‘Teammates’: When a New Organizational Actor Collides with the Human Ecosystem of Work,” arrives at an uncomfortable finding. [1] The danger is not that software fails. The danger is that it succeeds at the task while quietly removing the reason a human role existed in the first place.
Consider what a role actually is. A job title is the visible part. Underneath sits a web of small, unglamorous functions — the check-ins, the informal handoffs, the person who notices when something feels off. None of these appear in a job description. All of them can be absorbed by an agent that was only hired to do the visible part.
The Task Is Not the Job
This is where the collision begins. An agent is deployed to handle a discrete function: draft the report, route the ticket, summarize the thread. It performs that function well. What no one mapped is the human work that clustered around it — the conversations that happened while waiting for the report, the judgment calls made during the routing, the relationship built by being the one who summarizes.
Those peripheral activities were never the job. They were the soil the job grew in. Remove the task, and the soil erodes without a single alarm sounding.
When Success Looks Like a Clean Dashboard
The paper’s authors describe something they call an ecosystem of work. [1] The phrase matters because it reframes the problem: an agent is not replacing a task, it is altering a habitat. An ecosystem does not have a single keystone task. It has interdependencies — some obvious, most invisible. An agent optimized for one node cannot see the edges connecting it to others.
So the metrics improve. Response times drop. Throughput rises. Every dashboard turns green. Meanwhile, the informal apprenticeship that used to happen in the margins has no metric, so its disappearance registers as nothing at all. The system reports health while the thing it measured has been hollowed out.
The Judgment Nobody Assigned to Anyone
Here is the sharpest edge of the finding. When an agent takes over a task, the human judgment embedded in that task does not transfer. It evaporates. The person who used to make a call — is this urgent, is this person okay, does this exception matter — no longer has the context to make it, because the context arrived through doing the work.
No one decides to eliminate that judgment. It simply stops being exercised. And a skill that stops being exercised does not wait around. It atrophies. Six months later, the organization discovers it can no longer make a call it used to make reflexively, and no one can point to the day the capability left.
The Unintended Consequence Arrives Late
The paper’s core warning is temporal. [1] The damage does not appear at deployment. It appears at the moment the system is fully live — when the humans have reorganized around the agent, when the old workflows are gone, when there is no path back. That is when the missing judgment becomes visible, and by then the people who held it have moved on or forgotten how.
This is not a failure of the technology. It is a failure of imagination at the design stage. The teams that deployed the agent asked what it would do. They did not ask what would stop being done.
Seeing the Edge Before It Cuts
The moment of clarity the paper offers is not a solution. It is a way of looking. Before an agent takes a task, ask what human work lives in the shadow of that task. Ask who learns by doing it, who notices by being near it, who decides by holding it. Those are the things that will not show up in any log.
An agent can be a genuine teammate. It can lift work that no one should have to do. But it will never raise its hand and say: I have replaced something you did not know you needed. That recognition has to come from the people still in the room — and it has to come before the room is empty.