Getting Real on Customer Support. Volume 1.
Published May 21st, 2007 in Software, AttitudeI’m starting a series of articles inspired by Getting Real book by 37signals. Chapter 14 of this book tells about customer support in software development. And guys from 37signals (creators of Basecamp and Ruby on Rails) have some good points worth sharing.
In the restaurant business, there’s a world of difference between those working in the kitchen and those out front who deal with customers. It’s important for both sides to understand and empathize with the other. That’s why cooking schools and restaurants will often have chefs work out front as waiters so the kitchen staff can interact with customers and see what it’s actually like on the front lines.
A lot of software developers have a similar split. Designers and programmers work in the “kitchen” while support handles the customers. Unfortunately, that means the software chefs never get to hear what customers are actually saying. That’s problematic because listening to customers is the best way to get in tune with your product’s strengths and weaknesses.
The solution? Avoid building walls between your customers and the development/design team. Don’t outsource customer support to a call center or third party. Do it yourself. You, and your whole team, should know what your customers are saying. When your customers are annoyed, you need to know about it. You need to hear their complaints. You need to get annoyed too.
(c) Getting Real. Chapter 14.
Spread the Word: del.icio.us Digg Furl Reddit Technorati
3 Responses to “Getting Real on Customer Support. Volume 1.”
Please Wait
Leave a Reply