3 ms·
Your post seems to reinforce the article to me. There should already be people researching the customer/market. It seems redundant to have product do research a
by juve1996 3y ago
Your post seems to reinforce the article to me. There should already be people researching the customer/market. It seems redundant to have product do research and then have UI/UX also do that same research (as in your first example.)
- balls187 3y ago>There should already be people researching the customer/market. But there isn't, and hasn't been historically, based on my experience. OP is spot on.
- fnordsensei 3y agoEither way, it's immaterial who does it, only the results matter. Though I agree, it either isn't done, or it's done poorly, with little rigor, or dubious research methodology. The field of UX is very, very guilty of this as well. Some people seem to think that just because it's qualitative research, you can feel free to go with your gut, or rely on unsubstantiated data. The same methodology that would get you thrown out of a university can thrive in some organizations.
- blululu 3y agoFor many software products User != Customer.
- juve1996 3y agoDoesn't really change the point. If the users don't equal the customer then UI/UX doesn't matter at all so long as customers keep buying it. In this scenario, firing UI/UX makes the most sense, because it doesn't matter. If the user IS the customer, then it might matter. But this would be easier handled by product - they would understand their customer's and market's needs. The majority of web/adtech use cases do not need this level of research, hence why they're all getting fired. They aren't doing important work like designing a cockpit. They're just making some changes every few years that frustrate people for a week and then gets redone in another few years.