I have found that in a situation like this the best defense you have is to clarify your job description with your manager or CTO. By having your responsibilities defined in "writing" you hold the pass key to throw your weight around in the fighting ring especially when it comes to issues that directly coincide with your expertise.
Once you have the authority make sure that when a project is planned out, anything you feel that should be necessary is planned into the Functional Requirements Documentation, such as; "Qualitative research", as you mentioned. You'll find that once it is in writing you'll have "a foot in the door". It then comes down to relying on your research and reason to sway the team in one direction or another. Hope that helps. Good Luck! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=37605 ________________________________________________________________ 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
