3 ms·
This is an important lesson and a post I'm glad frequents the front page, because the lesson is far from learned. Here's another one. The customer is always ri
by godelski 3y ago
This is an important lesson and a post I'm glad frequents the front page, because the lesson is far from learned.
Here's another one. The customer is always right __in matters of taste__. Users will often try to be helpful and make suggestions about how problems may be solved. This suggestion will often be bad. But remember that the system is more opaque to them so they may not see all the complexity that exists. BUT this does not mean that their issue is bad. If the user has an issue, the user has an issue and someone reporting is not just one. They're just the one to report. You can throw away the bad suggested solution and still address the issue. Read the suggestion instead as additional context in to understand what the user really is looking for, i.e. taste. Never respond with "rtfm" and instead with "here's a link to the specific section in our documentation with an explanation." Far too many developers think that simply because documentation exists that it is clear and understandable. Far too many times have I made a report, referenced the documentation, and gotten back "well you just need to <do complicated task> just rtfm." Even in instances where I've demonstrated a solution but am reporting unexpected behavior. Too many times I've gotten "well that's actually x's problem, not ours" and the cycle. If users are using your software, it's your problem and you must communicate upstream, not the user. This is why I do not contribute as much anymore. It's just too exhausting and I'm not alone.
And let's not rely on internal communities for reporting cough signal cough. I see these everywhere, places like Signal, Spotify, Microsoft, etc. If you got a github, leave it open and respond to it. I love Signal but the community forums are an absolute shithole of people who understand neither privacy or security. They are worse than the arch forums. Most internal communities, volunteer moderated, are destined for this unbearable quality. You're just creating a breeding ground for toxicity, not creating a centralized location for bug tracking and community engagement. You got to go wherever your customers are. If they keep trying to report on github you accept that that's where they come through, not send them down another channel where they must make another account. You're just hiding bugs that way and making your product worse.