It's hilarious to me that the Design/UX team is always the one making mistakes like this where I've worked.
We're just sitting there saying, even from a non-code point of view, this shit makes zero sense.
Ignored as usual.
We're just sitting there saying, even from a non-code point of view, this shit makes zero sense.
Ignored as usual.
Let us try our best to treat them charitably, forgive the mistakes we see, and provide input to help them do their work even better!
I had success working with Design/UX or any other specialists acknowledging that they spent more time thinking about it than I have, and that, of course, they will be the final decision makers on whether to accept or reject any inputs I give, before providing any feedback or ideas I have. Also, taking the attitude, not of "Let me teach you X", but of "Teach me whether you considered X and, if you have, why you haven't tried X yet".
The same sometimes applies to designers and developers: if developers don't design, then of course they won't make bad designs.
The gist of it all is: don't ridicule people for mistakes, even if they're in their supposed field of expertise. Just let them know they've made a mistake if you see one.
I think the reason is, devs view a design from the perspective of a simple user, they see it with fresh eyes, while the UI/UX team probably spent too much time tweaking the design to the point they got used to it and all its quirks and stopped seeing anything wrong with it.