Conference Buddies

March 11, 2009 8:30am – 10:00am
Speaker: James Hobart

Summary/Topics:

• Navigation/Taxonomy Basics
• Menu/Hierarchical Design Patterns
• Alternative Navigation Design
• Complex Taxonomy Case Study

UI Design Basics

• Consistency
• Clarity
• Terminology
• Provide clear feedback
• Correct “Mental Model”
• Task Alignment
• Enjoyable

Key Thoughts

• Avoid deep level hierarchy when possible (no more than 3 levels deep)
• Lower efficiency costs – shorten the amount of steps to do something
  Example:
  Google allows searches for movie times and stock quotes. Instead of going to Fandango or Scottrade, a user can just type their search in Google.
• Provide real-time feedback
• Present possibilities to help with selection
• Discovery engines can add value
• Help distinguish best choices – the buy now button on e-commerce sites are generally the largest call to action

Note: 18% of users automatically go straight to search rather than using a navigation system, as such, a search should always be available on a global level.

Definitions

Taxonomy – metadata – information about information
Navigation Models – basis for creating components to allow users to move around and find information

Navigation Examples

Hierarchical Tree View

An abstract view for navigation – users may not understand hierarchy. It’s been tested to show that if users do not find what they are looking for upon expanding on a tree view, they start over and go down the hierarchy again. This increases efficiency cost.

Tree/List View Combination

Similar to Tree View, but provides more information. Microsoft Outlook is a popular example of this structure. It has been proven successful for power users.

Menu Navigation Guidelines

• Choose a consistent global navigation scheme
• Sub-navigation should be tied to global navigation
• Beware of complex sidebar navigation
• Avoid fly-out menus with more than 3 levels (also be aware of horizontal and vertical spacing – horizontal space should not be too wide, and vertical margins should provide adequate spacing)

Menu Information Layering

• Set distinct layer thresholds (pick out the essential items to list and for any non-essential items, add a “more” link)
• Follow a 1-2-3 step to get users where they want

Folksonomy-Based Consumer Search/Taxonomy

Hierarchical structures based on user driven data, such as:

• Product reviews
• User driven tags
• User ratings

Note: Pitfall is that you must monitor the data. User driven data needs to factor in that users can drive the data differently in that some users may tag something as “hiking boots” and others as “hiker boots” or “hiking shoes.”

Remember…

• Taxonomies getting more complex
• Adapt navigation strategies to meet new information challenges
• Shield users from complexity
• Lower efficiency cost of navigation
• Leverage design patterns to repeat success

Writing Good Use Case – SD West 2009

March 11, 2009

Speaker: Terry Quatrani (UML Evangelist, IBM)

Conference Notes:

Keep a use case high level and don’t have it bogged down with features and details. The main function of a use case is to clearly communicate:

• the main justification for the software
• who will be using it
• the end goal for the actor/ user
• a  happy day scenario
• other main listed alternatives
• high risk identifiers

Use case should be in plan language giving the reader enough information to understand the justification and main purpose of the software without being lost in the details.

More information should follow in a technical UI document that flushes out the detail requirements. A good use case is high level and provides enough information.  Do not list out all details, alternative scenarios, risk factors, or “what if statements” – just focus on the major key areas.

Personas, Profiles, Actors, & Roles: Modeling Users To Target Successful Product Design – SD West 2009

March 11, 2009

Speaker: Jeff Patton (Architect, Interaction Designers, AgileProductDesign)

Conference Notes:
Building personas, profiles, actors & roles are key to understanding:

1. Who will be using the software
2. What is the profile of the target user – skills, user experience, levels of interaction
3. What is the function of the software
4. What is the responsibility of the user in relation to the software

This often starts by brain storming. More data is often available from market data, marketing departments, and UI studies.

Use of images of what your target personas is often helpful for people to connect with the attributes.  Keep attributes short and easy to remember.