Why employees always wait for the boss’s approval

In many companies, people ask for confirmation even when they understand the work. Before replying to a customer, changing a priority or organizing a task, they wait for a manager. The boss becomes the route through which everything must pass, and work slows down.

It is easy to describe this as a lack of initiative. Dependence often comes from how the organization distributes information, responsibility and risk. When boundaries are unclear or mistakes are judged after the fact, asking for approval becomes a prudent choice.

Imagine a customer-support employee who receives a simple request to move a delivery by a few days. The process is familiar and there is no cost, but the limit is not written. The employee asks the manager, who is in a meeting. The answer arrives the next day while the customer waits.

A second example concerns a marketing team changing a newsletter format. The test is reversible and the budget is unchanged, but a similar change was once criticized because it did not match the director’s preference. Since then, every variation is sent for approval. The issue is uncertainty about what will count as an error.

Start by recording recurring approval requests for two weeks. Note the decision, the person waiting, the manager involved, the response time and the stated reason. Look for patterns: missing information, no threshold, changing criteria or uncertainty about who has the final say.

Choose one frequent and relatively reversible decision. Define the expected result, the cost or risk limit, people to consult and the threshold for escalation. Put this agreement on one accessible page. “Choose the best option” is not a mandate if the criteria remain hidden.

The manager’s role is to protect direction, boundaries and learning rather than review every detail. When someone asks for confirmation, ask what they recommend, what evidence they used, which limit matters and what they would do if the result disappointed them.

After a month, check waiting time, requests sent to the wrong person and decisions reopened without new evidence. If a choice goes badly, review the process: was information missing, was the limit too broad or was a known rule ignored? The aim is not to stop people asking for help, but to make help necessary only when it adds value.

Distributing decisions also requires a way to learn from outcomes. A decision can be reasonable with the evidence available and still produce a disappointing result. Review the assumptions and the process rather than treating the outcome as proof that nobody should decide independently.

A small decision log preserves this learning. Record the date, subject, owner, criteria, limits and review date. Over time it shows which questions keep returning to the top and which rules could be made simpler.

Delegation fails when the manager continues to request updates on every detail. Agree on a few signals instead: expected result, deadline, main risk and review point. The person closest to the work can choose the method unless an explicit constraint applies.

The right to refuse a competing request is part of a real mandate. Someone who must protect a priority but cannot reject additional work has responsibility in name only. Define how exceptions are negotiated and who decides when priorities conflict.

The same logic applies to temporary projects. A project manager may coordinate the work, but budget, quality, timing and customer commitments still need clear owners. A job title does not assign decision rights by itself.

Measure the change with simple signals: less waiting, fewer requests sent to the wrong person, fewer reopened decisions and clearer next steps. If nothing improves, revise the mandate before adding another control.

When a decision exceeds its threshold, escalation should arrive as a useful package: situation, options, recommendation, risk and decision required. This keeps senior people from becoming a manual routing system and lets them focus on choices that truly need their responsibility.

Explain the new way of working to people affected downstream. A rule is clear only when they know whom to contact, what information to provide and when to expect an answer. Communication is therefore part of implementation, not a final announcement.

Do not document every activity in the company. Start with one workflow that creates friction, test the mandate and observe a real case. Extend the model only when experience shows the same ambiguity exists elsewhere.

The aim is an organization where control remains where it matters and autonomy grows where the risk allows it. Leadership becomes more useful when it clarifies direction and boundaries instead of repeatedly replacing other people’s work.

A useful distinction is between advice and consent. A colleague may have valuable experience and should be heard, while the decision owner still has the authority to choose. Treating every conversation as an approval process gives informal influence the same weight as a formal veto.

Make the decision visible after it is made. State what was chosen, why, who is affected and when the result will be reviewed. People are less likely to ask for the same approval again when they can find the reasoning and the boundary that applied.

The manager should also respect a delegated decision after asking for context. Requesting progress updates is different from reopening the choice after every comment. If the mandate is repeatedly withdrawn in practice, the team will correctly conclude that the written agreement is not real.

Some approvals exist because two objectives have never been prioritized. Sales may need speed, finance may protect margin and operations may avoid exceptions. Agreeing on the order of these criteria can remove more waiting than adding another person to the approval chain.

When a proposal is rejected, record a reusable reason. “Not a priority this quarter” is different from “the risk is too high” or “the team cannot support the change”. Clear reasons help people make better proposals and prevent the same question from returning unchanged.

The right to stop or cancel a choice also matters. If new evidence weakens the original case, the owner should be able to pause the work within the agreed limits. Learning from a decision requires room to change course, not only permission to begin.

Approval requests also increase when priorities compete. A person may know how to complete the task but not which promise takes precedence. Make the order visible so employees do not have to guess which criterion matters most.

A useful review asks whether the employee had enough context at the moment of choice. Do not judge the decision only with information that appeared later. This makes feedback fairer and prevents people from protecting themselves with another approval.

Publish a short list of decisions that are already delegated, with examples, limits and the escalation route. People may continue asking because they remember an old rule or do not know that the boundary has changed. Visibility is part of authority.

The manager should explain the change to colleagues who receive the decision. If another department still treats the manager as the only valid approver, the employee will be pushed back into dependence. Autonomy works across a process, not only inside one team.

Review the agreement when the work, risk or team changes. A threshold that was sensible for a small volume may become too broad later. Scheduled review keeps autonomy connected to the real situation.

An employee should also know how to escalate without presenting a vague request. A useful escalation includes the situation, the options considered, the recommendation, the risk and the decision needed. This helps the manager decide rather than reconstruct the problem.

The first experiment should be small enough to observe. Choose one workflow, announce the new boundary, review real cases and ask what information was missing. A focused trial creates better evidence than a general instruction to be more autonomous.

Communicate the final choice in plain language so downstream colleagues can act without opening a second approval loop. State what changes, for whom and from when.