Almost every new leader fails at delegation in one of two directions, and usually both, a few months apart. The first failure is keeping everything. They were promoted because they were excellent at the work, so they keep doing the work, and the team waits while their manager becomes the bottleneck. The second failure is the overcorrection. Burned out and finally convinced they need to let go, they hand off a project, walk away, and reappear weeks later to discover it went sideways, at which point they conclude that delegation does not work and quietly take it all back.
Both failures come from the same misunderstanding. People think delegation is a transfer, that the work leaves your hands and lands entirely in someone else's. It is not. Delegation is giving away the task and the authority to do it, while keeping the accountability for the outcome. That last part is the whole discipline. The moment you give away accountability, you have not delegated. You have abdicated, and the two look similar right up until something breaks.
What you give away, and what you keep
The cleanest way I know to hold the balance is to be explicit about three different things, because conflating them is what causes most delegation to fail. There is the task, the work itself. There is the authority, the right to make decisions about how the work gets done. And there is the accountability, the answer to "whose outcome is this." Good delegation hands off the first two completely and never touches the third.
This means you have to actually give away the authority, not just the labor. If you hand someone a task but reserve every real decision for yourself, you have not delegated; you have assigned them homework that you will grade. People can feel the difference immediately, and it kills ownership. The person doing the work needs to be able to make the calls that the work requires, including some you would have made differently. That is the price of delegation, and if you are not willing to pay it, you should not pretend to delegate.
What you keep is accountability. If the project fails, the answer to "who is responsible" is still you, in front of your own boss. This is not a burden to resent. It is the thing that keeps you appropriately engaged. Because you still own the outcome, you stay close enough to catch problems early, which is exactly the involvement that separates real delegation from disappearing.
Delegate the outcome, not the method
The most common way managers strangle a delegation is by handing over the method instead of the outcome. They describe, step by step, how they would do it, and then judge the result against whether the person followed their steps. This guarantees you a slightly worse copy of yourself and a person who never learns to think.
The better move is to be ruthlessly clear about the outcome and the constraints, and then genuinely silent about the method. Define what success looks like, what the deadline is, what the non-negotiables are, the budget, the dependencies, the things that absolutely cannot break. Then let them find the path. They will solve it differently than you would, and some of the time their way will be better. The rest of the time it will be good enough, which is the actual standard, because a team of people doing things 85 percent your way is far more powerful than a team waiting for you to do everything 100 percent your way.
Match the leash to the person and the stakes
Accountability without abdication does require staying connected, and the right amount of connection is not fixed. It depends on two variables: how proven the person is at this kind of work, and how high the stakes are if it goes wrong. A senior person on a low-stakes task needs almost nothing from you. A newer person on a high-stakes task needs real checkpoints, not because you do not trust them, but because that is how you keep your accountability honest without yanking the work back.
The mechanism I rely on is checkpoints agreed in advance, not surprise inspections. At the start, you and the person decide together when you will check in and what you will look at. That distinction matters enormously. A checkpoint you both planned is support. A check-in you spring on them the moment you get nervous is surveillance, and it tells them you never really let go. Set the cadence up front, then hold to it, and resist the urge to hover in between.
Example: Imagine handing off a quarterly planning process to someone for the first time. You do not give them a playbook. You give them the outcome, a plan the whole team can execute against, the three constraints that cannot move, and a single checkpoint at the halfway mark to review the draft together. They run it differently than you would have, structuring it around themes instead of departments, and it comes out better than your version. Your accountability stays intact because of that one checkpoint. Their ownership stays intact because between the start and that checkpoint, you left them alone.
When it goes wrong, the response is the whole game
Eventually a delegated piece of work will go wrong, and how you respond in that moment teaches your whole team whether your delegation is real. If you take the work back and finish it yourself, you have just announced that delegation is conditional on nothing ever going wrong, which means it was never real. People will stop accepting hard assignments, because the downside is too high.
What you do instead is help them fix it while keeping the accountability where it belongs, with you in front of others and with them inside the team. You do not throw them under the bus externally; that is your outcome to own publicly. Internally, you debrief honestly so they learn. Handled that way, a failure becomes the most valuable thing you can give a developing leader, which is the experience of recovering from a real mistake with the authority still in their hands.
The point of delegation is capacity, not relief
People delegate to get tasks off their plate, and that is a fine short-term motive, but it is not the real prize. The prize is a team that can carry outcomes you used to carry alone, which is the only way anything scales. That requires giving people room to make real decisions, and at our company we try to keep the work itself visible enough that staying accountable does not require hovering. A shared system where you can see how a project is moving, in tools like Atlas, lets a manager keep their accountability honest without taking the authority back.
Hold the line in the middle. Give away the task and the authority without flinching. Keep the accountability without using it as an excuse to take control back. That balance is uncomfortable, which is exactly why most people collapse to one side or the other. The leaders who learn to live in the tension are the ones who eventually run things far larger than themselves.