KPIs are the ultimate indicator of where you want your team to spend their time. The old adage that people do what they're get paid to do holds true. If you're paying people to do QBRs, they'll do them. If you're not, it will be harder for them to do so. So as you're developing your KPIs, think about where you want your team to spend their time. If that's where they're spending their time today, great. Write some KPIs that will add motivation to their already busy days. If, however, they're spending times on areas where you don't want them to focus, use the KPI rollout to pivot their time and attention to an area that will be a better use of their time.

I’ll share 2 questions – one is behavioral based, and one is situational. One of our core values is Extreme Ownership. I ask candidates to “Tell me about a time when you had to convince someone to do something in order for you to meet a goal or deadline. Why did you need to convince them? What was the goal/deadline? What was the result?” What I like about this question is it embodies all things CS - accountability; influence (usually without authority; partnership and teamwork; creativity… I look for an answer that helps me understand the what, the how, and most importantly, the why. Influencing someone because you missed something and now are in a crunch is very different than your new leader assigning you a nebulous project with a clear deadline, but not much direction. One of the best answers I’ve gotten was around a ‘still in development' product that was sold to a customer prior to the CSM taking the account. The customer was frustrated with the length of time it was taking to go GA - and with 2 missed delivery dates already. was asking for specifics to bring to their senior leadership regarding the 3rd promised delivery date. The candidate talked about the challenge first of understanding what the use case was as well as what was promised in the sales process. The candidate had to help the customer define the use case and then went back to the AE to understand what was sold. They then went to the product team to understand the product functionality and engineering to get timelines, which were still a ways out. They went back to the customer with the updated information and the customer was extremely unhappy. The candidate held a cross functional meeting internally - they were able to get alignment internally to prioritize the product to get within 2 weeks of the 3rd deadline, which was much improved from 6 weeks. The customer was cautiously optimistic, and when the vendor was able to deliver on the newly agreed upon timeline and the product worked as expected, over a period of weeks the customer moved from a detractor in sentiment to a promoter. The other question I’ll talk about here is “If you were to join us, what would you do in the first 90 days to build trust with your peers, leadership, and cross functional team members? (NOT CUSTOMERS) What I am looking for here first is whether their instinct is to lead by process or by people. Some candidates say they schedule meetings to understand the product, and some say they want to know what makes the team tick. I also listen to see if they tend to ask for help or go it alone. Neither are right or wrong; it helps me understand how they tend to work. I then look for them to share specifics on ways they would engage, and if it would be different for each group or more of a cookie cutter approach. This is really important for us as all of our CSMs are fully remote, and they need to be able to work with a variety of people at different levels in different ways.

In my experience, in order to retain good Customer Success talent, here are things that you must offer: * Clear career growth opportunities * Invest in ongoing training and development * Foster a positive, inclusive team culture where achievements are recognized and employees feel valued * Encourage work-life balance by offering flexibility and supporting initiatives * Provide competitive compensation and benefits to ensure employees feel financially supported, which I feel we do a great job of at Zendesk.

When interviewing new Customer Success Managers, I prioritize strong communication skills and professionalism as fundamental requirements for the role. Additionally, I seek evidence of their proven track record in essential role-related skills. I also inquire about instances where they've demonstrated "Extreme Ownership" of accounts and situations, along with lessons learned from past missteps, whether internal or with customers.

This is one of the most critical components of customer success leadership both when establishing a CS function or joining a team with an already established CS org. If a CS team sits within the sales organization, there may be a natural alignment already anchoring the full team to joint business-based KPIs like churn reduction or retention/renewal outcomes. In this case, it's important to recognize how each team contributes to those shared outcomes - while the KPIs may be shared, the path to achieving the KPIs can (and likely should) differ by team. For example, CS may lean more into product adoption and customer value assurance in service to retention or renewal outcomes, whereas sales is responsible for growing the customer base or growing the renewal. If the sales and CS teams are managed separately within the organizational structure, it becomes even more key to have conversations around how CS incentivization and measurement models serve the broader organizational and business outcome goals. For example, showcasing how boosting customer product adoption through well-timed customer engagements leads to customer value and stronger renewal outcomes. One of the most effective ways to anchor teams on commonly shared KPIs is to be very specific about how the actions (inputs) lead to results (outcomes) - ensuring this narrative is reinforced consistently through the organization. It's also important to be transparent on each team (sales/CS) around how team members are measured if there are differences in accountability structures - this builds trust and confidence that while actions may differ, 'skin in the game' is present for all teams in service to business outcomes.

It's all about alignment. Product, Marketing, and Success need to be well aligned on the adoption goals and need to execute cross-functional programs to drive those goals. You need to be specific about which users should be using the app in what ways, and on what frequency. You also must be able to measure (and slice/dice) adoption to move the needle. In a prior company, we put someone in a dedicated role that played between these 3 functions with a specific focus on driving customer adoption through all channels (in-app paired with events, emails, community posts, CSM motions, etc.). It worked well because: * We were able to isolate the user personas we expected to see in the application weekly/monthly and measure their actual adoption * We were able to see which parts of the app the various personas were using * We built a weekly cadence to certain activities that each persona should do in the application * We built campaigns and materials to push specific personas to do specific activities in the app * We rolled out those digital campaigns in coordination with CSMs monitoring accounts and discussing the same things with our champions in accounts * The person in the role was highly motivated, creative, and understood our product and users deeply It can certainly be done without a dedicated person, but it's often difficult to carve out the appropriate time and departmental focus to achieve real movement.

Sure thing! Start by deeply understanding the customer journey... Identify: identify gaps in onboarding, adoption, and renewals. Define: List out clear processes and playbooks to ensure consistency while staying flexible as the company scales. Leverage: Make use of technology automation and data early to track customer health and engagement. Align: Collaborate closely with Sales, Product, and Support to create a seamless customer experience. The base for the above is to construct a customer centric culture within the team to drive long term success.

I want to first understand which activities or metrics correlate to churn, renewal and expansion. Then I know how to target my CS team and which activities to track off the back of that, as well as which metrics I need to keep a close eye on. So I don't think there's an easy one size fits all answer here. But I certainly think that broad strokes I will be tracking Health/adoption,GRR and NRR wherever I am, as well as understanding where you're losing WHY and WHO you're losing - is it specific company types, sizes, tenure etc.

I've found two KPIs to be difficult to commit to: 1. Customer Health. If you have a robust algorithm to measure customer health (influenced by a number of inputs ), it can be hard commit to a certain outcome. To frame this another way, I've often observed customer health scores as being a bit of a black box where it's hard to tie the actions you take to specific outcomes when there could be a number of variables outside of your control that influence the ultimate score. I much prefer to commit to lead measures that are directly within the control of the team. KPIs related to customer engagement are a good example of things that are more directly within the team's control. 2. Upgrade rate. Many CSM teams are measured on Net Revenue Retention. As part of this, your CSMs may be responsible for identifying growth opportunities within the install base of customers. I find it's effective to measure the team on how many growth opportunities the team identifies but not the close rate or upgrade rate, especially if the Sales or Account Management team owns the closing motion. 

Technical Support response targets! We’ve all been there, and being the first Success Hire is super exciting. You get to wear many hats, get involved all the way through the customer lifecycle and be scrappy to get customers what they need. For us at the beginning, that meant taking on a lot of Technical Support tickets for our EMEA customers, especially in the morning before our then US-based tech support team was online. On the one hand, this gives you a lot of valuable product knowledge that can help you be an impactful CSM, but on the other hand, it can mask the business need to expand technical support teams and can hurt your focus in the long term. If you can, explain early the difference between CS and Tech support KPIs and ensure that anything you take on is temporary!