6 ms·
Every engineering-minded founder/CEO will come up with this idea once in their career, get badly burned, and quickly realize why roles like customer success exi
by paxys 4y ago
Every engineering-minded founder/CEO will come up with this idea once in their career, get badly burned, and quickly realize why roles like customer success exist.
Having developers answer support tickets and follow up on leads is a terrible use of their time (especially considering how much you are paying them) and they will be terrible at it. In the worst case they will piss off customers and actually harm your business.
Imagine if the situation was flipped, and your CEO went "sales reps need to understand engineering complexity, so from now on they will each have to fix 10 bugs a month."
If there are problems with bug & feature prioritization, customer satisfaction or the product feedback loop, focus on fixing them the right way (and involving the right roles) instead of taking shortcuts.
- jahewson 4y agoWontfix: User error.
- justinjlynn 4y ago"Our product isn't right for your needs. What you need is (competitor's product). Here, I'll give their engineer a ring and let them know exactly what you need and why and get you the best price."
- lucasyvas 4y agoI've done many support calls, but I was always the last choice because I was extremely candid with the customer. When something was a bad bug, I'd say "Wow, that's bad. We'll try to fix it as soon as we can" Apparently that's frowned upon since the goal is to beat around the bush with "hmm.. that's not supposed to happen, so sorry" as a means to absolve us of as much accountability to the customer as possible. I have a philosophy that simply doesn't align with how most businesses want to run customer support, so while I wouldn't mind doing it, I am probably only making it worse in their mind.
- Areading314 4y agoI think theres a middle ground. There is clearly a lot of benefit for having the people building the app experiencing the pain of users using the app. I also think that exposure is a great learning opportunity for engineers. But for certain types of businesses/apps its not scalable to have engineers handle every support call.
- chrsig 4y agoThe middle ground that I use, as an engineer, is to review customer communication on support tickets that get escalated to my team. Not every day or every issue, or any other regimented basis. But I do try to stay close to raw customer feedback. It can be useful to see what details gets lost between the customer and layers of support before it gets to an engineer.
- qazpot 4y agoIIRC wordpress does this for new hires. Everyone spends their first few months in Customer support, which is a nice middle path to the extreme you are suggesting. This is also good for new hires as they get to a grounding on what matters (customer experience).
- a-dub 4y agomy first job ever did this. qa and customer support were combined which made it the best place to learn all the ins and outs of a very complicated product. after 3-6 months i had excellent knowledge of how the product actually functioned on the ground and how the customers approached it. highly recommended as a training scheme! especially in cases where engineers have a lot of influence on product design. (although, in a high volume ticket oriented environment, or a highly structured testing environment, the benefits fall off dramatically. the big value was setting things up from scratch in different contexts and seeing where people struggled)
- markx2 4y agoIt's Automattic, not wordpress. It is also not measured in months. Rotations into Support (for a week IIRC) once a year used to happen as it was deemed important, until the day it was no longer important and was stopped.
- bluedino 4y agoJohnson Controls (they make automotive interiors among other things), has every employee work on the production line for their first two weeks. Even the CEO.
- willsmith72 4y agoI came in ready to disagree with you... until I read the article. Engineers joining usability tests is a great thing. Engineers talking with PMs and joining early discovery is a great thing. But I would quit immediately if I were put on a customer support rotation. This seems idiotic.
- gopalv 4y ago> I would quit immediately if I were put on a customer support rotation Why? I sort of thought similarly about a decade ago, until I actually was on the end of a giant on-call tree almost permanently for 3 years. I wasn't the first person they'd call and not even the second, third or fourth. But eventually someone would call me and ask me to jump in & dig through it - I loved it, because eventually that's just a neat puzzle with an angry customer attached (if I could walk in someone else's shoes for a week, it would be rachelbythebay's). I also did primary on-call out of solidarity with the team. And 1 week out of every 20-odd wasn't hurting me as much as I thought it would, but the customer contact gave me enough weapons to argue with the PM teams when it came to "customers want 'faster horses', stop working on cars" arguments. I could actually see the product used and talk to the people who are struggling with it, better than the stage-managed customer advisory board they setup for each year's sales kick-off. Of course, there's a vastly different "competency rearrangement" disease which you might be referring to, which is spread through out the article. If engineering is good at doing things, they get things to do that have nothing to do with engineering - QE is slow, get engineering to fix QE process, product has bugs in prod at a customer, get an engineer to fix it reactively, customer conversations aren't closing fast enough, get a credible engineer to talk to their engineers, if product can't figure out what to build in what order, get an engineer into that conversation. Eventually, engineering is doing a lot of things half-competently and the company chugs along, dragging the other people who aren't failing hard enough to get fired because the engineers stop every buck passed to them.
- willsmith72 4y agoOk but I see that as something totally different. Of course I'm ok with being "on-call" (and do that for 1 week out of around every 8 right now), as a 3rd+ level support. But the impression I got from the article was something totally different. I'm more than happy to receive a request like "something weird happened with this user's account, can you look into the data/logs?", but not, "Hi, I can't log into my account, what should I do?". That is the customer support I got the impression of from the article
- trap_goes_hot 4y ago"One test is worth a thousand opinions" I worked at a SMB where everyone in the company had to perform some customer facing duties every month. No, we weren't terrible at it, and it helped all of us gain an appreciation of a different point of view. No customer was pissed off (in fact some were impressed when they realized they were talking to senior management), and while the company is no longer in business (for various other reasons) there was no noticeable harm caused by this.
- Beltalowda 4y agoI've done plenty of direct customer support as an engineer, and I think everyone won because of it. This was usually on some more difficult issues, or issues that involved an actual bug. Why bother going through a support person if I can just talk to the customer myself and explain the issue better, or ask the right questions straight away? Seems to me that's not a waste of time, but a time saver for everyone. Same with feature requests; a support person can fob a person off with "thank you for your feedback" and create an internal issue with no context, or I can talk to the customer myself, get a good idea of what problems they're running in to, and discus with them how to best fix it. Sometimes these are almost trivial fixes or changes, but a support person doesn't always realize that. In general keeping an eye on the support inbox gives me a better idea of how customers are using our service and what kind of things they're running in to. The amount of time/money spent on this is minimal, if it even exists at all, especially considering this is the sort of thing you can do a bit later in the day when you're not producing the sharpest code in the first place (I usually don't anyway). Even as a mostly backend engineer I've gotten a lot of value out of it, and I think our customers and the business overall have as well. That said, forcing developers who don't want to do this is probably a bad idea: they will do a shoddy half-job, be unhappy, and no one wins.
- ilyt 4y agoThat kinda depends on type of customer. If issue hitting you is actual problem with usability or how the system works, sure, direct contact with customer can solve that quickly and efficiently. Like, if your company is providing API to developer and you get contact with dev that have some errors using it, that can be very productive. But most of customer support is "they didn't read the docs/googled hard enough" type. It might be not for your field but that's what it is.
- Beltalowda 4y ago> But most of customer support is "they didn't read the docs/googled hard enough" type. It might be not for your field but that's what it is. Yes, and those weren't the type of support requests I would handle; although keeping an eye on the support inbox every few days to see patterns where customers are struggling with was still useful; sometimes it can just be fixed by changing the wording on a label, or adding a link to the documentation. Customer support isn't always good at communicating these issues to developers, and many PMs are more focused on the "big things" rather than little details like this, but ... they do make a product better and it costs very little effort. Similarly, if a customer started getting difficult/ranty I would just tell support to deal with it. I've had people go off on entire tangents about the Bush presidency and Iraq war (in ~2016-2017...) because of a minor inconvenience. I'm not going to deal with that kind of silliness. There are some very odd people in the world...
- mschuster91 4y agoThe problem is, as soon as you have multiple people involved in a communication chain, details get lost, and feedback loops become really extensive because of all the latency involved - and CSRs hate to be paper pushers. The worst case is in large organizations when bug reports to a vendor have to go through the company's purchasing department... because that's three transitions where information is delayed, misrepresented and lost: user => purchasing dept, purchasing dept => vendor CSR, vendor CSR => vendor developer. In the worst case, add another step for vendor developer => outsourcing company rep and outsourcing company rep => outsourcing company developer. Each communication step, unless it's a critical bug that warrants putting everyone in a shared call, adds anything from two to sixteen hours worth of latency, leading to feedback taking days or weeks. I have found to like the model of: 1. Customer contacts a project manager / support rep (depending on the organization - the former will be prevalent in the agency world, the latter in the classic SaaS/old-school software world), to inform them about a bug. 2. CSR/PM does an initial triage: can they reproduce the bug, is it an already known bug? If it is a valid and new bug, the known-to-that-point details get passed to a developer. 3. Developer contacts the customer for further information and direct troubleshooting, and involves other departments (ops, dba) as needed on their own 4. In case of higher effort bugs / feature requests, developer coordinates with PM for bureaucracy (creating tickets, test cases, ...) 5. Bug gets fixed, tested, and deployed 6. CSR/PM contacts customer and asks them for re-testing on their end.
- _jal 4y agoI find it kinda hilarious how many engineers here at a startup-focused message board are so quick to shout "not it!". I've done tons of direct customer support over my career. I still do sometimes, and I lead my department. (No, this is not a waste, it has a strategic use of my time to keep people happy.) The message I'm responding to doesn't point in this direction, but so many other comments make it clear it is a status thing for them, that they consider themselves above directly serving customers. All I can say to those people is don't leave your cushy HugeCo job for a real startup. You will have to humble yourself in far worse ways than asking, "how can I help you?"
- willsmith72 4y agoTo that, I would say I've done support on a startup and that's totally fine. The customers were familiar and came with real problems or questions, and often helped drive the direction of the product. That's completely different to doing a week of enterprise support for a large company on a product with millions of users. One is more like helping a product find its product-market fit, validating ideas, or even realising the company needs to pivot. The other is mindless, boring and in 99.99% of cases unproductive for the product.
- sb8244 4y agoYes, I came to reflect this sentiment. In startups there's a push for founder-led sales because it's the best way to learn from your target customers. It's the same for engineers. The quickest way to validate your assumptions, see where the rough edges are, identify an easy bug, etc. is directly from the customer. I found that doing it myself with a support rotation was the best way to do this. That said, it's not "throw engineers into the deep end". It was managed by support team to optimize my time and their benefit. We were able to mutually teach each other a ton.
- iwillbenice 4y ago> Imagine if the situation was flipped, and your CEO went "sales reps need to understand engineering complexity, so from now on they will each have to fix 10 bugs a month." Picking up the telephone and debugging areas of expertise YOU created or are already responsible for is much easier than making a sales guy into a pseudo-engineer. Also, paradoxically, some of the best product features I've come across literally started as a ghetto-coded-idea by a Technical Account Manager (sales engineer). Said features were later formalized and picked up officially by engineering, but the nexus of the product feature started with a non-dev. Sorry for the ramble/rant. My point is this: Don't get so married to job titles. It can be limiting in my humble opinion.
- P5fRxh5kUvp2th 4y agoIt only works if developers have the autonomy to make decisions on what to work on. It does no good to expose a developer to customer problems if they are unable to make the decision to fix it. At that point it's just wasted effort.
- freemrkt8 4y agoI think what you mean to say is not everyone can handle more than learning one functional set of skills. Which is sad and lazy thinking. If you can drive a car and program a machine you can handle two common “roles” in our economy. Clearly only being capable of one role is a joke. Me thinks this feels more like vanity and laziness; the engineer is not to slum it with the call-center rabble.
- Test0129 4y ago> Me thinks this feels more like vanity and laziness; the engineer is not to slum it with the call-center rabble. Lol. It’s not that I have a 10 hour day already. Nor is it because I have a specialized, very expensive skill set that is not properly utilized. Nor is it that I already do 3 different jobs. Nor is it that I am already on 12x5 pagerduty rotation. No, it is because I am filled with vanity and laziness. I don’t want to slum it with customer support. Lol. On the contrary this is just yet another MBA spreadsheet jockey trying to “get their moneys worth” out of developers. We already do much more than nearly every other job title in this industry. Every task that isn’t immediately obvious it goes to someone else ends up on a devs desk. Just stop. Or pay me an extra 80k to handle CSR. Your choice.
- freemrkt8 4y agoPoor developers keeping society afloat with no help whatsoever. Let’s give the food producers your benefits. They’re probably far more valuable to me than you will ever be. Why empower you with such economic agency then?
- Test0129 4y agoIf you want the actual answer society pays people commensurate to their individual value. NBA stars make millions because of the level of entertainment they provide, and the value they bring to sponsors. I make a lot of money because not everyone can do my job and I provide an outsized value to tech companies. Despite many attempts to drive developer wages into the ground with code camps and other non-sense apparently it's a difficult enough job not everyone can do it. For comparison, garbage men make a LOT of money (at least where I am) because their job isn't easy and no one wants to do it. No one wants to hear they're worth less than someone they perceive to be doing an "easier" job. Truth is, that's how society values people.