Do your AI agents need an org chart?
Kelsey McKeon · 10 November 2026
Read the originalRetool's survey of 300 technology leaders found half worry about AI agents making decisions with no clear owner, and recommends naming an owner and scope before launch.
Kelsey McKeon, writing on the blog of Retool, a company that sells software for building internal tools and AI agents, reported its survey of 300 technology leaders. The findings suggest organisations have spread agents across teams faster than they have decided who answers for them. The article argues that each agent needs a named owner, a defined scope and access rules enforced at the data source.
- Half of the leaders with agents in production named agents making decisions with no clear owner as a top concern.
- Ownership varies: 42% have domain teams own agents with central oversight, 27% have one team own all agents, and 10% have no formal structure.
- Thirteen percent said an agent took an unintended action in a production system in the past year, and 7% did not know whether they had an incident.
- Seventy percent measure time saved, but only 43% track business outcomes such as revenue or cycle time.
The figures come from a vendor that sells tools for building agents. A team adding agents could name an owner and scope for each before launch and judge each agent by its output, as the article recommends.
Assign every AI agent a named owner and a defined scope before launch, and update both when people or processes change.
Derived by Working Surface from the article; more in the Playbook. Source line: Every agent should have an owner and a defined scope, with access tied to both through guardrails IT sets.
13 November 2026: AI agents earn more freedom when a team limits what they can reach, from data to design components, and adds a check that does not depend on a glance.