User Centered Design
From Wikipedia, the free encyclopedia
User-centered design (UCD) is a philosophy and a process. It is a philosophy that places the person (as opposed to the 'thing') at the center; it is a process that focuses on cognitive factors (such as perception, memory, learning, problem-solving, etc.) as they come into play during peoples' interactions with things. UCD seeks to answer questions about users and their tasks and goals, and then use the findings to drive development and design (Katz-Haas).
Contents |
[edit] Purpose
UCD answers questions about users and their tasks and goals, then use the findings to make decisions about development and design. UCD seeks to answer the following questions:
• Who are the users of the document?
• What are the users’ tasks and goals?
• What are the users’ experience levels with the document, and documnents like it?
• What functions do the users need from the document?
• What information might the users need, and in what form do they need it?
• How do users think the document should work?
(Katz-Haas)
[edit] Elements
[edit] Visibility
Visibility helps the user construct a mental model of the document. Models help the user predict the effect(s) of their actions while using the document. Important elements (such as those that aid navigation) should be emphatic. Users should be able to tell from a glance what they can and cannot do with the document.
[edit] Accessibility
Users should be able to find information quickly and easily throughout the document, whether it be long or short. Users should be offered various ways find information (such navigational elements, search functions, table of contents, clearly labeled sections, page numbers, color coding, etc). Navigational elements should be consistent with the genre of the document. ‘Chunking’ is a useful strategy that involves breaking information into small pieces that can be organized into some type meaningful order or hierarchy The ability to skim the document allows users to find their piece of information by scanning rather than reading. bold and italic words are often used.
[edit] Legibility
Text should be easy to read: Through analysis of the rhetorical situation the designer should be able to determine a usefulfont style. Ornamental fonts and text in all capital letters is hard to read, but italics and bolding can be helpful when used correctly. Large or small body text that is also hard to read. (9-11 pt sans serif and 11-12 pt serif is reccomended.) High figure-ground contrast between text and background increases legibility. Dark text against a light background is most legible.
[edit] Language
Depending on the rhetorical situation certain types of language are needed. Short sentences are helpful. Unless the situation calls for it don’t use jargon or technical terms. Many writer will choose to use active voice, verbs (instead of noun strings or nominals), and simple sentence structure.
(Katz-Haas)
[edit] Rhetorical Situation
A User Centered Design is focused around the rhetorical situation. The rehotircal situation shapes the design of a information medium. There are three elements to consider in a rehtorical situation: Audience, Purpose, Context.
[edit] Audience
The audience is the people who will be using the document. The designer must consider their ages, geographical location, ethnicity, gender, education, etc.
[edit] Purpose
The purpose is how the document will be used, and what the audience will be trying to accomplish while using the document. The purpose usually includes purchasing a product, selling ideas, performing a task, instruction, and all types of persuasion.
[edit] Context
The context is the circumstances surrounding the situation. The context often answers the question: What situation has prompted the need for this document? Context also includes any social or cultural issues that may surround the situation.
(Kostelnick)
[edit] References
User Centered Design and Web Development by Raïssa Katz-Haas: [1]
Designing Visual Language: Strategies for Professional Communicators by Charles Kostelnick, David D. Roberts and Sam Dragga
 |
This article is uncategorized. Please help improve this article by adding it to one or more categories, so it may be associated with related articles (how?). Please remove this tag after categorizing. This article has been tagged since December 2006. |
