Previous Slide (14 of 32)  Main Menu  Next Slide (16 of 32)
What We Learned from Participants

  • Even with a simple paper prototype, designers tend to be unwilling to accept input and change
  • Team Building (Trust in Usability Expert & Results)
  • Prove problem (i.e., video tape user experiences)

Developers tend to think the solution they built is the "right" solution and don't like the concept of reinvesting their time to fix something that isn't broke.

We experienced the same inflexibility even with the paper prototypes which are so easy to fix! Hopefully making people aware that changes now will save more rework later can have a big impact. In addition, watching a real user get confused and frustrated with a paper design can cause developers to recognize the need for change.

A word of advice, that we all need to follow; avoid the temptation to interrupt an user with "but what we are trying to do." or "you don't understand the model." If they don't understand it without you interpreting for them, it is a sure bet that an user sitting by themselves out on the internet will have the same problem.

Previous Slide (14 of 32)  Main Menu  Next Slide (16 of 32)

Slide 15 of 32
Comments: Happily Received!
Home Pages: Miller's & Rettig's
Updated: 01.20.1998