| Any design done by anyone should get the same benefit of testing and iteration, regardless of whether it was a 'designer' or a 'design agency' or a 'developer'. Biggest issue I run in to (from dev/tech perspective) when working with any 'design' person is that, in pretty much every experience I've ever had (done this for 20+ years in the web world), the person/team doing the design work has one of two issues: 1. they've never done web work 2. they don't provide enough state information You put 3 toggle buttons and a sample piece of information in a mockup... but don't 'design' out what should happen when mutually exclusive things happen... FML. Because regardless of what choices I make to fill in the blanks (and there are always blanks), they're inevitably "wrong" from someone's view (the original design person, or someone on the client's team, etc) because they're now being presented with a decision to make that they didn't have to think about before. It may come across as subtlety "passive aggressive", depending on how you word it, but... damn it - when you put a dozen widgets on the screen and indicate they're linked together - you need to actually think about every single possible state (and step flow, etc). The more 'application-oriented' something is, the less useful I've found "designer" input to be, outside of giving basic font/color/styling guidelines. It's worse when the people label themselves "UX", but still don't provide any of the state info. |