Structure Principle

STRUCTURE.

In my blog post, Principles of User Interface Design, we touched on various aspects of user interfaces. This feature will discuss few specific points of one of the aspects - Structure - followed by few examples.

Why do you need your site to be structured?

Well, you need your customers/prospects to understand quickly what need of theirs will your product/service fulfill. It is important for the visitors to find relevant information quickly, and get easy access to additional information if necessary. Your public domain, which is the place for introducing all that you do, can and will change in the future. Having a good and expandable structure would make this job easy and seamless. Having a good structure (which also means not random, but structured set of keywords) will also make the site findable on search engines. The customer also needs to have alternate paths to key areas and information on the site for better decision-making.

How can you achieve structure in your web site?

Main idea is to establish the information architecture for site content areas in providing clear, visitor-specific paths to useful and relevant information.

• Internal site linking structure - have logical grouping/linking between main navigational elements (either left or top) and secondary/direct navigation (right, center, or bottom).


• Linking between sections - have good cross-linkages and quick jumps to important sections of your site (for example: customer stories, case studies, thought-leadership blogs).


• Page-specific navigation - it is not a bad idea to design page-specific navigation and access to information. In fact, each page has to serve a specific purpose and it's a mistake to have all pages behave the same in a large site. For example, "About us" section needs to be very different than a section about "Products/Services" not just in presentation and writing style, but also in flow.


• Keywords as sections - site visitors will feel at home with the structure of the site, if we make user keywords as section names.


• Site Exits - design specific click-to-action elements for a logical exit from your site. For example: Inquiry Forms, Downloads, Feedback, Sign-ups, Share/Like.

Few examples of sites with good structure:

• mozilla


• vector consulting


• protolize


• sumagency


• greenpepper


• bearskinrug


• bbc


• usa gov


• abebooks


• rotten tomatoes

Structure it now; structure it well.

Stay with us for more features on other principles with more examples.

Principles of User Interface

This article simply lists down in brief the few principles that need to be adhered to and kept in mind, while creating or analyzing user interfaces. Following this, we'll take a look at few examples for each points in question, as series of features.

Principles

• structure
  
  
  
  • organize user interface purposefully
  
  
  • make it meaningful and useful based on clear, consistent models apparent and recognizable to users
  
  
  • put related things together; separate unrelated things
  
  
  • differentiate dissimilar things, make similar things resemble one another
  
  
  
  


• simplicity
  
  
  
  • make simple, common tasks simple to do
  
  
  • communicate clearly and simply in user's own language
  
  
  • provide good shortcuts that are meaningfully related to longer procedures
  
  
  
  


• visibility
  
  
  
  • keep all needed options and materials for a given task visible
  
  
  • do not distract user with extraneous and redundant information
  
  
  • do not confuse user with too many alternatives for performing same task
  
  
  
  


• feedback
  
  
  
  • inform actions or interpretations
  
  
  • inform changes of state or condition
  
  
  • inform errors or exceptions
  
  
  • keep model of communication - relevant, clear, concise, and in language familiar to user
  
  
  
  


• tolerance
  
  
  
  • reduce cost of mistakes and misuse by allowing 'undo' and 'redo'
  
  
  • prevent errors by tolerating varied inputs and sequences and by interpreting reasonable actions
  
  
  
  


• reuse
  
  
  
  • reuse internal and external components and behaviors; maintaining consistency with purpose
  
  
  • reduce the need for users to rethink and remember
  
  
  
  

Watch this space for some concrete examples...

Principles of User Interface Design

from the theory of Larry Constantine and Lucy Lockwood in their usage-centered design, the principles are:

Structure Principle

• organize the user interface purposefully


• make it meaningful and useful based on clear, consistent models apparent and recognizable to users


• put related things together; separate unrelated things


• differentiate dissimilar things, make similar things resemble one another

Simplicity Principle

• make simple, common tasks simple to do


• communicate clearly and simply in user’s own language


• provide good shortcuts that are meaningfully related to longer procedures

Visibility Principle

• keep all needed options and materials for a given task visible


• do not distract user with extraneous and redundant information


• do not confuse user with too many alternatives for performing same task

Feedback Principle

• inform actions or interpretations


• inform changes of state or condition


• inform errors or exceptions


• keep mode of communication – relevant, clear, concise, and in language familiar to user

Tolerance Principle

• reduce cost of mistakes and misuse by allowing ‘undo’ and ‘redo’


• prevent errors by tolerating varied inputs and sequences and by interpreting reasonable actions

Reuse Principle

• reuse internal and external components and behaviors; maintaining consistency with purpose


• reduce the need for users to rethink and remember

The user interface of an application will often make or break it.  Although the functionality that an application provides to users is important, the way in which it provides that functionality is just as important.  An application that is difficult to use won’t be used.  Period.  It won’t matter how technically superior your software is or what functionality it provides, if your users don’t like it they simply won’t use it.  Don’t underestimate the value of user interface design nor of usability.