Distinguish ONLY ME by necessity from ONLY ME by default — tasks you never made delegable aren't genuinely non-delegable
Before delegating a task, verify it is not ONLY ME by default rather than by necessity—if the task requires your unique judgment only because you've never built documentation, systems, or relationships to make it delegable, it's a disguised delegation candidate.
Why This Is a Rule
Many tasks classified as ONLY ME (Classify every task as ONLY ME, COULD DELEGATE, or SHOULD NOT EXIST — then eliminate or delegate everything outside ONLY ME) are non-delegable not because they inherently require unique judgment but because the infrastructure for delegation was never built. "Only I can handle this client relationship" may be true today — but only because you never introduced the client to a colleague, never documented the client's preferences, and never built a handoff process. The task is ONLY ME by default (accumulated dependency) not by necessity (inherent requirement for unique judgment).
The distinction matters enormously for attention allocation. Tasks that are ONLY ME by necessity (strategic decisions, value trade-offs, creative vision) genuinely require your irreplaceable contribution. Tasks that are ONLY ME by default (undocumented processes, unshared relationships, hoarded context) require a one-time investment in delegation infrastructure (documentation, introduction, training) that converts them from ONLY ME to COULD DELEGATE permanently.
Every task kept ONLY ME by default is a delegation investment you're deferring — and the deferral compounds. The longer you avoid building the delegation infrastructure, the more the task's context accumulates in your head, making the eventual documentation more difficult and the apparent non-delegability more convincing.
When This Fires
- When classifying tasks using Classify every task as ONLY ME, COULD DELEGATE, or SHOULD NOT EXIST — then eliminate or delegate everything outside ONLY ME's ONLY ME / COULD DELEGATE / SHOULD NOT EXIST taxonomy
- When you notice a large ONLY ME category and want to verify it's genuinely non-delegable
- When feeling overwhelmed by tasks "only you can do" — many may be delegation infrastructure deficits
- When someone asks "why can't someone else handle this?" and you can't articulate a necessity-based reason
Common Failure Mode
Conflating accumulated dependency with inherent uniqueness: "Only I understand this system well enough to make these decisions." Maybe — but is that because the decisions genuinely require your unique judgment, or because you never documented how the system works? If a competent person with good documentation (The competent stranger test: could someone with skills but zero context produce an acceptable result from your spec alone?) could make 80% of these decisions, the task is ONLY ME by default, not necessity.
The Protocol
(1) For each ONLY ME task, ask: "Why does this require me specifically?" (2) If the answer references your unique judgment, values, relationships, or strategic position → ONLY ME by necessity. Retain. (3) If the answer references undocumented knowledge, unshared context, or missing infrastructure ("because I'm the only one who knows how...") → ONLY ME by default. This is a disguised delegation candidate. (4) For default-ONLY-ME tasks: estimate the one-time investment to make it delegable (documentation, training, introduction, system setup). (5) If the investment is less than 3 months of continued personal execution → make the investment now. The ROI is permanent attention recovery.