You Can Debug an Agent. You Can’t Debug a Person.
Good leaders read people. Bad managers confuse the person for the tool they already know how to use.
Traditionally, the ability to discern and evaluate another person’s judgment was the hallmark of a good leader. Yet the twin obsessions of the last decade — the builder mindset and organizational flattening — have made the skill rare. I’ve argued before that executives get the middle management they deserve: companies flattened their management layers because so much of that management was low-value work that deserved to go.
This is the other side of that coin. Management that was worth keeping was worth keeping because they were good at understanding people.
I made the point last week that AI is turning product managers from builders into operators. Managing a team of builders in the past gave rise to a specific category of ineffective management: the artifact-inspector. The PM builder produced an artifact — a spec, a launch, a feature — and managers could look at it and judge it. The manager read that and believed he had thereby read you. Reviews and checklists existed to make that job possible; the work arrived as objects, and objects can be examined. Once the objects could be examined without him, the layer collapsed, correctly.
Managing an operator offers no such object to assess. The work is never finished, so there’s nothing to inspect. What you’re assessing instead is a person’s attention over time, because the real failure of someone operating an agent isn’t a bad deliverable. It’s observation fatigue: not noticing that the waves have changed direction and the storm clouds are gathering.
That puts the pressure back on the oldest leadership skill there is. “Is this a good PRD” gives way to “is this person calibrating the system well” — reading the right signals, tuning the right things, catching drift early. It’s judgment about someone else’s judgment, and you have to get close to the work to see it.
Here is the new danger — people use tools they are familiar with, and this can give rise to the same inefficient manager, wearing a new costume. Leaders who came up in the flat-org years, and who now spend their days operating agents, reach for the techniques that work on agents and aim them at people.
Picture the manager this produces. Their days are spent operating: the model misbehaves, they re-prompt it; the output drifts, they retune it; the pipeline stalls, they rewire it. Fast, iterative, effective — the correct relationship to a machine.
But then a strong performer on their team goes quiet. The manager does what the tools trained them to do: treat the silence like a line stoppage and get things moving again. More structure, a tighter check-in, a pointed note about the missed signal, a re-prompt aimed at a person. Six weeks later the person on their team is interviewing elsewhere, and the manager is genuinely puzzled. Their attempted fix was only correct for an agent, not for the human on their team.
Here’s the core reason. A lot is being said about product teams managing autonomous agents, and thus acting like managers. But a lot is riding on the term ‘autonomy’ in this sense. An agent has autonomy of execution: it plans its own steps, picks its tools, retries when it fails. What it doesn’t have is autonomy of will — a preference of its own about where it should go. A person has autonomy of will. If you hand a person a goal, they can disagree, disengage, or leave. Agents can’t. That’s exactly why while you can operate the agent, you must lead the person.
To expand the ship building analogy of the product operator: the people on your team should be experts at operating the ship. But you cannot operate the crew.
Look closely and the two bad managers are the same type. The builder-turned-manager judged you by your artifact and thought the deliverable was you. The operator-turned-manager debugs you like a system and thinks the correction is leadership. Different tools, one mistake: taking the person for the instrument you already know how to handle. But a person is neither an artifact nor an agent. What makes them their own category is the will, the very thing that neither the PRD nor the AI agent has. That’s why flattening was right to cut the artifact-inspector, and why it would be a mistake to rebuild her in a new costume. Same hollow management, new tool.
The leader worth retaining is the one who anchors on a skill that hasn’t changed: reading the person. AI raises the value of that skill precisely by automating everything around it. You can walk away from something you built. You cannot walk away from something you operate. And you cannot walk away from the people doing the operating — which is why the scarcest role left is the one who keeps a room of operators sharp, motivated, and unwilling to leave, and who knows the difference between the machine and the person running it.