3 ms·

Ok, but what about in a startup / limited budget scenario where you can't afford dedicated UX people, something that is often the case?

• tensor 10y ago
  Then you pick the person on the team most interested in design and get them to learn how to do design right. They become 50-75% design and the rest whatever they were doing before. Being good at development or some other domain doesn't necessarily correlate with being good at design. Developers understand that their trade takes time and effort to learn, it amazes me that some of them can't understand that it's the same for other domains.
  • joesmo 10y ago
    But we already have engineering experts in the field telling product it's not a good idea. The problem isn't the lack of expertise, it's the lack of ability to push back on a stupid task. The point is, there is no mediation here. If a UI/UX person can tell them what a bad idea is, so should an engineer be able to. Thus, engineering cannot be the slave of product in an effective organization and product that insists on its pixel perfect designs is by definition low quality (because nobody is perfect).