4 ms·

I also know a "support guy" who absolutely kicks ass. Probably a better dev than most of us regular product engineers. Makes me think support is actually way ha

I also know a "support guy" who absolutely kicks ass. Probably a better dev than most of us regular product engineers. Makes me think support is actually way harder than the actual app dev. I also wonder if the incentives are a little bad with this setup. Product devs' crappy code turn into tricky puzzles for our support team. Legend has it, RAD Game Tools used to have just 1-2 devs on each tool, and you'd do the support for your tool. Feels like this would pretty strongly encourage you to make your stuff good. And you'd have everything in your head too. I wish I knew of more similar setups in the web world.

FiatLuxDave 2y ago
I agree about how aligning the incentives can make a huge difference. The first product I was ever a product manager (and SME) for, I assisted the support team with escalations. This meant that every weird new bug or strange situation would hit me the same day. This really shortened the feedback loop on getting stuff fixed. It also made it so that I became aware of quirks or things that weren't working quite right from the customer's perspective, which is gold for a PM. That information I learned doing support escalations helped in the design of version 2 of the product, which is still in production 22 years later. I strongly recommend having the PM be the highest point of escalation in the support chain. It really incentives them to make a quality product.