cross-posted from: https://lemmy.world/post/41155139
cross-posted from: https://lemmy.world/post/41155034
cross-posted from: https://lemmy.bestiver.se/post/841355
cross-posted from: https://lemmy.world/post/41155139
cross-posted from: https://lemmy.world/post/41155034
cross-posted from: https://lemmy.bestiver.se/post/841355
I tend to agree with that one. I’ve heard it phrased “Don’t ask users what they want. They don’t know. Just give them something to work off of, because they most definitely know what they don’t want”.
But there’s a catch that I’ve seen twice now: If a feature doesn’t work correctly when you present it, users lose trust and avoid it. That could mean they use the ‘long way around’ when creating entities instead of just copy/pasting them, or that they unnecessarily refresh web pages instead of trusting the state that’s displayed to them.
Even when you tell them that their behaviour is … not optimal, they stick to it.
Don’t give users an ugly prototype for exactly that reason. Also, users conflate looks and functionality so make it don’t look ugly. You should give them an MVP. Emphasis on the V for “viable”. The things it does it should do well. It should just do the minimum amount of things.