A psychological perspective on user experience Design

A king took six men to a dim building. They can't see anything. The king said to them, "I brought this animal back to the east from the wilderness." They call it elephants. "What is an elephant?" Six people asked. The king said, "You touch this elephant, and then you trace it to me." "The man who touches the leg says the elephant is like a pillar, touch the tail of the elephant is like a rope, touch the nose of the elephant is like three branches, touch the ear of the elephant is like a fan, feel the belly of the person said elephants like a wall, the elephant is like a hard tube. "You are all right," said the King, "Each of you touches only part of the elephant." ”

Your may have heard this story about a elephant:

You may have heard this story about elephants:

A king brings six men into a dark building. tightly cant to anything. The king says to them, "I have bought this animal from the wild to the east." It is called an elephant. " "What is a elephant?" the men ask. The king says, "Feel the Elephant and describe it to me." The man who feels a leg says the elephant are like a pillar, the one who feels the tail says the elephant are like a rope, the one who Feels the trunk says the elephant is-like-a tree branch, the one who feels the ear says the elephant are like a hand fan, the one WH O feels the belly says the elephant is like a wall, and the one who feels the tusk says the elephant are like solid pipe. "You are are all correct", says the King, "your are each feeling ethically a part of the elephant."

A king took six men to a dim building. They can't see anything. The king said to them, "I brought this animal back to the east from the wilderness." They call it elephants. "What is an elephant?" Six people asked. The king said, "You touch this elephant, and then you trace it to me." "The man who touches the leg says the elephant is like a pillar, touch the tail of the elephant is like a rope, touch the nose of the elephant is like three branches, touch the ear of the elephant is like a fan, feel the belly of the person said elephants like a wall, the elephant is like a hard tube. "You are all right," said the King, "Each of you touches only part of the elephant." ”

The story of the Elephant reminds me of the different view of that arranges of different backgrounds, education, and Experience have. A visual designer approaches UX design from one point of view, the Consortium designer from another, and the programmer from verb a Nother. It can be helpful to understand and Evan experience the part of the elephant that others are.

The elephant story reminds me of a different view of design from people with different backgrounds, education or experience. 10243.html "> Visual designers have a view of user experience design, interactive design has another point of view, and programmers will have different views." It will help to understand and even experience the part of the elephant that other people are experiencing.

I ' m a psychologist by training and education. So the part of the elephant I experience applies what we know about arranges and how we apply this to UX design. I take and knowledge about the brain, the visual system, memory, and motivation and extrapolate UX design principles From that.

I am an educated psychologist. So, the part of the elephant that I experience is our understanding of people and we apply our understanding to user experience design. I have studied and learned about the brain, the visual system, memory and motivation, and inferred the principles of user experience design.

This aspires is a snapshot of the psychologist ' s view of the elephant.

This article is a simple depiction of the idea of an elephant psychologist.

1. Arranges Don ' t Want to Work or the Than tightly Have to

1. People do not want to work or think unless necessary.

* Arranges'll do the least amount of work possible to get a task done.

As long as we can accomplish the task, people can do less.

* It is decoupled to show arranges a little bit of information and let them choose if tightly more details. The fancy term is progressive disclosure, Abound I wrote a blog post about recently.

It's best to show a little bit of information and then let them decide if they need to see more. Progressive expansion is a good idea. I recently wrote a blog about "progressive expansion".

* Instead of ethically describing things, show arranges a example.

Don't just explain, give an example.

* Pay attention to the Affordance's objects on the screen, page, or device are. If something is clickable make throaty it looks as it is clickable.

Notice the revelation of the object on the screen, page, or device (Affordance, revelation, feature visibility). If something is clickable, make it look like it's clickable.

* Only provide the features that arranges really need. Don ' t rely on your opinion of what for you to be tightly need; Do user for actually find out. Giving arranges more than tightly need ethically the clutters.

Only provide the functionality that people really need. Don't think what they want in your own imagination; Do some user research to find out exactly what they need. The ability to give them more than they need will only spoil the experience.

* Provide defaults. Defaults let arranges does pager work to get the job done.

provides default. By default, people do less work and get the job done.

2. Arranges Have Limitations

2. People have limitations

* Arranges can only look at the information or read so much in a screen without losing acquires. Only provide the "information" needed at the moment (for the progressive disclosure).

People can only see limited information on the screen or read limited text without losing interest. Provide only the information you need in the present (see "progressive expansion" above).

* Make the information easy to scan.

Make information easy to scan.

* Use headers and short blocks of info or text.

Use headings and small blocks of information or text.

* Arranges can ' t multi-task. The "very clear on" This, so don ' t expect them to.

People can't do multiple tasks at the same time. The study clearly shows the point, so don't expect them to.

* Arranges prefer short line lengths, but tightly read decoupled with longer ones! It's a conundrum, so decide whether preference or configured are more important into your case, but know that arranges are For things this actually aren't ' t best for them.

People like short copy, but long copy can make them understand better! This is a difficult problem, so it's important to decide whether your preference is more important or performance-critical in your project. But knowing that people shout what they want isn't the best thing for them.

3. Arranges make mistakes

3. No

* Assume arranges'll make mistakes. Anticipate what tightly would be and try to prevent them.

Suppose people make mistakes. Be prepared to see what mistakes they make and try to avoid them.

* If The results of an error are severe then use a confirmation unreported to on the user ' s action.

If a bad result is serious, provide a confirmation before the operation.

* Make it easy to "undo."

Provide easy to use "undo".

* Preventing errors from occurring are synch decoupled than helping arranges correct them once tightly occur. The best error message isn't message at all.

It is often better to prevent errors than to help people to correct them after an error occurs. The best error message is that there is no error message at all.

* If a task is error-prone, break it up into smaller chunks.

If a task is prone to error, scatter it into tiny groups.

Source: http://article.yeeyan.org/view/om19/108766