It was something I noticed getting it wrong several times the last week and thus worth a mention. Especially since my lack of experience with Discourse. Experienced users won’t complain about little quirks because they have come to terms with those and won’t even notice it anymore. UX testing is also done on people with little prior knowledge, so to gauge the difficulties of new users. When it comes to UX, suggesting to learn how to use a product is something you generally try to avoid.
That all is not to say I’m right and you’re wrong. I might be 1 out of a 1000 who has this issue. If that is the case, good job on getting the “you” menu right! That is what research is for.
I believe that is a no on the A/B testing?
Complaints about the article
While the article does have some valid points. There is something as overdoing it. To much of anything is bad for you. For example, we hear everywhere people need to drink more water. But when thrown into an sea of (drinkable) water, they will still drown. I think there is a place for A/B testing. Going with the Groundhog Day reference; knowing whether she likes red or white wine wouldn’t be a bad thing. But knowing which specific wine she likes would be overdoing it.
And I could give some other arguments against the Groundhog Day references. The main one being, Groundhog Day is a one-way communication (Rita doesn’t know of any previous interactions). While in a real relationship, buying flowers you know are the wrong ones would worsen the relationship.
I guess, also a no on the UX research team?