I’ve spent the last few months moving work off my plate. Research, publishing, scheduling, pipeline management — most of it runs now without me touching it. But there’s a short list of things that keep ending up back in my hands.
I’ve stopped treating that list as a failure of process.
It’s a diagnostic.
The easy answer (and why it’s useless)
Most people say “judgment can’t be delegated.” Technically true. Practically useless.
Everyone I know who says it uses “judgment” as a bucket for whatever they don’t want to think through. That’s not judgment. That’s avoidance with a respectable name.
The things I actually can’t delegate are more specific. More embarrassing to admit.
What keeps landing back on my desk
Three things this quarter.
Positioning decisions. I can hand over research. I can brief someone on the competitive landscape. But the call on where a new thing sits — how it’s framed against what already exists — I keep pulling that one back.
Tone drift. Something is slightly off in how I want to show up on certain channels. I feel it. I can’t articulate it. And because I can’t articulate it, I can’t hand it over.
Which signals matter right now. I have data. I have dashboards. But the call on which number is the canary this month — that one requires context I haven’t written down anywhere.
None of these are too complex to delegate.
That’s the uncomfortable part.
The real reason
When I’m honest about it, the things I keep are the things I haven’t thought through clearly enough to explain.
Not a capability ceiling. A clarity debt.
I’m making calls on intuition I haven’t stress-tested. I know the answer but I don’t know the rule. And if I don’t know the rule, there’s nothing to hand over. There’s nothing for someone else — or a system — to operate on.
It works until it doesn’t. Until I’m unavailable. Until the context changes and the intuition no longer applies. Until I’ve built something that only functions because I’m personally holding it together.
That’s a fragile kind of competence.
Turning it into useful pressure
I’ve started treating the un-delegatable list as a forcing function.
Every few weeks I pick one item and try to write it down. Not a process doc. Not a formal brief. Just: what is the actual decision I’m making here, and what rule am I applying?
If I can write it, I can delegate it.
If I can’t write it, that’s where I need to spend more time thinking — not more time executing.
The writing isn’t the goal. The clarity is. The writing just proves I got there.
What the list keeps teaching me
The work I hold onto longest is usually the work I understand least.
I keep it because letting go feels risky. But the risk isn’t in the handover. The risk is in the gap I haven’t closed yet. The thing I haven’t made legible — to someone else or to myself.
There’s a version of this where I tell myself I’m just being thorough. Careful. These are important calls, they deserve my attention.
Sometimes that’s true.
Most of the time it’s just discomfort wearing the costume of diligence.
The useful question isn’t “what can I delegate?” It’s something smaller:
What am I keeping — and is the reason a real gap, or just friction I haven’t pushed through yet?
Most of the time, when I actually sit with it, it’s friction.
The delegation can wait. The clarity can’t.