Put the coaching into context.
Read an experience-based story about building confidence, or explore an illustrative scenario about coaching through a weakening sponsor relationship.
Confidence, Not Capability When the Sponsor Goes QuietGood coaching starts with curiosity, not a verdict.
Before deciding what someone needs, understand the person, look at the work together, and ask what is getting in the way.
My approach is to build confidence and judgment, then help turn individual growth into shared team capability. That means clear expectations, practical support, honest feedback, and ownership that stays with the person doing the work.
Explore the approach
This is the approach I aim to bring to Customer Success leadership. It is a guide to adapt to the person and situation, not a script every coaching conversation must follow.
A missed commitment or a hesitant customer conversation is an observation, not a complete explanation. The next step is to understand whether the person needs a new skill, more confidence, clearer expectations, fewer obstacles, or a combination.
Coaching is not only for something that has gone wrong. A strong performer may be ready for a new capability, a more complex account, or an opportunity to help others grow.
Six steps to draw from. Support that changes as the person grows.
Understand their strengths, goals, and view of the situation. Use real work to explore whether the issue is skill, confidence, capacity, or process before choosing the support.
Ask“What’s getting in the way?”
Connect the development goal to the customer outcome it should support. Agree on what better looks like in observable terms, what support is needed, and when you will review progress together.
Ask“What would better look like?”
Shadow a call, review an account plan, or walk through a customer situation together. Explain what you notice, which questions you ask, and why you choose a particular next step.
Say“Here’s what I’m noticing, and why.”
Let the CSM lead the next attempt. Debrief with specific feedback, then look for whether they can apply the learning in a different situation rather than simply repeat your steps.
Ask“Walk me through your recommendation.”
Invite people to share a demonstrated strength through peer shadowing, a team discussion, or a reusable playbook. Recognize their contribution and check whether others can use the learning, rather than treating a recorded session as proof of adoption.
Ask“What could others use from this?”
Look for changes in behavior, judgment, and customer progress, not just completed activities. Keep what helps, adjust what does not, and consider whether recurring obstacles call for a better process rather than more individual coaching.
Ask“What changed? What should we adjust?”
I want people to feel safe asking questions, raising risks, and acknowledging mistakes early. My responsibility is to respond with curiosity, give honest feedback, and help clarify the next step.
Support does not mean removing responsibility. We should leave the conversation knowing who owns the follow-through, what help is available, and when we will reconnect.
An anonymized example from my leadership experience.
I worked with a strong CSM who wanted to deepen her fluency in a customer’s cloud environment. This was a development opportunity, not a performance turnaround.
With customer approval, I demonstrated how to review the environment, notice capabilities worth exploring, and turn those observations into questions about how the customer worked. The point was not to make her do every technical task herself. It was to strengthen her judgment about what to ask and when to involve an engineer.
She then applied the approach in another account, and we reviewed her reasoning together. Later, I invited her to share the approach through recorded team enablement.
The progression mattered: see the work, apply it independently, then help others learn. Sharing the session created a learning resource; whether others adopted the approach was a separate question to check.
These are signs I look for, not a scorecard to apply identically to every person. The evidence should match the development goal and the work they actually own.
Start with the person’s agenda, not just your account checklist. Choose the questions that fit the conversation rather than trying to get through them all.
You do not need to use every step at once. Start with one observable situation, ask for the person’s perspective, and agree on one useful next step.
Read an experience-based story about building confidence, or explore an illustrative scenario about coaching through a weakening sponsor relationship.
Confidence, Not Capability When the Sponsor Goes QuietCapture what you observed, consider alternative explanations, and agree on practice, support, and a review point.
Open the worksheetKeep coaching notes private, respectful, and focused on development. The worksheet is a conversation aid, not an employee-rating system or a substitute for your organization’s formal processes.
The goal is not to become the person every decision must pass through. It is to help people build the judgment to lead the next situation with greater independence.
Back to the conversation prompts