When I ask managers what their most important responsibility is, the answers cluster around two themes: delivering results and developing people. When I ask how they spend their time, the first theme dominates and the second barely registers. Not because they don’t care about development. Because nobody showed them how to do it inside the daily work of managing.

Development gets treated as a separate activity — something that happens in a training room, a mentoring session, or an annual development plan conversation. The manager’s job is to run the operation. Development is something HR handles, or something that happens when there’s time, which means it doesn’t happen.

This is the fundamental misconception. Development doesn’t happen alongside the work. It happens through the work — when a manager uses everyday interactions as opportunities to build capability. The one-on-one where you ask a question instead of giving an answer. The project debrief where you explore what the person learned, not just whether they delivered. The delegation where you choose the task for their growth, not your convenience. Each of these is a coaching moment. And the managers who learn to create them consistently produce teams that are measurably more capable, more engaged, and more likely to stay.

What “Coaching Stance” Actually Means

A coaching stance is not a technique. It’s a way of orienting toward the person in front of you. In every interaction with a direct report, you have a choice between two orientations:

The expert orientation: “I know the answer, and my job is to give it to you.” This is the default for most managers because it’s fast, it’s efficient, and it was the orientation that earned them the promotion. The expert solves problems, provides direction, and makes decisions. The team executes.

The coaching orientation: “You have more capability than you’re currently using, and my job is to help you access it.” This orientation assumes that the person in front of you can think through the problem, develop their own solution, and build judgment in the process. The coach asks questions, creates space for thinking, and provides support without removing ownership.

Neither orientation is always right. The skill is knowing when each one serves the moment. But most managers use the expert orientation 90% of the time when the ratio should be closer to 50/50 — and for experienced direct reports, closer to 20/80. The coaching stance isn’t about abandoning expertise. It’s about deploying it strategically rather than reflexively.

The Four Leadership Modes (and When to Use Each)

Coaching is one of four modes a manager operates in. Understanding all four prevents the common mistake of trying to coach when a different mode would be more effective:

Directing: Clear instruction with defined expectations. Use when someone is new to a task, the stakes are high and time is short, or there’s a compliance or safety requirement. “Here’s what needs to happen, by when, and how.”

Teaching: Sharing knowledge or skill that the person doesn’t have. Use when the gap is a knowledge gap, not a thinking gap. “Here’s how our budgeting process works — let me walk you through the model.” Teaching transfers information. Coaching develops judgment.

Mentoring: Sharing your experience to provide context and perspective. Use when someone is navigating a situation you’ve been through and would benefit from your story. “When I was in a similar situation, here’s what I learned.” Mentoring offers perspective. Coaching draws it out.

Coaching: Asking questions that help the person think through the situation and develop their own solution. Use when the person has the capability to figure it out but hasn’t fully thought it through, when the developmental benefit of working through the problem outweighs the efficiency of giving the answer, and when building independent judgment is more valuable than delivering the fastest outcome.

The most common manager mistake is defaulting to directing or teaching when coaching would produce a better outcome. The second most common mistake — usually made by managers who’ve just discovered coaching — is trying to coach when the situation calls for directing. A new employee asking how to submit an expense report doesn’t need coaching. They need a procedure. A tenured team lead asking how to handle a difficult stakeholder conversation probably does need coaching, because they likely have the capability and would benefit from developing it.

Why Most Managers Default to Telling

If coaching produces better development outcomes and most managers know they should do it, why do they default to telling? Three reasons, each addressable:

Speed. Giving the answer takes 30 seconds. Asking questions and helping someone think through it takes 10 minutes. When you have 12 direct reports and seven meetings today, the 30-second version wins. This is a real constraint — but the math changes when you consider that the 30-second answer produces the same question again next time, while the 10-minute coaching conversation builds the capability to handle it independently. Coaching is slower in the moment and dramatically faster over months.

Identity. Most managers were promoted because they were excellent problem-solvers. Their identity is built around being the person who has the answer. Coaching requires a different identity: being the person who helps others find the answer. For leaders whose self-worth is tied to being the smartest person in the room, this shift feels like a demotion. It’s actually a promotion — from producing answers to producing people who produce answers — but it doesn’t feel like one until you’ve experienced the result.

Skill. Nobody taught them how. Management training (when it exists at all) focuses on directing: how to set goals, give feedback, run meetings, evaluate performance. The coaching skill — asking questions that produce thinking, holding space for someone to work through a problem, resisting the impulse to solve — is rarely included. And it’s genuinely a skill, not just an attitude. A bad coaching question (“Don’t you think you should talk to them about it?”) is just a directive disguised as a question. A good coaching question (“What’s the real challenge here for you?”) opens a conversation that the person didn’t know they needed to have.

What Coaching Looks Like in a Regular One-on-One

You don’t need to overhaul your management style to start coaching. You need to change how you use the one-on-one meetings you’re already having.

Most one-on-ones follow a predictable pattern: the direct report shares updates, the manager asks clarifying questions, the manager gives advice on the two or three issues that surfaced, and both move on. That’s a status meeting with some problem-solving. It’s not developmental.

A coaching-oriented one-on-one shifts the structure. The first half is still updates and operational discussion — that’s necessary. But the second half shifts to a development question: “What’s the most important thing you’re working on developing right now, and how can I help?” or “What situation this week stretched you, and what did you learn from it?” or “What conversation are you avoiding, and what’s getting in the way of having it?”

These questions take five minutes. They produce development conversations that wouldn’t happen otherwise. And over months, they build a relationship where the direct report brings their development needs to the manager proactively — not because they were told to, but because they’ve experienced the value of thinking through challenges with someone who asks good questions instead of just giving good answers.

In an earlier post, I shared a five-question coaching conversation framework that any manager can use immediately. The questions are: What’s the real challenge here for you? What have you already considered? What would you do if you had to decide right now? What are you most worried about? What will you do, and by when? Each question is designed to move the conversation from surface-level problem presentation to genuine thinking. You don’t need to use all five every time. Start with one.

The Compound Effect of Manager-as-Coach

The return on a coaching stance compounds in ways that directing can’t. When you direct, you produce a result. When you coach, you produce a result and build a capability. After six months of consistent coaching:

Your direct reports bring you problems pre-thought rather than raw. They’ve internalized the coaching questions and started applying them to their own thinking before they walk into your office. Your workload shifts from decision-making to decision-enabling, which frees you for the strategic work your role actually requires.

Your team starts coaching each other. The norms you modeled — asking before telling, exploring before solving, debriefing after doing — become team norms. Development becomes distributed rather than dependent on you.

Your retention improves. Research consistently shows that employees who report having a manager who develops them are dramatically more engaged and less likely to leave. The coaching stance doesn’t just build capability. It builds the kind of relationship that keeps people invested in their work and their team.

And perhaps most importantly, you develop the next generation of leaders who coach their own teams — which is how the TGC&C coaching philosophy describes the ultimate goal: develop leaders who develop others.

Three Things You Can Do This Week

1. In your next one-on-one, resist the first impulse to solve. When your direct report brings a problem, pause before you answer. Ask one question: “What have you already considered?” Then listen. You may still end up providing input, but you’ll have honored their thinking first and learned something about how they approach problems.

2. Add a development question to the end of every one-on-one this week. After the operational discussion, ask: “What’s one thing you’re working on getting better at, and how did this week go?” Five minutes. No preparation needed. Just curiosity about their growth. The consistency of asking — every week, not occasionally — is what makes it developmental.

3. Notice your ratio of telling to asking across your interactions this week. Just notice it — don’t try to change it yet. How many times did you give an answer versus ask a question? How many times did you solve versus explore? Awareness of the ratio is the first step toward shifting it. Most managers discover they’re at 85/15 or 90/10 in favor of telling. Even moving to 70/30 transforms the development experience for their team.

The coaching stance is the leadership capability that multiplies every other capability you have. A manager who coaches well is a better delegator, a better feedback-giver, a better developer of people, and a better builder of teams — because the coaching stance infuses all of those activities with a developmental orientation that directing alone can’t provide.

If you want to develop as a leader who develops others, a coaching engagement is where the work gets personal. We help you identify the patterns that keep you stuck in the expert mode (often through Hogan and EQ-i data), design experiments for shifting toward a coaching stance in your specific context, and debrief what’s working and what isn’t over months of structured practice. Learn about our coaching approach →

Want to explore how to build a coaching culture on your team or across your management layer? A discovery call is a good place to start. Schedule a discovery call →