What to Protect, What to Delegate, and What to Let Go Of as a CS Leader

1 - > Are you a customer success leader? 2 - > If so, I want you to open your 3 - > calendar right now. 4 - > Look at this week, look at what's on 5 - > it. 6 - > Now, ask yourself honestly, how much of what's 7 - > on that calendar did you put there intentionally?

8 - > How much of it reflects your priorities as 9 - > a CS leader? 10 - > The strategic work, the team development, the thinking 11 - > time, the things that actually moved the needle, 12 - > and how much of it just accumulated, meetings 13 - > that got scheduled because someone needed you, recurring 14 - > calls that nobody has canceled in 18 months, 15 - > back-to-back-to-back blocks that leave 16 - > no room to actually think. 17 - > For most customer success leaders, the honest answer 18 - > is that their calendar is a reflection of 19 - > everyone else's priorities, not theirs.

20 - > And the result is a leader who is 21 - > constantly busy, constantly responsive, and consistently running out 22 - > of time for the work that actually matters. 23 - > Your calendar is not just a scheduling tool. 24 - > It's a strategic asset. 25 - > And if you're not designing it intentionally, someone 26 - > else is designing it for you.

27 - > That's what this episode is about. 28 - > So let's get into it. 29 - > Welcome to the CS RevSpeak podcast, where we 30 - > talk about practical insights, strategies, and frameworks that 31 - > will help customer success leaders who carry a 32 - > revenue number, drive sustainable growth, maximize customer lifetime 33 - > value, and crush their numbers. 34 - > Let's see what is actually happening here, because 35 - > I think it's worth understanding before we talk 36 - > about how to fix it.

37 - > Customer success leadership is one of the most 38 - > cross-functional roles in a SaaS business. 39 - > You're connected to sales, to product, to support, 40 - > to finance, to the executive team. 41 - > Everyone has something they need from customer success, 42 - > and because CS is fundamentally a relationship-driven 43 - > function, there's a cultural expectation, sometimes explicit, sometimes 44 - > just absorbed, that a good CS leader is 45 - > always available, always responsive, always there when someone 46 - > needs something.

47 - > And so the calendar fills up. 48 - > Customer escalations, cross-functional things, team check-ins, 49 - > leadership meetings, one-on-ones that run long, 50 - > and somewhat in the middle of all of 51 - > that, the strategic work, the work that only 52 - > you can do as a leader of this 53 - > function, gets squeezed into the margins, early mornings, 54 - > late evenings, the gaps between meetings that are 55 - > too short to do anything meaningful in. 56 - > Here's what that actually costs.

57 - > Not in terms of stress or sustainability, although 58 - > those are real. 59 - > In terms of outcomes, when a CS leader 60 - > is perpetually reactive, the team feels it. 61 - > Decisions take longer because the leader is never 62 - > in a focused headspace to make them. 63 - > Coaching gets rushed or skipped because there's no 64 - > protected time for it.

65 - > Strategic initiatives stall because every time the leader 66 - > sits down to think, something urgent pulls them 67 - > back into execution mode. 68 - > And the function stays stuck at a certain 69 - > level of performance because the customer success leader 70 - > never has the bandwidth to lead it to 71 - > the next level. 72 - > A CS leader who designs their calendar intentionally 73 - > is a fundamentally different kind of leader. 74 - > They show up to one-on-ones prepared.

75 - > They have time to think before they have 76 - > to decide. 77 - > They can work on the org instead of 78 - > just in it. 79 - > And that difference compounds over time into a 80 - > team that performs at a higher level. 81 - > So the starting point is this, your calendar 82 - > is a leadership decision.

83 - > Every block on it is either something you 84 - > choose or something you're allowed. 85 - > And the first step in designing it well 86 - > is taking ownership of that distinction. 87 - > Before I share what I protected in my 88 - > own calendar, when I was a VP of 89 - > customer success, I want to acknowledge something. 90 - > The right calendar structure is not one size 91 - > fits all.

92 - > What it looks like depends heavily on where 93 - > you are in your journey as a CS 94 - > leader, specifically whether you're in early stage mode 95 - > or scaling mode. 96 - > Because two phases make very different demands on 97 - > your time. 98 - > And what serves you well in one can 99 - > actually hold you back in the other. 100 - > In early stage, when you're building a function, 101 - > when a team is small, when processes are 102 - > still being figured out, your calendar is going 103 - > to be heavily weighted towards execution.

104 - > You're in the details, you're in customer conversations, 105 - > you're building playbooks and sitting in on calls 106 - > and sometimes doing the work alongside your CSMs, 107 - > because that's how you understand what needs to 108 - > be built. 109 - > That's appropriate. 110 - > And that's right for that phase. 111 - > But here's where a lot of CS leaders 112 - > get stuck.

113 - > They never recalibrate, the org grows, the team 114 - > expands, the complexity increases, and the leader is 115 - > still spending their time the same way they 116 - > did when the team was three people. 117 - > Still in every escalation, still reviewing every renewal, 118 - > still running every customer call that matters. 119 - > And the team never develops because the leader 120 - > never creates the space for them to lead. 121 - > Scaling mode requires a fundamentally different calendar orientation, 122 - > less execution, more enablement, less doing, more developing, 123 - > less being in the work and more designing 124 - > the systems that make the work run without 125 - > you.

126 - > I remember when this shift happened for me. 127 - > I had built a team that was strong, 128 - > genuinely capable people who knew their accounts and 129 - > cared deeply about their customers. 130 - > And I realized one day that I was 131 - > selling their work in a way that wasn't 132 - > serving them anymore. 133 - > I was in account reviews, they could have 134 - > led.

135 - > I was in calls, they didn't need me 136 - > on. 137 - > And by being there, I was signaling unintentionally 138 - > that I didn't fully trust them to handle 139 - > it, that I needed to be involved for 140 - > things to go well. 141 - > That shift I made was to ask myself 142 - > a different question every time something landed on 143 - > my calendar. 144 - > The question was not, can I add value 145 - > here?

146 - > The answer to the question is almost always 147 - > yes. 148 - > You can almost always add something. 149 - > The question was, is my presence here the 150 - > best use of my time given everything else 151 - > I'm responsible for? 152 - > The question produced very different answers.

153 - > And it started freeing space for the work 154 - > that only I could do. 155 - > Let's get specific because I think the most 156 - > useful thing I can give you in this 157 - > episode is a clear picture of what belongs 158 - > on your calendar as a protected, non-negotiable 159 - > block. 160 - > And why? 161 - > First thing is to protect your strategic thinking 162 - > time.

163 - > And I want to be direct about this 164 - > because I know how it sounds. 165 - > Blocking time to think feels indulgent when your 166 - > team needs things and your inbox is full 167 - > and there are fires to put out. 168 - > But here's the reality. 169 - > The most important decisions you make as a 170 - > customer success leader, how to structure the team, 171 - > how to position CS internally, how to respond 172 - > to a pattern you're seeing across your book, 173 - > how to coach a leader on your team 174 - > who is struggling.

175 - > None of those decisions get made well in 176 - > the margins. 177 - > They require uninterrupted, focused thinking time. 178 - > And if you don't protect it, it won't 179 - > exist. 180 - > What this looks like in practice.

181 - > I'm talking about two to three blocks per 182 - > week, maybe 60 to 90 minutes each when 183 - > you're not in meetings, not responding to messages 184 - > and not available. 185 - > This is where you work on the org, 186 - > strategy documents, coaching prep, thinking about a difficult 187 - > decision, reviewing the health of the team's portfolio 188 - > with a fresh eye, whatever is most important 189 - > that week for you to give focused attention 190 - > to. 191 - > Protect it like you would protect a customer 192 - > commitment because it is one, a commitment to 193 - > leading your function well.

194 - > The second thing is to protect your one 195 - > -on-ones with your direct reports. 196 - > And I don't just mean having them on 197 - > a calendar. 198 - > I mean having them consistently on time fully 199 - > prepared and never canceling them. 200 - > Your one-on-ones are your primary leadership 201 - > tool.

202 - > They are where you coach, where you assess 203 - > performance, where you build the kind of trust 204 - > that makes a teamwork. 205 - > When you cancel them, especially when things are 206 - > busy, which is exactly when your team needs 207 - > them most, you send a signal. 208 - > You signal that their development is optional. 209 - > That when things get hard, the first thing 210 - > to go is the investment in them.

211 - > Protect your one-on-ones. 212 - > Reschedule before you cancel and you show up 213 - > to them prepared. 214 - > The third thing to protect is your customer 215 - > time. 216 - > Even as you scale and delegate more operational 217 - > work to your team, you should never fully 218 - > disconnect from customers.

219 - > You don't need to be in every account 220 - > or every call, but you do need to 221 - > stay connected somehow to the customer experience and 222 - > keep it grounded in what your team is 223 - > navigating. 224 - > It sharpens your coaching. 225 - > It gives you credibility in leadership conversations and 226 - > it signals to your team that customer relationships 227 - > matter to you. 228 - > What this looks like at the VP level 229 - > is deliberately selective.

230 - > I'm talking about a handful of strategic accounts, 231 - > executive relationships, escalation reviews. 232 - > You don't have to have a full book. 233 - > You need a curated presence. 234 - > The fourth thing to protect is your own 235 - > recovery time.

236 - > I'm naming this explicitly because CS leaders are 237 - > among the most prone to burning out quietly. 238 - > The work is relentless. 239 - > The demands are high and the culture of 240 - > the function rewards responsiveness above almost everything else. 241 - > You need wide space on your calendar, not 242 - > as a luxury, as a leadership requirement.

243 - > A leader who is depleted makes worse decisions, 244 - > coaches less effectively and models an unsustainable pace 245 - > for their team. 246 - > Protect lunch, protect the end of your day, 247 - > protect at least one morning a week where 248 - > you're nodding back-to-back meetings from the 249 - > moment you open your laptop. 250 - > Let's talk about delegation. 251 - > Delegation is where the calendar conversation gets really 252 - > hard because most of the things that eat 253 - > CS leaders' time are things they genuinely can 254 - > add value to.

255 - > The customer escalation, the renewal that's at risk, 256 - > the cross-functional thing that's going sideways. 257 - > Being in those things isn't wrong. 258 - > The question is whether being in those things 259 - > is the best use of your time at 260 - > this stage or whether it's time to hand 261 - > them to someone on your team. 262 - > Here's the framework I'm wanting to use.

263 - > There are three categories of work. 264 - > Work that only you can do. 265 - > Strategic decisions, leadership team, representation, work design, executive 266 - > relationships, coaching your direct reports. 267 - > This is your highest leverage work.

268 - > It should be the center of gravity of 269 - > your calendar. 270 - > There's also work that your team can do 271 - > with your input. 272 - > Account strategy for complex situations, difficult customer conversations, 273 - > cross-functional escalations that need a senior voice. 274 - > This is where you're a resource.

275 - > You don't have to be the owner. 276 - > Your job here is to coach and advise 277 - > and not to take over. 278 - > And then there's work that your team can 279 - > own entirely. 280 - > Operational reporting, standard customer touch points, renewal execution 281 - > for your healthy accounts, team rituals and meetings 282 - > that don't require your presence.

283 - > This is what gets delegated fully, not partially. 284 - > The challenge for most customer success leaders is 285 - > the middle category. 286 - > They stay too involved in work their team 287 - > can handle with input because it's hard to 288 - > let go of things you're good at and 289 - > care about. 290 - > And I understand that feeling, but staying in 291 - > the middle category at the expense of your 292 - > highest leverage work is one of the most 293 - > common ways CS leaders limit both their own 294 - > impact and their team's development.

295 - > Now here's the piece most CS leaders miss 296 - > entirely when they think about delegation. 297 - > It's not just about handing off operational work, 298 - > it's about delegating strategic initiatives to your CSMs 299 - > and doing it deliberately. 300 - > So think about a work that lives on 301 - > your to-do list that never gets done. 302 - > The playbook that needs a full revamp, the 303 - > onboarding process that's been patched together and needs 304 - > a complete rethink.

305 - > The QBR template that's outdated, the customer feedback 306 - > loop that nobody has formalized. 307 - > These are real strategic projects that matter for 308 - > the health of your function. 309 - > And they sit on your list quarter after 310 - > quarter because you never have the bandwidth to 311 - > give them the attention they deserve. 312 - > Here's the shift.

313 - > Those projects don't have to live on your 314 - > list. 315 - > They can live on a CSM's list as 316 - > a stretch assignment, a development opportunity and a 317 - > genuine contribution to the function. 318 - > Delegating a strategic initiative to a CSM does 319 - > two things simultaneously. 320 - > It gets the work done and it develops 321 - > the person doing it.

322 - > A CSM's who leads a playbook revamp is 323 - > building project management skills, cross-functional collaboration skills 324 - > and the system's thinking muscle they wouldn't develop 325 - > from account work alone. 326 - > A CSM who owns a process improvement initiative 327 - > is learning how to think about the function, 328 - > not just your book. 329 - > These are the experiences that build future CS 330 - > leaders and you create them by giving your 331 - > team real work with real ownership, not just 332 - > more accounts.

333 - > What this requires from you is a very 334 - > different kind of involvement. 335 - > You're not doing the work, but you're also 336 - > not fully absent. 337 - > You're setting the brief, what problem are we 338 - > solving? 339 - > What does success look like?

340 - > What are the constraints? 341 - > You're checking in at key milestones. 342 - > You're available as a thinking partner when they 343 - > get stuck and you're reviewing the output and 344 - > giving meaningful feedback. 345 - > That's the leader's role in delegated initiatives.

346 - > Non-ownership, sponsorship. 347 - > One practical move I'd recommend at the start 348 - > of each quarter, do a calendar audit. 349 - > Go through every recurring meeting on your calendar 350 - > and ask two questions. 351 - > Does this require my presence or could someone 352 - > on my team lead it?

353 - > And if I stopped attending this, what would 354 - > actually happen? 355 - > You'll be surprised how many meetings survive that 356 - > question. 357 - > And once they don't, those are your first 358 - > delegation opportunities. 359 - > Do the same thing with your strategic project 360 - > list.

361 - > For every initiative sitting on your plate, ask, 362 - > is there someone on my team who could 363 - > own this with the right brief and the 364 - > right support? 365 - > More often than not, the answer is yes. 366 - > And handing it over with real ownership, not 367 - > just task assignment is one of the highest 368 - > leverage moves you can make as a scaling 369 - > customer success leader. 370 - > I wanna close this segment with something that 371 - > took me longer than I'd like to admit 372 - > to fully internalize.

373 - > Letting go of things is not a sign 374 - > that you don't care. 375 - > It's a sign that you trust your team 376 - > and a team that is trusted to lead, 377 - > whether that's an account, a process or a 378 - > strategic project, develops faster, performs better and ultimately 379 - > makes you more effective as a leader because 380 - > they're carrying more, which means you can focus 381 - > on what only you can do. 382 - > Let's bring this together. 383 - > First, your calendar is a leadership decision.

384 - > Every block on it is either something you 385 - > chose or something you allowed. 386 - > Taking ownership of that distinction is a starting 387 - > point for designing a calendar that actually reflects 388 - > your priorities. 389 - > Second, what your calendar looks like depends on 390 - > where you are. 391 - > Early stage, you're close to the work and 392 - > that's right.

393 - > Scaling, the shift is toward enablement systems and 394 - > developing your team. 395 - > The leaders who get stuck are the ones 396 - > who never recalibrate as the org grows. 397 - > Third, protect the non-negotiables, strategic thinking time, 398 - > one-on-ones with your direct reports, selective 399 - > but deliberate customer presence and your own recovery 400 - > time. 401 - > These are not optional.

402 - > They are the foundation of sustainable high-impact 403 - > CS leadership. 404 - > And fourth, delegate with intention. 405 - > Know the difference between work only you can 406 - > do, work your team can handle with your 407 - > input and work your team can own entirely 408 - > and do a quarterly calendar audit to make 409 - > sure your time is actually distributed the way 410 - > you intend it to be. 411 - > Here's what I know from being in the 412 - > VP of CS seat and from working with 413 - > CS leaders who are navigating exactly this.

414 - > Designing your calendar well is one of the 415 - > highest leverage things you can do as a 416 - > leader. 417 - > Not because it may be more organized, but 418 - > because it changes what you're able to give 419 - > your team, your customers and your function when 420 - > you're operating from a place of intention rather 421 - > than reaction. 422 - > If you're in a season right now where 423 - > you have the opportunity to be deliberate about 424 - > how you build your role, or if you're 425 - > feeling the weight of a calendar that's been 426 - > designed by everyone else's needs, that's exactly the 427 - > kind of conversation I have with CS leaders 428 - > in my one-on-one executive advisory and 429 - > coaching program.

430 - > Well, look at how you're spending your time, 431 - > what's actually driving your highest impact and how 432 - > to build a rhythm that's both sustainable and 433 - > strategic. 434 - > If that's where you are, I'd love to 435 - > work with you. 436 - > If you want to see if this is 437 - > the right fit for where you are today, 438 - > schedule a free consult call at csrevspeak.com 439 - > forward slash coaching.

440 - > Thanks for being here. 441 - > I'll see you in the next one. 442 - > If you enjoyed today's episode and you want 443 - > to learn more about CS RevSpeaks coaching and 444 - > training services, head on over to www.csrevspeak 445 - > .

com. 446 - > I specialize in working with customer success leaders 447 - > who carry your revenue number, and I look 448 - > forward to helping you confidently run a revenue 449 - > -generating customer success team. 450 - > Don't forget to connect with us on LinkedIn 451 - > and join our customer success leaders hub for 452 - > more discussions, resources, and networking opportunities. 453 - > You can access the links on the share 454 - > notes.

455 - > See you next episode.