This is one of those threads that won't ever tip either way, because 'it depends'. Everything that's been said here is valid. Let me throw out one more scenario (that I work in)- very large scale products. We have separate folks who do
1. User Research/ Sketches/ Wireframes/ Process Flows/ UI/ non-production level prototypes/ Usability (this seems bigger only because I expanded all the steps involved) 2.Visual Design/ Branding/ CSS 3. Front End Dev All 3 report into the same structure, but these roles need to be separate because they are all each full time roles. Yes, I 'work in Visio' (Omnigraffle in my case) all day, but I don't get paid because of my killer Omnigraffle skills. This forum knows better what I bring to the table. In large scale products like the one that I work on, people working on all three will result in overall mediocrity. If I were leading an effort to build say a small 5-10 'page' website, it would be foolish to hire to do the same. If I were designing a really complex product (like say a medical device or such), Design Research would probably be a separate role. And so on. There is such a wide spectrum of products & projects in the marketplace, that there is space for all. Saying that wireframes need to go, or designers should not code is just plain wrong. > That's not to say I don't think more people should be doing more prototyping and less wireframing, because I do. > However, I realize that there are a number of environments that require heavy documentation (e.g. government, > corporate) and so in those contexts I see wireframes w/behavior notes as being valuable. -- -Vishal http://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
