Atiba de Souza.Start a conversation
WritingLeadership

You Delegated the Task. You Never Delegated the Thinking.

By Atiba de Souza

An editorial cover image for a piece on You Delegated the Task. You Never Delegated the Thinking. The cover reads: LEADERSHIP You Delegated the Task. You Never Delegated the Thinking.

The list that came back untouched

I was working with a doctor who was planning an open house. Before he left for a week and a half of vacation, he gathered his team and gave them the list. Everything that had to be ready by the time he got back, for an event four or five weeks after his return.

He came back and asked what had gotten done.

Zero.

Not half. Not the easy items. Zero percent of the list. Meanwhile the regular work was done, all of it, because the regular work was the work they knew they were paid for.

His first read, and probably yours, is that the team dropped the ball. That is not what happened. They made a decision, and it was a rational one. Nobody had told them why the open house mattered or how the pieces fit together, so the list was not a priority. It was an extra sitting on top of the work that pays them. Given that choice, a person picks the paying work every time, and does not feel bad about it.

Zero percent. Not because the team was lazy. Because the list was the only thing he delegated.

He thought he had delegated the work. He had delegated the doing. He kept the deciding.

Delegate thinking, not tasks

Delegate thinking, not tasks. That is the whole model, and it is where most delegation advice quietly fails you. The advice is usually about the task: write the SOP, hand it off, check the box, move on. Follow it and you get hands. You do not need more hands. You need people who can run the thing without you standing in the room, and that only happens when the thinking moves.

Which raises the question almost nobody asks: how do you know whether the thinking actually moved?

Here is the test, and it is the only one I trust. Did a decision move?

A task has a finish line. A decision has a fork. Hand off a task and you hand off doing. The person produces what you would have produced, the way you would have produced it, and reports back. The choice never left your desk. Nothing about you had to change, which is exactly why it feels so productive.

Hand off a decision and you hand off choosing. They pick something you might not have picked. That is not a side effect of the handoff. That is the entire product. If you can still overrule the output without anyone noticing that something changed, you did not delegate thinking. You delegated typing.

Delegating a decision: handing someone the authority to choose, the context to choose well, and the certainty that being wrong will not cost them that authority. Remove any one of the three and you have handed them a task with extra steps.

Read that definition again and count how many times you have done all three. For most leaders the honest number is close to zero, and they have delegated a great many tasks.

What you are actually protecting when you keep the decision

Here is what nobody says out loud. Keeping the decision feels like quality control. It is almost never quality control. It is one of three fears wearing a lanyard.

The first is clean: if they choose wrong, it lands on me. True. That is the job.

The second is the honest one: if they do not need me to decide, what am I for? Nobody wants to say that in a meeting. Most of the hoarding comes from there.

The third is the one that costs you comfort: I will have to watch this get decided at a level below mine and not reach in. Yes, you will. That is the tuition. There is no version of this where you get the owner and skip the watching.

So the price of fixing this is not a system. It is a feeling you have to sit through.

The four dollar decision that told me everything

On a weekly team call, Shaina Ballesteros was stuck. Two podcast hosting services, four dollars a month apart. Roughly $15 or $19, less than a thousand pesos a month on the table, and a person I trust was frozen, because she was afraid of getting it wrong.

Earlier, Sophia Mendoza had run a cold-email campaign that spent almost a thousand pesos and produced nothing. She had told me she was disappointed in herself.

So I gave Sophia the bigger budget.

Read that back. The person who had just lost money was the one I handed more of it to. Not despite the failure. In front of it, in the same conversation, on the same call. I told her she got to decide whether we spend even more on it. She said she wanted to spend more. I said okay.

And here is the part that matters. Had I treated Sophia's failed campaign as the reason to take spending decisions off her, both women would have learned the same lesson on the same call. Shaina would have learned it from watching. Sophia would have learned it from living. Neither of them would have decided anything again without checking with me first, and I would have called that good management.

Shaina's problem was never the four dollars. The size of the decision is not the size of the fear. A stalled small decision is not a small-decision problem. It is a permission problem. And you do not fix a permission problem by shrinking the decision. You fix it by handing over a bigger one.

The three legs, and which story proves which

Every leader I know who can actually hand over a decision is standing on three things, and none of them is a template. Vision. Openness. Great questions. It is the spine of the thing. Aimed at a team, the three look like this.

Vision. If a person cannot rank your priority against the work they already know they are paid for, your priority loses. This is the doctor, and it is the biggest lever in this piece. He had the right list and no why. A team without the why will always default to the work they understand.

Openness. This is the hardest one, and the one people misread. Openness is not a feeling you perform in a meeting. It is the condition where a wrong answer can be said out loud in the room without the person losing standing. Sophia said the thing almost nobody says, that she was disappointed in herself, and the response was a bigger budget, not a smaller one. Reverse that, and you get a team that hides bad results until hiding them is impossible. Understand the difference between openness and confession: confession is about you, Openness is about whether the truth can survive contact with your reaction.

Asks great questions. Not telling, not fixing. A question is what makes them do the thinking instead of you, and the highest-value place it shows up is not the handoff. It is the return: asking how it went instead of announcing what you would change. This is the leg with no story in this piece. The doctor proves what happens when vision is missing and Sophia and Shaina prove what openness buys. The third leg you have to take from the return section, because that is where it does its work, and it is the leg you will fake first. "How did it went" is easy to say and hard to say with your hands in your pockets.

Rank matters, so here is mine. Vision is the biggest lever. Openness is the hardest to sustain. Great questions are the cheapest to imitate and the ones you will get wrong first. And the smallest thing in this entire piece, the thing people spend the most hours on, is the handoff mechanics. The wording. The template. The chart with the boxes on it. Nobody was ever liberated by a better template. You can have a beautiful handoff document and still be the only person on the team who decides anything.

When not to do this

I am not telling you to hand over everything.

Do not delegate a decision when the downside cannot be reversed. Signing authority you cannot claw back, legal exposure, money you genuinely cannot replace. In those cases, delegate the decision about how, and keep the decision about whether. Say so plainly, so the line is visible and nobody has to guess where it sits.

Do not delegate a decision you cannot describe the purpose of in one sentence. If you cannot say why it matters and how it fits, you have not delegated anything. You have set a trap.

And do not delegate as a test. If any part of you is waiting to see whether they sink, do not hand it over. Delegation as a trap is worse than no delegation, because it burns the person and confirms the thing you were afraid of.

The return is where this dies

There is a moment where decision delegation gets killed, and it is almost never the handoff. It is the return.

You come back from the trip, the launch, the conference, the week that ate you. You walk into a decision your team made without you. It is not the decision you would have made. You can see three things wrong with it inside a minute.

You think you are helping. From their side, you are weather.

Your return does not land as support. It lands as disruption, and it lands hardest on decisions you no longer understand well enough to improve. When you re-enter delegated work, you do not upgrade the decision. You delete the person who made it. Everyone watching learns the actual rule, which is that the work is theirs until the owner walks into the room.

Which means the next time you leave, the smart move on their part is to focus on the regular work. Because the regular work is the only thing that survives your return.

What movesTask delegationDecision delegation
What the person receivesA listA purpose and a budget of authority
What they get to chooseHowWhether, and which
When they get it wrongYou take it backTheir authority holds
What you do when you returnFix itAsk how it went
What the team learnsDeciding is dangerousDeciding is the job

A task

A decision

You hand off work

What moved

They do what you would have done

You still decide and they still wait

You leave and the paid work wins

You return and re-decide

Lesson lands. Deciding is dangerous.

Vision set. Why it matters and how it fits.

Authority granted. The call is theirs.

Failure does not remove authority

Owner

You return and ask how it went

Lesson lands. Deciding is the job.

Three questions before you hand it over

Before you open your mouth, run the decision through this. It uses nothing you do not already have.

One. Can you say why it matters and how it fits, in one sentence? If it takes a paragraph, the vision is not there yet, and a list without a why loses to the paying work.

Two. Is the downside survivable? Not comfortable. Survivable. If being wrong here would take the person's standing, their budget, or the business down, this is not the decision to hand over. Somewhere on your desk is a decision where a loss is a lesson instead of a wound. That one.

Three. On return, can you ask how it went instead of fixing it? If the honest answer is no, you have not finished deciding this. You are still attached, and your return will reverse whatever you hand over today.

Monday

You do not need a system. You need one conversation and then a nerve you have to hold for weeks.

Pick one decision you currently make on your team's behalf. Use the three questions. Not the biggest one. One where being wrong is survivable, where you can say why it matters and how it fits in a sentence, and where you can honestly picture yourself asking how it went.

Tell the person who should own it three things: why it matters, how it fits with everything else they are carrying, and that the call is theirs now. Then say the hard part out loud, so they hear it and not just you. If you get it wrong, I am not taking it back from you.

Now the part that no delegation framework will do for you.

All three fears will show up. The first one is easy to spot because it has a deadline attached: if they choose wrong, it lands on me. It will. That is the job, and it is why you picked a decision where the landing is survivable. The second is quieter and arrives about three days in, usually disguised as a sudden strong opinion about a detail that did not matter to you last week. That is not expertise. That is the question of what you are for, showing up in a meeting agenda. The third gets you on the return, when you see three things wrong in a minute and every instinct tells you that fixing it is help. It is not help. From their side it is weather, and weather teaches a team to build for storms instead of building for customers.

Expect the team to hedge. If you have ever reached back in after handing something over, they already know the real rule, and it is not the one you said out loud. They will check with you on small things. They will ask permission they have already been given. They will give you a version of the decision that leaves a door open for you to walk through. That is not a personality flaw on their side. That is a memory. The only thing that overwrites it is a return where you touch nothing, more than once, until the record changes.

And the real test is not the handoff. The handoff is a conversation, and conversations are easy. The test is the first time they choose differently than you would have and the thing wobbles. Everything before that moment was a speech. That is where you find out whether you meant it, and so do they.

You already know which decision it is. You have been holding it because you are good at it. That is exactly why it is the one to hand over.

A task done is a task done. A decision delegated is a person built. You only get one of those from a to-do list, and it is not the one you are short on.