>the "UX people" you describe were doing important work right? Maybe stuff like testing/QA, building domain knowledge, analyzing feedback, building trust with c

>the "UX people" you describe were doing important work right? Maybe stuff like testing/QA, building domain knowledge, analyzing feedback, building trust with clients/users, writing specs, mockups, documentation, designing UI components etc. I think the frustration with "UX people" is that they aren't necessarily doing any of those well-defined things that are all part of UX, but instead doing some nebulous stuff because nobody really knows what UX means. Calling some people on the team "UX people" carries the implication that everybody else on the team (testers, customer service, documentation, ui designers, backend devs, SREs) are somehow not working on UX. Everybody on a product team is a UX person, so for somebody to only be a UX person essentially means they have no role.