I once shipped a new product, and was surprised to receive no negative feedback from users regarding content quality.
Happens out, UX team placed the "Send Feedback" button below the infinite scroll content feed.
Happens out, UX team placed the "Send Feedback" button below the infinite scroll content feed.
Ideally, there is a QA pass on staging, involving the designer, in which more than "does this feature work as written in the ticket" is the question you try to answer before releasing the feature. Many teams don't do this, and the blame for that lies with different people in different organizations I've worked in.
But developers often sneeringly deride designers for not catching things like this — "you had one job, lol" — but the sad truth is that there's no testing suite to help designers catch stupid mistakes. Speaking practically, the unit tester for a design is often the developer who tries to build it. Imagine what your interpreter or compiler or testing framework would say about your intelligence if it could talk!
I recall a new marketing executive who touted that they had improved the youtube ads so much that NOBODY had skipped a single improved youtube ad!
They made the ads all so short that you couldn't skip them.
If they were trying "skiping not allowed in 60+ sec long ads", then it would be bad
Maybe for your attention span or what YOU like but maybe not for what they are actually buying ads for... Money
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.