I was responding to the Cooper thread but thought this might be a different topic. I agree that spending time on the IxD of a product before requirements are written in theory should result in a stronger, more innovative product. The problem I've run into in my last two positions (ecommerce and now, media) is that the product analysts/managers view any pre-requirements work as their role. They want to do the research, then they write requirements which state how the product should be designed and they are the decision makers during design. Ultimately, they drive the design. And not one of the product folks I've worked with come from the IxD, IA or usability arenas.
This is a conflict for me as the product analysts/managers are ultimately concerned with driving revenue not UE. Explaining that a higher quality UE will increase revenue gets lip service but hasn't changed anything. Have any of you had similar experiences? How do you handle it? Thanks for any suggestions, Karen ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ 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
