> these details are often lost in the two-week sprint cycle or other realities of modern software development process
Indeed. This is why we should abandon the "modern" software development process. Bureaucracy & consulting appears to be producing shit software. By whatever means necessary, the developer needs to be made to care more about the quality of the final product.
Making "UI/UX" a label, project category or other management abstraction is a gigantic red flag to me. This tells me it is everyone's job, therefore it is effectively no one's job. Someone needs to take deep ownership in things that end in "experience" or it won't work.
You'd be amazed at what others around you will start stepping up to if you set even the tiniest example. Certainly, there are those who will do bad work on purpose, but you won't change those. All you can do is your best and let HR take care of the rest.
Indeed. This is why we should abandon the "modern" software development process. Bureaucracy & consulting appears to be producing shit software. By whatever means necessary, the developer needs to be made to care more about the quality of the final product.
Making "UI/UX" a label, project category or other management abstraction is a gigantic red flag to me. This tells me it is everyone's job, therefore it is effectively no one's job. Someone needs to take deep ownership in things that end in "experience" or it won't work.
You'd be amazed at what others around you will start stepping up to if you set even the tiniest example. Certainly, there are those who will do bad work on purpose, but you won't change those. All you can do is your best and let HR take care of the rest.