AI Leadership Principles / People

How do we lead teams where people work alongside AI agents?

Start with bounded, end-to-end workflows and name a human owner for every agent. Define what agents may do alone, what needs approval and when they hand over to a person. Redesign roles around supervising and improving agents, and measure outcomes per workflow.

Why it matters now

Agents take actions, not just produce text, and that changes the leadership question. Someone has to decide what an agent may do, check its work and answer for the result. It is close to how I run Herman Foundry: agents carry much of the routine work, and people carry the judgment. It works when the boundaries and the ownership are clear, and it fails when they are not.

Common mistakes

  • Agent projects driven by hype rather than a defined workflow.
  • No clear accountability for what an agent decides or does.
  • Governance that lags behind how agents are actually used.
  • Giving agents broad access before they have earned trust.

What to do instead

  1. Start bounded. Choose a contained, end-to-end workflow with clear inputs and a clear result.
  2. Name a human owner. Every agent has a named person who answers for its work.
  3. Define autonomy. Write down what an agent may do alone, what needs approval and when it must hand over to a person.
  4. Redesign roles. Shift people towards setting goals, reviewing output, handling exceptions and improving the agents.
  5. Measure per workflow. Track quality, speed, cost and errors for each workflow, not overall activity.

Your first step this week

Pick one routine workflow and write down which steps an agent could do, which need a person’s approval and who would own the result. That is your first agent brief.

All AI leadership principles and guides · 100 AI use cases by function

Sources

Want to work through
this with your team?

I help leadership teams make these decisions and turn them into working systems, as a fractional or interim AI leader.

The AI Impact Sprint ↗