Yesterday I did something extremely exciting, I booked my flight and accommodations so that I can attend SupConf! Previously I’ve written about choosing support as a career, and about how we can make support cool. The community behind SupConf, Support Driven, and the conference itself is a great way to help accomplish this. If you are in support, and are passionate about it, I highly recommend checking out both Support Driven and SupConf both.
Some of my colleagues at Automattic are helping organize the event, and some are also speaking. The line up of speakers and topics looks amazing in general. I’m very much looking forward to spending time with people from a bunch of different companies all dedicated to providing excellent support.
The icing on the cake is that the venue is Automattic HQ in San Fransisco. Getting to visit the company office is pretty neat. To get to visit it while learning and participating at SupConf so I can take home new ideas to help bring happiness to the people who use our products is awesome!
Today I’ve been thinking a bit about support as a career again and wondering why so many people think of it like a entry or lower position. Besides one of the big reasons that I talked about before I think there are other things that come into play here as well.
One of the huge things is that being able to code has become very cool. In the case of Automattic two of the largest groups of employees we have are developers and support. In the media, and particularly tech media, it’s the people making the products that have become the rock stars. Either making something from scratch, finding a bug and fixing it, or conceiving a new feature and bringing it to life for tonnes of people to use, has to be very satisfying. Come on, that is cool! Why wouldn’t you want to aspire to be able to do that?
Another reason is most of my fellow Happiness Engineers are problem solvers. We want to fix things. If that happens to a bug or an improvement to our products how great would it be to go and fix it on the spot if a customer brings it to our attention. During one conversation someone pointed out to me a typo on one of our support documents. While we were talking I opened another window and fixed it. Even that tiny change impressed them and felt very good to me to have the power to resolve it.
There is no reason though that both developers and support roles can’t both be seen as cool. Support is cool and we should all be rock stars too. How do we turn things around and show the world how awesome support is? With coders they have that almost tangible result of their work. Look, see that? That’s what I made today. Maybe one of our tangibles could be all the hugs we get from users. There are not many days that go by that I don’t receive some sort of amazing feedback from someone I’ve talked with because either I or my colleagues have helped them. That is a powerful gift.
If we are doing our jobs well we could also say things like this: See this change? While talking to a bunch of people I knew there had to be a better way to do this, and after working with our developers here it is. Another scenario could be: While chatting with people it really seemed that this new feature would really help them accomplish their goals. Start that conversation and then become the champion behind it getting built and out there for everyone to use. We might not be the ones actually building or making, but we should be able to point to all kinds of examples where we’ve influenced the products based on our conversations. That to me is cool!
It’s up to us to help show the world that being in support is both awesome, and a viable career option in the right environment. How do we do that? Let’s find ways to show how rewarding and important great support is. If we can do that we can draw even more people into this career. That means more great co-workers and it could convince more companies to invest and make support a more prominent role with them.