On 24/11/2010, at 1:26 PM, dnagir wrote: > Thanks to all who replied. Appreciate it. > > Assuming the designer is available most of the time, then it seems all > agree here that: > > 1. Continuous communication between dev<-->business<-->designer is the > key. > 2. Making it right is an iterative approach. > 3. Dev and Designer should speak the same "language" and understand > each other's tools. > 4. It is a team effort and cannot (should not) be done by exchanging > screens via emails or so. > > (this just sounds as a normal Agile-ish style... why wouldn't it...) > > From this perspective, if the designer is not a part of a team; but > rather doing "once-off", "pay and go" stuff, the failure of UX seems > to be imminent. > > In this situation options are: > 1. Get a good designer on-board (might not be an available solution > ATM). > 2. Keep as close as possible to the original design while continuously > updating the application. > > The option #2 can probably work only so much.
An Option #3 would be to make sure whomever you work with is available to be around during integration and future iterations, basically try to collaborate with them a little more (that is, if they're open to it). – tim -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-ocea...@googlegroups.com. To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
