Coaching Through Capability Gaps

🌱 When Enthusiasm Cools Into Doubt

In the last lesson, you handed structure to a willing beginner and deliberately kept the encouragement in your pocket, because their drive didn't need topping up. But people don't stay beginners for long. A few weeks in, once the novelty wears off and the work turns out to be harder than it looked, that same eager report can lose their spark. This lesson is about the style that meets them there: coaching. Where directing was high direction and low support, coaching turns both dials up.

By the end of this lesson, you will have learned to:

  • Diagnose the disillusioned learner, the report with partial skill and wavering commitment who needs both dials turned up.
  • Explain the why behind the method while inviting the concerns that surface a confidence wobble.
  • Design tapering check-ins that grow skill and confidence together, lightening your involvement as capability shows up in the evidence.

🩺 Diagnosing the Partly-Skilled, Wavering Report

Coaching fits one specific person: someone who has picked up part of the skill but whose commitment has slipped or gone shaky. They can now do pieces of the task, but they've also discovered how much they don't know, and the early enthusiasm has cooled into doubt. It's a genuinely different situation from the willing beginner. The beginner had no skill but plenty of drive, so you added no support. This person has some skill but wobbly drive, so you add support back in.

That's why both dials go up. They still need instruction, because the skill gap is real. But they also need encouragement, because confidence is the thing quietly leaking out. Give only direction and you get a compliant but anxious report who executes without believing in themselves. Give only support and you cheerlead someone who still doesn't know how to do the harder parts. Coaching is high direction plus high support, and its signature move is that you always explain the why.

A quick note on the word "coaching," because it does double duty in this learning path. Right now it names one of the four leadership styles. Later you'll meet a developmental coaching conversation, a question-led method you can layer onto any style. Keep them separate: here, Coaching is a style, not a questioning technique.

💡 Explaining What, How, and Why While Inviting Concerns

In directing you covered what to do, how to do it, and by when. Coaching keeps all of that and adds two things:

  • The why: The reasoning behind the method, so the person builds judgment rather than just following steps.
  • An open invitation: A space for their questions and concerns, which is where the support half of Coaching actually lives.

That invitation is how you surface the confidence wobble instead of letting it fester silently. Let's see how this is played out in a conversation between a manager (Victoria) and her direct report (Milo):

  • Victoria: Here's the method, and here's why it matters. If you map the dependencies first, you catch the conflicts before the meeting, not in front of everyone.
  • Milo: That makes sense. I guess I'm worried about a dependency I didn't map coming up live.
  • Victoria: Good, that's exactly the worry worth naming. What would you want to do in that moment?
  • Milo: Park it and follow up after? I don't have to solve everything on the spot.
  • Victoria: Right. Notice how much you already know how to handle. Let's build that into your plan.

Watch how the "why" turned a step into a reason Milo could reason from, and how the simple question drew out a real fear that could then be worked through. That is coaching: teach the logic, then make room for the doubt.

📈 Check-Ins That Grow Skill and Confidence Together

Coaching isn't a single conversation; it plays out across a series of check-ins. Each check-in should review real evidence of the work, build confidence by asking what went well, and set a clear accountability point for next time.

Check-in 1: Lead TogetherCheck-in 2: Prompt Their ThinkingCheck-in 3: Hand Back Ownership
Review evidenceExamine the work together and point out what meets the standard.Ask them to assess the work before adding your perspective.Have them present the evidence and draw their own conclusions.
Build confidenceAsk what went well and reinforce the progress you observed.Ask which decisions they feel more confident making now.Ask them to name what they can handle independently.
Set accountabilityDefine the next steps and milestone clearly.Agree on the next milestone together.Have them propose the next milestone and plan.

Leader involvement: High → Lower
Report ownership: Low → Higher

The crucial detail is that this arc moves. As competence shows up in the evidence, deliberately lighten your involvement by handing back more of the reasoning and pulling back on step-by-step instruction. A coaching plan that looks identical in week three and week one isn't coaching; it's monitoring. Your fingerprints should fade as their capability grows, preparing them for the more hands-off styles ahead.

Coaching is the high-support response to a confidence dip, where providing the why matters just as much as instructing the how. Next, you'll put this to work: first by spotting the specific cues that distinguish a coaching moment from the other three styles, then by running a live coaching conversation where the test is whether you can explain the logic while drawing out a report's true concerns, and finally by mapping a series of tapering check-ins that fade your fingerprints as their capability grows.

Sign up

Join the 1M+ learners on CodeSignal

Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal