Post on LinkedIn March 16, 2026
Delegation gets treated as a leadership skill. In practice, it is a clarity problem wearing a leadership costume.
When delegation fails repeatedly, the instinct is to look at the person who received the work. They didn’t follow through. They missed the standard. They needed more guidance than expected. Sometimes that’s true. More often, the breakdown happened before the work ever left your hands, in the moment you handed something over without fully defining what “done” actually meant.
This is not a minor distinction. It determines whether delegation builds capability in your team or quietly trains them to wait for your correction.
What gets handed off versus what gets defined
Most delegation looks like this: you identify work that doesn’t require your direct involvement, you assign it to someone with the apparent capacity to handle it, and you move on to the next thing. The assumption underneath that sequence is that the person receiving the work understands what success looks like from your perspective.
That assumption is responsible for significant leadership frustration.
You have a mental picture of the finished product. It includes standards that feel obvious to you because you’ve built them over years of doing similar work. The problem is that those standards live entirely in your head until you make them explicit. The person you’ve delegated to is working from their own mental picture, shaped by their experience, their interpretation of the brief, and their best guess about what you actually need.
When the work comes back, and it isn’t right, both of you are operating in good faith. The gap between what you expected and what was delivered is not a performance gap. It is an information gap, and it was created upstream of the handoff.
Liz Wiseman’s research in Multipliers captures a related dynamic. Leaders who consistently get the most from their teams are not those who delegate most frequently. They are those who create the conditions for others to do their best thinking. That includes giving people enough clarity about the outcome that they can exercise genuine judgment in how to get there, rather than spending their energy trying to reverse-engineer what the leader wants. (Wiseman, Multipliers: How the Best Leaders Make Everyone Smarter, multipliersbooks.com)
The three things that have to be named
Before work leaves your desk, three things need to be explicit. Not implied, not assumed, not obvious to anyone who’s been paying attention. Written down or stated clearly enough that the person receiving the work could repeat them back without guessing.
The first is the outcome, and this is different from the task. A task describes the activity. An outcome describes the result the activity is meant to produce and why it matters. “Draft the proposal” is a task. “Draft a proposal that gives the client enough information to make a decision at Thursday’s meeting without needing a follow-up call” is an outcome. The second version tells the person what the work is actually for, which changes how they approach every decision inside it.
The second is the standard. What does good look like? Where is the line between a draft that needs minor refinement and one that needs to go back to the beginning? Most leaders can answer this question instantly when they see the finished work. The gap is that they haven’t answered it before the work begins. Naming the standard in advance does two things: it gives the person doing the work a reference point for their own judgment, and it removes the subjective element from the review conversation when the work comes back.
The third is ownership. Who decides when this is done? Who can make calls inside the work without checking back? Where does the boundary sit between their authority and yours? Unowned decisions are the most common reason delegated work stalls or escalates back up. When ownership is named clearly, the person doing the work knows what they can run with and what genuinely needs your input. Without it, they default to caution, and every uncertainty becomes a question that lands back on your desk.
Why leaders skip this step
Defining outcomes, standards, and ownership before a handoff takes time. Not significant time, but real time, and it happens at a moment when most leaders are already moving fast, and the path of least resistance is to hand the work over with a quick verbal brief and trust that the rest will sort itself out.
There is also something more honest to name here. For leaders who built their careers on doing the work well, articulating the standard can feel awkward. The standard is intuitive. It has been internalized through years of practice. Translating it into words that someone else can work from requires a kind of deliberate effort that doesn’t come naturally when the standard feels self-evident.
But self-evident to you is not the same as self-evident to someone with a different context, a different experience base, or a different tenure in the role. The standard that lives in your head is not available to anyone else until you surface it.
Harvard Business Review’s research on delegation effectiveness found that one of the most consistent failure points is the gap between what leaders think they communicated and what the person receiving the work actually understood. Leaders consistently overestimate the clarity of their handoffs, not because they are careless, but because they have context the other person doesn’t have. The mental shorthand that makes communication feel complete on one end frequently doesn’t carry across. (HBR, “To Be a Great Leader, You Have to Learn How to Delegate Well,” hbr.org)
What changes when you name it first
When delegation is built on explicit outcomes, clear standards, and named ownership, several things shift in ways that compound over time.
The volume of check-ins drops. Not because people are less engaged, but because they have a reference point they can work from independently. They know what they’re aiming for, and they know what level of decision they can make without coming back to you.
The quality of the work improves. Not dramatically overnight, but consistently. People produce better outputs when they understand what the output is actually for, not just what they’ve been asked to do.
Your correction load decreases. Work that comes back wrong requires diagnosis, feedback, and often a second round. Work that was scoped clearly from the start requires only refinement. The downstream cost of a vague handoff is almost always higher than the upfront cost of properly defining the work.
And over time, your team builds judgment rather than compliance. There is a meaningful difference between a team that executes instructions well and a team that understands the standard well enough to make good calls inside the work without constant supervision. The first requires your ongoing presence. The second doesn’t.
A practical test
Before the next significant piece of work leaves your desk, answer three questions out loud or in writing.
What does success look like when this is complete, specifically enough that the person doing the work could measure it themselves?
What would make you revise the work versus approve it, and have you communicated that distinction clearly?
Who owns the decisions inside this work, and where does their authority end?
If any of those answers are unclear to you, they will be even less clear to the person receiving the work. That gap is worth closing before the handoff, not after.
Delegation is not a transfer of labour. It is a transfer of ownership. And ownership is clear only when the destination has been named.
Sources
Liz Wiseman, Multipliers: How the Best Leaders Make Everyone Smarter Available at: multipliersbooks.com
Harvard Business Review, To Be a Great Leader, You Have to Learn How to Delegate Well Available at: hbr.org/2017/10/to-be-a-great-leader-you-have-to-learn-how-to-delegate-well
