Hacker News new | ask | show | jobs
by newt 5635 days ago
I watched a presentation online by a large software company who used to to do this. They deprecated this as "prioritization by whoever shouts the loudest". Once a crash-bug-reporting system was in place it simply went away, as they had accurate enough data on how many people were affected, and could prioritize based on that. This won't help if it's not a crash bug, but the criticism of "prioritization by whoever shouts the loudest" is still valid.
1 comments

"prioritization by whoever shouts the loudest"

...I'm actually not getting why this is a bad thing. The people shouting on your crash-bug-reporting system are unhappy enough to go out and yell at you rather than simply grumbling to themselves and continuing to use your program. Doesn't it make sense customer-service-wise to appease those folks who are going to yell about the bugs in your program and negatively influence peoples' opinions?

The mapping between degree of discontent and aggressiveness is different for different people.

Because of that, listening better to those shouting harder reinforces the notion that "the assholes get what they want".