Stop Calling It Delegation
Trust is not the absence of the manager. It is a specific structure most managers skip because they mistake it for micromanagement.
When a report says "I've got it," are they asking for authority or for your absence? Most managers hear the second, call it trust, and walk away. Trust is not the absence of the manager. It is a specific structure most managers skip because they mistake it for micromanagement.
At one company, a director on the ops team spent 3 weeks renegotiating a vendor contract and came back with worse terms than before. Her manager found out at the board meeting.
When asked, she said: "I didn't want to bother you with the details." She thought she was being trusted. Her manager thought he was delegating. Both were wrong.
Delegation is not the absence of the manager. It is a specific structure: the manager hands over the decision, keeps responsibility for the outcome, and checks in at 2 clear points, once at the start to set the downside boundary and once near the end to catch drift. The work in the middle belongs to the report.
Dumping looks similar from 10 feet away. The decision is handed over. The manager disappears. The report executes. The difference only becomes visible when something goes sideways, because with dumping there is no checkpoint, no downside boundary, and no shared definition of done. The report discovers this at the worst possible moment, usually in front of someone senior.
Managers dump and call it delegation for 3 reasons, all defensible in the moment and costly at scale.
One: they confuse autonomy with absence. A report who says "I've got it" is not asking for isolation. They are asking for the authority to run the work. Those are different things, and the trust that lets a small business grow depends on the distinction.
Two: the check-in feels like micromanagement. It isn't. Asking what's the downside if this goes wrong? and who else has information we don't? at the start is not supervision. It is the one conversation that turns a task into a delegated decision.
Three: the manager is busy. 10 minutes at the start and 10 minutes at the end feel like a tax on a calendar already full. Skipping them feels like respect for the report's time. It is the most expensive skip on the calendar, the same false economy that shows up when you delegate without deciding what to eliminate or automate.
The test is simple. When the work goes poorly, does the report say "I didn't want to bother you" or "here's where I went wrong and what I learned"? The first answer is evidence of dumping. The second is evidence of delegation.
A director who says "I didn't want to bother you" has not been given permission to bring bad news. That permission is granted at the start, in the first 10-minute conversation, or it is not granted at all.
No check-ins, no delegation. A bill arrives at the board meeting instead.