A director I worked with once told me about the coaching conversation that went sideways. His top engineer, Priya, had been passed over for a promotion. She was frustrated. Disengaged. Showing up but checking out. He did what felt right: sat her down and walked through a goal-setting framework. Let’s map out what you need to hit for the next cycle. Clear targets, quarterly milestones, weekly check-ins.
Two weeks later, she handed in her resignation.
The strategy wasn’t wrong in the abstract. It was wrong for that moment. Priya didn’t need a roadmap. She needed someone to help her reframe how she saw herself after a setback. A cognitive behavioral approach would have started with what she was telling herself about the rejection. A strengths-based conversation would have reminded her of everything she’d already built. Instead, she got a spreadsheet.
This is the problem with learning leadership coaching as a set of techniques. You collect strategies like tools in a box, but you don’t learn when to reach for each one. What follows is an attempt to fix that. Five coaching strategies, each with a real scenario showing when it works, when it doesn’t, and what it actually looks like in practice.
What Are the Five Core Leadership Coaching Strategies?
Each strategy starts from a different assumption about what the person you’re coaching actually needs.
Transformational coaching assumes they need to see themselves differently. Solution-focused coaching assumes they already have most of what they need and just need help finding it. Cognitive behavioral coaching assumes their thinking patterns are getting in the way. Strengths-based coaching assumes they’ll grow faster by doubling down on what they’re already good at. Systemic coaching assumes the problem isn’t individual; it’s relational.
That’s not ranking. The right strategy depends on the person and the moment.
How Does Transformational Coaching Work in Practice?
Transformational coaching starts with identity, not behavior. Instead of asking “what should you do differently?” it asks “how do you need to see yourself differently to lead at the next level?”
This is the approach for moments where someone’s self-concept is the bottleneck. They have the skills. They have the experience. But they’re still operating from an older version of who they think they are.
Scenario: The reluctant senior leader. Marcus got promoted to VP six months ago but still runs every decision through his former boss. He attends leadership meetings but rarely speaks up. When asked for his perspective on strategy, he defers. His team sees it and it’s eroding their confidence in him.
A transformational coaching conversation with Marcus wouldn’t start with “how can you be more decisive in meetings?” It would start with “who were you as a director, and what parts of that identity are you still carrying?” The work is helping Marcus recognize that the behaviors that made him a great director (executing well, staying aligned with his boss, being a reliable pair of hands) are exactly what’s holding him back as a VP.
When it works best: Career transitions, identity shifts (IC to manager, manager to executive), situations where someone has the capability but hasn’t given themselves permission to use it.
When to skip it: If someone needs to fix a specific problem by next Friday, transformational coaching is too slow. Save it for development, not firefighting.
What Makes Solution-Focused Coaching Different?
Solution-focused coaching flips the typical coaching conversation. Instead of spending time diagnosing what went wrong, it asks: when has this worked before?
The assumption is powerful. Most people already have experience solving some version of their current problem. They’ve just forgotten, or they haven’t made the connection between a past success and the present challenge.
Scenario: The overwhelmed new manager. Roshni was promoted three months ago and she’s drowning. She can’t say no to requests from senior stakeholders. Her calendar is 90% meetings. She hasn’t had a one-on-one with her direct reports in two weeks. She comes into a coaching session saying “I’m failing at everything.”
A solution-focused coach wouldn’t explore why she’s overwhelmed or map out time management frameworks. They’d ask: “Tell me about a week in the last month where things felt more manageable. What was different?” Roshni might remember a week where she blocked Friday mornings for her team. Or a time she pushed back on a request by suggesting an async update instead of a meeting.
That’s the raw material. The coach helps her find the pattern in her own successful moments and build a plan from there.
When it works best: Specific, bounded problems. Someone who’s capable but stuck. Situations where you need momentum in 1-2 sessions, not months of development.
When to skip it: If the person genuinely hasn’t solved anything like this before (new role, new domain, new type of challenge), there’s no past success to mine.
Read more: Coaching Employees in the Workplace: A Manager’s Guide
How Does Cognitive Behavioral Coaching Change a Leader’s Thinking?
Cognitive behavioral coaching (CBC) borrows from clinical psychology but applies it to professional performance. The core idea: the stories we tell ourselves about events shape our responses more than the events themselves.
Leaders develop thinking patterns over years, and some of those patterns stop serving them. The manager who interprets every piece of critical feedback as a personal attack. The director who assumes silence in meetings means disagreement. The team lead who catastrophizes every small project delay into a career-ending disaster.
Scenario: The feedback-avoidant manager. Dev has strong technical skills and his team produces excellent work. But he avoids giving direct feedback because he believes people will “shut down” or “lose motivation.” When pressed, he admits he once gave a team member critical feedback early in his career and the person cried. That single experience became a rule: honest feedback = hurting people.
A CBC approach would surface that belief, examine the evidence for it (one incident, years ago, with a person he barely knew), and help Dev test a different assumption. What if honest feedback, delivered well, actually helps people? The coach might have Dev try giving specific, positive feedback first, then gradually work toward constructive feedback with one trusted team member.
The shift isn’t instant. Thought patterns built over a decade don’t disappear in one session. But naming the pattern is half the battle.
When it works best: Recurring behavioral blocks that the person recognizes but can’t seem to change. Confidence issues. Avoidance patterns. Situations where someone keeps “knowing” what to do but not doing it.
When to skip it: If the problem is situational (bad team dynamics, unclear role, organizational chaos), changing someone’s thinking won’t fix a structural issue. Don’t therapize a systems problem.
What Does Strengths-Based Coaching Look Like?
Strengths-based coaching starts with what’s already working. Instead of identifying gaps and building development plans to close them, it asks: what would happen if this person spent 80% of their energy on what they’re naturally good at?
The point is strategic allocation, not ignoring weaknesses. A manager who’s exceptional at building relationships but mediocre at process design shouldn’t spend six months in a process improvement course. They should learn just enough process skill to avoid failure and then invest deeply in what makes them distinctive.
Scenario: The quiet strategist. Ananya leads a product team. Her skip-level feedback says the team loves her thinking but wishes she’d “be more visible.” Her manager wants her to present at all-hands meetings and be more vocal in cross-functional meetings. Ananya dreads both.
A strengths-based coach would push back on the assumption that Ananya needs to become a polished public speaker. Instead, they’d ask: where does Ananya’s strategic thinking already show up? Turns out she writes brilliant strategy documents that people share across the company. She’s excellent in small group discussions where she can build on others’ ideas.
The coaching conversation shifts from “how do we fix your visibility problem” to “how do we create more situations where your strengths are visible?” Maybe that’s a monthly strategy memo with her name on it. Maybe it’s leading small working groups instead of presenting to 200 people. The goal is building on what’s already strong, not fixing what’s naturally difficult.
When it works best: Development conversations. Helping someone find their niche as a leader. Situations where a person is being pushed toward a generic “good leader” mold that doesn’t fit them.
When to skip it: When there’s a genuine skill gap causing real harm. If a manager can’t have basic difficult conversations, routing around that gap with strengths-based work just delays the problem.
How Does Systemic Coaching Address Team-Wide Problems?
Systemic coaching zooms out. Instead of coaching the individual, it coaches the individual within their system: the team, the relationships, the organizational dynamics they operate inside.
Most coaching treats the person sitting in front of you as if they exist in isolation. But leaders don’t operate alone. A manager’s behavior is shaped by their team’s expectations, their boss’s pressure, the company’s incentive structures, and the unspoken rules of their organizational culture. Understanding these dynamics requires real empathy for everyone involved, not just the person being coached.
Scenario: The bottleneck leader. Karan runs an engineering team of 12. Every decision flows through him. His team complains he’s a bottleneck. His boss says he needs to delegate more. But when Karan tries to delegate, things fall apart. Tasks come back incomplete. Deadlines slip.
An individual coaching approach might work on Karan’s delegation skills. A systemic approach would ask: why does this team need Karan to be the bottleneck? What function does it serve? Turns out Karan’s team has unclear role boundaries. Two engineers think they own the same area. The junior engineers don’t know what “done” looks like because the team has no shared standards. Karan isn’t a bottleneck by choice. He’s the only one who holds the whole picture because nobody else was set up to.
The systemic coaching work involves Karan, but it’s aimed at the team’s operating system: clarifying roles, building shared standards, and creating feedback loops that don’t all run through one person.
When it works best: Repeated team-level issues that survive individual coaching. Situations where you’ve coached three different people on the same team and the problem persists. Organizational change. Merger integration.
When to skip it: When the problem genuinely is one person. Not every issue is systemic. Sometimes a manager just needs to improve a specific skill.
When Should You Use Each Strategy? A Side-by-Side Comparison
Picking the right strategy means reading the situation correctly. The table below maps each one to the moments where it fits.
| Transformational | Solution-Focused | Cognitive Behavioral | Strengths-Based | Systemic | |
|---|---|---|---|---|---|
| Best for | Identity shifts and career transitions | Specific, bounded problems | Recurring mental blocks | Development and differentiation | Team-level dysfunction |
| Starting question | ”Who do you need to become?" | "When has this worked before?" | "What are you telling yourself about this?" | "What are you already great at?" | "What’s happening in the system around you?” |
| Time to results | 3-6 months | 1-2 sessions | 6-8 weeks | 4-8 weeks | 3-6 months |
| Coach skill level | High (requires depth) | Moderate (structured) | High (pattern recognition) | Moderate (observation) | Very high (systems thinking) |
| Risk if misapplied | Over-philosophizing when action is needed | Ignoring deeper issues | Over-pathologizing normal reactions | Avoiding real weaknesses | Blaming “the system” for individual issues |
| Works well with | Senior leaders, high-potentials | New managers, anyone stuck | Feedback-avoidant leaders, perfectionists | Anyone in a growth phase | Cross-functional teams, reorgs |
Mastering one strategy is the easy part. Diagnosing what someone needs and choosing accordingly is where experience actually shows. Many experienced coaches blend two strategies in a single conversation: solution-focused to build early momentum, strengths-based for longer-term development.
Try Risely’s coaching assessment to identify where your coaching instincts are strongest and where you might be defaulting to the same approach every time.
Four Coaching Models That Give Your Conversations Structure
Strategies tell you what approach to take. Models tell you how to structure the conversation once you’ve chosen your approach. Think of models as conversation blueprints. Here are four that work across most leadership coaching strategies.
GROW: The Workhorse
GROW (Goal, Reality, Options, Way Forward) is the most widely used coaching model for a reason: it’s simple, it works, and you can learn it in an afternoon.
A GROW conversation with a struggling project manager might go like this. Goal: “I want to run Monday standups without them turning into 45-minute complaint sessions.” Reality: “Right now, everyone brings up blockers and we spend the whole time troubleshooting. I don’t have an agenda.” Options: “I could set a strict 15-minute timer. I could create a separate channel for blockers. I could restructure the agenda with one update per person.” Way Forward: “I’ll try the structured agenda this Monday. Two minutes per person, blockers go in the Slack channel, we troubleshoot in pairs after.”
Simple. Concrete. Done in 20 minutes.
OSKAR: Built for Strengths
OSKAR (Outcome, Scaling, Know-how, Affirm + Action, Review) is the natural partner for strengths-based coaching. The scaling step is what makes it distinctive: you ask the person to rate where they are on a 0-10 scale, then explore what got them to that number instead of what’s keeping them from 10.
That reframe matters. If someone rates themselves a 6, most coaches ask “what would get you to an 8?” OSKAR asks “what have you already done to get from 0 to 6?” It surfaces existing competence.
CLEAR: For Deeper Conversations
CLEAR (Contract, Listen, Explore, Action, Review) works well when the coaching conversation needs to go deeper. The “Contract” step at the beginning is key: you explicitly agree on what this conversation is about and what’s in bounds. That’s especially useful for sensitive topics like team conflict, career dissatisfaction, or performance concerns.
The “Listen” step is active and reflective: the coach mirrors back what they’re hearing and checks understanding before moving to explore solutions.
STEPPA: When Perception Is the Problem
STEPPA (Subject, Target, Expectations, Perception, Perception Gap, Alternatives) is built for situations where someone’s perception of reality doesn’t match the reality around them. The two Perception steps (exploring the person’s view, then identifying gaps between that view and what others see) make it particularly useful alongside cognitive behavioral coaching.
A manager who believes their team “doesn’t respect them” might discover through the perception gap step that the team actually respects their expertise but wishes they’d share context more openly. That’s a very different problem with a very different solution.
Which Model for Which Strategy?
You can pair any model with any strategy, but some combinations work especially well:
- Transformational coaching + CLEAR: The contracting step gives space for vulnerable conversations about identity
- Solution-focused coaching + GROW: The structured simplicity helps keep conversations focused on outcomes
- Cognitive behavioral coaching + STEPPA: the perception gap steps directly support examining thought patterns
- Strengths-based coaching + OSKAR: the scaling question naturally surfaces existing strengths
How Do You Start Using These Strategies Today?
You don’t need certification to start. You need willingness to practice and enough self-awareness to notice when you’re defaulting to the same approach regardless of the situation.
Start by naming your default. Most managers have one coaching move they repeat. Maybe you always go to goal-setting (solution-focused). Maybe you always ask about feelings (cognitive behavioral). Recognizing your default is the first step toward expanding your range.
Next, try one new strategy this week. Pick the approach that feels least natural to you. Use it in a low-stakes conversation. A casual one-on-one, a development check-in. See what happens.
Then ask for feedback. After a coaching conversation, ask the person: “Was that helpful? What would have been more useful?” Their answer will teach you more than any coaching book.
If you want to identify your coaching strengths and blind spots before you start experimenting, Risely’s leadership assessment gives you a starting point. And if you want to practice coaching conversations in a low-risk environment, try Merlin, Risely’s AI coach, to test different strategies and get real-time feedback on your approach.
For more on building coaching skills in the workplace, see our complete guide on coaching employees and our list of recommended coaching books for deeper reading.