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!

The important thing is to start measuring items. Your initial 'goal' may be off, but you won't know that until you start measuring it and having your team work towards a KPI. Be open with them that this is a trial period that nobody's performance will be managed based on if they hit the number out of the gate. And then adjust from there -- if people are overachieving, up the target; if people are consistently struggling to hit, lower the bar. Once you've found the sweet spot, then you can add compensation, performance management, etc. on top.

There are two questions I always like to ask during an initial interview with a candidate: 1. Tell me about a problem you have worked on and how you solved it? - In full transparency, I actually borrowed this question from an article I read about Elon Musk's interview questions. I found the reasoning behind this question to be extremely interesting. First, you gain insight into the types of challenges the candidate has come across and their thought process for overcoming those challenges. Second, Musk says that this question shows him if the candidate truly worked on resolving this problem. Someone who was integral in the solution of a problem will know all the details and be able to explain in length what they were thinking was during the process. I have found a lot of success in asking this question. 2. I ask candidates to share with me a time they had to articulate value of their product/solution to a customer. As I mentioned in another question, showcasing your company's value is one of the most important responsibilities of a CSM. If a candidate does not have experience with this, how can I expect them to articulate value to our customers?

Developing quarterly or annual customer success OKRs and tying them to individual projects involves a structured approach: 1. Understand Company Goals: Align OKRs with overall company goals. 2. Define Objectives: Set specific objectives for the team. 3. Identify Key Results: Establish measurable Key Results for each objective. 4. Align Projects: Assign individual projects that contribute to Key Results. 5. Assign Ownership: Specify ownership of projects to team members. 6. Set Milestones: Break down projects into milestones with timelines. 7. Monitor Progress: Regularly track progress and adjust as needed. 8. Iterate and Improve: Continuously refine the OKR process. 9. Communicate Effectively: Keep teams informed and engaged. This structured approach ensures alignment with company goals, accountability for outcomes, and effective project execution to drive success in customer success initiatives.

My philosophy is that I want everyone on my team to be eligible for a raise, so it’s my job to help them understand what they need to do so that I can make the case to the business. Just as they are the advocate for our customers, I am the advocate for them. It’s not just about the quantitative - there are many qualitative things I consider when recommending a pay rise. Some of the most common pieces of advice I give to my team are: 1. Make sure you are a master of your business. Exceed your metrics or have a clear explanation of where and why you fell short. It isn’t essential that CSMs are always over 100% on everything, but you should have a clear plan that addresses why you are behind. 2. Are you having an impact outside of your specific book of business? Are you helping others when you can? Are you seeking out and taking on additional projects and opportunities when they come up? 3. Are you upholding the values of the team and organization? Are you having a net-positive effect on the morale and engagement of your peers around you?

While I have been at HubSpot for a long time (13+ years), many opportunities have come up over time that I have had to assess new opportunities. Here are the things I tend to look at when considering a role; * Market Evolution * Size and growth potential of the market the company plays in * Stage of evolution : is this a horizon that is in its late stages or on the cutting edge? * Potential : is this a single product/one trick pony or do * Product * Do customers love their product/service? * Who are their competitors and how does their solution stack up? * Are they a leader or laggard? Have they shown product/service innovation? * Leadership and Culture * Are they proud of their vision, values and culture, even if they are against the grain? * How visual/vocal is their executive leadership? * Do people love the company? Are they staying there or leaving after short periods of time? * How do they treat failure? * Skills and Growth * Does my past experience lend well to the role? * Are there opportunities for me to build new skills? * What is my potential for impact on the business priorities? * Does this role help me build skills for the next position I hope to achieve?

This somewhat depends on the company and its products. In general I would say that having technical skills can be helpful for a CSM…an additional plus in the trusted advisor role. The CSM's primary responsibility is to develop strong relationships with the customers key stakeholders, understand their business objectives and requirements, and ensure they are achieving their desired outcomes and obtaining value from the company's products or services. Having some technical knowledge can be an advantage if the company's products are very technical and / or complex. If the CSM has some technical proficiency then this can enable the CSM to better understand the customer's challenges / problems and provide more effective solutions. This elevates the CSM as the trusted advisor in the eyes of the customer. These skill can be particularly useful when looking for expansion opportunities within their existing assigned accounts The technical skills should be secondary to the softskills required of a CSM as I described elsewhere. I believe the technical skill should be more broad and solution oriented rather than in-depth knowledge on a product or technology. The CSM should be mindful that they don’t get pulled into areas that are out of scope for the CSM such as technical support and sales engineering.

It's really important to be prepared for any interview you take the time to do, both out of respect for the hiring manager's time and your own. That said, I view an interview as a conversation and opportunity for both parties to learn about each other. Here are two tips for being prepared and showcasing yourself in the best way: * Any presentation or demonstration project should be done explicitly for the hiring company. Many Customer Success roles will require candidates who advance multiple rounds to prepare a presentation, written project, or sample QBR. Though interviewing multiple rounds for multiple roles is time consuming and often downright exhausting, it's critical that you make sure what you put forward shows preparation and willingness to do the role. I often give candidates a prompt with sample scenarios that are unique to the skill sets the job requires or situations we're experiencing and trying to solve for. The interviewees who stand out most are those who take the time to prepare as the prompt requests. We often get candidates who say "oh, this is a QBR I did at my old company, does that work?" While I totally understand that doing presentations for multiple roles in an interview process takes a lot of time, those who prepare specifically for us send the message that they will do the work and want the job. * Do your research... but don't make it weird. It may sound silly, but it's true! Candidates should be as versed as possible with what the company does, their target market, ideal customers, etc. Likewise, candidates should have looked at the hiring manager's LinkedIn to be familiar with their basic background and any known mutual connections. The critical part, however, is that the candidate uses the background information they've researched as part of their answers to questions. Resist the urge to say something like "Hey, Go Eagles! ... I saw you went to North Olmsted High School." Fun fact: a candidate really said that to me. The awkward conversation that followed highlighted that no, we didn't go to school together, nor did we have mutual acquaintances, but they found it on social media and thought it would be a cool fact to share.

As CSMs we are expected to be trusted advisors to our customers. We gain trust by helping our customers address their challenges and achieve their business objectives. We become advisors when we learn to anticipate questions or concerns and we guide our customers toward successful outcomes. To gain credibility, our communication with the C-Suite must be concise, assertive, and informative. If you can explain the how and confidently tell me what to do next, that's incredibly valuable. 1. How are we doing? 1. Help me see that you understand my business, our mission, and our goals. When given the opportunity, don’t simply present adoption metrics, help me understand what they mean relative to what my business goals are and ask for clarification where needed. If we have achieved significant time to value and you have saved my business significant money or time, those are wins I’d love to know. If things are stalling, help me understand why with concrete examples and ask for my help with clear actions for me or a member of my team to take. 2. Were there any serious challenges we faced? What role did you play? Let’s face it, things don’t always go as we’d like. However, if you can keep the C-Suite informed and updated, you will earn their trust in a way that will influence how they view you as a key trusted vendor, in many cases even more so than when things go well. 2. How are we doing relative to similar customers? 1. The C-Suite regularly reviews industry and analyst reports (Ex: Gartner, Forrester) as well as intel to understand market trends and maintain a competitive edge. By regularly reviewing the same resources and providing thought leadership, you could help influence decision making throughout their organization 2. As you support customers in similar industries or business segments or share anecdotes with peers, you’ll start to see certain similarities and differences. If your customer is operating in a more innovative manner that you believe has helped them realize value with your software and supported their business goals, definitely let the C-Suite know 3. What are other things we could be doing to achieve the outcomes we desire? 1. Once you have gained credibility with your customer by supporting them through a few milestones, you have earned the right to ask for a deeper partnership. So think deeply about what this new partnership will look like. How might integrating your solution with another one of their key business tools help them operate efficiently? How might using another module of your software help them save costs from a duplicate solution? If you can hone in on a few high-impact actions your customer can take and assert your position as to why these actions will help, your C-Suite might offer the sponsorship you need to make this a reality.