User Experience/Myths about UX

From Apache OpenOffice Wiki
Jump to: navigation, search


Quick Navigation




About this page

We heard many things about UX, some are true and some are ... questionable. So this page is intended to clarify some of the often made misconceptions. And if you know more, then please add them - or just contact the User Experience Team at ux-discuss and ask if they're true ;-) Thanks!

General Myths about User Experience

Advanced functionality doesn't hurt - newcomers just won't use it!

Myth: Sometimes features seem to be designed for advanced users or to cover each usecase one can think of. If normal people don't need this advanced functionality, they just won't use it and so it doesn't hurt, does it?

Answer: Yes it does hurt! Each piece of functionality added to a system requires interaction - menu space, buttons, keybindings, advanced settings. This will automatically lead to an increased overall complexity that frightens or overwhelmes users. So if you are in doubt if a feature makes sense for many people, then better omit and just serve their needs - you keep the complexity limited and people will be happy anyway!

UX designs the buttons, did you anytime see different outcome?

Myth: If you ask UX, you get a nice dialog layout and that's it. So what is it all about?

Answer: Yes, the result of the User Experience work are GUIs, because it's the communication interface between the user and But it is not about plain buttons, interaction does also have time component, questions the sense of features, respects the target user's abilities and learning capabilities. Thus, it requires a deep understanding about both the use of the software and the user. All those carefully made decisions end up in the final GUI we propose. just needs to borrow the feature ideas from other products - and everything will work fine!

Myth: Many people assume that it is just as easy as copying a strong-desired feature from other software products to just make people happy!

Answer: Yes this works. But only if you have the same kind of problems to solve with that feature, and the original software behaves exactly like, and the users of both software applications do have exact the same needs and expectations. If anything will be slightly different - and it will - don't just copy features and their behavior. You will never know if you copy mistakes. You will never know if it fits into the overall interaction concept of It just makes it harder for people to learn and to explore such new features (working steps, dialogs, keybindings) - although it was meant well, of course!

Personal tools