To the front pageThe Interaction Designer's Coffee Break - Weekly postings and quarterly articles about interaction design  
  To the front pageSign inTo the frontpageSearch in GUUUI postingsAbout GUUUI  
   
 

BROWSE GUUUI POSTINGS

 

41

Stanford Guidelines for Web Credibility

Stanford Persuasive Technology Lab has compiled 10 guidelines for building the credibility of a web site.

1. Make it easy to verify the accuracy of the information on your site.
2. Show that there's a real organization behind your site
3. Highlight the expertise in your organization and in the content and services you provide
4. Show that honest and trustworthy people stand behind your site
5. Make it easy to contact you
6. Design your site so it looks professional
7. Make your site easy to use - and useful
8. Update your site's content often
9. Use restraint with any promotional content
10. Avoid errors of all types

On their site you'll find more details and supporting research.

Links:

  • The Stanford Guidelines for Web Credibility

Henrik Olsen - March 02, 2003

Permanent link Comments (0)

See also: Credibility, Trust and Privacy (6) 


 

42

Investor Relations Website Design

NN/g has tested 42 users performing investment-oriented task on 20 company websites. Some of the results showed that:

- 70% of the users completed the tasks
- 35% of the users couldn't get a copy of the company's latest quarterly report
- 77% couldn't find the high/low share prices for an earlier quarter

Jakob Nielsen concludes that:

- Individual investors are intimidated by overly complex IR sections and need simple summaries of financial data.
- Professional investors are using other sources of financial information and just want management's visions about the company's future
- Both individual and professional investors want company background information and overview of recent news

If you can afford it, NN/g offer a 121 pages report with 65 design guidelines for improving IR usability ($248).

Links:

  • The article Investor Relations Website Design

Henrik Olsen - February 18, 2003 - via Jakob Nielsen's Alertbox

Permanent link Comments (0)

See also: Research (93)  Sections (5) 


 

43

How to design print-friendly pages

In the article, Printing the Web, James Kalbach provides 10 guidelines on how to design print-friendly pages:

1. Remove navigation
2. Remove or change graphical ads
3. Use relative page widths
4. Use serif fonts
5. Add citation information
6. Remove dark backgrounds
7. Write out URLs
8. Display the print-friendly version before printing
9. Collate all information (e.g. parts of an article) into the final print version
10. Ensure that colour coding isn't required to understand content

In the article you'll also find advice on where to learn how use style sheets (CSS) and XSL to control printing formats.

Links:

  • The article Printing the Web

Henrik Olsen - February 09, 2003

Permanent link Comments (0)

See also: Web page design (23) 


 

44

User-Centered URL Design

Jesse James Garrett looks at the readability of URLs and some techniques to improve human guess-ability.

Links:

  • The Essay
  • Jesse's IA resources

ben hyde - January 27, 2003

Permanent link Comments (0)

See also: URLs (3) 


 

45

56 Rules to Design By

Bob Bailey's December newsletter should be required reading by all. It consists of 56 design guidelines, all backed by quality research, with references!

Links:

  • Dec'02 UI Design Update Newsletter

Ron Zeno - January 07, 2003

Permanent link Comments (0)

See also: Guidelines and Standards (10) 


 

46

Palm OSŪ User Interface Guidelines

This online book describes how to design applications for Palm Powered(TM) handhelds so that they conform to Palm, Inc's user interface guidelines. Read and use it if you are an interaction designer, application designer, or a developer and you are considering creating applications that run on Palm OSŪ.

It is well know that the Palm OSŪ UI Guidelines are established through extensive fieldwork, and therefor some of these insights may provide you solutions and concepts that resolve typical problems in designing web sites and webbased applications that run on PDA's in general.

Links:

  • Table of Contents

Pieter-Jan Pruuost - December 06, 2002

Permanent link Comments (3)

See also: Online books (5)  Guidelines and Standards (10) 


 

47

14 Principles of Polite Apps

Human react to computers in the same way they react to other humans. If we want users to like our interactive designs, we should create them to behave like likeable persons. They should be polite and humble servants to us.

Alan Cooper has listed 14 principles to create accommodating designs. Some of his requirements for the polite system are:
- Be interested in me, recognize me, and know who I am and what I like
- Be deferential to me
- Keep me informed about what's going on but don't bother me with your personal problems
- Be self-confident - don't not pass responsibility off onto me
- Do not force choices on to me
- Don't be stubborn, be flexible
- Give instant gratification
- Be trustworthy and dependable

Cooper claims that polite designs are no harder to build than impolite ones. I don't agree with that. It takes effort to be polite and accommodating – just like in real life.

Links:

  • The article 14 Principles of Polite Apps

Henrik Olsen - November 20, 2002 - via iaslash

Permanent link Comments (0)

See also: Guidelines and Standards (10) 


 

48

How to create the best user experiences with Macromedia Flash

Flash is a very powerful tool, but is of no added value if the designer does not master the tool or the medium. Macromedia has the Usability Guidelines you've been looking for. Designed for the 21st Century Flash Designer q;)

Links:

  • Macromedia's Flash Usability Guidelines, Tips & Tricks, Examples, Cases, and Whitepapers

Pieter-Jan Pruuost - October 17, 2002

Permanent link Comments (0)

See also: Flash (6) 


 

49

NN/g report on e-commerce search

NN/g has observed 64 US and Danish users attempting 344 search tasks on 20 US e-commerce sites. The users had a success rate of only 64% in finding what they wanted. The report offers 29 design guidelines. Some highlights:

- Provide a clearly visible search box on every page
- Provide a simple search, with one search box and one search button
- Accept synonyms, spelling errors and variant forms of keywords typically used by customers
- Accommodate multiple-word input
- Always include search criteria, scope and items found in search results page
- Beware of long search result lists, as only few users look past page 2 of search results
- Take the users directly to the item when a search returns only one matching result
- On the "No results" page, make it clear why the search failed, allow the user to begin a new search, and provide alternative ways of locating products
- Support search for non-product terms

Links:

  • The 51 pages report Search ($49)

Henrik Olsen - October 09, 2002

Permanent link Comments (0)

See also: Search (24) 


 

50

Should we abandon usability guidelines?

In the article "Evolution Trumps Usability Guidelines", Jared M. Spool calls web usability guidelines into question.

In his opinion we can't assume that following guidelines will result in more usable sites if they haven't been tested properly in various contexts. Following such guidelines can even harm the usability of a site:

"This means that following untested guidelines is like drinking water from an unidentified source. It might quench your thirst, but it could also make you very ill."

The problem with guidelines is an old one in interface design and has been discussed intensively in the literature. Some of the most important conclusions here is, that usability guidelines has proven very useful, but they should be used with caution:

- Never use a guideline without considering its relevance in the context it will be applied to
- Never base your design choices solely on guidelines - use other methods to verify its usefulness
- Study how users interact with you designs

Links:

  • The article Evolution Trumps Usability Guidelines
  • Lyle Kantrovich's comment to the article

Henrik Olsen - October 01, 2002

Permanent link Comments (1)

See also: Guidelines and Standards (10) 


<< Back More >>

Browse GUUUI postings

Methods and the design process

Usability testing (30)  Prototyping and wireframing (32)  Cost-justification and ROI (19)  The design process (14)  Personas (13)  Requirement Analysis (12)  Card sorting (8)  Implementing user-centred design (7)  Expert reviews (6)  Web log analysis (7)  Eye-tracking (7)  Site and flow diagramming (4)  Use Cases (3) 

Design elements

Navigation (46)  Web page design (23)  Search (24)  Guidelines and Standards (10)  Links (12)  Text (13)  Forms (11)  Ads (6)  Site design (8)  Shopping Charts (5)  Error handling (5)  Sections (5)  Home pages (2)  Design patterns (4)  E-mails (1)  Personalization (1)  Sitemaps (1)  Print-freindly (1)  Help (2) 

General aspects

E-commerce (21)  Accessibility (11)  Information architecture (12)  Persuasive design (13)  Visual design (14)  Search engines (7)  Credibility, Trust and Privacy (6)  Web applications (2)  Intranets (1) 

Technology

Flash (6)  URLs (3)  Download time (2)  Javascript (3)  Web standards (2)  Browsers (2) 

Humor

Cartoons (8)  Funny tools and games (10)  Bad designs (7)  Fun with Jakob Nielsen (6)  Designs with humor (3)  Fun music and videos (4)  Fun posters (2)  Funny 404 pages (2)  Misc humor (3) 

Ressource types

Research (93)  Tips and guidelines (65)  Tools (51)  Books (32)  Cases and Examples (12)  Interviews (10)  Primers (9)  GUUUI articles (8)  Posters (5)  Online books (5)  Glossaries (2)  People and organisations (2) 

Information sources

Blogs (11)  Websites (9)  Discussion lists (4)  News (3)  Newsletters (3)  Online magazines (3)  Wikis (1) 

 

 
     
  To the front pageSign inTo the frontpageSearch in GUUUI postingsAbout GUUUI