Earlier quoted context omitted.
I agree. Things for some people, they don't work for others. But you cannot blame users and say "oh its how you configured it" "its good out of the box" etc. If its failed for 1 user, its a shit product. If its a success for 1 user, it's a great product. It's GOOD for a user to say they find it easy and why. It's GOOD for a user to say they find it hard and why. 1 helps the user give a product a second chance by lear…
> If its failed for 1 user, its a shit product. That is a dangerous over-generalization. Let's say -ferinstance- you have kick-ass , seriously best-at-what-it-does software that's only localized in Japanese, and a uniglot USian attempts to use it. They're gonna have a hard time. The software will very likely fail them, because they will be unable to understand anything they're being told by the software. Does that ma…
From the perspective of the user, if the product fails for that user, its a shit product.
I don't mean the product itself is actually shit.
Like I say:
If its works well for a user. It's a great product. If its fails for a user. It's a shit product.
From the perspective of that user.
But we can learn from both the users who like it, and the users who hate it. But we cannot blame the problems the user has, solely on the user.