Why Does Everything Still Come Back to Me After I Delegate It?

That conclusion feels earned. It's also wrong, because those two handoffs failed for two completely different reasons, and the second failure only looked like proof of the first.

Delegated work comes back through four doors: no written rule, no real authority, no announcement to the people affected, or you taking it back. How the work lands on your desk tells you which door is open. And three of the four are on the owner, not the employee.

Ask how it came back, not why

Stop asking why it came back. Ask how. The form of the return is the diagnosis, and it takes no investigating at all.

Somebody asks you a question. Or asks your permission. Or a customer complains to you directly. Or you look at what got done, don't like it, and redo it.

That's four different failures in one costume. Treat them as one problem and the next attempt fails as reliably as the last.

Say the business is a commercial cleaning company, and February's attempt came back as questions, roughly six a week about crew swaps and site access. August's came back as customer calls, because three account contacts never heard there was a new scheduler.

Four doors, four fixes

Each door has one fix, and they don't swap.

Door three is the cheapest to fix and the one most often skipped. Ten minutes of emails would've saved that August attempt completely.

Door one is the most common on a first try. Owners hand over the doing and keep the deciding, which gets you a person doing the work and asking you how to do it.

If it's coming back as approval requests, the fix is a conversation as much as a document. Getting a manager to decide covers what has to change, and why encouragement alone won't do it.

Door four: the one nobody counts

This one's uncomfortable. You gave somebody the scheduling. They built next week's schedule. You looked at it and rebuilt it.

You didn't take the task back, exactly. You just fixed this one, and then the next one, and by the fourth week you're scheduling again and nobody ever decided that.

The test is one question: was the difference a standard or a preference? A standard is a rule you can write in one sentence that a stranger could apply. A preference is how you personally would've done it.

Correct standards every time. Leave preferences alone, even when yours is better, because the cost of correcting preferences is that the person stops making decisions at all.

Say you go back through the rebuilds and find most of them were preferences. Route order, mostly, on jobs where any order would've worked fine.

The habit under door four is solving every problem yourself, which is the firefighter pattern. It feels like responsibility, and every rebuild hands the job back to you a little more.

Two lines before the next handoff

Before you hand anything over again, write two lines. If you can't write both, it isn't ready and it'll come back.

Line one is the rule: the sentence that makes the common case obvious without you. Line two is the anouncement: who you're telling, by name, that this person owns it now. Write both before the handoff conversation, since most reversals are visible in advance if anybody checks for the missing line.

Then add the exception. It takes ten seconds. Name the single condition where it does come back to you, and everything else is settled by definition.

Why keep at it? Because it's the same work that carries the exit number, and every door you close moves a buyer's read of how much the business depends on you.

A couple more things worth checking. If the handoff that keeps failing is scheduling or something else that happens constantly, at least you picked the right candidate, but if it's something that happens twice a year, the failure was in what you picked to hand off. And the standard delegation framework is sound, it just assumes the handoff worked, so it won't diagnose a reversal for you.

Owners who never close these doors run into them again at the worst possible time. When the exit conversation starts at home, an owner who can't step back is negotiating from a business that won't let them.

The owner-side habit behind doors two and four has its own article, and it's worth being honest about. The approval chair is comfortable, which is why it survives three separate attempts to leave it.

Pick the last thing that came back to you and name how it arrived. That one word tells you which door to close.

Before the next handoff, it's also worth seeing how much still routes through you. Keystone measures that, and right now it's closed while the build is finished. You can join the waitlist at https://app.trykeystone.io.

When it opens, the diagnostic is 18 questions and about four minutes, and it returns three scores and your value range with the most likely figure locked, calibrated against 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records.

Closing one door is a morning's work. Closing all four across every recurring decision in the business is the operating layer, and that's months most owners don't have spare. A Full Operations Modernization installs it in a live system your team runs, and scoping starts on the Full Operations Modernization page.

FAQ

Why does delegated work keep coming back to me?

It returns through one of four doors: no written rule, no real authority, no announcement to the people affected, or you taking it back by correcting the work. How it arrives on your desk tells you which door is open.

What is reverse delegation?

It is work moving back up from the person who owns it to the owner, usually without anybody deciding it should. The common forms are a question, an approval request, a customer routing around the new owner, and the owner redoing the work.

Why do my employees keep asking me questions?

Because the rule that answers the common case was never written down, so the task was handed over and the deciding was not. Write the sentence that makes the three most frequent questions obvious and hand the rule over with the task.

How do I make delegation stick?

Write two lines before the handoff: the rule that makes the common case obvious, and the list of people you will tell by name that this person now owns it. Add one exception, then correct standards only and leave preferences alone.