Back in April, I started a new role as a customer success engineer with DigitalOcean. Admittedly, I didn’t know what to expect coming from being a systems administrator. During the interview process, I got the impression that the role was a mixture of account management, solutions engineering, and support.
Now three months into the role, I can confidently say that with regard to duties, my impression was more or less spot on. But in practice, the role is so much more than that. It’s more than taking care of discounts, payments, and other account level issues. It’s more than specing out a solution for a customer, or writing scripts to provision that solution automatically. It’s more than just making sure that an issue is fixed, or that you have the answer to every technical question.
There’s a relational element to customer success that’s hard to quantify. The best way I can explain it is like this:
Suppose your grandmother, significant other, or best friend suddenly starts up a company. They come to you and ask you, “Heya! I want to use
What would you do? If you’re invested in that person, you’d likely do everything you can to help them out. In practicality, it might look like:
- Taking a hands-on approach to managing their account to ensure that they have a butter-smooth on-boarding process
- Take an extended time to understand what they’re doing with their business and what they’re looking to do on the platform
- Advising them about any pitfalls that they might encounter along the way
- Making sure that they now about everything on the platform that will help their business grow
- Showing genuine concern and empathy when things aren’t going so smoothly
- Being transparent about the platform’s shortcomings/weak areas and suggesting ways that they might be able to work around those weaknesses
In short, you’d do everything you feasibly can to make sure that their company grows and succeeds. So yes, being a customer success engineer (or customer success manager, in other industry-specific parlance) is different than being an admin.
So how does one make the transition from being an admin to being a customer success engineer/manager?
Moving from Admin –> Customer Success
The last three months have been a challenge, I won’t lie. I’d developed some bad habits in my last role, and it comes down to two big ones:
- Lack of empathy (largely due to ticket crunching…when your team addresses hundreds of tickets a day, it’s hard to have enough time to be empathetic in every one)
- The aforementioned being myopic when addressing issues/tickets
In short, I didn’t care. I didn’t have time to care. Don’t get me wrong, it’s not that I didn’t want to care. The last thing I think anyone wants in their job is to come off as apathetic and disinterested. However, high volumes of support tickets don’t lead to an environment that engenders empathy and a holistic focus on customer accounts.
So how did I get past that? Well, for one, starting a new role helped. I didn’t feel as burned out, and being in a new environment was refreshing. Also, accountability is another HUGE help. When you’re part of a team that calls you out for not being empathetic, or showing genuine care for your customers, you learn quick that you need to change your behavior. The other thing that’s helped is being involved in the customer success community. For me, that’s looked like:
- Reading up on customer success literature (So far, the book that’s helped with the transition the most has been Farm, Don’t Hunt)
- Being present and (somewhat) active in the Support Driven Slack channel
- Reaching out to other customer success organizations, like Glide Consulting to see how they do Customer Success
Also, it’s taken asking myself the hard questions about how I approach customer issues and taking a step back when I realize I’m defaulting to a break/fix mentality. That’s definitely not fun.
Now, I’m prone to wanting to make everything repeatable and testable. I blame it on my training as an academic researcher. I love patterns and I love it when I can make something fit into a pattern that I just automate and set on autopilot. I’ve found that’s not how Customer Success works. Why? Relationships. Like I mentioned earlier, Customer Success is more than fixing a single problem. It’s about establishing trust and rapport with customers and being invested in their growth. There are patterns and methods that I’ve found in some of the interviews I’ve been doing, but they’re certainly well-suited to a “one-size-fits-all” approach. They take tweaking, adjusting, and above all, the ability to admit that those methods may just not work for a customer success organization. All that to say the journey into Customer Success requires hard work and for me, quite a bit of introspection to reflect on what I do on a daily basis to see if it fits within a Customer Success mold.
So if you’re just starting out in Customer Success from a more technical role, and you’re finding it hard, don’t worry. It’s not an easy transition. But if you take some time to reflect on your default habits, get involved in the customer success community and be open to the fact that it’s going to take some time to make the transition into the new role, you’ll be off to a good start.comments powered by Disqus