I didn't come to customer success through the traditional route. No CS bootcamp. No SDR-to-AE-to-CSM pipeline. I came through premium support — the kind where your customers are paying for direct access and have real expectations about the speed and quality of your answers.
It was a good school. Fast feedback loops. High stakes on every ticket. And a product knowledge depth that I think most people who jump straight into CS never fully develop, because they didn't have to. In support, you learn the product because the alternative is getting humiliated in a support thread in front of the customer who is already frustrated with you.
When I moved into CSM, I thought the hard work was done. I knew the product. I knew how to talk to people under pressure. I thought I was a few new vocabulary words away from being good at the job.
I was wrong.
What Actually Transferred
The foundation was real. I don't want to undersell it — there are things I built in support that I still rely on every day, and that I think took years to develop correctly. They show up in ways that are hard to teach from a CS onboarding deck.
What came with me ✓
- How to talk to a frustrated customer without escalating the room — and without being condescending about it
- Holistic product knowledge. Not just features but how they interact, where they break, and what customers actually run into in production
- Creative problem solving under constraint — when the product doesn't do the thing, you find the thing the product almost does
- Tool fluency: ticket systems, internal escalation paths, cross-functional relationships, knowing who to call and how to frame it
- Reading the emotional temperature of a conversation and adjusting tone without losing substance
- Knowing when a customer is actually upset about the thing they're upset about — and when they're upset about something else entirely
What I had to build from scratch
- Business context — understanding the customer's company, goals, and internal politics well enough to advise, not just assist
- Value conversations — naming what the product is actually worth to this specific customer, in their language, tied to outcomes they care about
- Discovery — asking open questions, listening without jumping to solutions, building a picture before proposing anything
- Proactive motion — finding the problem before the customer does, not just solving the one in front of you
- Strategic framing — tying individual asks to bigger business objectives, not just resolving them in isolation
- Renewal and expansion thinking — understanding the commercial relationship and what it takes to grow it
The left column was genuinely useful. The right column was the job.
Support trains you to be excellent at the thing in front of you. That's the skill — fast, accurate, clear, helpful. The faster and more accurate the better. Every instinct you develop points toward resolution.
CSM, I learned, is not about resolution. It's about relationship. And the gap between those two things is wider than it looks from the outside.
The Paradigm Shift I Wasn't Ready For
The biggest adjustment — and I mean this took me longer than I want to admit — was learning to sit with a problem before trying to fix it.
In support, speed is a virtue. A ticket comes in, you triage, you resolve, you close. The whole system is built around throughput. When you've spent years operating that way, it becomes reflexive. Someone describes a problem and your brain is already three steps into the solution before they've finished the sentence.
In CSM, that reflex works against you.
The question I had to teach myself to ask — on every call, with every new piece of information — was not "how do I fix this" but "why does this need to be fixed, and what happens if it doesn't?" That second question is where the real work lives. That's where you find out whether a feature request is a genuine blocker or a distraction from a deeper workflow problem. Whether a complaint about pricing is about price or about perceived value. Whether a champion is asking for something because they need it or because they're signaling political pressure from above.
It sounds simple in writing. It is genuinely hard in practice, especially when you're wired to move fast.
Learning to Zoom Out
The practice that changed things most for me — and that I still do deliberately, even with accounts I've had for a year — is what I think of as zooming out at the start of every meaningful conversation.
With new customers, it's obvious. You don't know their world yet. You need to ask before you advise. But with long-tenured accounts, there's a trap: you think you know their situation, so you skip the questions and go straight to the familiar rhythm of the relationship. And then something shifts in their business — a reorg, a new budget cycle, a new stakeholder — and you're the last person to find out because you stopped asking.
Before every QBR or renewal conversation, I write down two things: what I think I know about this customer's current priorities, and what I'm assuming I know that I haven't actually confirmed recently. The second list is always longer than it should be. That gap is where I focus the first 15 minutes of the call.
Zooming out is also how you catch the problems before they become incidents. A customer who seems fine might be running a workflow you've never asked about — a workaround for something the product doesn't do well that's adding hours to their week. They didn't file a ticket about it because they stopped expecting a fix. The reactive CSM never finds out. The proactive one asks "walk me through how your team actually uses this on a Tuesday" and gets an earful.
I'm Still Learning
I want to be honest about something: this transition has been hard in ways I didn't expect, and I'm still in the middle of it. Not in a stuck way — I've grown a lot, and the work has compounded. But I don't think you ever fully arrive at "strategic" and stop having to work at it. The reactive instinct doesn't disappear. It just gets quieter.
There are still calls where I catch myself sprinting toward a solution before the customer has finished painting the picture. There are still moments where I close a conversation feeling like I handled it well, then sit with my notes afterward and realize I never asked the one question that would have told me what was actually going on.
What's changed is that I notice it now. And I've built enough of a practice around slowing down — the zoom-out habit, the deliberate discovery, the discipline of asking "why does this matter?" before "how do we fix this?" — that the instinct has somewhere better to land.
The support background isn't a liability. The product knowledge, the instinct for customer empathy, the ability to problem-solve under pressure — those are real advantages in CS. What took me time was understanding that they were foundation, not ceiling. That the job required a whole additional layer of thinking that I had to build from scratch.
It's been a fun, hard ride. And I'm still figuring it out.
This is part of an ongoing series about what actually works in customer success — including the things that took longer to learn than they should have.