The Five-Minute Delegation Script
You've spent the last three weeks reading your Origin Code from the inside out. First the Over-Functioning Mandate: the rule that ties your safety to your output, and insists rest has to be earned before it's allowed. Then the Blame Node: the rule that routes every organisational failure back through you first, before the facts are even in. Then, last week, the Silent Operator: the rule that keeps you flawless and quiet so nobody has reason to look closely. Reading a rule clearly is real progress. It isn't the same as interrupting it in the ten seconds before you actually hand a piece of work to someone else, which is the one moment all three rules tend to show up at once, fastest and loudest.
This week is a change of pace. Not another file to open. A script: five literal minutes, run immediately before you delegate, built to get the work out of your hands before the old code has time to talk you out of it.
Why Delegation Is Where All Three Rules Collide
Delegation looks like a logistics problem: who has capacity, who has the skill, who owns the deadline. For a leader running any version of the Origin Code, it's rarely just that. Picture the moment itself: a piece of work lands on your desk that you could hand off cleanly, and instead you find yourself keeping it "just for now," rewriting a colleague's draft instead of giving feedback on it, or scheduling the handoff conversation for a day that keeps quietly slipping. That hesitation has a shape, and it's usually one of three.
The Over-Functioning Mandate reads "let someone else do this" as "stop earning your safety," and answers with a dozen good-sounding reasons why it's actually faster to just do it yourself. The Blame Node calculates, correctly, that if you keep the task you also keep total control over the outcome, and total control feels like the only real insurance against a failure landing back on you. And the Silent Operator knows that handing work off means explaining what you know out loud, in a form someone else can question, which is a small, specific act of being seen.
Three separate rules, one shared conclusion: keep it. We've already looked at the psychology underneath this, back in the Delegation Dilemma: the Self-Enhancement Bias that makes your own involvement feel like the secret ingredient, and the Identity of the Doer that turns letting go into a threat to your worth. That diagnosis was accurate, and it still isn't enough on its own, because naming why delegation feels dangerous doesn't tell you what to actually do in the ten seconds before you hand the work over. That's the gap this script is built to close.
The good news is the same three rules that make delegation hard also tell you exactly what a working script has to do. It has to remove the ambiguity the Over-Functioning Mandate exploits, name a responsibility narrow enough that the Blame Node can't expand it, and get the ask out of your hands fast enough that the Silent Operator doesn't get a vote.
The Five-Minute Delegation Script
Run this immediately before you hand off a piece of work you'd normally keep, while the urge to just do it yourself is still active. It's meant to be quick and slightly uncomfortable. That's the point.
Minute 1 - Name the task, and name the rule. Write one sentence: what you're about to hand off, and which rule is actually driving the reluctance. Is it the Over-Functioning Mandate, insisting rest and delegation both have to be earned? The Blame Node, pre-deciding that any bad outcome is still yours? Or the Silent Operator, treating the act of explaining your own thinking out loud as too much exposure? Naming it correctly matters, because the next four minutes are addressed to the specific rule you just named, not a generic anxiety about letting go.
Minute 2 - State the authority tier. Use the three-tier language from the Zero-Ambiguity Delegation Protocol covered earlier in this newsletter: can this person Decide independently, Decide after checking with you, or only Recommend for your approval. Choose one, out loud or in writing. Vagueness here is exactly what lets the Over-Functioning Mandate quietly reclaim the task later, through a stream of "quick check-ins" that were never actually agreed.
Minute 3 - Write down what you're still responsible for, and stop there. Not the outcome. The setup, and the check-in cadence you'll actually keep. This is the direct answer to the Blame Node: your responsibility in this delegation is defined narrowly, in advance, in writing. A disappointing result later has a specific, bounded cause. It is not a verdict on you.
Minute 4 - Write the actual sentence you'll send or say. Not "let me know if you have any questions." That line reads as generous and functions as an exit ramp, keeping the door open for you to quietly take the task back the moment it gets difficult. Say something concrete instead: "This is yours to decide. Update me Thursday. I'm not reviewing it before then."
Minute 5 - Send it before the five minutes are up. The old rules reassert themselves fast once real urgency returns, and the deadline inside this exercise is doing real work. It gets the ask out of your hands while the decision is still consciously yours, and not the Over-Functioning Mandate's, the Blame Node's, or the Silent Operator's.
What happens next is usually the harder part, and it isn't in the script, because it can't be scripted. The discomfort of having handed something off in a form someone could question is precisely the exposure the Silent Operator has spent years protecting you from. Sitting in that discomfort, and watching nothing catastrophic follow it, is the actual evidence. Not a sixth minute. A few days of proof.
Why This One Matters More If You're Queer
If you're an LGBTQ+ executive, the calculation underneath all of this often carries extra weight, and I don't think that's paranoia. Authority that was hard-won, in rooms that weren't built assuming you'd hold it, can feel like it comes with less margin for error than the same authority held by a straight or cisgender peer. Handing off a visible piece of work, imperfectly explained, can register not just as a personal risk but as evidence someone might use, consciously or not, that you don't quite belong at the level you've already reached. That's a real cost calculation, not an overreaction, and it's exactly why a vague, feelings-based approach to delegation isn't good enough for you.
It also compounds with the Identity Tax, the extra energy cost of code-switching and hyper-vigilance that your peers simply don't pay. Every one of these five minutes takes longer when a chunk of your processing capacity is already spent managing how you're read in the room. That's not a reason to skip the script. It's the reason the script exists in a form specific enough to run on autopilot, rather than asking you to talk yourself into delegating fresh, from feeling, every single time.
This is where the script's precision does double duty. A clearly stated authority tier and a narrowly defined responsibility don't just interrupt the Mandate, the Node, and the Operator internally. They also leave a clean, professional record of what you actually asked for and why, one that can't be quietly reframed later as abdication, disorganisation, or someone who "can't manage." Delegating well, on the record, is one of the more concrete ways to build the kind of authority this newsletter exists to help you reclaim: not despite handing work off, but because of how deliberately you did it.
Next week, we leave the Origin Code behind and look at Relational Deficits and Systemic Boundaries, starting with Absorbing the Static.
I coach senior LGBTQ+ executives and leaders to dismantle their survival scripts and reclaim their executive capacity. If you want to talk through your situation, book a free Strategy Session. If you want an expert diagnosis of one specific pattern in a single working session, book The System Diagnostic.
