When every decision routes through one person, employees stop building judgment and service delivery slows to the manager’s availability.

Most managers do not wake up planning to create a dependent team.

They want consistency. They want to protect the customer. They want to prevent mistakes.

So an employee asks a question, and the manager answers it. An exception appears, and the manager decides. A small risk surfaces, and the manager takes control.

It feels helpful.

Until the team starts bringing everything back.

Soon the manager is approving routine choices, resolving every disagreement, rewriting updates, and becoming the human password required to unlock the operation.

A manager who must touch every decision has not created control. They have created a queue.

Three hours without the operating system

Imagine a Service Desk supporting 15,000 employees. The manager insists on approving priority changes, customer-wide communications, workarounds, and escalations to specialist teams.

On Monday morning, the manager enters a three-hour client meeting. Thirty minutes later, VPN failures begin appearing across several regions. Analysts notice the pattern. Remote Support identifies a safe workaround. But nobody has authority to publish it, raise the incident priority, or open a major-incident bridge.

Messages pile up in the manager’s chat. Tickets continue arriving. Analysts repeat the same manual troubleshooting while waiting for direction.

By the time the manager returns, the Service Desk has received 900 contacts. Abandonment has risen sharply, the resolution target is gone, and specialist teams are only beginning the investigation.

Employees feel powerless and then get blamed for not acting. Customers wait longer and lose productive time. Service delivery absorbs breached targets, avoidable transfers, and duplicated effort. The organization pays for an incident that technology caused—but managerial dependency amplified.

When capable people must wait for permission to use their capability, delay becomes part of the operating model.

Why people stop deciding

Employees pay attention to what happens after they exercise judgment.

If independent decisions are routinely reversed, criticized publicly, or treated as overstepping, escalating the decision becomes the safer behaviour. The manager may call it caution. The employee experiences it as self-protection.

Over time, judgment receives less practice. Confidence falls. People learn to ask, “What does the manager want?” instead of, “What does the situation require?”

This is not proof that every dependent team has learned helplessness or that managers should disappear. Some decisions genuinely require authority, experience, or risk acceptance.

The issue is whether escalation is being used for exceptional decisions—or as a substitute for clear guardrails.

Build judgment before you need it

Managers should define decision rights before the pressure arrives. What can employees decide? When must they consult? What thresholds require escalation? Who acts when the manager is unavailable?

Give people bounded authority, realistic scenarios, and feedback after decisions. Coach the reasoning, not only the outcome. A reasonable decision can still produce a bad result; punishing it teaches people to avoid future responsibility.

Organizations should also measure approval waiting time. If work repeatedly pauses for one person, that dependency belongs in the risk register—not in the manager’s performance mythology.

The test of leadership is not whether the team needs you. It is whether the team can still think when you are not there.

Key Takeaways

  • Every decision needs a clearly defined owner.
  • Use guardrails instead of routine permission seeking.
  • Practise judgment before high-pressure situations.
  • Coach reasoning without punishing responsible initiative.
  • Treat approval bottlenecks as operational risk.

Discussion question: If your manager disappeared for one working day, what decisions would immediately stop?