How Do I Stop My Team Asking Me Questions They Could Answer Themselves?

The manager may be causing the problem

This is uncomfortable. Managers often complain:

“My team can’t think for themselves.”

Then when somebody asks a question, the manager answers it in five seconds. What exactly are we training? If the quickest route to an answer is asking you, people will keep using it.

Start answering questions with questions

The simplest shift is:

“What do you think?”

Then wait. This may feel painfully slow at first. It is still worth doing.

Do not answer your own question after three seconds

This is where managers sabotage themselves.

“What do you think?”

Silence. Manager immediately says:

“Well, what I would do is…”

No. Let them think.

Use “Humour me”

If the employee says: “I don’t know,” try:

“Humour me. If you did know, what would you say?”

Very often, something useful appears.

Ask what they have already tried

“What have you done so far?”

This distinguishes: genuine difficulty; from automatic escalation. It also tells you whether the person has engaged their own judgement.

Ask for options

“What are the options?”

This is a very useful thinking question. Now the employee has to move beyond describing the problem.

Then ask for a recommendation

“Which option do you recommend?”

That is where ownership starts becoming visible.

Do not turn “bring me solutions, not problems” into nonsense

Sometimes people genuinely do not yet have the answer. That is okay. You still want early warning. The better standard is:

“Bring the issue early, and bring as much thinking as you reasonably can.”

Distinguish thinking questions from permission questions

Sometimes the employee is not really asking for help. They are asking:

“Will you take responsibility for this decision?”

That is different. Listen to the language.

“Can I?”

“Should I?”

“Is it okay if…?”

If the decision is genuinely theirs, say so.

Use the phrase “This is your decision”

This can be extremely useful.

“I’m happy to help you think it through, but this is your decision.”

Now ownership stays where it belongs.

Clarify what people are authorised to decide

Constant questions often reveal unclear authority. If nobody knows what they can decide, asking the manager is rational. Define: what they can decide; what needs consultation; what genuinely requires approval. That will remove a lot of unnecessary upward traffic.

Responsibility without authority creates permission-seeking

You cannot say:

“You own this.”

Then require approval for every meaningful action. That is not ownership. It is delegated responsibility with retained control.

Give decision boundaries

People often need guardrails. For example: you can approve up to X; resolve customer issues within Y; make roster changes within Z; escalate anything outside those boundaries. Now they know.

Use thresholds instead of constant case-by-case permission

This is much more scalable. Every recurring decision should not need to be reinvented.

Ask whether you have previously punished initiative

This is important. Maybe the employee once made a sensible decision. You said:

“Why didn’t you ask me first?”

What did they learn? Ask next time. If you want independent judgement, be careful how you react when people use it.

Different does not mean wrong

An employee makes a decision you would not have made. Was it still reasonable? Within authority? Within risk? If yes, let it stand. Otherwise you will train people to guess your answer rather than develop their own judgement.

Do not make yourself the answer key

You do not want employees thinking:

“What would the manager choose?”

You want:

“What is the sensible decision here?”

That is stronger.

Explain your reasoning when useful

Sometimes the employee genuinely lacks experience. Give context.

“Here are the factors I would consider.”

That is more developmental than simply giving the answer.

Teach the decision logic

What matters? Customer impact? Cost? Risk? Precedent? Timing? Once people understand the logic, they can use it again.

Build a deeper well

Judgement develops through experience plus reflection. Decision. Outcome. Review. Learning. Next decision. Over time, the employee develops a deeper well to draw from.

Do not remove all uncertainty

Employees sometimes want certainty before acting. Business rarely provides it. Managers need to help people become comfortable making sensible decisions with incomplete information. Ask: “What do we actually know?” Then:

“What are we assuming?”

That improves judgement. Ask: “What is the downside if you are wrong?” This helps calibrate the decision. Low-consequence and reversible? Perhaps they should decide. High-consequence and irreversible? Perhaps consultation makes sense.

Teach recoverable versus irreversible decisions

Not every decision deserves the same escalation. This is a useful way to build confidence.

Push low-risk decisions down

If the consequence is minor and recoverable, let people practise. That is how judgement grows.

Stop treating every mistake as proof they should have asked

This is one of the biggest barriers. Someone makes a reasonable decision. It does not work. Manager says:

“You should have checked with me.”

Now we are back to permission culture. Instead ask: What did you know? What did you consider? What did you learn?

Review reasoning, not hindsight

A bad outcome does not automatically mean the decision was bad. Judge the thinking based on what was known at the time. And challenge lucky bad decisions The reverse matters too. Poor reasoning can produce a good result. Still coach the thinking.

Build recommendation-first escalation

A useful team standard is: When escalating, bring: the issue; the evidence; the options; the recommendation; what you need from me. That changes the quality of questions quickly.

Put this expectation in writing

If it matters, make it part of how the team works. Not a manager mood.

Use one-on-ones to review decision-making

Ask: What decisions did you make this fortnight? Which did you escalate? Why? Which could you handle yourself next time? That makes judgement development deliberate.

Track recurring questions

This is very useful. What questions do people keep asking you? Look for patterns. Perhaps the issue is not confidence. Perhaps the business lacks a rule, process or source of information.

If the same question appears repeatedly, fix the system

Do not answer it for the hundredth time. Ask: Can this become: a checklist; decision rule; FAQ; process; training point? That removes unnecessary dependence.

Do not turn every answer into a policy

You do not need bureaucracy for every edge case. Use judgement. Capture recurring and important decisions.

Build access to information

Sometimes employees ask because the manager holds all the information. Pricing. Customer history. Stock. Policy. If you want people to decide, they need relevant information.

Do not hoard context

Context improves judgement. Share enough for people to understand why things matter.

Let people see the score

If employees cannot see the evidence, they will keep asking the manager what is happening. Useful visibility supports self-management.

Define What Success Looks Like

A lot of questions are really:

“Is this good enough?”

If the standard is clear, people can self-assess more.

Teach people to self-check before asking

A simple rule: Before bringing the question, ask yourself: What do I think? What evidence do I have? What are my options? What would I recommend? That alone changes behaviour.

Ask them to write it down

For more complex questions:

“Send me three bullets: issue, options, recommendation.”

Writing improves thinking.

Do not make this punitive

The point is not to make asking difficult. It is to make thinking normal.

Keep legitimate escalation easy

You still want people to raise: safety; legal; ethical; serious customer; significant financial risk. Do not create such a strong “think for yourself” culture that people hide important risk.

The goal is not fewer questions at any cost

The goal is better questions. This is critical. You want the level of questions to rise.

Early questions may be basic

Fine. As capability grows, routine questions should reduce. More complex ones should remain. That is progress.

Watch the level of escalation

Six months ago:

“Can I send this email?”

Today:

“I’ve got a commercial trade-off between these two options. Here is my recommendation.”

Excellent. That is development.

Recognise independent thinking

When somebody makes a sensible decision without you, say so.

“Good judgement. You didn’t need me for that.”

That reinforces the behaviour. Do not punish people for not consulting you when they did not need to This sounds obvious. It happens. Managers feel left out. Then pull decisions back upward. Be careful.

Ask yourself whether you like being asked

Another uncomfortable one. Being consulted can feel good. Important. Needed. But if your goal is stronger people, you cannot require permanent dependence for emotional reassurance.

The manager's job is not to be the oracle

The more people who can answer sensible questions themselves, the stronger the team becomes.

Stop being proud that everyone comes to you

Sometimes that is trust. Sometimes it is dependence. Know the difference.

Build other sources of judgement

Not every question should go to one manager. Who else can help? Experienced colleagues? Specialists? Useful peer relationships reduce bottlenecks.

Encourage peer problem-solving

Before coming to the manager, perhaps they can discuss with an appropriate colleague. But avoid creating informal committees for every tiny decision. The objective is still decision-making.

Do not let consensus replace ownership

“Everyone thought…”

Fine. Who owns the decision? Keep that clear.

Teach people to make the call

At some point, thinking needs to become action. Do not let analysis become another form of dependence.

Use time limits where useful

“Take ten minutes, decide what you recommend, and come back.”

That can build confidence.

New employees need more support

Of course. Do not expect instant independence. But begin the thinking habit early.

Ask new starters “What do you think?” too

Even when they do not know much yet. You can then add context.

Experienced employees should need less routine input

If they do not, investigate. Authority? Confidence? Habit? Manager behaviour? Something is maintaining dependency.

Avoid learnt helplessness

If every difficult situation results in someone senior taking over, people may eventually stop trying. That is learned helplessness.

Keep the problem ball with the right person

Employee brings the problem. Manager supports. Employee leaves with the next action. That is a good pattern.

Watch reverse delegation

It often happens in one sentence.

“Could you just speak to the customer?”

Manager says:

“Sure.”

The ball moved. Notice it. Try:

“What do you think you need to say to them?”

Then coach.

Do not rescue because you can do it better

You probably can. That is not the point. The employee needs to become capable.

Use small decisions as training

Judgement develops through repetition. Let people practise.

Increase autonomy when evidence supports it

As reliability and judgement grow: reduce approvals; widen thresholds; reduce check-ins. That creates visible progression.

Make autonomy conditional on ownership

More freedom requires: keeping commitments; raising risks early; telling the truth; using judgement. That is the bargain.

Reduce autonomy if the evidence requires it

If performance becomes unreliable, more support may be appropriate. But explain why.