A purchase order waits for one signature. A customer waits for one answer. A designer waits for one approval. Across the office, small queues begin forming around a single desk, and the manager at its center feels indispensable because everyone needs something from them. That is the trap. A manager can become so useful that usefulness turns into dependency, and dependency can quietly become one of the most expensive forms of inefficiency an organization creates.
Bottlenecks rarely begin with bad intentions. Managers become bottlenecks because they were rewarded for being capable problem solvers, so difficult decisions naturally migrate toward them. Soon, they approve expenses, rewrite proposals, settle customer complaints, review designs, resolve conflicts, and make decisions their teams could have handled themselves. Work continues, which makes the system look functional. Nobody notices that the entire organization has begun moving at the speed of one person’s calendar.
Apple’s success under Steve Jobs illustrates a more complicated lesson about executive involvement. Jobs was deeply involved in important decisions, yet Apple also depended on strong functional leaders and teams capable of carrying substantial responsibility. The distinction matters. At a construction company, Reuben discovered that supervisors were delaying routine purchases because they had learned that asking senior management was safer than making a decision. He created clear spending boundaries. The approvals queue shrank, supervisors became more decisive, and Reuben discovered that control had been masquerading as quality.
Bottlenecks often hide behind the language of standards. “Nobody can do this properly unless I check it” sounds responsible until the manager becomes the final inspector for everything. Celeste, a creative director, once reviewed every campaign headline before publication because she believed her involvement protected the brand. One morning, six minor approvals consumed the time she needed for an important client meeting. Her deputy asked, “Which of these decisions actually required you?” The question landed harder than criticism because it exposed a habit that had been disguised as excellence.
Delegation is therefore more than handing somebody a task. It means transferring enough context, authority, and accountability for another person to make a sound decision without returning for permission every few minutes. Toyota’s emphasis on solving problems close to the work offers a useful management principle because knowledge and authority become more effective when they meet near the source of the problem. A manager who approves everything may feel central to the organization, but centrality is not leadership. Leadership creates more people capable of exercising judgment without needing constant rescue.
The uncomfortable test is simple: what happens when the manager disappears for a week? If work freezes, customers wait, and employees gather around an empty chair, the organization has built dependency rather than leadership. Strong managers create systems where decisions travel outward, responsibility follows authority, and competent people can act without waiting for permission. The best evidence of managerial success may therefore look strangely unimpressive from the outside. Nobody is asking for approval because everyone already knows who owns the decision, what boundaries apply, and what happens next.
