player-coach-chapter-6

 

Chapter 6: Coaching vs. Fixing — The Art of Asking Questions

The shift from fixing to coaching is the difference between creating dependency and building capability. It begins with asking better questions.

Learning Objectives

• By the end of this chapter, you will be able to distinguish between coaching and fixing and recognize when you are doing each.
• By the end of this chapter, you will be able to identify the hidden costs of fixing problems for your team.
• By the end of this chapter, you will be able to apply the GROW coaching framework in common management situations.
• By the end of this chapter, you will be able to craft questions that stimulate thinking rather than prescribe answers.
• By the end of this chapter, you will be able to create a coaching habit that replaces your fixing reflex.

Table of Contents

• Introduction
• The Fixing Reflex: Why We Do It
• The Hidden Costs of Fixing
• What Coaching Really Means
• The GROW Coaching Framework
• The Art of Asking Questions
• Building a Coaching Habit
• Real-World Examples
• Case Study: The Fixer's Transformation
• Key Terms
• Summary
• Practice Questions
• Discussion Questions
• FAQ

Introduction

A team member knocks on your door. They have a problem. You listen for a moment, recognize the issue, and within seconds you're offering solutions. "Have you tried this? What about that? Here's what I would do." They leave with an answer, grateful for your help. You feel useful, competent, and efficient. This is the fixing reflex—and it is one of the most damaging habits a manager can have.

When you fix problems for your team, you may solve the immediate issue, but you create long-term dependency. Your team learns to bring you problems, not solutions. They stop thinking for themselves. Your door becomes a bottleneck. And you remain a player, not a coach.

Coaching is the alternative. Instead of providing answers, you ask questions. Instead of solving problems, you help others learn to solve them themselves. Coaching feels slower in the moment but creates exponential returns over time. This chapter will help you understand the difference between coaching and fixing, master the art of asking powerful questions, and build a coaching habit that transforms your team's capability and your own effectiveness.

The Fixing Reflex: Why We Do It

The fixing reflex is deeply ingrained, especially for those promoted for their technical expertise. Understanding why we fix helps us interrupt the pattern.

It's Faster (in the moment)

When you already know the answer, it takes seconds to give it. Coaching takes minutes or hours. In a busy world, fixing feels efficient. But this is short-term thinking. The same person will return with the same problem, or a similar one, because they haven't learned to solve it themselves.

It Feels Good

Solving problems triggers dopamine. Being the expert feels validating. Gratitude from team members reinforces the behavior. Fixing meets our psychological need for competence and significance.

It Reduces Anxiety

When you're unsure if your team can handle something, fixing ensures it's done right. It reduces your anxiety about outcomes. But this short-term relief comes at the cost of long-term capability.

📘 Definition: The fixing reflex is the automatic tendency to provide solutions to others' problems rather than facilitating their own problem-solving.

The Hidden Costs of Fixing

Fixing may seem helpful, but it carries steep hidden costs that accumulate over time.

• Stunted problem-solving skills: Your team never develops the ability to solve problems independently. They become dependent on you.
• Reinforced helplessness: Each time you fix, you subtly communicate that they are not capable. They learn to bring you every problem.
• Bottleneck creation: You become the sole source of answers, limiting your team's throughput and your own capacity.
• Missed learning opportunities: Problems are powerful teachers. When you solve them, you rob your team of the chance to learn.
• Disempowerment: Your team feels untrusted and undervalued. Engagement and initiative decline.

🔑 Key Insight: Every time you fix a problem for someone, you are effectively saying, "I don't believe you can figure this out." Even if you don't mean it, that's the message received.

What Coaching Really Means

Coaching is not about having all the answers. It is about helping others discover their own answers. It is a mindset shift from expert to facilitator, from teller to asker.

📘 Definition: Coaching is a developmental process in which a manager helps team members improve performance, solve problems, and build capabilities through questioning, listening, and structured support—rather than providing direct solutions.

The Coaching Mindset

• Belief in potential: You assume your team members are capable of figuring things out, even if they haven't yet.
• Patience for process: You accept that learning takes time and that mistakes are part of growth.
• Curiosity over certainty: You ask questions because you're genuinely curious about their perspective, not because you're leading them to your answer.
• Focus on ownership: You want them to own the problem and the solution, not depend on you.

The GROW Coaching Framework

GROW is the most widely used coaching model. It provides a simple structure for coaching conversations.

G — Goal

What does the person want to achieve? Clarify the goal of the conversation. Make it specific and measurable. Sample questions: "What would you like to accomplish in this conversation?" "What outcome would be most helpful?" "How will you know this problem is solved?"

R — Reality

Explore the current situation. What's happening now? What have they tried? What's getting in the way? Sample questions: "What's happening right now?" "What have you tried so far?" "What's the impact of this issue?" "Who else is involved?"

O — Options

Generate possibilities. What could they do? Encourage brainstorming without judgment. Sample questions: "What options do you see?" "What else could you try?" "What would you do if you had no constraints?" "Who could help you?"

W — Will (or Way Forward)

Commit to action. What will they do? When? What support do they need? Sample questions: "Which option will you choose?" "What's your first step?" "When will you do it?" "What might get in the way, and how will you handle it?"

💡 Example: Instead of telling a team member how to handle a difficult client, use GROW: "What would make this conversation successful?" (Goal) "What's happening with the client now?" (Reality) "What approaches could you take?" (Options) "Which one feels right, and what's your next step?" (Will)

The Art of Asking Questions

Questions are the coach's primary tool. But not all questions are created equal. The art lies in asking questions that open thinking rather than close it down.

Powerful Questions

• Are open-ended (cannot be answered with yes/no).
• Start with "what," "how," "who," or "tell me more."
• Avoid "why," which can sound judgmental (e.g., "Why did you do that?").
• Focus on the future and possibilities, not just the past.
• Are simple and clear.

Examples of Powerful Questions

• "What's the real challenge here for you?"
• "What have you considered so far?"
• "What would an ideal outcome look like?"
• "What's one small step you could take?"
• "What resources could help you?"
• "What's the hardest part about this?"
• "If you knew the answer, what would it be?"

📝 Note: The goal is not to ask a perfect sequence of questions. It's to be genuinely curious and to trust that the person has the capacity to find their own way with your support.

Building a Coaching Habit

Shifting from fixing to coaching requires deliberate practice. It won't happen overnight, but you can build the habit.

Start Small

Pick one common situation where you typically fix. Commit to asking at least three questions before offering any advice. For example, when someone asks "What should I do?" respond with "What do you think you should do?" or "What options are you considering?"

Use the "Question Pause"

After asking a question, pause and wait. Let them think. Resist the urge to fill the silence with your own ideas. The thinking happens in the silence.

Reflect After Interactions

After a conversation, ask yourself: Did I fix or coach? What could I have asked differently? What did I learn about their thinking? Reflection accelerates skill development.

Get Feedback

Ask your team: "How am I doing at helping you solve your own problems? Do I give too many answers? When would you like me to ask more questions?" Their feedback is invaluable.

📊 Research: A study of managers who shifted from fixing to coaching found that within six months, their teams reported higher engagement, solved more problems independently, and reduced the frequency of escalations by 40%.

Real-World Examples

💡 Example 1: The Support Manager's Shift
Rosa managed a customer support team. When agents brought her complex issues, she often took over and handled them herself. Agents felt relieved but also untrusted. Rosa started using GROW: "What have you tried?" "What else could you try?" "What support do you need from me?" Agents began solving more issues independently. Within three months, escalations dropped by 50%, and Rosa had time to improve team processes.

💡 Example 2: The Engineer Who Stopped Prescribing
Tom, a tech lead, was known for giving detailed technical direction. His junior developers became passive, waiting for his instructions. A coach suggested Tom ask more questions. When a developer asked how to implement a feature, Tom said, "What approaches have you considered? What are the trade-offs?" The developer returned with a solid plan. Tom realized his "answers" were limiting his team's growth.

💡 Example 3: The Consultant Who Coached Clients
Elena was a consultant who always gave clients detailed recommendations. She noticed clients often didn't implement them. She shifted to a coaching approach, asking questions that helped clients discover their own solutions. Implementation rates soared, and clients reported deeper learning. Elena became more sought-after because she helped clients build capability, not just dependency.

Case Study: The Fixer's Transformation

📊 Case Study: Marcus's Coaching Journey

Scenario: Marcus led a team of project managers. He was the go-to person for every problem. Team members constantly interrupted him for advice. Marcus felt indispensable but exhausted. He worked 10-hour days, and his team showed little initiative. A 360-review revealed that his team felt he didn't trust them and that they had stopped thinking for themselves.

Analysis: Marcus was a classic fixer. He solved problems quickly, which felt helpful but created dependency. His team brought him every issue because they knew he would solve it. They had lost confidence in their own problem-solving abilities. Marcus's fixing reflex was costing him time, energy, and his team's development.

Intervention: Marcus committed to a three-month coaching experiment. He told his team: "I'm going to stop giving you answers. Instead, I'll ask questions to help you find your own solutions. It may feel awkward at first, but it will help you grow." He used the GROW model in every interaction. He asked: "What's your goal? What's happening now? What options do you have? What will you do?" He resisted the urge to prescribe.

Outcome: The first weeks were hard. Team members wanted quick answers. Some were frustrated. But Marcus held firm. Within a month, team members started bringing solutions, not just problems. They became more confident and resourceful. Interruptions dropped by 60%. Marcus had time to focus on strategic priorities. His team reported feeling more trusted and engaged. Marcus's transformation from fixer to coach multiplied his impact.

Key Takeaway: Marcus's story shows that the fixing reflex can be unlearned. It requires patience, discipline, and a belief in your team's potential. The payoff is a more capable team and a leader freed to do strategic work.

Key Terms

• Fixing reflex: The automatic tendency to provide solutions to others' problems rather than facilitating their own problem-solving.
• Coaching: A developmental process of helping others improve performance and build capabilities through questioning and support.
• GROW model: A coaching framework structured around Goal, Reality, Options, and Will.
• Powerful questions: Open-ended questions that stimulate thinking and exploration.
• Question pause: The intentional silence after asking a question to allow thinking time.
• Dependency loop: The cycle where fixing reinforces the team's reliance on the manager for solutions.
• Ownership: The sense of responsibility and commitment a person feels toward a problem or task.
• Facilitative leadership: A leadership style focused on enabling others to find their own solutions.
• Curiosity: A genuine interest in understanding others' perspectives and thinking.
• Coaching habit: A consistent practice of using coaching behaviors in daily interactions.

Chapter Summary

• The fixing reflex is natural but costly: It feels efficient but creates dependency and stunts team growth.
• Hidden costs of fixing: Stunted problem-solving, reinforced helplessness, bottlenecks, missed learning, and disempowerment.
• Coaching builds capability: It helps others discover their own solutions and builds lasting skills.
• The GROW framework structures coaching: Goal, Reality, Options, Will provide a simple, effective conversation guide.
• Powerful questions are key: Open-ended, curious questions stimulate thinking and ownership.
• Building a coaching habit takes practice: Start small, use the question pause, reflect, and seek feedback.

Practice Questions

1. Think of a recent situation where you fixed a problem for someone. What was the cost of your fixing? What might have happened if you had coached instead?
2. Choose a current challenge a team member is facing. Write out a GROW coaching conversation you could have with them.
3. List five powerful questions you could use when someone asks you for advice.
4. Identify one situation this week where you will commit to asking three questions before offering any solutions.
5. Reflect on Marcus's case study. What specific behaviors changed? How did his team respond?
6. How would you explain the difference between coaching and fixing to a fellow manager?
7. What might get in the way of your coaching habit? How will you address those obstacles?

Discussion Questions

1. Why is it so hard for experts to shift from fixing to coaching? What psychological factors are at play?
2. How can organizations create cultures that value coaching over fixing? What systems or incentives might help?
3. When is fixing actually appropriate? Are there situations where providing answers is the right choice?
4. How might coaching differ across cultures? Are there cultures where direct advice is expected and questions are seen as evasive?
5. What role does trust play in coaching? How do you build enough trust for coaching to be effective?

Frequently Asked Questions

Q1: What if my team genuinely lacks the knowledge to solve the problem?

Coaching doesn't mean never sharing knowledge. It means sharing it in a way that builds capability. You might ask, "What do you already know about this? What information would help you?" Then point them to resources or teach in a way that they can apply next time. The goal is to gradually reduce their dependence on you.

Q2: How do I handle team members who just want me to give them the answer?

Be transparent about your approach. Explain that your role is to help them grow, and that means they'll need to think through problems themselves. Use questions to guide them. Over time, they'll learn that you won't give easy answers, and they'll start coming with their own ideas. Patience is key.

Q3: What if we're in a crisis and there's no time for coaching?

In genuine emergencies, fixing may be necessary. But be explicit: "I'm going to handle this one because it's urgent, but afterward let's debrief so you can handle it next time." Use the crisis as a teaching moment. If you're always in crisis mode, that's a sign that your lack of coaching has created dependency and you need to invest more time in development.

Q4: How do I know if I'm coaching effectively?

Look for signs: your team brings solutions, not just problems. They seem more confident. You spend less time on issues they could handle. They ask each other for help instead of always coming to you. You can also ask them: "How helpful was our conversation? What could I do differently?"

Q5: What if I ask questions and they just say "I don't know"?

This is common, especially with people used to being told what to do. Respond with curiosity: "If you did know, what might you say?" or "What's one possibility?" or "What would you guess?" Encourage them to think out loud. Over time, they'll become more comfortable with the thinking process.

---

← Back to Book Home | ← Previous Chapter | Next Chapter: Letting Go of Perfection → | Back to Top

Copyright & Disclaimer

COPYRIGHT NOTICE:

All original text, chapter content, explanations, examples, case studies, problem sets, learning objectives, summaries, and instructional design are the exclusive intellectual property of the author. This content may not be reproduced, distributed, or transmitted in any form or by any means without prior written permission from the copyright holder, except for personal educational use.

⚖️ DISCLAIMER

This textbook is intended for educational purposes only. While every effort has been made to ensure accuracy, leadership theories and organizational practices may evolve over time. Readers should consult current professional standards and qualified advisors for specific organizational situations. The author and publisher assume no responsibility for errors or omissions or for any consequences arising from the use of this information.

Permissions and Licensing:
For permissions, inquiries, or licensing requests, please contact:
kateulesydney@gmail.com