تفویض اختیار یعنی انتقال مسئولیت، نه پخش کردن کار

One of the most common management mistakes is believing that assigning a task automatically means delegating authority.

It does not.

Very often, we have only distributed the work.

The responsibility still sits with the manager, the decision still belongs to the manager, and the person who is supposed to move the work forward has to return for permission at every step.

From the outside, this looks like delegation. In practice, it only creates traffic.

For years, I thought that being involved in every detail gave me more control.

Later I learned that more control does not always mean better management.

Sometimes it simply means the team does not know where its decision authority begins and ends.

Real delegation starts with one simple question:

What result is this person responsible for?

Not merely what tasks they need to perform.

The result matters more than the task list.

If you tell someone, ‘You are responsible for customer follow-up,’ a lot is still unclear.

But if you say, ‘You are responsible for making sure no sales opportunity remains without a defined follow-up,’ the perspective changes.

Now that person has to decide.

They have to prioritize.

They have to report.

And most importantly, they have to be accountable.

But responsibility without authority is meaningless.

If every small discount, call, time change, or minor decision still requires manager approval, that person is not responsible for the result; they are simply executing instructions.

That distinction matters.

Managers often say, ‘I gave them authority,’ when in reality they only assigned work.

At the first disagreement, they take the authority back.

At the first mistake, every decision returns to the manager.

And then we ask why the team never becomes independent.

Teams do not become independent through slogans.

They become independent through clear decision boundaries.

In my view, proper delegation needs four things to be explicit.

First: the expected result.

Second: the scope of authority.

Third: the measurement criteria.

Fourth: the review point.

If those four are unclear, the manager either interferes constantly or the employee never knows whether the decision was right.

If you are responsible for purchasing, for example, you should know the amount you can approve.

Which suppliers are approved.

Which conditions require manager approval.

What the red lines are.

When those things are clear, speed improves.

But more important than speed is the growth of people.

Someone who is always waiting for instructions never becomes the next manager.

A future manager is someone who makes decisions within the right boundaries and sees the consequences of those decisions.

That means you have to let people make some choices themselves.

Even when your own choice might have been slightly different.

This is difficult for managers.

Because very often we interfere not because the team’s decision is wrong, but because it is not exactly the decision we would have made.

Those are not the same thing.

If the outcome is right, the method does not always have to be your method.

If management becomes an exercise in copying the manager’s mind, the team does not grow.

You only create smaller versions of the manager.

A good team should be able to discover methods that are better than the manager’s.

Good delegation creates that space.

But freedom without accountability is also a mistake.

Delegation means freedom to decide alongside responsibility for the result.

Not freedom without measurement.

That is why reporting matters.

Not reporting for moment-by-moment control.

Reporting for learning.

What decision did you make?

What happened?

What worked?

What should change?

When that conversation exists, even mistakes become assets.

When it does not, mistakes are either hidden or repeated.

Over time, I learned that a team afraid of making mistakes also becomes afraid of making decisions.

Everything gets pushed upward.

And the manager who pulls everything upward becomes the bottleneck.

So delegation is not only about reducing the manager’s workload.

It is about building organizational capacity.

It means making decision-making possible in several places, not only in one person.

This is especially important in small organizations.

Usually one or two people are more experienced, so naturally everything gathers around them.

But if that continues, company growth stops.

The organization grows only to the size of that person’s capacity.

No further.

To break that ceiling, knowledge has to move.

Authority has to move.

And measurement has to become clear.

Today, when I delegate, I try to speak less about ‘how to do it’ and more about ‘what result we need.’

If the risk is low, I let the person choose the method.

If the risk is high, the framework becomes stricter.

There is no single version for everything.

Smart delegation means matching the level of authority to the level of risk.

And one more point:

A manager has to tolerate decisions that are not identical to their own.

If you correct every difference, the team learns very quickly not to decide.

They learn only to guess what the manager wants.

Then the organization looks orderly, but it does not really think.

That is not the kind of order I want.

I would rather have a team that thinks, decides, makes controlled mistakes, learns, and improves.

For me, delegation today means exactly this:

Give the responsibility for real.

Define the authority clearly.

Measure the result.

And then let people grow.

If every decision still returns to you, you have not delegated yet.

You have only distributed the work.