I think a big problem is that most developers don't know how to judge the skills of a designer, to find out if they're worth listening to.
When being maintainer of some open-source software, I can usually tell which people are worth listening to on programming topics, because I'm a programmer. However when several people offer advice on design, how can I tell who actually knows about design, and who is just someone telling me what they would personally like?
Posted Sep 26, 2009 19:05 UTC (Sat) by man_ls (subscriber, #15091)
[Link]
A designer is still supposed to bring out rational arguments that make sense. See Baylink's comment above for knetworkmanager: it is not as if you need a usability lab to find out that it sucks. You just have to decide to spend your money or efforts on such issues.
Do you have an example where it would not be so easy to tell?