Three questions to ask before giving your team the answer.

Maybe you solved today's problem. But you may have missed an opportunity to develop tomorrow's leader.

One of the hardest transitions in leadership is moving from "I know how to do this" to "I know how to help someone else learn how to do this." Those are very different skills. The first made many of us successful individual contributors. The second is what makes us leaders.

Your team does not need another search engine.

If the relationship between you and your team becomes Problem → Manager → Answer, you create dependency. The employee learns: when I am uncertain, I should ask my boss what to do. And because the manager is rewarded for moving quickly, the cycle continues.

The leader feels useful. The employee feels supported. Work gets completed. Everyone thinks the system is working — until the manager has ten direct reports. Then fifteen. Then every decision is waiting for one person. The same leadership behavior that once felt helpful has now become an organizational bottleneck.

Ask before you answer.

There are three questions I believe leaders should become comfortable asking before immediately providing a solution.

1. What do you think is happening?
This question forces both people to slow down. Before solving, understand the problem. What is actually happening? What evidence do we have? What assumptions are we making? Who is affected? Sometimes the employee has already identified something the leader has not considered — and sometimes the problem they initially describe is not the actual problem at all.

2. What options have you considered?
This moves the employee from reporting a problem to thinking about possibilities. Maybe the options are imperfect — that's fine. The purpose is not to test whether they can guess your answer. The purpose is to help them practice judgment. A leader who immediately corrects every imperfect idea teaches people to stop offering ideas. Instead, get curious: what are the advantages of that option? What worries you about it? Who else could be affected? Now you are coaching.

3. What do you recommend?
This is the most important question. A recommendation requires ownership. It forces the person to move from "here is the problem" to "here is what I think we should do." They may be wrong — that is okay. Leadership development requires allowing people to exercise judgment before they are perfect at it. You can still challenge the recommendation, provide additional context, and make the final call. But now you understand how the person thinks, and they understand that you expect them to think.

Coaching does not mean never giving an answer.

There is a tendency in leadership content to turn good ideas into absolutes. This should not become "never tell your employee what to do." Sometimes the right thing to do is provide clear direction. A crisis is not always the moment for a coaching exercise. A new employee may genuinely lack the experience required to evaluate the options. A safety, ethical, or regulatory issue may require immediate clarity. Good leadership requires judgment.

The principle is simpler: do not give the answer automatically. Ask yourself — does this person need my answer right now, or would they benefit more from my questions? That distinction matters.

The ARC perspective

This is Relational Leadership. Leadership happens through relationships, and one of the most important messages you communicate to someone is: I believe you are capable of thinking.

Asking someone for their perspective communicates trust. Asking them to consider options creates development. Asking for their recommendation creates ownership. And working through the decision together creates connection.

Your job is not simply to make sure today's task gets completed. You are helping build the person who will face tomorrow's problem when you are not there.