4 ms·

The problem with that is that you are having engineers who cost the company $75+ an hour spending time doing the job that can be done by someone costing ~$30 an

• terpua 16y ago
  It has to be part of your culture (ie when hiring). As for the cost, it pays back in understanding your customer better and getting engineers working on the right things. I have been part of too many engineering teams working on the wrong things because of a lack of customer interface.
  • markkanof 16y ago
    As long as the developers really have the ability to make changes based on the support requests they are receiving. I've been in the situation where each developer would take a day of the week handling support. But the support requests could be for any of the software built by the entire development team, not just the things that the individual developer worked on. So then in many cases the developer was acting as an extremely expensive email/call filter. And the only lesson being learned was that some of the other developers weren't very good at their jobs.
• samaparicio 16y ago
  The cost of prioritizing the wrong things and ignoring what's important to your customers far outweighs the higher cost of engineers. Also, consider that engineers can fix problems faster.
  • studer 16y ago
    Except that "what's important to your customers" isn't necessarily "what's important to the last caller, or the angriest one". That model doesn't really scale beyond a certain number of customers...