You may have delegated the activity while keeping the decisions, standards, and consequences with you. Delegate the win by making the result, ownership, boundaries, support, and proof visible before the work begins.

You may have delegated the work while keeping ownership with you

You ask someone to prepare the proposal.

They gather the information, arrange the slides, and send you a draft. You review it, change the central message, rewrite the recommendation, and decide what the client should see first.

The employee did the work.

You still carried the result.

This happens in many forms. Someone collects the data, but you decide what it means. Someone contacts the customer, but every response requires your approval. Someone coordinates the project, but you resolve the conflicts, set the priorities, and recover every delayed commitment.

You have delegated activity.

You have not delegated the win.

That may explain why you continue feeling responsible for everything. Tasks leave your desk, but the thinking, decisions, and consequences keep returning.

Delegation begins when another person owns what must become true—not merely the activity required to produce it.

This does not mean disappearing after assigning the work. It means transferring a meaningful result together with the decisions, boundaries, support, and proof needed to carry it.

A task tells people what to do

A task names an activity.

Prepare the report.

Call the customer.

Coordinate the event.

Talk to the supplier.

Conduct the training.

These instructions can move work quickly, especially when the activity is familiar and the expected result is already understood.

But many assignments are not that simple.

“Call the customer” could mean confirming receipt, apologizing for a delay, recovering trust, negotiating a new commitment, or gathering information before a decision.

The employee may complete the call and still miss what mattered.

This is why leaders sometimes say, “I delegated it, but I still had to finish everything.”

The employee may say something different:

“I did exactly what I was asked to do.”

Both may be telling the truth.

The task was completed. The win was never made clear.

A win describes what must become true

A win tells the person what the activity must accomplish.

Instead of saying, “Call the customer,” you might say:

“Help the customer regain confidence that we own the delay. Confirm which part of the order they need first, agree on a commitment we can keep, and surface any decision you need from me before three this afternoon.”

Now the person can see what success looks like.

The call is only one move. The result is restored confidence supported by a credible commitment.

Instead of saying, “Prepare the meeting,” you might say:

“Prepare the team to decide which two projects we will protect this month and which work will wait. Give them the information they need to see the trade-offs before they enter the room.”

Again, the activity remains. But the person now understands what the activity must make possible.

The shift is simple to describe:

From completing an assigned task to owning a defined result.

Making that shift requires more than changing one sentence. The leader must be willing to transfer parts of the work that often remain hidden.

Pause and look at what you are still holding

Think about the last important assignment you delegated.

What did the other person actually receive?

They may have received the activity, deadline, and format. But who kept the decisions? Who defined the standards? Who managed the difficult relationships? Who decided when the work was finished?

Who worried about the result at night?

If the answer is still you, then the task moved but ownership did not.

This is not always a mistake. A new employee may need close direction. A high-risk assignment may require decisions that remain at your level.

But sometimes leaders hold too much because they have become accustomed to carrying it.

They delegate what can be seen and keep what feels consequential.

The employee prepares the deck. The leader owns the message.

The employee gathers the options. The leader owns the recommendation.

The employee follows up. The leader owns the commitment.

Over time, employees become efficient assistants to the leader’s judgment. They stay busy without developing the ability to carry an important result.

Begin with the result, not the steps

The first conversation should make the win visible.

Ask yourself:

What must become true when this work succeeds?

Do not begin with everything the person must do. Start with the result another person should be able to see, experience, decide, or use.

Suppose you want an employee to investigate recurring customer complaints.

You could say:

“Review the complaints from the last three months and prepare a report.”

The person may count the complaints, classify the issues, and produce a clean presentation.

The report could be accurate and still fail to move anything.

A clearer delegation would be:

“Identify the two moments where customers are most often left without clear ownership. Recommend one change we can test next month, and show the evidence behind your recommendation.”

Now the person has a result to carry.

The research, analysis, and presentation serve that result.

This connects with the earlier work of moving decisions closer. A person cannot truly own a win while every meaningful choice remains with the manager.

Explain why the result matters

People make different choices when they understand the reason behind the work.

Suppose you delegate the preparation of a monthly operations review.

Without context, the employee may include every available number because a complete report appears more professional.

But perhaps the meeting exists to identify customer commitments at risk.

Tell the person:

“The leadership team does not need another summary of everything that happened. They need to see which commitments may fail, why they are at risk, and what decision could protect them.”

The reason shapes the work.

The employee now knows which information deserves attention and which details can remain in the written report.

Purpose does not require a long motivational speech.

Sometimes one sentence is enough:

“This matters because the customer cannot plan unless we give them a commitment they can trust.”

“This matters because the supervisor should not remain the approval point for a decision the team already understands.”

“This matters because the meeting must release the work, not create another meeting.”

When the reason is visible, people can adapt without losing the direction.

Make ownership unmistakable

A task may be assigned to someone without that person feeling responsible for the final result.

They may see themselves as the coordinator, messenger, or support person. When a problem appears, they bring it back to the manager.

Clarify ownership early.

You might say:

“You own this customer concern until the commitment is fulfilled. Other departments may contribute, and I will help when authority is required, but the customer should not have to find another owner.”

Or:

“You own the recommendation. I may challenge your reasoning, but I do not want you to give me a pile of information and wait for me to decide what it means.”

Notice the difference.

Ownership does not mean the person performs every task alone. It means the person remains accountable for moving the result across the required contributions.

They coordinate. They follow what is missing. They raise risks early. They know when support is necessary.

And when someone asks who owns the result, the answer is clear.

Transfer enough authority to carry the result

You cannot delegate a win while withholding every decision required to achieve it.

Imagine telling someone:

“You own the event.”

Then the person discovers that every supplier choice, schedule adjustment, communication, and expense requires your approval.

They own the anxiety.

You own the event.

Authority should travel with the result.

The person needs to know which choices they can make, which choices require consultation, and which choices must return to you because the consequences exceed their boundary.

For example:

“You may choose the supplier, adjust the activity sequence, and communicate directly with participants. Keep the total cost within the approved budget. Return to me if the venue, date, or promised outcome must change.”

The boundary protects what matters without forcing routine decisions upward.

This is not unrestricted freedom. It is responsible decision space.

The person can act without guessing whether every move will be questioned later.

Do not turn your preferred method into the only acceptable method

This may be one of the hardest parts of delegation.

You know how you would do the work.

Your sequence feels logical. Your language has worked before. Your format is familiar. You can see the fastest path from assignment to result.

Then the employee chooses another approach.

You feel the urge to correct it.

Pause.

Ask whether the difference threatens the result, violates a boundary, or creates a meaningful risk.

Perhaps the person’s method is simply not your method.

When you require people to reproduce every choice you would make, you are not transferring ownership. You are extending your hands through another person.

There are moments when the method matters. Safety procedures, legal requirements, brand commitments, and technical standards may need exact compliance.

But where judgment is part of the work, allow more than one valid path.

The win should be firm.

The method may remain flexible.

Agree on what support looks like

Delegation fails when support is confused with rescue.

The employee receives the work. Difficulty appears. The leader steps in, takes over the customer conversation, rewrites the proposal, or calls the uncooperative department.

The immediate problem may disappear.

So does the employee’s ownership.

Support should help the person continue carrying the result.

Before the work begins, discuss what support may be needed.

Does the person need access to information?

Will another department respond only with your introduction?

Is technical advice available?

What decision or obstacle would justify your involvement?

This allows the employee to ask for help without handing the work back.

You might say:

“If another department has not responded after two clear requests, bring me the history and the commitment you need. I will help remove the obstacle, but you will remain the owner of the result.”

The distinction is important.

You are supporting the owner.

You are not replacing the owner.

Set a checkback without taking the work back

Some leaders avoid checkbacks because they want to show trust.

Others ask for updates so frequently that the person never feels trusted.

Neither approach helps the work.

A useful checkback is an agreed point where both people examine movement, risks, decisions, and support.

It is not a surprise inspection.

It is also not a full transfer of responsibility back to the leader.

Suppose the assignment will take two weeks. Waiting until the final day may create unnecessary risk. Asking for updates every few hours may create unnecessary control.

You could agree:

“Let us check on Wednesday afternoon. Bring the customer response, any risk to the commitment, and the next decision you intend to make.”

The employee knows what to bring.

The leader knows when to expect visibility.

Between checkbacks, the person has room to work.

The checkback protects the result without making the leader the center of every move.

Name the proof before the work begins

You and the employee may imagine different endings.

You think the customer concern is complete when the customer has received the correct item and confirmed that operations can continue.

The employee thinks it is complete when the replacement request has been sent to logistics.

Both may say, “Done.”

The proof settles the difference.

Ask:

What will we be able to see when the win has been achieved?

For a proposal, proof may be that the client can recognize the problem, understand the recommended first move, and decide whether to continue.

For a meeting, proof may be a clear decision, one owner, a due date, and the evidence expected afterward.

For a customer concern, proof may be the customer’s confirmed result—not merely the internal transfer.

Proof makes ownership concrete.

It prevents activity from being mistaken for completion and gives the employee a basis for deciding whether more work remains.

The delegation conversation needs a handshake

A handshake is an agreement both people can describe.

Before the conversation ends, the leader and employee should hold the same picture of the delegation.

Use six questions:

What is the win?
What must become true?
Why does it matter?
Which customer, priority, commitment, or result does it serve?
Who owns it?
Who remains responsible for moving the complete result?
What decisions travel with it?
What may the person decide, and what must be consulted or escalated?
What support and checkback are available?
When will progress be reviewed, and how will the leader help without taking over?
What proof will show completion?
What must be visible before both people call the work done?

This is not a form the leader must recite mechanically.

It is a practical play: a repeatable choice and action used in a recurring leadership moment. The internal leadership architecture defines a play as something leaders can retrieve and use when pressure makes the familiar response tempting.

In this case, the familiar response is task assignment followed by correction, rescue, and control.

The new play makes the win and ownership visible before the person begins.

Ask the person to play the delegation back

After an important delegation, ask the person to explain the agreement in their own words.

Not because you want to test their memory.

You want to see whether both of you are carrying the same result.

Ask:

“What do you understand the win to be?”

“Which decisions will you make?”

“When will you involve me?”

“What proof will tell us that the work is complete?”

The answers may expose confusion early.

The employee may think you want a complete solution while you expect only a recommendation. They may assume every customer message requires approval. They may not know that they are expected to coordinate another department.

A two-minute conversation can prevent days of rework.

It can also reveal something you failed to clarify.

Delegation is not a speech delivered by the leader. It is an agreement built between two people.

Do not delegate only what you no longer want to do

Some leaders treat delegation as a way to remove low-value work from their calendars.

Routine administration, follow-ups, documentation, and coordination are passed downward. Important analysis, customer judgment, planning, and decision-making remain with the leader.

Employees receive more tasks.

They do not receive more meaningful contribution.

This creates a familiar complaint:

“I delegate all the time, but my people are not growing.”

Growth does not come from volume alone.

People grow when they carry results requiring judgment, coordination, decisions, and learning.

That does not mean assigning work beyond their readiness. It means finding a meaningful result they can carry with appropriate boundaries and support.

Perhaps the employee has prepared reports for months. The next delegation could include deciding which issue deserves leadership attention and recommending the response.

Perhaps the supervisor has scheduled meetings. The next delegation could include producing a specific decision from the room.

Move more than labor.

Move contribution.

Do not dump the win and disappear

Delegating the win can be misused.

A leader assigns a difficult result, says, “You own this,” and becomes unavailable. The employee lacks authority, information, or support. When the result fails, the leader points to the assigned owner.

That is not delegation.

It is abandonment with accountability language.

The owner should have a realistic chance of carrying the work.

Ask what conditions the result requires. Does the person have access to the right people? Can they see the necessary information? Will other leaders respect their authority? Is there enough time to learn without creating unacceptable risk?

Ownership needs support, especially while it is developing.

The organization’s supervisory material describes the desired movement as from rescuing to building ownership. It also makes clear that responsibility should be transferred without abandoning support or taking the work back.

The challenge is to avoid both extremes.

Do not carry everything for people.

Do not leave people alone with work they cannot yet carry.

Watch what happens when pressure arrives

Delegation often looks clear until the deadline becomes threatened.

The manager becomes anxious. The employee’s approach takes longer than expected. A customer asks a difficult question.

Then the familiar play returns.

“I’ll handle this.”

The manager takes over because the result matters.

There may be moments when taking over is necessary. The consequence may be too serious, or the remaining time too short.

But if this happens repeatedly, the team learns that ownership lasts only while the work is easy.

The Leader’s Game describes this pattern clearly: a manager may understand delegation but still take over when a deadline is threatened. Under pressure, leaders return to the response most available to them.

So prepare for the pressure moment.

Agree beforehand on what the employee should do when the commitment is at risk. Should they revise the plan, recommend options, ask for a specific decision, or call for additional help?

Make the response visible before the problem appears.

Delegation becomes dependable when it survives difficulty.

Do not take the whole result back because one part needs help

Imagine an employee carrying a customer recovery.

The financial exception exceeds their authority. They bring the decision to you.

You approve the exception, then contact the customer yourself, direct logistics, and close the case.

The decision needed you.

The complete result did not.

A more disciplined response would be:

“I will approve the exception because the amount exceeds your boundary. You remain the customer owner. Confirm the revised commitment and follow it through to completion.”

Only the decision moves upward.

Ownership stays where it belongs.

This distinction matters because complex work often includes decisions at several levels.

Delegation does not require every choice to remain with one person. It requires the result to retain a visible owner while the correct authorities contribute.

The system must recognize the delegated owner

You may delegate a result clearly, but the organization may continue treating you as the real owner.

Other departments ignore the employee and wait for your message. Senior leaders direct questions to you. The system requires your approval at every stage.

The employee quickly learns that the authority you offered is not recognized elsewhere.

Look around the delegation.

Who has access to the required information?

Whose name appears as the owner?

Who is invited to the decision meeting?

Who receives the follow-up questions?

Who is held accountable by the measures?

The broader work of making execution daily matters here. Ownership will not survive if routines, permissions, and leadership behavior keep pulling the result back to the manager.

Sometimes the most useful support is public recognition of the owner:

“Maria owns this result. Please work with her directly. I will remain available for decisions outside her boundary.”

One sentence can shift how the organization responds.

Review the win, not only the employee

When the work is complete, do not review only whether the employee performed well.

Review the delegation itself.

Was the win clear?

Did the person receive enough authority?

Were the boundaries useful?

Did the checkback happen at the right time?

Did the system recognize the owner?

Which part required unnecessary escalation?

This keeps the conversation from becoming a judgment of the person alone.

The leader may discover that the assignment was unclear. The employee may realize that they waited too long before surfacing risk. Both can identify what to repeat or change.

That is Strategic Learning at work: make what matters clear, act, follow what becomes visible, and improve the next move.

The goal is not merely to complete one delegation.

It is to improve the organization’s ability to transfer and carry meaningful work.

Start with one win you usually keep

Choose one result you often carry personally.

Not the largest one.

Choose something meaningful enough to require judgment but contained enough for another person to practise ownership.

Then prepare the delegation:

Name what must become true.
Explain why the result matters.
Choose the owner.
Transfer the decisions that can responsibly travel with the work.
Clarify the boundaries and available support.
Agree on the checkback and proof.

Have the conversation.

Then resist two temptations.

Do not disappear when difficulty appears.

Do not take the work back simply because the person’s path differs from yours.

Stay close enough to support the result and far enough away for ownership to become real.

Build people who can carry the win

You will always have tasks to assign.

The organization also needs people who can carry results.

People who can see what must become true, make decisions within clear boundaries, coordinate others, surface risks, seek useful support, and follow proof until the work is complete.

That ability does not grow because you tell people to take more ownership.

It grows when you give them something meaningful to own.

Delegate the win.

Then make the authority, support, checkback, and proof strong enough for the win to remain with them.

The next article, Meetings That Move Work, will examine another place where ownership often disappears: the meeting where people discuss important work, agree in general, and leave without a clear decision or commitment.

Delegate the Win, Not Just the Task