Review a Delegated Task — Did It Actually Stay Delegated?

Delegation drift is one of the most common and least-named patterns in founder-led businesses. Here’s how to spot it and fix it.

Delegation drift looks like this: you hand something over genuinely. You felt good about it. The person seemed capable. The brief was reasonably clear. And then, over the following weeks, something quiet happens.

You check in a little more often than you planned. The person’s output comes back for a small adjustment. You make a decision within the task that was supposed to be theirs. Then another. And then, without quite noticing when it happened, you’re once again the person doing most of the thinking — even though the task is nominally still delegated.

This is delegation drift. It’s extremely common, rarely named, and almost always more about process gaps than about the capability of the person it was delegated to.

The Real Problem

Delegation drift creates a particularly expensive operational pattern because it gives the appearance of delegation — the task is no longer on the founder’s list — while actually preserving most of its cognitive load. The founder is still the decision-maker, still the quality controller, still the person the outcome ultimately depends on. They’ve added the overhead of coordination without actually reducing the burden of the work.

For the person the task was delegated to, drift has a different cost: it signals, gradually but unmistakably, that the delegation wasn’t real. That their judgment isn’t actually trusted. That they’re executing rather than owning. This erodes both motivation and the willingness to invest in developing genuine capability.

The Big Idea

A delegation audit — checking whether delegated tasks have actually stayed delegated — is one of the highest-value operational reviews a founder can do. It reveals where process gaps need closing, where decision authority needs clarifying, and where the drift has been a symptom of a brief that was never quite complete enough to allow genuine handover.

How to Make It Work

1. Choose One Delegated Task to Audit

Pick something you delegated in the last month that you considered successfully handed over. Something that felt like a clean delegation at the time. Now look at it honestly: how is it actually operating?

Are you still making decisions within it that you thought were theirs? Is the output coming back for adjustment more than once? Are you reviewing it more closely than the brief suggested you would? Have you stepped back in ‘just to help’ more than once?

2. Diagnose the Drift

If the answer to any of those questions is yes, there has been some drift. Before drawing any conclusion about the person, look at the process: was the brief specific enough about what done looks like? Was the decision authority clear — did they know what they could decide independently? Was there a defined feedback loop, or did review happen ad hoc?

In most cases of delegation drift, at least one of these elements is missing or ambiguous. The drift isn’t because the person couldn’t handle it — it’s because the structure didn’t fully support it.

3. Choose Your Response

Once you’ve identified the gap, you have two options.
Option one: reset the delegation properly. Update the brief to close the specific gap. Clarify the decision authority. Rebuild the feedback loop. Have an explicit conversation with the person about what the reset looks like and why.

Option two: acknowledge that this task isn’t ready for the level of delegation you attempted, and consciously move it back to a lower level — explicitly. Tell the person why, and define what would need to be true to move it up again. This is better than drift because it’s honest and gives the person a clear development path.

What you should never do is let the drift continue without naming it. Unnamed drift leaves everyone in a confusing limbo — the founder frustrated, the person uncertain, and the work in nobody’s genuine ownership.

4. Build a Regular Delegation Review

A monthly delegation audit — even just 20 minutes reviewing your current delegated tasks against the criteria above — prevents drift from accumulating undetected. Small course corrections made regularly are far less disruptive than large corrections made when the drift has been going on long enough to cause real problems.

Why This Works

A delegation audit that identifies and addresses drift turns delegation from a one-time event into an ongoing operational practice. It keeps the ownership clear, the briefs current, and the feedback loops active. Over time, it produces a culture where delegation is real — not nominal — and where the people tasks are delegated to know they genuinely own what they’ve been given.

🛍️ RESOURCE
If you’d like a ready-made structure to make your delegation briefs more complete from the start — and reduce the drift that incomplete briefs cause — the Clear Delegation Checklist in my Etsy shop walks through everything a brief needs: outcomes, decision authority, feedback loops, and escalation paths → ETSY LINK

The Real Goal

Delegation that stays delegated — where the ownership is genuine, the process is clear, and the person handling the task can work with confidence and independence. A delegation audit is how you make sure that’s actually happening, rather than assuming it is.

💬 Your Turn

Is the thing you delegated last month actually still delegated?
If it’s drifted — what’s the specific gap, and what are you going to do about it?
Share in the comments.

⏭️Up Next

Next week we move into Systems — specifically whether your business could run without you for a week, and what that question reveals about your operational architecture.
See you Monday.