Posts Tagged ‘definitions’

What is UX Design?

January 12, 2009

UX design = combining three types of activities
Designing a “user experience,” therefore, represents the conscious act of:

• coordinating interactions that are controllable (choosing food ingredients, training waiters, designing and programming buttons)

• acknowledging interactions that are beyond our control (uncomfortable seats in a 100-year-old theater, lack of fresh produce in winter, low-hanging clouds that hide a sunset.)

• reducing negative interactions (providing tents as emergency shelters at outdoor events in case of rain; making sure restaurant seating next to the noisy kitchen door is the last to be filled, putting in an extra intermission so folks can stretch their legs).

A good user-experience designer needs to be able to see both the forest and the trees. That means user experience has implications that go far beyond usability, visual design, and physical affordances. As UX designers, we orchestrate a complex series of interactions.

From: Eric REISS: A definition of ‘user experience’

Click Investment

January 5, 2009

‘Click Investment’ is the amount of clicks a user has to do in order to get what s/he wants (return of investment)

Wireframe

June 13, 2008

“A wireframe is a simplified view of what content will appear on each screen of teh final product, usually devoid of colour, typographical styles, and images. Also known as schematics, blueprints, prototypes.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p.265

Flow charts (vs. site map)

June 13, 2008

“Flow charts attempt to visualize a process, usually centered around a specific task or function, For web-based processes, flow charts often represent a series of screens that collect and display infromation to the users. Also known as flows, user flows, process charts.”

“What seperates a flow from a site map is that in the former, time is the defining factor. The relationships between the steps are sequential, not structural or hierarchichal . While site maps capture an information structure that may or may not match the user’s experience of the site, a flow chart defines a process from beginning to end.

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p. 229

Content audit and content inventory

June 13, 2008

“Content inventory is a list of all the information contained in a web site, along with data that describes the information from several points of view, like target audience or location. Also known as a content analysis or content audit (…)

The main distinction between these two documents [content inventory and content audit] is the level of granularity. In essence, the distinction is how much of the site you describe. With an inventory, the intent is to capture and describe every piece of content on the site. A content audit captures and describes less, focussing perhaps on the main content areas of the site or the top two levels of navigation after the home page. An audit establishes a boundary around the scope of the investigation.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p.167

Concept model

June 13, 2008

“A concept model is a diagram that shows the relationships between different abstract concepts. You can apply the concept modeling technique in a variety of circumstances to explain different aspects of a website. Also known as concept maps or affinity diagrams.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p.137

Personas

June 13, 2008

“A summary representation of the system’s intended users, often described as real people. Any project can have one or more personas, each representing a different kind of audience for the system. Also known as: user profiles, user role definitions, audience profiles.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p.15

Orphaned pages

June 12, 2008

“[Orphaned pages are] pages that can only be accessed by direct links from another page but that do not have a home in the site hierarchy.” (eg. disclaimer)

From: Reiss, E.L. (2000), Practical Information Architecture, Harlow: Pearson Education, p. 127

Pogo sticking

June 12, 2008

“Whatever you do, don’t cut something up into tiny pieces or force visitors to perform a lot of back and forth navigation. Navigation designers call this phenomenon ‘pogo-sticking’.”

From: Reiss, E.L. (2000), Practical Information Architecture, Harlow: Pearson Education, p. 117

Scent

June 12, 2008

“In information architecture terms, ‘scent’ refers to the hints a visitor gets from the words and types of words used to label particular subjects.”

From: Reiss, E.L. (2000), Practical Information Architecture, Harlow: Pearson Education, p. 107