By Errin O'Connor — Founder & Chief AI Architect, EPC Group · Microsoft Solutions Partner across all six designations · G2 Leader in BI consulting
Allie K. Miller — former AWS and IBM AI leadership, and one of the few voices in this industry whose frameworks actually get implemented rather than just reposted — stood on a stage in New York this year and said the thing most executives are still resisting: AI is not a tool. We would love to treat it like a tool, she noted, because tools make us feel secure. But we have entered the era of autonomous teammates, and the human role is shifting from writing prompts to operating like a chief operating officer of AI staff.
She is right, and the psychological reframe she is asking for is the hard part — most organizations are still budgeting, governing, and securing AI like it's Visio with opinions. But the moment you accept her frame, a very old and very boring discipline comes due, and this is the part the keynote circuit never gets to: companies have run teams of workers for a century, and every functioning company answers the same five questions about every worker. Nobody is answering them about the AI ones.
The five questions every org chart answers
Think about what your company knows about any human employee, on day one, without anyone considering it exotic. Who are you — an identity, credentials, a badge. What is your job — a role, a scope, a boundary you don't cross. What do you cost — a salary line someone approved and someone monitors. How are you doing — a review, against criteria, on a cadence. How do we part ways — offboarding, access revocation, a documented exit. Five questions. A century of management science. The entire apparatus we call an employment file.
Now run Miller's autonomous teammates through the same five. Who are they? In most tenants — nobody; they run under the human's identity. What is their job? Undefined; scope is whatever the inherited permissions allow. What do they cost? Unknown until the consumption bill lands — and per-token pricing means your AI staff now has a payroll line that nobody is managing; industry analysts already project per-developer AI spend rivaling salaries within two years. How are they doing? Nobody reviews agent output systematically; we spot-check when something feels off. How do we part ways? Ask an enterprise to terminate one specific agent in under an hour and watch the meeting calendar fill up. We adopted the teammates and skipped the employment file. That is the entire risk posture of enterprise AI in 2026, stated in one sentence.
The Non-Human Org Chart
The framework I build with clients is deliberately unglamorous, because the power is in the unglamour. We call it the Non-Human Org Chart, and it applies the five questions with the Microsoft stack the client already owns. Identity: every agent gets an Entra workload identity — its own name, credential, and conditional-access policy; identity inheritance ends as a matter of written policy. Job description: scope defined in permissions and Purview boundaries — which data, which tools, which actions, at what thresholds; one sentence per agent, signed by a named human manager. Payroll: token budgets with monitoring and escalation, routed deliberately — small models for routine work, frontier models where the problem earns them; that routing is cost control, not ideology. Performance review: logged output sampled on a cadence against written quality criteria — the same evidence layer that satisfies an auditor doubles as the review file. Termination: deprovisioning tested, timed, and owned by a name, not a committee.
Twenty-nine years in this industry has taught me that the enterprises that survive platform shifts are never the ones with the most exciting adoption story. They are the ones that made the new thing boring fastest — governed, inventoried, reviewed, and revocable. I watched it with SharePoint sites, with Power BI workspaces, with Azure subscriptions. Miller's teammates are the same movie with higher stakes: this time the ungoverned thing doesn't just store your data. It acts on it.
What I tell clients to do
One. Accept Miller's frame fully — then act on its implication. If they're teammates, open the employment files. This week.
Two. Build the Non-Human Org Chart for your top ten agents: five questions, five columns, ten rows. You will not enjoy the blanks. That is the point.
Three. Assign every agent a named human manager whose own performance review includes the agent's conduct. Accountability that isn't attached to a person isn't accountability.
Four. Put the token payroll under the same discipline as the human one — budgets, thresholds, monthly review. Nobody runs headcount on vibes; stop running agent spend on them.
The five-column register
Ship the Non-Human Org Chart as a living register (Dataverse or SharePoint list): AgentID (Entra object) · JobSentence · Manager (named human; agent conduct appears in the manager's review) · TokenBudget/period plus alert thresholds plus model-routing tier · ReviewCadence plus last-review score · KillSwitchOwner plus last-tested time-to-kill. Board report: top-ten agents by spend and by risk, quarterly, next to headcount.
Where I land
Miller gave the market the right metaphor, and I want to finish it for her. If every employee is becoming a COO of AI teammates, then every enterprise is becoming a company whose workforce is partly non-human — and a company that cannot name, scope, pay, review, or terminate part of its workforce is not transformed. It is exposed. The org chart is the oldest governance technology we have. It is time it learned to hold entries that don't eat lunch — and EPC Group's AI Governance practice builds exactly that.
The data behind this (sources and verification)
- Allie K. Miller — Activate 2026 keynote — AI is not a tool; autonomous teammates; human role shifting from prompt-writer to COO of AI staff.
- Gartner (via CIO, June 24, 2026) — Per-developer AI token spend on track to rival salaries within two years — the payroll line is literal.
- Gartner agentic AI prediction — Approximately 15% of day-to-day work decisions made autonomously by agentic AI by 2028.
- Anthropic product team disclosure — Roughly two-thirds of the product team's code is now agent-written — the autonomous teammate era is already present at frontier labs.
Third-party figures above are attributed to their named sources as of the Last verified date. EPC Group audit figures are directional findings from client engagements. Items marked [VERIFY] must be confirmed before external quotation.
Frequently asked questions
Do AI agents really need performance reviews?
Yes — sampled output against written criteria is both quality control and the evidence file auditors and carriers ask for. Without a review cadence, the only signal is a user complaint or a compliance incident.
How do we budget tokens like payroll?
Budgets per agent or workload, monitoring thresholds, escalation paths, and deliberate routing: small models for routine work, frontier models where the problem earns them. The routing decision is cost control, not ideology.
Who is the agent's manager?
A named human whose own performance review includes the agent's conduct — accountability unattached to a person is not accountability. The manager approves the one-sentence job description and owns the kill-switch.
What goes in an agent's job description?
One sentence of purpose plus enforced boundaries: which data classes, which tools, which action thresholds — encoded in Microsoft Purview permissions, not left to prompts. The sentence is signed by the named manager.
How is this different from service-account management?
It extends the same discipline: identity plus scope plus logging. The additions are autonomy thresholds, token payroll, and review cadence — things service accounts never needed because they didn't act on your data autonomously.
Ready to act on this?
Start with the practice most relevant to your estate, or reach out directly for a senior-architect conversation.
📧 contact@epcgroup.net · 📞 (888) 381-9725
Multiple models. One truth.