Hi all, I'm in charge of a 2 day workshop with a bunch of skilled developers regarding user experience. I want to show that an understanding of the users interaction flow and the user goals are as important as technical knowledge.
One of the things I want to try out is focusing on a top down approach for development to break away from the usual focus on the platform and architecture. One idea I have is to split them up in smaller groups, hand over a pack of feature requests to half of them, and a few user scenarios to the other half. And then let them work out a paper prototype from this. So now to my question, I want to make it clear that the understandning of more that the separate features is important and also how the focus on the user interface often change how the domain and datamodel is constructed. Any ideas or input on this? --- Håkan Reis Dotway AB +46(768)510033 My blog || http://blog.reis.se My company || http://dotway.se Our conference || http://oredev.org - See you in 2008 ________________________________________________________________ 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
