Managing a Mixed Team of People and Agents

Adding agents to a team does not simply increase headcount. It changes how work is described, assigned, reviewed, and escalated. If ownership remains vague, automation can make ambiguity move faster.

Give Every Agent a Role Charter

Define the outcomes the agent owns, data it may access, tools it may use, limits it must respect, service level, and conditions that require escalation. Name the human owner who can change the charter and answer for performance.

Avoid roles such as “general assistant.” A narrower role—invoice evidence collector, release-note drafter, or support triage agent—is easier to evaluate and safer to improve.

Make Work State Visible

People need to see what agents are doing without reading every trace. Use a shared queue with clear states: planned, running, waiting, needs review, completed, failed, and cancelled. Show the current objective, last verified step, blocking condition, and next action.

Handoffs should include evidence and unresolved questions. An agent that merely says “I could not complete the task” creates work; one that identifies the exact blocker reduces it.

Manage the System, Not the Personality

Measure cycle time, correction rate, duplicated work, safe escalations, cost, and downstream outcome. A charming conversational style should not hide unreliable operations.

Teams also need new routines: reviewing failures, updating instructions, curating examples, retiring unused automations, and deciding which work should remain human.

The strongest operating model does not ask people to compete with agents. It gives each side work suited to its strengths and makes responsibility unmistakable at every handoff.