| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

UX and IA Resources

Page history last edited by PBworks 16 years, 2 months ago

UX and IA Resources

sketch pad


Deliverables Overview

 

 

UX/IA

 

UCD Process according to UPA

Analysis Phase

  • Meet with key stakeholders to set vision
  • Include usability tasks in the project plan
  • Assemble a multidisciplinary team to ensure complete expertise
  • Develop usability goals and objectives
  • Conduct field studies
  • Look at competitive products
  • Create user profiles
  • Develop a task analysis
  • Document user scenarios
  • Document user performance requirements

Design Phase

  • Begin to brainstorm design concepts and metaphors
  • Develop screen flow and navigation model
  • Do walkthroughs of design concepts
  • Begin design with paper and pencil
  • Create low-fidelity prototypes
  • Conduct usability testing on low-fidelity prototypes
  • Create high-fidelity detailed design
  • Do usability testing again
  • Document standards and guidelines
  • Create a design specification

Implementation Phase

  • Ongoing heuristic evaluations
  • Work closely with delivery team as design is implemented
  • Conduct usability testing as soon as possible

Deployment Phase

  • Use surveys to get user feedback
  • Conduct field studies to get info about actual use
  • Check objectives using usability testing

 

 


Site Evaluation

Heuristic Site Evaluation >>


Simulation Tools

An Introduction to the Newest Simulation Tools - for Boxes & Arrows by Scott McDowell


Competitors Analyisis


Field Studies / Interviews

Work shops

Jess McMullin: Design games


Stakeholder Interviews

"In fact, one of my favorite questions is to ask stakeholders what a typical day in their work life is like. What seems like an icebreaker actually yields important insights into their frustrations or what they would like to see happen with the site."....

 

"If you swap business cards and get to know your interview subjects by name, it really takes little additional effort to email your “stakeholder design team” (which is what they are) periodic updates on the progress of your work. You will also often find that follow-up interviews are appropriate, appreciated, and yield helpful clarification on earlier points. If after the interviews your stakeholders call with new ideas and email supporting documents or articles they come across, you’ve built a great relationship that could make your design even better."

 

Setting Up Business Stakeholder Interviews by Michael Beavers for Boxes & Arrows

 

Backcasting

an interesting technique to kick off a large project and get all the information for a sound start of the discovery phase

slideshow of a presentation at the IA summit 2007 by Matthew Milan and Sam Ladner.


Focus Group Analysis

Focus Group Page >>


Personas & Scenarios

How to develop and use Personas & Scenarios >>

Use Cases

 


Card Sorting

Card Sorting Page >>

 


Controlled Vocabularies, Facet Analysis, Thesaurus - all things Findability

fantastic resource: Willpower Information


 

Eye Tracking


Site Traffic Analysis

Inventory

Prioritization Matrix

(note to self: worksheet on desktop - Templates&Tools)

Adam Polanski: Faceted Feature Analysis


Feature list, wish list, nice to haves


Navigation Systems

Hierarchical, Trees

 

Paradigms

Classification Systems: Facets

Tag Clouds

The future of Tag Clouds

A Blog on Tag Clouds: tagclouds.com


Good Templates, Stencils, Tools etc

IA Institute Tools

Jesse James Garrett

Founder of Adaptive Path

infodesign - List of tools

RIA stencils for visio from Bill Scott's 'Looks good works well'


WIREFRAMING

Guuui! Visio - the interaction designer's nail gun (3rd edition)

 

SCREEN DESCRIPTION DIAGRAM

“The page description diagram is a tool to allow designers and information architects to stay comfortably within their own realms without compromising communication.” Dan Brown's Article 'Where the Wireframes Are: Special Deliverable #3' on Boxes & Arrows - VERY VERY USEFUL

also explained very well by D. Keith Robinson in SpoolCast: Creating Advanced Web App Deliverables with D. Keith Robinson


UX Creative

on simplicity and feature fatigue

"Defeating Feature Fatigue," ( http://tinyurl.com/yu46jo )

suggested consumers will likely choose a more feature-rich product

over one that appears simpler, but they'll be less likely to make

future purchases from the same vendor if it's not usable.

Harvard Business Review via UIE

 

Web 2.0

Web 2.0: The Power Behind the Hype - Jared Spool on rapid Web 2.0 application development.

Blogging


Usability

 

User Testing

User Testing Page >>

 

 

Accessibility

w3 guidelines

compliance checklist


Tasks for a successful REDESIGN of sites

Copy Writing

Pet Goat - 'My Account'

Who's talking?- my (standard) recommendation on this subject is:

Semantics: Me and mine, you and yours - Who's talking?

Refer consistently to the user as 'you' and 'yours' and you'll see how much more mature, easy and elegant it is. It makes more sense and your entire copy will be more coherent.

'You can change your details in 'My Details'

'To update your medical history go to 'My Medical History'

Great classic piece by Peter Merholz (August 98! - still relevant): 'Use "Your" when referring to the personalized area for a Web site. Leave "My" for the inner dialog of tortured junior high first person narratives.'

http://www.peterme.com/index081098.html


eCommerce

All about eCommerce >>

 


Search

Plenty about Search and SEO

piece about analyzing search logs

 


 

Presentations:

 


valuable resources

 


PROCESS

Goal Directed Design

Coopers - very well presented!

Rinse and Repeat - UX framework

Jakob Nielson on Iterative Design for a good user experience: The Usability Lifecycle

Selling IA

 


PM

How to determine a new version number

(from a step two article)

..., if the current version number is 3.0, the next version could be:

  • Version 3.01, if minor 'bug fixes' are made to the site, as part of ongoing incremental improvements.
  • Version 3.1, if some improvements are made to the intranet but the overall site is not significantly changed or enhanced.
  • Version 3.5, if key issues are addressed, or significant functionality is added to the site.
  • Version 4.0, if there is a major rework of the site, such as developing and implementing a new information architecture.

Use a version number to communicate the size of what is being done, and to set expectations for how much will be delivered.

...

 

Comments (0)

You don't have permission to comment on this page.