Coaching Instead of Commanding

In a small team, the pressure to move fast often pushes a lead into telling mode. You see a problem, you know the fix, and you say it. That works in the moment,

Level: Team lead
Setting: Small team
Core skill: Drawing out answers
Common pitfall: Always telling
Practice to try: One question before advice

What this looks like in real work

In a small team, the pressure to move fast often pushes a lead into telling mode. You see a problem, you know the fix, and you say it. That works in the moment, but over time it creates a team that waits for instructions. Coaching instead of commanding looks different. It means pausing before you give the answer and asking a question that helps someone else find it. For example, when a team member brings you a snag in a process, you might ask, "What have you tried so far?" or "What do you think is the real blocker here?" The goal is not to withhold your knowledge but to build their ability to think through similar problems without you.

In practice, this shifts your daily interactions. Instead of starting meetings with a list of directives, you start with a question about what the team sees. Instead of solving a customer issue yourself, you ask the person handling it what options they considered. It feels slower at first, but it builds capability. You are still responsible for outcomes, and you still step in when needed. The difference is that your default moves from giving answers to drawing them out. That default is what makes a small team resilient and less dependent on you for every decision.

Why it trips people up

The biggest reason leads fall into telling is that it feels efficient. When you already know the answer, explaining it takes less time than guiding someone to discover it. In a small team, where everyone wears multiple hats, that efficiency feels necessary. But the short-term gain comes with a long-term cost: people stop thinking for themselves. They learn that the fastest path is to ask you, and you become the bottleneck. Another trap is identity. Many leads are promoted because they were excellent doers. Their expertise is part of their value, so not sharing it can feel like holding back. They worry that asking questions will make them look unsure or that the team will think they do not know what to do.

There is also the fear of losing control. If you let someone else work through a problem, they might choose a different path than you would. That can be uncomfortable, especially when you are accountable for the result. But coaching does not mean abandoning your judgment. It means using questions to guide thinking while keeping the door open to step in. The real trip-up is believing that your job is to have all the answers. In a small team, your job is to build a group that can find answers together. That requires tolerating the awkward pause after you ask a question instead of filling it with a directive.

The mistake that quietly hurts

The mistake is always telling. It looks harmless because you are being helpful. Someone comes to you with a problem, and you give them a solution. They leave grateful, and the work moves forward. But over time, this pattern erodes confidence and ownership. Team members begin to doubt their own judgment. They stop proposing ideas because they assume you will override them anyway. The quiet hurt is that you end up with a team that executes but does not think. When you are absent, decisions stall. When you are present, you are swamped with questions that people could answer themselves. The team becomes a reflection of your instructions rather than a collection of capable individuals.

This mistake also hides problems. If you always provide the answer, you never hear the reasoning behind the team's struggles. You miss chances to correct flawed thinking or to learn from their perspective. In a small team, that lack of insight is costly because you cannot be everywhere. The more you tell, the less you know about what is really happening. The fix is not to stop giving advice altogether. It is to make advice the second move, not the first. By asking a question first, you keep the ownership with the person who brought the issue, and you gain a clearer view of their thought process. That small shift prevents the slow decline into dependency.

A practice you can repeat

One question before advice. This is a simple, repeatable practice that fits any conversation. Whenever someone brings you a problem, a decision, or a request for help, your first response is a question. It does not have to be clever. It just has to invite them to think. For example, you might ask, "What options have you considered?" or "What is your read on the situation?" Only after they answer do you offer your own view. This practice works because it forces a pause. It signals that you trust their ability to contribute and that you are interested in their thinking, not just in dispensing answers. It also gives you valuable information about where they are stuck.

To make this a habit, start small. Pick one meeting or one recurring issue and commit to asking a question first every time it comes up. You can even write the question on a sticky note as a reminder. At first, it may feel artificial, and people might be surprised. But within a few weeks, they will start arriving with their own analysis, because they know you will ask for it. Over time, you can expand the practice to more situations. The goal is not to never give advice. The goal is to make drawing out answers your default, so that advice becomes a deliberate choice rather than a reflex. That single change can transform how your team operates.

What to say and do

When you want to coach instead of command, your words and actions need to align. Start by asking open questions that cannot be answered with a simple yes or no. For example, "What is your goal here?" or "What would a good outcome look like?" These questions help the other person clarify their own thinking. Then, listen without interrupting. Let them finish, even if you already see a solution. After they have shared, you can reflect back what you heard: "So the main challenge is X, and you are weighing Y and Z." This shows you are paying attention and helps them feel understood. Only then should you offer your perspective, and even then, you can frame it as one option among others.

Here are a few phrases you can use in the moment: "What have you tried so far?" "What do you think is the best next step?" "If you had to decide without me, what would you do?" These questions are short and practical. They work in hallway conversations, in one-on-ones, and in team meetings. Pair them with body language that signals openness: put down your phone, turn toward the person, and give them time to think. If they are stuck, you can ask a narrower question, like "What is the one thing that would make this easier?" The key is to resist the urge to jump in with the answer. By making a question your first move, you create space for them to grow, and you learn more about the situation at the same time.

When the stakes get higher

Coaching is easier when the problem is small and the timeline is relaxed. But what about when the stakes are high, a deadline is looming, or a mistake could be costly? That is exactly when the pull to command is strongest. You might think, "There is no time for questions; I need to tell them what to do." In some cases, that is true. If there is an immediate safety issue or a critical decision that cannot wait, you should step in and direct. But most high-stakes situations are not emergencies. They are important, and they feel urgent, but there is still time for a question. In fact, asking a question under pressure can be even more valuable because it helps the team stay calm and think clearly rather than react.

When the stakes are high, adjust your approach rather than abandon it. You can ask a more focused question, such as "What is the biggest risk you see right now?" or "What do we need to decide in the next hour?" You can also set a time limit: "Let us take five minutes to hear your thoughts, then we will decide together." This keeps ownership with the team while acknowledging the urgency. If you do need to give a direct instruction, explain why. "I am going to ask you to do X because of Y, and here is how it fits with what you were thinking." That way, you are still teaching, not just commanding. The goal is to build a team that can handle pressure, and that only happens if they practice thinking under pressure with your support.

Questions new leaders ask

Q: What if I ask a question and they do not know the answer? A: That is fine. The purpose is not to test them but to start a conversation. If they are stuck, you can offer a hint or ask a simpler question. You can say, "What part of this feels most unclear?" Then guide them from there. The goal is to help them think, not to leave them stranded.

Q: How do I balance coaching with getting work done? A: Coaching is not separate from getting work done; it is a way of getting work done that builds capability. Start with small, low-risk situations. As you and your team get more comfortable, you can use it in more areas. You will still give direct instructions when needed, but over time you will need to do that less because people will be able to solve more on their own.

Q: What if someone just wants the answer and gets frustrated with questions? A: Acknowledge their frustration and explain your intent. You might say, "I know you want a quick answer, and I want to help you build the skill to handle this next time. Let us spend two minutes on your thinking, and then I will share my view." Most people will appreciate the investment once they see the benefit. If they are truly stuck or the situation is urgent, give the answer and then debrief later.