When capable employees must seek permission for routine decisions, management does not create control. It creates a queue.

I have seen teams full of experienced people who could diagnose the problem, explain the risk, and recommend the right action—then sit and wait because only the manager was allowed to decide.

It usually begins with good intentions. A leader wants consistency, fewer mistakes, or visibility into what is happening. So approvals are added.

Then another approval is added because something went wrong once.

Before long, the manager becomes a human traffic light and the team forgets how to cross the road without permission.

The IT delivery example: an Application Support team that cannot act

Imagine an Application Support team responsible for a customer-ordering platform. The team knows the application, understands common failure patterns, and has documented recovery procedures.

One morning, order confirmations begin failing intermittently. An experienced analyst identifies a stuck processing queue. The approved recovery procedure is straightforward: pause one service, clear the failed messages into a recovery queue, restart processing, and monitor results.

The analyst has performed the procedure before. The risk is low, the steps are documented, and the business impact is growing.

But policy requires the manager’s approval.

The manager is in another meeting. The analyst sends a message, updates the incident ticket, and waits. The Service Desk continues receiving calls. Sales teams begin chasing orders manually. Customers receive no confirmations and submit duplicate orders because they are unsure whether the first transaction worked.

Forty minutes later, the manager approves the exact action the analyst recommended at the start.

The recovery takes five minutes.

The technical problem lasted less than an hour. The management design created most of the delay.

The damage goes beyond response time

For employees: experienced people learn that judgment is neither trusted nor required. Initiative becomes risky because acting without permission may be punished, while waiting is procedurally safe. Over time, employees stop bringing recommendations and simply bring problems.

For service delivery: queues form around a few managers, restoration slows, and minor issues become major incidents. Managers become overwhelmed by decisions that should never have reached them, leaving less time for coaching, planning, risk management, and stakeholder leadership.

For customers: delays, duplicate transactions, inconsistent communication, and avoidable downtime become visible. Customers experience the approval chain as poor service—even if every internal box was correctly checked.

For the organization: expensive capability sits idle while work waits for authority. The organization pays for experienced specialists but operates them like entry-level staff. It also creates concentration risk: when the approver is unavailable, the service becomes unavailable with them.

What human behaviour tells us

People adapt to the environment around them. When independent decisions are repeatedly blocked or second-guessed, employees may reduce initiative and defer responsibility. This can resemble learned helplessness: not because people are incapable, but because experience teaches them that effort and judgment do not reliably change the outcome.

Decision avoidance can also become rational. If waiting for approval protects an employee from blame while acting creates personal risk, the safest behaviour is obvious: wait.

This is not proof that every employee should receive unlimited authority. It is a reminder that behaviour follows the consequences built into the system.

‍

Discussion question: What routine decision is your team still waiting for permission to make?