Great article Whitney, the It's not just UI is the most challenging one in my experience, we need to continue to hammer away on that message! Here are the one's I disagree on- 2. …a step in the process: Its no more/ less a step in the process than say business development is a step in the process. On the contrary, I'd assert that it is a (important) step in the process, so that UX considerations are not ignored. Having defined deliverables (process flows, sketches, wireframes, research docs etc) is not necessarily a bad thing, specificity has its place in the process. Of course it needs to be an ongoing part of the product development cycle, but UX is not any different than others.
5. …just about the user: It is just about the user. While we work within the constraints of the business models (or collaborate with the mba types in defining them), its not our primary value/ responsibility. A successful product has to tread the fine line between good business models & a successful user experience, but our role IMHO is ensuring the latter is achieved. 8. …the role of one person or department: It is- that of UX designers. I understand what you mean, but I'm afraid some people may construe this as 'anyone can do it', why hire us then? While 'we don't have a set of best practices that we can robotically implement', we do have the necessary & unique skill set to make products easy & enjoyable to use. Thank you guys so much for the positive feedback. I really look > forward to hearing how the piece helps facilitate conversations > between you and your teams. Please let me know! -Vishal www.vishaliyer.com ________________________________________________________________ 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
