Trust was not the hard part of delegating
I handed over a monthly report to someone I trusted completely, and it still nearly went out wrong. The task went across. Everything I knew about it stayed with me.
Part 3 of 5 in Becoming a Lead.
I once handed a monthly stakeholder report to someone I trusted completely, and it nearly went out in a state I would not have been happy to put my name to.
He was capable. He was not careless. He did roughly what I had asked, which was the problem, because what I had asked was “can you take the monthly report”. That was the entire brief.
What I had not said was who actually reads it, what tone it needs to carry, how deep the detail should go, or the date it truly has to be finished by rather than the date on the calendar. All of that was in my head, and none of it made the trip. It came back thinner than it needed to be and later than was comfortable, and I ended up going in to salvage it.
The question I thought I was answering
Up to that point I had been treating delegation as a trust decision. Do I believe this person can do this. If yes, hand it over. If no, keep it or give it to someone else.
The answer that day was an unqualified yes, and it still nearly went wrong, which is how I found out I had been asking the wrong question.
Trust is necessary. It is the thing that makes you willing to let go at all, and without it you never start. But trust is about the person, and almost everything that went wrong was about the work. Nothing about his ability would have told me that he did not know the finance lead skims it for two numbers and ignores the rest. I knew that. I had known it for so long I had stopped noticing it was knowledge.
What a handover actually has to carry
The task is the easy part to transfer, because it is the part that is already written down somewhere.
What lives only in your head is the rest of it. Who the audience really is, as opposed to who is on the distribution list. What this thing is for, which is often not what it looks like it is for. How much detail earns its place before it starts costing you attention. What good looks like, in a form more useful than “good”. And when it is actually needed, which is nearly always earlier than the deadline, because someone has to read it before it goes anywhere.
None of that is a specification and I am not suggesting you write one. It is closer to a conversation you have once, properly, at the start, instead of a correction you make repeatedly at the end.
The test I use now is simple enough. If the person could do the work exactly as asked and still produce something I would rewrite, then I have not finished handing it over.
Control to influence
The shift underneath all of this is from control to influence, and it is daunting. You go from being able to determine an outcome to being able to shape the conditions around it and then living with what comes out.
It can be done, and it rests on something less mystical than it sounds: whether you have put the energy in beforehand, so that when a judgement call arrives and you are not in the room, the person makes the call you would have made. Not because they are guessing at what you want, but because they have enough of what you know to reason it out themselves.
That is the real work of delegating, and it happens before the handover rather than during it. Influence is not a weaker form of control. It is control exercised earlier, through someone else’s judgement instead of your own hands.
This is the same transition as the promotion itself, arriving in a smaller and more specific form. The measure moved from what you produce to what your judgement lets other people produce, and delegation is where that stops being an idea and starts being a Tuesday afternoon.
On guardrails
Letting go with guardrails sounds like the safe middle path, and it can quietly be the riskiest option of all, because it feels like a control that is not really there.
A guardrail that only catches a problem at the end is not a guardrail. It is a deadline with better branding. What I had on that report was a date, and a date told me it had gone wrong at the precise moment it was too late to do anything but rescue it.
The ones that work are early, small and cheap. A look at the outline before the writing starts. A short conversation at the point where the shape is decided but the effort has not been spent. Neither of those is supervision, and both of them are recoverable without anyone doing the work twice.
The dive and save, and what makes it worth something
I did go in and fix that report, and I would do it again. There are moments where the thing has to be right and there is no time left for anything else.
But going in is a decision with a cost, and the cost is that you have just demonstrated the safety net exists. Do it often and people stop reaching for the edge of what they can do, because you have shown that you will always catch it.
The part that made it worth something was not the salvage. It was going back afterwards and working through the gaps with him, deliberately, as growth areas rather than as a post-mortem on a near miss. Same conversation, entirely different meaning, depending on whether you frame it as what went wrong or as what you now both know.
And I owed him most of that conversation, because the brief was mine.