Whenever you go to a restaurant, every staff member that you meet has an impact on the product, in this case your dining experience. From the hostess that smiles as you enter the door to the chef that checks on your food personally, the team shows the quality of the product.
Carolyn had a wonderful perspective on this a few episodes ago. She said, “Your support team is a measure of the quality of the product.” On this episode, we talk about what this means and how effective it is as a reference point.
It’s the long awaited part two of last week’s episode! And by long awaited, we mean a week. But that’s long enough, right?
Your support team interacts with customers more than anyone else in your company. When you know exactly what the customers want, how do you present a case for that to your development team?
Getting a seat at the proverbial table is tough. Lots of companies (hopefully not your’s though) see customer support as just another expense. A cost center. One more thing to minimize at all costs.
But we know you’re more than that. That’s why this week we’re looking at growing your team’s influence and convincing other teams to listen!
There’s a pipeline that runs from your support team over to your product team. Through it flows ideas, pain points, and a wealth of knowledge from your customers. But how do we prioritize that versus feature work, and how can support influence that?