Oct 27, 2026

When Every Decision Comes Back to the Manager

A sudden increase in approvals can look like low ownership when it may signal that authority, trust, or expectations have changed.

A manager and employee reviewing a decision together in a quiet office

An employee who used to make decisions independently now brings everything back to the manager.

Should this email go out? Is this the right priority? Can they move forward with the customer? Does this wording look acceptable?

At first, the manager is relieved to be included. Then the pattern becomes exhausting.

The conclusion arrives quickly:

“They have lost ownership.”

That may be true. But a sudden increase in approval-seeking can also mean that the employee’s authority changed, trust was damaged, or the consequences of acting independently became less predictable.

Before telling someone to be more decisive, understand why waiting became safer than deciding.

Approval dependence is a behavior, not a diagnosis

The visible behavior is easy to describe. The employee waits. The manager answers. Work slows down.

The cause is less obvious. The employee may lack confidence, or they may be adapting to a manager who reverses decisions. A role may have expanded without clarifying which decisions remain theirs. Two leaders may be giving conflicting direction, making independent action expensive.

The same behavior can emerge from very different conditions. “Needs too much direction” describes the symptom without explaining its timing.

Ask when the employee began bringing decisions back and what happened immediately before it.

People learn where initiative is welcome

Employees notice what happens after they act.

If a decision is supported, even when the outcome is imperfect, initiative becomes easier. If it is questioned publicly, reversed without explanation, or used later as evidence of poor judgment, initiative becomes a risk calculation.

The employee may still care deeply about the work. They may be trying to avoid making the next decision that will create exposure without meaningful authority.

Managers sometimes create this pattern while believing they are providing support. Frequent edits, last-minute overrides, and requests to be included in every step can teach an employee that independent action is not actually wanted.

Look for the authority gap

Ownership requires more than a task assignment. It requires the ability to choose, prioritize, and respond to consequences.

If an employee is held responsible for the outcome but cannot set the timeline, change the scope, or resolve dependencies, approval-seeking becomes predictable. They are being asked to own the result without owning the decisions that produce it.

Map a few recent examples:

  • What decision did the employee make?
  • Who changed or questioned it?
  • What authority did the employee believe they had?
  • What consequence followed?

The pattern may show that the employee needs coaching. It may also show that the manager needs to restore the decision boundary.

Do not fix a bottleneck with more monitoring

When decisions slow down, managers often add more checkpoints. The intention is to prevent mistakes. The result can be a system in which no one feels authorized to move.

The employee asks more often because approval is required more often. The manager sees the extra requests as proof that the employee cannot operate independently. Oversight increases again.

This loop creates dependency while appearing to address it.

If the work needs review, define the review point. If the employee owns the decision, let them own it within a clear boundary. If the manager must approve, acknowledge that the role is designed that way instead of blaming the employee for waiting.

Rebuild independence in a bounded way

The answer is not to tell the employee to “just decide” and then criticize the first decision that differs from the manager’s preference.

Choose a limited area where authority can be explicit. Name the outcome, the constraints, and the decisions that do not need approval. Agree on when the employee should escalate and what information the manager needs.

Then let the employee act long enough to see whether the pattern changes. A single delegated decision is not a test; a stable boundary is.

If the employee moves with more confidence, the earlier problem may have been uncertainty about authority or trust. If they still avoid reasonable decisions despite clarity and support, the diagnosis shifts toward capability, confidence, or commitment.

The manager may need to change too

It is uncomfortable to discover that an employee’s lost ownership is partly a response to the manager’s behavior.

The manager may need to tolerate decisions that are different from their own. They may need to give feedback after the outcome instead of taking control before it. They may need to explain why a decision changed rather than simply replacing it.

That does not mean every employee choice should be accepted. It means independence cannot grow where the manager’s approval is the only safe definition of correctness.

Separate the workflow problem from the employee problem

If every decision comes back to the manager, the team has a bottleneck. The bottleneck may be the employee’s judgment, the manager’s control, or a role whose authority was never made real.

Treat the pattern as information. Reconstruct when it began, examine what happened after independent decisions, and create one clear boundary to test.

The goal is not merely to make the employee stop asking questions. It is to restore a working relationship in which questions are useful, decisions are owned, and accountability matches authority.

That is the kind of dynamic TeamClarity is designed to clarify before a manager mistakes approval dependence for a character flaw.

TeamClarity

Have a real case? Submit it.

If this pattern feels familiar in a real employee situation, the TeamClarity preview now includes an early-access case submission section you can use to share what changed.

Share This Essay