4 ms·
If "almost everyone" fails some expectation, is the problem with the people or the expectation? The average user might not be super invested in the application
by crznp 6y ago
If "almost everyone" fails some expectation, is the problem with the people or the expectation?
The average user might not be super invested in the application, they just know that something doesn't work, which is frustrating. If their only outlet for that is a bug report, the developers get overwhelmed with bad bug reports and users get the expectation that the developer is going to fix all their problems for them.
If the outlet is a feedback form instead, maybe the user can feel listened to in a small way and move on. The developer doesn't have to sift through a bunch of issues, they can just follow up if there seem to be any hot-spots that are causing a lot of frustration.
- Arnavion 6y agoI don't see how replacing "sift through a bunch of issues" with "sift through a bunch of feedback forms" makes the developer's job any easier.
- smeej 6y agoThat's my point. Things have to be designed with the understanding that "people who won't read the instructions" are the rule, not the exception. That has to be the expectation if anything is ever going to improve. Unless you know you're dealing with a very specific subset of the general population who loves reading, design around things that don't need to be read.
- kelnos 6y agoExactly; the problem here is that there's a repository that allows issues to be filed, when the owners don't want issues reported there. Issues should just be turned off on that repository (and if you can't do that, I'd consider that a big missing feature). You need to guide people to do the right thing based on the interface itself; people overwhelmingly don't read instructions.