Hi, I'm in a transition stage, moving from developer to business systems analyst. In this new role, I'm trying to incorporate some usability guidelines and improve user interaction. I get quite a bit of push back from the developer team members.
They claim certain things cannot be done. However, being a developer, I know some things can be done. There was even a point, since I still have access to the environment that I wrote some code to prove it. I cannot go on doing that for the rest of my career. But, I would hate to give up the fight, and allow good interaction design to take a backseat to quick, dirty, & cheap development. How do some of you, who have been in my situation, handle these types of resistances, so that your application can be a good and usable one? Thanks, Elle ________________________________________________________________ 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
