Why Do My Managers Keep Avoiding Difficult Decisions?

Responsibility without authority creates hesitation

You cannot tell somebody:

“You're responsible for this result.”

while retaining every meaningful decision required to produce it. That creates a strange kind of pseudo-ownership. The manager is responsible when things go wrong. But they are not really empowered to act when something needs deciding. No wonder they check. Authority should broadly match responsibility. Not unlimited authority. Appropriate authority.

Look at what happened last time they decided

This is an uncomfortable leadership question. Suppose your manager previously made a sensible decision without asking you. You disagreed. What did you say? Perhaps:

“Why didn't you check with me?”

Perhaps you immediately reversed it. Perhaps you criticised the result without discussing the thinking. What did they learn? Next time, ask first. Leaders can accidentally train permission-seeking while simultaneously complaining that their managers lack initiative. If every imperfect decision gets punished, decision avoidance becomes rational.

Stop confusing a different decision with a bad decision

A manager may make a decision you would not have made. That does not automatically make it wrong. Perhaps both options were reasonable. Perhaps they had different information. Perhaps their judgement needs refining.

But if you require managers to reproduce exactly the decision you would have made, why employ managers? You have created messengers. Leadership development requires some tolerance for sensible variation.

Difficult decisions are rarely difficult because there is no answer

Often they are difficult because the answer has consequences. Someone will be disappointed. A customer may complain. An employee may become defensive. Money may be lost. There is uncertainty. The manager may have to say no. They may need to challenge somebody.

They may have to accept responsibility if the outcome is poor. That is where judgement becomes real. It is much easier to make a decision when everybody will be happy with it. Leadership begins to show when that is not possible.

Teach them that their job is not to eliminate uncertainty

Newer managers often want certainty before deciding. They ask:

“But how do I know this is definitely the right decision?”

Often, you don't. Business decisions are frequently made with incomplete information. The job is not always to discover the perfect answer. It is to:

understand the issue; gather enough evidence; consider sensible options; understand the risk; make your best judgement; act; and then learn from what happens. That is management.

Ask for their recommendation before giving yours

When someone brings you a difficult decision, resist answering immediately. Ask:

“What do you think?”

Then:

“What are the options?”

“What are you concerned about?”

“What does the evidence say?”

“What do you recommend?”

“Why?”

Now you can see their thinking. That is much more useful than merely seeing whether they happened to guess the same answer as you.

Don't accept “I don't know” too quickly

Sometimes: “I don't know” means exactly that. But sometimes it means:

“I'm frightened of being wrong.”

Or:

“I haven't thought about it yet.”

Or:

“If I wait long enough, you'll decide for me.”

So try:

“Humour me. What's your best judgement?”

Or:

“If you had to decide today, what would you do?”

Or:

“What would you advise another manager in exactly this situation?”

You are not forcing false certainty. You are helping them move beyond avoidance.

Make them distinguish facts from fear

A useful decision conversation separates: What do we know? from: What are we imagining might happen? Managers can become paralysed by hypothetical consequences. What if the customer leaves? What if the employee resigns? What if the supplier gets angry? Possible. But how likely?

What evidence do we have? What is the cost of not deciding? That last question is often missing. Delay has consequences too.

No decision is still a decision

Managers sometimes behave as though waiting is neutral. It isn't. If poor performance continues while you avoid the conversation, that is a decision. If a customer issue remains unresolved, that is a decision. If a process stays broken, that is a decision.

If two employees remain in conflict because nobody wants to intervene, that is a decision. You have chosen the status quo. Once people understand that, indefinite delay starts looking rather different.

Put a time around the decision

Not every difficult question should be answered instantly. Sometimes more information genuinely is needed. Fine. Agree: What information? Who will obtain it? By when? When will the decision be made? Now you have thoughtful delay rather than avoidance. There is a big difference.

Don't let consultation become camouflage

Good managers consult. They ask experts. They seek alternative views. They involve people affected. That can produce better decisions. But consultation can also become a sophisticated form of procrastination. Another meeting. Another opinion. Another stakeholder. Another spreadsheet. Eventually ask:

“What specifically do you still need to know before you can decide?”

If the answer is vague, perhaps the problem is no longer information. Perhaps it is courage.

Teach managers how to bring a decision upwards

Some decisions genuinely need senior approval. Fine. But even then, do not accept:

“What do you want me to do?”

Ask for: The issue. The evidence. The options. The risks. The recommendation. Now they are still thinking like a manager even though somebody more senior owns the final decision. That is very different from handing the whole problem upwards.

Let the decision remain theirs when it should

This is where leaders often sabotage development. The manager presents their thinking. It is sensible. Then the senior leader says:

“Leave it with me.”

Why? If the manager has the authority and capability to act, let them act. You can support. You can challenge. You can add information. But keep the decision where it belongs. Otherwise you have taught them that serious thinking still ends with the boss taking over.

Review decisions afterwards

Judgement develops through reflection. After an important decision, ask: What happened? What did you expect to happen? What surprised you? What did you get right? What would you do differently? What will you remember next time? That turns experience into learning. Without reflection, people can repeat the same poor decision process for years.

Capture useful decision knowledge

Some decisions contain lessons the organisation should remember. Why did we choose this supplier? Why did we change this policy? What happened with that customer? What did we learn from the failed project?

If that reasoning lives only in one person's memory, the organisation can end up re-litigating the same question later. Capture important decision knowledge. Not every tiny choice. The decisions whose reasoning will matter again. That strengthens future judgement.

Don't undermine the manager afterwards

Suppose an employee dislikes their manager's decision and comes to you. Be careful. If you immediately overrule the manager, you may solve one problem while creating another. Ask:

“Have you discussed this with your manager?”

Understand the reasoning. If the decision needs changing, involve the manager in that conversation. Otherwise the organisation learns: If you dislike a decision, appeal upwards. And managers learn: My decisions aren't really decisions. That guarantees more escalation.

Difficult people decisions are often the ones most avoided

Performance. Behaviour. Role fit. Promotion. Ending an arrangement. Saying no to someone valued. Those decisions have emotional consequences. Managers may delay because they hope something will change. Sometimes it does. Often the problem simply gets older. The question becomes: What evidence am I waiting for that I don't already have? That can be revealing.

Don't demand courage without creating clarity

It is easy for a senior leader to say:

“Just make the call.”

But if the organisation has never clarified: the standard; the authority; the decision criteria; the escalation boundaries; then “be more decisive” is not particularly useful coaching. Help managers understand the framework within which judgement should operate. Then ask them to exercise it.

There are decisions managers should escalate

Independent thinking does not mean making every decision alone. Escalate appropriately where there is:

serious safety risk; legal exposure; ethical concern; major financial consequence; something beyond delegated authority; a genuine crisis; or an issue where the manager does not yet have the necessary experience. Good judgement includes knowing when not to decide alone.

The objective is not reckless independence. It is appropriate decision-making.

Look for a pattern of permission-seeking

Listen to the language.

“Can I...?”

“Should I...?”

“What would you do?”

Occasionally, fine. But if those questions dominate, ask:

“Why do you think you need my permission for this?”

Perhaps the answer exposes unclear authority. Perhaps lack of confidence. Perhaps previous leadership behaviour. Perhaps habit. Once you know why, you can develop the right thing.

Give feedback on the reasoning

If the manager's decision was poor, do not only say:

“Wrong answer.”

Ask: Where did the thinking go wrong? Was important evidence ignored? Did they misunderstand authority? Did they fail to consider risk? Did they act too quickly? Did fear drive the decision? Did they fail to speak to someone they should have consulted? Now you are developing judgement. That is far more valuable than simply replacing one decision.

Notice good judgement

Someone makes a difficult but sensible call. Notice it. Particularly if the outcome was not perfect. You might say:

“I think the reasoning was sound even though the result wasn't what we hoped for.”

That is powerful. It tells the manager that thoughtful judgement matters. If you only praise decisions that produce perfect outcomes, people may become increasingly risk-averse.

The leader's aim is to become less necessary for ordinary decisions

Over time, ask: Which decisions still need me that shouldn't? What was once appropriate escalation may now be unnecessary dependence. A manager should gradually become capable of carrying more. The level of decision that reaches you should move upwards.

If it never does, either their judgement is not developing or you are not releasing enough authority. Both deserve attention.

A simple decision-development process

When a manager brings you a difficult decision, try:

1. Clarify the issue

What actually needs deciding?

2. Establish the facts

What do we know?

3. Identify the authority

Whose decision is this?

4. Explore options

What could we do?

5. Examine consequences

What are the risks and trade-offs?

6. Ask for a recommendation

What do you think we should do?