If you have been following this blog for a while, you might have noticed that I haven’t been posting as many links as I used to. There are two reasons for that.
The way we talk about things can limit how we think. We will design better if we talk about what people use our designs for, rather than the device they use them on.
I feel the need to jump into the discussion about Facebook’s proposed “dislike” button. The wisdom of the crowd is probably wrong on this one.
People hate it when a loud video slaps you in the face without pressing play. For that reason, many people will tell you that autoplay is bad UX. But is it?
This is it: the final question. And it’s a doozy. With all the talk of A/B tests in the UX community, it’s funny that you never hear about their more sophisticated cousin very often. So today we answer:
“What the hell is a multivariate test?”
Second last question! Another one about A/B testing, and you might be surprised how much I hear this one in real life.
Today we will answer:
“What if my favorite design doesn’t win the A/B test?”
In the business world — which is where UX lives, mostly — everything has a cost. UX is no different. So when you start telling your clients or bosses that they should do A/B testing, they might ask:
“How much does an A/B test cost?”
A/B testing is one of those seemingly simple things that is only simple when you know how it works and what it is good for.
So today we will answer:
“What should I A/B test?”
