Who designs, supervises and answers for your AI agents, and who to hire first
For each role, write who does this work today (a name, a part of someone's job, a vendor, or nobody), and what changes as agents take on more of the work.
| Role | Who holds it today | Share of a job | Gap or next step |
|---|---|---|---|
| Roles that still matter | |||
| Accountable AI executiveOwns the AI portfolio and the decision to stop an agent | |||
| AI product ownerDecides what an agent is for, what it may not do, and when it hands back to a person | |||
| Data engineerPipelines, access rules and quality checks the agents act on | |||
| Data scientistLess routine analysis; more tests of whether agent output can be trusted | |||
| ML engineerFrom shipping models to running agent systems | |||
| Governance specialistMaps systems to the rules that apply, runs reviews, keeps the records | |||
| TranslatorKnows enough of the technology, the business and the people to get a system adopted | |||
| Roles that are new | |||
| Agent orchestratorDesigns the workflow: which agent does what, with which tools, within which limits | |||
| Agent evaluatorBuilds the tests and sample checks that decide whether an agent keeps running | |||
| Agent reliability engineerMonitoring, drift, limits and the switch that stops an agent | |||
| Oversight designerDecides where a person approves, where a person reviews after the fact, and where the agent acts alone | |||
Agent name:
Write a name in each box. R is the person who does the work; A is the one person who answers for it. Each row gets exactly one A. At a small company one person may hold several columns. That’s fine as long as every row has an owner.
| Agent work | Responsible (R) | Accountable (A) | Consulted | Informed |
|---|---|---|---|---|
| Design the workflow | ||||
| Set its authority limits | ||||
| Evaluate its outputs | ||||
| Run and monitor it | ||||
| Stop it | ||||
| Answer for the outcome |
Check: can the person in the A box for "Stop it" have the agent switched off within a day, without asking anyone else? Yes No
Tick each step when it is done. Move to the next only when the one before has paid for itself.
For each person on the team, write the role they hold, the role it is moving toward, and what they need to get there. People stay when they can see the route.
| Person | Role today | Role next | What they need (training, a project, a mentor) |
|---|---|---|---|
Common routes: data scientist to agent evaluator; ML engineer to agent reliability engineer; product manager to oversight designer.
Three questions to ask each quarter: