Wednesday, April 9, 2008

Usability Guidelines Ch.1

Design Process and Evaluation

The best way to get started designing a website is for many different people to propose design solutions.  This is called parallel design.  Then you should always follow up with usability testing of users to work out any problems with the site.

This chapter discusses 11 steps to get a successful website.

1. Provide Useful Content
- engaging, relevant and appropriate information for your target audience.
- content is most important aspect of the site, more so than navigation and visual design, according to studies.

2. Establish User Requirements
- customer support lines, surveys, interviews, bulletin boards.
- need more communication between users and developers.
- 4 or 5 different sources is a good start.

3.  Understand and Meet User's Expectations
-users utilize past experience and knowledge to gage expectations.
-use familiar navigation schemes and formatting to make it easier for them.

4.  Involve Users in Establishing User Requirements
- users are most valuable in helping designers know what a system should do, not helping determine the way to have the system do it.

5.  Set and State Goals
- set goals of site BEFORE the design process begins.
- determine function, content, audience, and a unique look and feel.

6.  Focus on Performance before Preference
- make decisions about navigation, content, format, and interaction before choosing colors and graphics.

7.  User Interface Issues
- user level of experience
- computer and connection to Internet
- types of tasks

8.  Be Easily Found in the Top 30
-you need appropriate meta-content and page titles, the number of links to the site and updated registration with search engines.

9.  Set Usability Goals
- how fast will users find the specific info.
- testing will be more effective this way.

10.  Use Parallel Design
- several designers propose ideas and use best elements from each design.
- propose solutions

11.  Use Personas
- keeps design team focused on same types of users.
- definition: hypothetical "stand-ins" for actual users that drive the decision making for interfaces.  They represent real people.
- typical to use 3 to 5 personas. Include name, age, photo, work and computer proficiency.

No comments: