> A few thoughts - first I often call "What a product should do" > Business requirements - not functional requirements.
Yes! My ideal process: 1) Business Requirements -- what the business wants to do 2) UI Spec - what the user experiences to deliver #1 successfully 3) Functional Spec - what the machines do to deliver #2 successfully Before, during, and after all of these steps, there are many opportunities for research. My concern is when #2 and #3 are reversed. Or when #1 is dumb. -Cf Christopher Fahey ____________________________ Behavior biz: http://www.behaviordesign.com me: http://www.graphpaper.com ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
