I'm not trying to perpetuate or initiate any kind of ACD vs. UCD death-match, but ACD is very, very new to me, and thus I'm curious.
Something Robert mentioned early in the thread: "As in, the need the user has at a given moment may only exist because you created/encouraged an expectation in the first place, but then you say a good experience isn't about meeting expectations." got me wondering: Consider a situation where a system (app/service/what-have-you) is being designed to tackle a common task or set of tasks (one for which many products/services already exist) in a profoundly new way. Does researching potential users and their needs/expectations present a flaw in that their perceived needs and expectations are biased due to the many products/services that they may already be using to accomplish the task? Is this a situation where ACD would then have a better chance at introducing change and innovation due to the idea that in ACD its the activity of the carrying out the task itself that is looked at and preconceived notions are somewhat ignored. Furthermore it sounds as though there is room for ACD and UCD to live harmoniously within the same project? Am I understanding that correctly? Forgive me if I've got this all wrong, or if this is clear as mud. -adam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=30048 ________________________________________________________________ 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
