How to write a personal principle about delegation that survives a real deadline

"Delegate more" is advice almost every overloaded person has heard, and almost none of them keep following once the week gets hard, because the moment it's supposed to apply to keeps slipping past unnoticed. A personal principle about delegation is not a resolution to trust people more in general. It is a rule about a specific, recurring moment: a task lands in front of you that someone else could plausibly do, and you have to decide, right then, whether to hand it off or keep it — written on a calm day, before the deadline that will make keeping it feel like the only safe option.

Why "let go of control" cannot be kept or broken

"Trust your team more," "stop being a bottleneck," "let go of control" — these describe a person you would like to be in general, not a decision you can point to. You can sincerely believe you delegate well, right up until you notice that the same report has been quietly living on your desk for a year, past three people who could have learned it if you'd ever handed it over. Nothing about "let go of control" would have caught that, because it never named the specific moment where the task could have gone to someone else and didn't.

The two failures pull in opposite directions

"I'm bad at delegating" usually means one of two very different things, and the fix depends on knowing which.

The first is holding on. A task arrives, and it genuinely is faster to do it yourself this one time — so you do, and the same is true the next time, and a year later "just this once" has quietly become the permanent arrangement. Nobody ever decided you should be the only person who can do this; it just kept being true on each individual day that doing it yourself was the path of least resistance, which is a different thing from it being the right long-term call.

The second is the opposite problem wearing the same name: handing off the task without handing off the authority to actually finish it. You assign the work but keep every real decision for yourself, so the other person has to check with you at each step anyway — which either turns into you redoing it under a different name, or, if you disappear instead of hovering, into someone guessing at decisions they were never actually given the right to make, and getting blamed for guessing wrong.

A rule aimed at the wrong one will not help. Telling someone who already can't let go to "delegate more" just adds guilt to the pile of things they're doing themselves. Telling someone who already hands work off without authority to "trust people more" makes them disappear further, which is not the same thing as trusting.

Mine your own pattern instead of guessing which one you are

Do not start by asking "am I good at delegating." Ask instead:

• Is there a task I have done more than three times that someone else could plausibly learn, and if so, why hasn't it moved?
• The last time I did hand something off, did I also hand over the right to decide how it gets done, or did I keep checking every choice?
• When something I delegated didn't go the way I wanted, did I give clear enough terms up front, or did I find out what I actually wanted only after seeing what I didn't?
• Is there a piece of work on my plate right now that I am keeping mostly because handing it off would take longer than just finishing it myself today?

Write the specific instance, not the tidy self-assessment. "I have rewritten the same weekly summary myself for eight months because explaining the format once felt like more effort than just doing it" tells you exactly where a rule needs to live. "I should delegate more" is a sentence you could write without learning anything about your own pattern, and it will not tell you what to do the next time that summary is due.

Write the rule about the handoff moment, not the intention

A principle here needs two parts, because the two failures above are about two different moments: whether you hand a task off at all, and what you actually give someone once you do.

For the holding-on pattern, the rule is about a threshold, not a mood: if I have done a task the same way three times, I write it down once and hand it to someone else the fourth time, even though doing it myself would be faster that day names a countable trigger you can check yourself against, instead of relitigating "is this the moment" under deadline pressure. For the authority pattern, the rule is about terms: when I delegate something, I say out loud which decisions the other person can make without asking me first — a task without stated decision rights was never actually delegated, it was just relocated with you still attached to it.

Run the same two tests that apply to any principle. Can it actually be violated — is there a specific instance where you can say, honestly, whether you kept it or not? And does it cost something — a rule that never once has you hand off a task when it would have been faster to keep it, or never once states real decision rights out loud, is decoration rather than a principle.

Attach behavior standards you can actually check

The principle stays general; the standards underneath it are specific enough that someone else — or you, a week later — could tell whether you met them. For a principle like I hand off what someone else can learn, and I give them the authority to actually do it, useful standards might be: I write instructions once instead of redoing a repeated task myself for the fourth time; before handing off a task, I state which decisions the other person can make without checking with me; I let a delegated task be finished in a way I wouldn't have chosen, as long as it meets the standard I actually stated; if I take a task back, I say why, instead of quietly absorbing it again. None of these require the outcome to be perfect. They only require that you can look back and say whether you did the thing, which is what keeps this from being a private intention to "trust people more" that nobody, including you, can actually check.

Where this differs from control, and from leadership

A principle about control is broader — it governs your general need to manage outcomes and environments, including plenty of things nobody else could do for you anyway. A principle about delegation is narrower and more specific: it governs one recurring decision point, the moment a piece of work could plausibly go to someone else, and whether it actually does. It is also not the same as a principle about leadership, which covers how you set direction and treat people in general. You can be a genuinely good leader in every other respect and still be the reason your own desk is the bottleneck, because leadership is about the people around the work, and this is about the specific mechanics of letting a task leave your hands.

Stress-test it against the task you're still holding

Take the specific piece of work from your own pattern-mining above — the report, the summary, the task three other people could plausibly do by now — and run the rule against it directly. If the rule would have you hand it off this week, in the way it describes, it has teeth; keep it as written. If it wouldn't change anything about this exact task, the rule is aimed at the wrong moment and needs rewriting, not abandoning — the overload you noticed is still real information, the first draft of the rule just didn't reach it.

Efficiency is one of the six areas CreedOS ships templates for, alongside social, emotion, money, health, and cognition, if you would rather start from an existing shape than a blank page. Each check-in has a note field for what specifically happened, not just a score, which is where a rule like this earns its keep — a task quietly redone by hand for the fourth time in a row is easy to miss day to day and obvious the moment a month of notes sits next to each other in the review. It is free, with no in-app purchases.