Delegation Drift
What breaks when the person you assigned to can't ask questions
I’ve been delegating work for most of my career. I thought I was pretty good at it.
You learn the basics early. Be clear about the outcome, not just the task. Leave room for the person to figure out the how. Follow up without micromanaging. And when something goes sideways, sit down with the person, find out where the disconnect was, have them play it back to you in their own words, confirm it in writing.
That system works. I’ve watched it work across teams, across organizations, across eighteen years of leading technology people through complicated problems.
Then I started delegating to agents.
The reconciliation that wasn’t
A few months ago I asked an agent to pull data from three different systems, analyze it, and build a reconciliation process to identify what was missing from our primary source.
The agent did exactly what I asked. It pulled the data. It performed the analysis. It returned the missing records.
Just the missing records. Nothing about where those records existed in the other systems. Nothing about why the inconsistency existed. Just a list of gaps with no map to explain them.
My team spent the next several hours investigating what the agent had already touched, trying to reconstruct the context the output didn’t include. The task was completed. The work wasn’t done.
I didn’t blame the agent. I blamed my instructions. And then I sat with something uncomfortable: a human would have asked. Before they got halfway through the work, someone on my team would have looked up from their screen and said, “Hey, do you want me to just flag the gaps or trace where this data actually lives?” And I would have said trace it, and we would have saved the better part of a day.
The agent didn’t ask. Not because it couldn’t. Because I hadn’t told it to.
The signal you don’t get
When a human misunderstands an assignment, I usually know before the work comes back. There’s a look. A pause in the hallway. An email that reveals the interpretation went sideways three days before the deadline. I’ve learned to read those signals. They’re not always obvious but they’re there, and catching a misunderstanding early is almost always cheaper than correcting it after the fact.
With an agent there’s no signal. The work just comes back. By the time you see the output, the misunderstanding has already run its full course. Whatever compounded in the gap between your instruction and the agent’s interpretation, that’s what you’re holding now.
This isn’t a technology problem. It’s a visibility problem. And it’s the same visibility problem from my last article wearing different clothes. You can’t read the room when there’s no one in it.
The adaptation I didn’t notice I was making
Here’s what I’ve started doing without a framework telling me to. When I’m writing instructions for an agent, I slow down in a way I don’t always slow down for people. I re-examine the ask. I think about what assumptions I’m carrying that the agent won’t share. I front-load the context that a human would have asked for in the first place.
I’ve started adding clarification prompts directly into the instruction set. Explicit permission for the agent to flag ambiguity before proceeding. Not because someone told me to. Because I got the reconciliation output and spent an afternoon figuring out what went wrong.
That adaptation is the right instinct. The problem is I’m applying it inconsistently, only when I remember, only on the tasks where a previous failure made me cautious. I haven’t built it into a repeatable practice. I haven’t taught it to the people I lead. I haven’t made it structural.
That’s delegation drift. Not a sudden failure. A slow slide between what you intended and what the agent interpreted, across dozens of small assignments, accumulating quietly until something surfaces that costs more to fix than it should have.
What delegation requires now
The assign-clarify loop that every management framework assumes depends on a human on the other end. Someone who will push back, ask questions, flag confusion before it compounds. That loop is the safety net underneath traditional delegation. Most leaders don’t think about it consciously because it happens naturally.
Remove the human and the loop disappears. What’s left is instruction quality. Your clarity at the moment of assignment is the only defense you have against drift.
That means delegation to AI agents requires a different front-end discipline. Define the outcome and the scope explicitly, not because you don’t trust the agent but because trust without clarity produces a list of missing records and a confused team. Build ambiguity flags into your instruction set by default. Create a review point before the output is final, not after. And document what you learn from every misalignment, not as a post-mortem but as an input to the next instruction.
None of this is complicated. All of it is intentional in a way that human delegation never had to be.
The question I’m sitting with
Think about the last thing you delegated to an automated process or AI tool. Did you write that instruction the same way you would have explained the task to a person? Or did you slow down, front-load the context, and anticipate the questions it couldn’t ask?
If there’s a difference in how you approached it, that difference is your new leadership practice. The question is whether you’re applying it consistently, or only when you remember to.