
Some managers don’t know how to delegate. Some cannot delegate because of organisational controls. And some simply don’t want to delegate. I have seen all three, and the differences are worth examining.
Over the years, I have observed something interesting about managerial behaviour.
We often complain that managers are overloaded, that decisions get delayed and that employees depend too heavily on their superiors.
The usual explanation is that managers don’t know how to delegate.
But I believe the problem goes much deeper.
Some managers become bottlenecks because of the way organisations structure responsibilities and decision-making. Some lack the ability to delegate effectively. And some deliberately retain control because they want others to depend on them.
I have encountered contrasting examples of these behaviours in my own professional experience.
What struck me most was that the difference between managers was not necessarily their technical knowledge, experience or seniority. It was how they viewed their authority and their responsibility towards the people working under them.
1. When the organisation itself creates the bottleneck
I don’t believe that every decision passing through a manager is evidence of poor delegation.
Organisations need systems of authority, financial controls and accountability. Certain decisions must pass through designated officials. Without proper approval limits and escalation procedures, delegation can create confusion and inconsistent decisions.
For example, a purchase executive may be authorised to negotiate with vendors and process routine purchases, while commitments above a specified financial limit require departmental approval.
That is a legitimate control mechanism.
The problem begins when organisations fail to distinguish between decisions that genuinely require managerial intervention and those that could be handled independently within established boundaries.
Routine matters start travelling upwards. Employees seek approvals even when policies already provide the answer. Managers become involved in activities that do not necessarily require their attention.
Eventually, the manager becomes the common point through which everything must pass.
This may not be the manager’s personal preference. It may simply be how the organisation has designed its operating system.
The distinction is important. Removing necessary controls in the name of delegation can create chaos. The objective should be to eliminate unnecessary dependency, not managerial oversight.
2. When managers don’t know how to delegate
I have also observed that technical competence and managerial competence are two different things.
A person may be extremely knowledgeable in a particular function but may not necessarily know how to develop people or distribute responsibility effectively.
Delegation requires more than assigning tasks.
A manager must explain expectations, establish boundaries, provide the necessary resources and allow employees sufficient freedom to perform their responsibilities.
Some managers struggle with this.
They may find it easier to do the work themselves than to explain it to someone else. They may expect employees to perform at their own level of experience and become frustrated when the results are not immediately satisfactory.
Others assign tasks but retain every meaningful decision.
The employee does the work, but the manager continues to control how it is done, when it is done and what decisions can be taken.
This is not effective delegation.
It is merely the distribution of workload without a corresponding distribution of authority.
Such managers may genuinely believe they are maintaining quality and efficiency. But in reality, they may be preventing employees from developing independent judgement.
This is primarily a managerial capability problem and can often be addressed through coaching, training and better role design.
But I believe there is another category that deserves considerably more attention.
3. When managers simply don’t want to delegate
In my view, this is one of the more damaging forms of managerial behaviour.
Some managers don’t merely struggle to delegate. They actively prefer others to remain dependent on them.
They want to be consulted, involved and recognised as indispensable.
Their importance is reinforced by the number of people who need their intervention.
I have seen behaviour that raises questions about the psychological motivations behind this tendency.
The need to exercise control
I have encountered managers who find it difficult to accept even minor deviations from their personal preferences.
I recall an instance from my early career when I was working as a junior manager and drafting official letters for submission to a senior officer.
On one occasion, I used the expression “Please see” in a draft. The manager changed it to “Kindly see”.
In the next letter, I used “Kindly see”. The manager changed it back to “Please see”.
Neither expression was inherently incorrect. Yet the manager repeatedly reversed my choice.
The issue was not whether one expression was better than the other. It was the absence of any consistent standard or meaningful improvement in the communication.
I began to wonder what purpose such corrections actually served.
There is a difference between reviewing a subordinate’s work to improve its quality and changing acceptable work merely because it is not one’s own.
I would describe the latter as control without contribution.
When this behaviour becomes habitual, employees gradually learn that even minor decisions are not really theirs to make.
The need to remain indispensable
Some managers appear to derive considerable satisfaction from being the person everyone depends on.
They retain information, insist on being consulted and remain involved in routine activities.
The department may struggle whenever they are unavailable, but they may interpret this dependence as evidence of their importance.
There can be several psychological motivations behind such behaviour:

These tendencies do not necessarily indicate a clinical personality disorder. However, when they become persistent, they can seriously undermine organisational effectiveness.
Keeping subordinates away from exposure
Another experience from my professional life was particularly revealing.
I worked under a departmental head who never involved me in official meetings held within the office. Nor did this officer take me along to meetings with other officials or external parties.
I was involved in performing official responsibilities, but I was not given opportunities to observe how related discussions and decisions took place.
Later, I worked with another departmental head who followed a completely different approach.
This officer invariably took me to meetings, both within the office and outside it.
The difference was remarkable.
By including me, the second officer exposed me to discussions, decision-making processes, official interactions and the way issues were handled at higher levels.
I could understand not just what needed to be done, but why it needed to be done and how decisions were arrived at.
The first approach restricted exposure. The second encouraged professional development.
Of course, not every meeting is appropriate for every subordinate. Confidentiality and the relevance of the discussion matter. But consistently excluding a person from relevant official interactions can deprive that person of valuable professional learning.
It also raises an important question: Does the manager see the subordinate as someone to develop or merely as someone to execute assigned work?
A manager can distribute work while simultaneously restricting the opportunities through which employees develop.
4. The psychological side: Why do some managers behave this way?
I find this aspect particularly interesting because it goes beyond conventional discussions about delegation.
Why would a manager retain so much work, involve themselves in every decision and make others dependent on them?
In some cases, the behaviour may be driven by psychological tendencies rather than genuine operational requirements.

These tendencies can overlap.
I would not automatically describe such behaviour as a personality disorder. Clinical diagnoses require proper professional assessment, and workplace behaviour alone is insufficient.
But organisations should not ignore persistent controlling and dependency-creating behaviour simply because the manager is technically competent or delivers short-term results.
5. The organisation sometimes rewards the very behaviour it complains about
There is another dimension that I believe organisations frequently overlook.
Managers who personally resolve every issue are often praised for their commitment.
Those who work late to clear pending decisions are considered dependable. Those who know every customer, vendor and operational detail are treated as invaluable.
But what about managers who develop employees capable of handling these responsibilities independently?
Their contribution may be less visible.
The organisation ends up rewarding personal intervention rather than the development of organisational capability.
It celebrates the manager who repeatedly rescues the department instead of recognising the manager who has built a department that rarely needs rescuing.
This creates a peculiar contradiction.
The organisation complains about managerial dependency while rewarding the behaviour that perpetuates it.
In some cases, the manager may even receive greater recognition precisely because the department cannot function without them.
The organisation has mistaken indispensability for effectiveness.
6. Role description versus role design: Where does the problem really lie?
This brings me to another distinction that I consider fundamental.
A job description tells us what a person is expected to do.
It lists responsibilities, reporting relationships, qualifications and expected outcomes.
But does it explain how the person is expected to perform those responsibilities?
Does it establish what decisions can be made independently? Does it define authority limits? Does it clarify how responsibilities are shared between positions?
These are questions of role design.
I believe many organisations devote considerable attention to preparing job descriptions but insufficient attention to designing how roles should actually function.
For example, an operations manager may be responsible for production, procurement, vendor coordination and timely delivery.
But if every production adjustment, routine purchase and vendor interaction requires personal approval, the organisation has created a role that is unnecessarily dependent on one individual.
The job description may be perfectly written. The role itself may be poorly designed.
And even a well-designed role can become a bottleneck if the person occupying it deliberately refuses to share authority or information.
This is why role design alone cannot solve every delegation problem. Organisational structure and managerial behaviour must be examined together.
7. How can an organisation identify the real problem?
I would not recommend automatically blaming managers whenever employees depend on them.
Instead, organisations should examine the underlying reasons.
Consider these questions:

The answers can help distinguish necessary control, managerial inability and deliberate dependency.
The corrective action must depend on the cause.
Organisational design problems require clearer authority and approval structures.
Capability problems require managerial development.
Deliberately controlling behaviour requires accountability, performance evaluation and, where necessary, changes in managerial responsibility.
Simply asking everyone to delegate more will not solve all three.
8. The ultimate test of managerial effectiveness
I often think that the effectiveness of a manager should be judged not merely by how much work gets completed under their supervision, but also by how well the department functions without their constant involvement.
Consider two managers.
The first is involved in practically every decision. Employees approach this manager for instructions, approvals and problem-solving. The department struggles whenever the manager is unavailable.
The second has established clear responsibilities, developed capable employees and distributed decision-making authority within defined limits. The department continues functioning smoothly even when the manager is away.
The first may appear more indispensable.
The second has created something much more valuable: an independent and capable team.
This is the difference between being personally essential to every activity and building an organisation that performs effectively through its people and processes.
A manager’s effectiveness should not be measured by how many decisions depend on them, but by how effectively the organisation functions without depending on them for every decision.
A final thought
From my own professional experiences, I have come to believe that managerial bottlenecks cannot always be explained by an inability to delegate.
Sometimes the organisation creates unnecessary dependency through its structure and approval systems.
Sometimes managers lack the skills to distribute responsibility effectively.
And sometimes managers deliberately retain control because being indispensable reinforces their importance, influence or sense of security.
The most damaging situation occurs when the organisation unknowingly encourages such behaviour.
Employees are denied opportunities to develop. Managers retain control. Senior management rewards visible intervention. And the organisation gradually becomes dependent on a few individuals.
The consequences extend beyond delayed decisions. They affect employee development, succession planning, organisational resilience and the ability to grow.
Perhaps the most important question every business owner should ask is:
Are we developing managers who build capable teams, or rewarding managers who make their teams dependent on them?
There is a fundamental difference between the two.
One builds organisational strength.
The other builds organisational dependency.
Explore more resources on business bottlenecks.
Explore more insights in the Knowledge Hub.
Discover more from Enterprise Insights
Subscribe to get the latest posts sent to your email.