Wow! Thanks for all the great responses. Lots of stuff there to think about (and do something about).
The main things I'm hearing: involve devs in design and designer(s) in implementation (at least in terms of proximity, taking part in their meetings, etc.) -- collaboration and communcation, be friends, build trust. Don't let them get ahead of you. And involve QA to evaluate what was built against the spec. Thanks also for the IA- and Agile-specific advice, though neither really apply in my situation -- we're building applications, so IA is only a small part. And we're not an Agile shop, so... @austingovella: I like the part about designing in prioritized layers. Nice. @bryanminihan: Regarding handling the front-end -- doesn't this depend on the technology you're using to some extent? Example: we're using GWT, where the HTML is (mostly?) auto-generated -- to style something (say, a control), you can either use CSS in a separate file or do it directly in the source code (which you then *can't* override in the CSS). @jonathanabbett: Clickframes sounds interesting -- I'll check it out. Thanks again to EVERYONE who replied. Much appreciated! Cheers, Martin Polley Technical writer, interaction designer +972 52 3864280 Twitter: martinpolley <http://capcloud.com/> On Tue, Aug 25, 2009 at 1:39 AM, Jim Drew <[email protected]> wrote: > You build in a QA team which is connected to both Dev and Design, ... ________________________________________________________________ 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
