مدیری که همه‌چیز باید از او رد شود، گلوگاه سازمان است

For years, I thought a good manager was the person who knew everything.

Every call went through them.

Every decision needed their approval.

They had the answer to every question.

If they were absent, work slowed down and everyone waited for them to return.

Back then, I saw that as power.

Today, I see it more often as risk.

If everything has to pass through the manager, the manager may no longer be managing; they have become the bottleneck.

That sentence may sound harsh, but I have seen it repeatedly in practice.

An organization where every purchase, discount, hire, response, and decision waits for one person may look controlled from the outside, but it is fragile inside.

Because the speed of the organization becomes equal to the speed of that one person.

If they are tired, the organization slows.

If they are ill, the organization stops.

If they make a mistake, the error spreads.

And if they leave, much of what we thought belonged to the company leaves with them.

It took me time to understand that a manager being involved in everything is not always responsibility.

Sometimes it simply means the system has not been built.

Instead of solving the problem, the manager becomes the route through which every problem must travel.

The difference matters.

Solving today’s problem is useful.

Building a system that solves tomorrow’s version without you is management.

In the early stage, managers naturally need to be close to the details.

When the team is small, processes are young, and people are new, direct involvement is necessary.

The problem begins when this condition becomes permanent.

The manager never teaches the organization how to function without them.

The team never learns to make decisions.

And instead of growing, the company starts orbiting around one person.

In the short term, this model can even feel good.

Everyone comes to you.

Everyone waits for your opinion.

You feel like the center of everything.

But being central is not the same as building.

If ten people ask you ten recurring questions every day, the issue may not be insufficient authority; it may be insufficient process.

One of the most important things I learned in management is that not every decision needs to be a management decision.

A manager should create the framework.

Define the boundaries.

Clarify what requires approval and what does not.

Make the red lines visible.

Define the range in which the team has authority.

And then genuinely let them decide.

That is delegation.

Not assigning work while keeping every decision.

Many managers delegate tasks but not authority.

They tell an employee to do the work, but every step still requires permission.

That is not delegation.

It is only distributing labor.

Real delegation moves responsibility and authority together.

Of course, freedom without boundaries is dangerous.

The goal is not for everyone to do whatever they want.

A good system makes three things clear:

What is the goal?

What is the decision boundary?

And how will mistakes be reviewed?

When those three things are clear, the team can grow.

When they are not, you either get chaos or dependence.

I think many managers are afraid of their teams making mistakes.

So they keep everything for themselves.

But there is an uncomfortable truth:

A team that is never allowed controlled mistakes never becomes independent.

If managers try to protect people from every mistake, they unintentionally protect them from growth as well.

A small mistake that is recorded and reviewed is a training cost.

A large repeated mistake is a system failure.

Those two are not the same.

A good manager knows where experience is safe and where higher risk demands stricter process.

In sales, a small discount may be delegated.

A major credit-term change may not be.

In purchasing, choosing between two approved suppliers may be delegated.

Working with an unknown supplier may require approval.

Good management is intelligent boundary design.

Not control of everything.

Information matters too.

If information exists only in the manager’s head, delegation is almost impossible.

A team cannot make good decisions without data.

That is why system building is not just software and forms.

A system means the right information reaches the right person at the right time.

That may be a CRM.

A dashboard.

A checklist.

Or a simple approval flow.

Tools matter, but clarity matters more.

Once work is recorded, the manager can step out of daily operations and begin seeing patterns instead of only putting out fires.

They can see why an error repeats.

Why a team is slow.

Why one customer repeatedly creates problems.

Why a process takes three times longer than it should.

This is where a manager moves from daily operator to system designer.

That shift in perspective became very important to me.

A strong manager is not someone no one can function without.

A strong manager is someone whose presence adds value, while their absence does not stop everything.

Those are very different things.

If your team cannot do anything without you, it may not be loyal; it may be dependent.

If they call you for every issue, it may not mean you are highly trusted; it may mean the process is unclear.

If all information lives with you, it may not be control; it may mean the organization has no shared memory.

This perspective is uncomfortable for many managers.

Because part of managerial identity is tied to feeling necessary.

We like to believe things cannot move without us.

But the goal of management should not be to make the manager more necessary.

It should be to make the organization stronger.

Sometimes the best evidence of good management is that you can disappear for a few days and work still moves correctly.

Not because nobody needs you.

But because routine work does not need you.

Your time should be spent on decisions that genuinely require management.

The future.

Risk.

People.

Structure.

Culture.

And problems whose answers do not yet exist in the system.

Today, when I see an extremely busy manager, I do not only admire the effort.

I also ask a question:

Why does so much work still need to remain in that person’s hands?

Sometimes the team is weak.

Sometimes the team is new.

But very often, the answer is that the manager never found the time—or never chose—to build the system.

Real management eventually means reducing dependence on yourself.

Transfer your knowledge.

Document the process.

Give authority.

Measure the outcome.

And most importantly, accept that you will not always make the best decision yourself.

That last part may be the hardest.

When a good team is built, it will make some decisions better than the manager.

Because it is closer to the problem.

It has fresher information.

And it lives with that subject every day.

A manager does not need to be the smartest person in every room.

They need to create the conditions in which the best decision can come out of the room.

For me, this is where professional management separates from traditional management.

The traditional manager is the center of power.

The professional manager is a designer of capacity.

One makes every road end at themselves.

The other creates more roads.

If the organization works only when you are there, you have not yet built an organization.

You have built yourself a very large job.

And perhaps the first step toward real management is asking yourself:

Which task is still in my hands today only because I never built the system for it?