Before testing: If you want a product with good UX, do you give the programmers a list of functions or a list of scenarios?
Usually people write a functional spec for a software/website they want, which they then give to the programmer. The programmer will create a program/website with the functions you requested. The programmer comes back and feels great about this product he created for you, with all the functions you asked for, maybe even threw in a few extra. You try the program and it has all the functions, but it is impractical. You want to add a new item to a list; it takes 5 clicks, etc. etc. So my questions are: Do you provide scenarios in your functional spec or does this get done afterwards? Should you be providing a list of functions or will a list of scenarios provide better results? ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
