Sometimes the fastest way to solve a problem is to give the answer. The harder work of leadership is knowing when not to.
There is a moment most leaders recognize. Someone brings you a problem, and before they finish explaining it, you can already see the answer.
Maybe you’ve dealt with something similar before. You can see where they went wrong, what they’re missing, and what they should probably do next. It would take five minutes to explain it, solve the problem, and send them on their way.
So we do.
It feels helpful. In the moment, it probably is. The problem gets solved, the work starts moving again, and everyone can get back to what they were doing.
But something else may have happened in that conversation. We solved the problem, but the person who brought it to us didn’t necessarily become any better at solving the next one.
That is one of the tensions of coaching leadership. Helping someone and developing someone aren’t always the same thing. Sometimes the most helpful thing we can do in the moment is exactly what keeps someone dependent on us over time.
Learning the difference has as much to do with our own discipline as it does with the person we’re trying to develop.
Coaching Leadership Begins Before We Give the Answer
Most leaders don’t intentionally create dependence. It happens gradually.
We get promoted because we’re good at solving problems. We develop experience, recognize patterns, and learn to make decisions faster. Eventually, people begin bringing harder problems to us because we’re responsible for helping solve them.
The ability that helped us become leaders can then become one of the things that limits us as leaders.
If every problem ends with my answer, people eventually learn that bringing me the problem is enough. They don’t necessarily need to wrestle with the options because they know I will. They don’t need to make the judgment because they expect me to make it.
The leader becomes the thinking department.
Then we wonder why people aren’t taking more ownership.
Sometimes the problem isn’t that people refuse to think for themselves. Sometimes we’ve created an environment where waiting for the leader is the safest and most efficient thing to do.
Coaching changes that dynamic.
Instead of beginning with the answer, we begin by trying to understand how the person is thinking.
What do you see happening?
What have you considered?
What do you think the real problem is?
What would you do if I weren’t here?
Questions like these aren’t powerful because there is something magical about asking questions. They’re useful because they move responsibility for the thinking back toward the person who owns the problem.
And they tell us something important too.
Before we can coach someone well, we need to know whether they actually need our answer.
Sometimes People Need Coaching. Sometimes They Need Direction.
There is a tendency to turn leadership ideas into absolutes.
Once we decide coaching is good, we can begin acting as though telling someone what to do is bad. It isn’t.
Someone learning a new role may need clear instruction. A person facing a situation they’ve never encountered may need our experience. When safety, ethics, customers, significant financial risk, or a serious deadline is involved, the leader may need to make the decision.
There is nothing admirable about watching someone struggle unnecessarily because we’ve decided every conversation must become a coaching exercise.
The real skill is judgment.
Does this person lack knowledge, or do they lack confidence?
Do they need an answer, or do they need room to think?
Is the risk high enough that I need to intervene, or am I stepping in because watching someone struggle makes me uncomfortable?
That last question matters.
Leaders often talk about developing people as though development is something we do to someone else. But developing people requires something from us too. It requires patience. It requires restraint. And sometimes it requires accepting a slower path today because we are trying to build greater capability tomorrow.
If every decision is optimized for speed, the experienced leader will almost always win.
But speed isn’t the only thing we’re responsible for developing.
Trust Is Built When We Let People Think
We often say we want people to take ownership. But ownership is difficult to develop when people don’t believe they’re trusted to use their judgment.
Trust doesn’t mean leaving someone alone and hoping everything works out. It means giving people responsibility appropriate to their capability and remaining available without constantly taking that responsibility back.
That’s a difficult balance.
Too little direction can feel like abandonment. Too much direction becomes control.
Coaching operates somewhere between the two.
A leader can clarify the outcome, establish the standard, identify important boundaries, and still leave room for someone else to determine what happens next. When the person gets stuck, the leader can help them think rather than immediately taking over the thinking.
That is where questions become useful.
Not questions designed to manipulate someone toward the answer we’ve already chosen. People recognize those quickly. Real questions require us to be open to the possibility that the person may see something we don’t.
That’s part of trust too.
If I ask someone what they think and then immediately explain why they’re wrong, eventually they’ll stop telling me what they actually think.
They’ll start trying to figure out what I want to hear.
That’s compliance, not ownership.
Coaching Still Requires Honest Accountability
Coaching isn’t soft leadership.
Sometimes a person has thought through the situation and still made a poor decision. Sometimes expectations were clear and weren’t met. Sometimes behavior needs to change.
Those moments still require directness.
A coaching approach doesn’t remove standards or accountability. If anything, it makes them more important because people need to understand the boundaries within which they have freedom to operate.
The difference is in how we respond when something goes wrong.
We can address the missed expectation without taking the entire problem back. We can be clear about what needs to change while still asking the person to think through how they will change it. We can hold someone responsible for an outcome without humiliating them or making every mistake evidence that they can’t be trusted.
Accountability and development belong together.
If we only coach and never hold the standard, people may feel supported but never improve. If we only correct and control, people may comply without ever developing the judgment to operate independently.
Good leadership requires both.
Leading by Example Changes the Coaching Conversation
There is another part of coaching that has nothing to do with the questions we ask.
People watch us.
They notice what happens when we make a mistake. They notice whether we become defensive when someone challenges our thinking. They notice whether we stay calm when something goes wrong or immediately start looking for someone to blame.
That behavior teaches long before we sit down for a coaching conversation.
It’s difficult to ask someone to take ownership if we avoid owning our own mistakes. It’s difficult to encourage honest communication if bad news consistently receives an emotional reaction. It’s difficult to ask someone to remain curious when our first response to disagreement is to defend our position.
Leading by example is sometimes discussed as though it means working hard and behaving ethically. Those things matter, but example goes deeper.
We model how to respond to pressure.
We model how to receive feedback.
We model whether being wrong is something to learn from or something to hide.
We model whether accountability means looking inward first or immediately looking for someone else to blame.
Those behaviors determine whether coaching feels like development or judgment.
The Stoic Discipline Behind Coaching
Stoicism repeatedly brings us back to ourselves.
When something goes wrong, our attention naturally moves outward. What did they do? Why didn’t they listen? Why aren’t they getting this? Why do I have to keep dealing with the same problem?
Some of those questions may be legitimate. People are responsible for their choices and performance.
But Stoicism asks us not to stop there.
What belongs to me in this situation?
My response does.
So does my judgment, my tone, my patience, my willingness to listen, and the decision I make about whether to intervene.
I cannot force another person to develop judgment. I can’t guarantee that someone will respond well to coaching. I can’t completely control whether they make the right decision after I leave the room.
I can control whether my own behavior creates the conditions for growth.
That is where coaching becomes a practice of self-control for the leader.
Sometimes the urge to give the answer isn’t about what the other person needs. It’s about relieving our own discomfort. Watching someone struggle is difficult when we know we could make the struggle disappear.
The Stoic response isn’t to become indifferent and let people fail.
It’s to become more deliberate about why we’re stepping in.
Am I intervening because the situation requires leadership?
Or because I need the discomfort to end?
Those can produce very different decisions.
The Goal Is Greater Capability
The purpose of coaching isn’t to have better coaching conversations.
It’s to develop more capable people.
Over time, the person who once brought every problem begins bringing possible solutions. The employee who once needed reassurance begins trusting their judgment. Someone who once needed detailed direction begins carrying an outcome with less involvement from the leader.
Eventually, some of those people begin coaching others.
That’s when leadership starts to multiply.
It doesn’t happen because the leader disappears. It happens because the leader becomes more intentional about where their involvement actually adds value.
Sometimes people need an answer.
Sometimes they need instruction.
Sometimes they need direct feedback.
And sometimes they need us to resist the urge to do any of those things long enough for them to discover that they’re capable of thinking through the problem themselves.
The difficult part is knowing which moment we’re in.
The next time someone brings you a problem and you already know what you would do, resist answering for just a moment.
Ask them what they think.
Then listen.
You may still need to give the answer.
But you may also discover they didn’t need your answer nearly as much as they needed the opportunity to develop their own.