User experience is the responsibility of everyone in the team.
We don’t have a UX Team. If the problem with your service is that the servers are slow and the UX Team can’t change that, then they aren’t in control of the user experience and they shouldn’t be called the user experience team.
Words are as much the interface as design.
This matches absolutely with something that I have been thinking about recently - specifically that User Experience (UX) as a discipline (and project planning line item) is a very artificial classification, and that whilst it may be beneficial to have team members who are specifically employed as UX experts, the “User Experience” should be considered as a holistic element of any project which encompasses everything from the information architecture through the visual design and front-end code and out to the back-end service interactions.
UX is not just about drawing grey boxes for visual designers to colour in and describing user journeys for developers to build - every single facet of digital design and development is contributing in some part to the user experience.
Expect a slightly more well-formed post on this subject very soon…