2 ms·
This article is about 10 times too long for the point it is trying to make. It could be summed up as "don't let implementation considerations quash your UX cre
by dasil003 17y ago
This article is about 10 times too long for the point it is trying to make. It could be summed up as "don't let implementation considerations quash your UX creativity."
That's a valid consideration for sure. But as a full UX developer with a nice bell curve of experience centered squarely over javascript and server side programming, and extending respectively through Photoshop/Illustrator on one side and Linux server admin on the other, I can speak from experience that when you have hard separations between the skill sets of your team, a lot gets lost in translation.
Knowing code is pretty much orthogonal to design creativity. If your goal is to create the most stunning and innovative design possible then I think there is some merit to the OA's thesis. However, most the time, time-to-market and length of iteration cycles are far more important than breaking new design ground (not to mention giving up the usability capital of tried-and-true UI design elements).
Having a cross-disciplinary team makes it possible to start performing usability testing and iterating rapidly even before graphic design is finalized. 9 times out of 10 this is going to result in a better product than trying to silo your people to force them "out of the box". If a mind-blowingly original design is what you want, you just need more creative people, not less cross-disciplinary ones.