I’m actively saying that when most people hear a little noise under the hood they do one of two things: ignore it or take the car to a mechanic and use a different transport method for a bit until it’s fixed.
I’m saying that if somebody casually mentions “my car does a little noise” over the watercooler and the other person goes “hey, have you popped the hood and checked the spark gap” or “can you pull up the on board diagnostics and maybe we can go over them now?” the usual reaction is to make up some excuse or get glassy eyed and move on with your day.
That is absolutely how that goes.
And no, it’s not optimal or even particularly reasonable, but that’s the thing, it doesn’t have to be. When the average person engages with a market product for fun or casual usage they are often willing to invest zero effort in improving it from the out of the box experience, at least early on. And that’s their prerogative. That low barrier to attrition is a key element of UX design, and it absolutely applies to technical issues.
So what you’re saying is, when you say “oh I’m having performance issues in Firefox”, you think it would be better for everyone to just ignore you, than for people to try and help you?
Or, you know, add some polite commentary, chime in with whether that matches your experience or not. That sort of phatic engagement stuff, if one really must chime in.
I mean, you always expect some level of “have you tried this”. Hell, I didn’t even begrudge the nod to the built-in profiler. That was a fair point.
By the time you get to “look at the extensions you don’t recognize, you may have accidentally installed a cryptominer” you may be overdoing it, though. Unless I’m your grandma or you’re actively manning a customer service call center.
Yeah, no, I’m actively saying just that.
I’m actively saying that when most people hear a little noise under the hood they do one of two things: ignore it or take the car to a mechanic and use a different transport method for a bit until it’s fixed.
I’m saying that if somebody casually mentions “my car does a little noise” over the watercooler and the other person goes “hey, have you popped the hood and checked the spark gap” or “can you pull up the on board diagnostics and maybe we can go over them now?” the usual reaction is to make up some excuse or get glassy eyed and move on with your day.
That is absolutely how that goes.
And no, it’s not optimal or even particularly reasonable, but that’s the thing, it doesn’t have to be. When the average person engages with a market product for fun or casual usage they are often willing to invest zero effort in improving it from the out of the box experience, at least early on. And that’s their prerogative. That low barrier to attrition is a key element of UX design, and it absolutely applies to technical issues.
So what you’re saying is, when you say “oh I’m having performance issues in Firefox”, you think it would be better for everyone to just ignore you, than for people to try and help you?
Given that I didn’t ask for any help, yeah.
Or, you know, add some polite commentary, chime in with whether that matches your experience or not. That sort of phatic engagement stuff, if one really must chime in.
I mean, you always expect some level of “have you tried this”. Hell, I didn’t even begrudge the nod to the built-in profiler. That was a fair point.
By the time you get to “look at the extensions you don’t recognize, you may have accidentally installed a cryptominer” you may be overdoing it, though. Unless I’m your grandma or you’re actively manning a customer service call center.