Hi Oliver, Do you think it wouldn't be better to focus on an activity-oriented approach instead of a goal-oriented one?
It seems to me that if a project gets to the point where no user data (be it from a proxy user, a customer service employee, a marketing representative, anybody who deals with users) is available, user needs as such cannot be traced and translated into user needs and goals nor a system response for the accomplishment of those goals can be created, for there are no recognizable and factual users in first place. By default, I would have switched to design something that works and caters for the accomplishment of activities; bringing new users, which to me are unknown, from beginners to intermediate level quickly. Given that user data is collected as this first activity-oriented release is used by people, the users' needs and goals would start to be defined as users start to materialise. Then, a second more goal-oriented user-centric release would ensue. I believe the Agile factor would serve with the iterative and evolutionary process of designing this system for a set of activities until user needs can be raised from minimally trustworthy sources. Do you guys think I would have lost an opportunity by following the approach above? Cheers, Luis We are in the discovery phase of the project, where we have absolutely no idea what the user needs are. ________________________________________________________________ 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
