The reason why I thought scenarios might assist programmers (on top of the feature list) is that scenarios might help programmers understand how the user will use the program. If they understand that users will need access to point A,B,F,G on a particular page and that they need to send it all via email in a certain time period, they will hopefully not design a program where you would have to go to point A,B,F,G on seperate pages and add the info to the email. But rather have access to A,B,F,G's content directly from the particular "page" you are at.
I thought it was pretty obvious that "feature list thinking" is what leads to mobile companies creating phones with a list of non-used features. If they understood scenarios, we might have had more "good" mobile phones. ________________________________________________________________ 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
