You're a communicator

These are the elements of the user experience, defined by Jesse James Garrett in his book. You can see that the User Interface design (UI) is located closer to the completion stage of the project. At this point, you're moving from a more abstract problem space towards a more concrete deliverable.


What happens with the term UX is that it implies that the product you're building is somehow customer-centric. That everyone in the company will agree that the user needs come first and that you're building from the bottom-up. The truth is that some other factors will come into play the more extensive the organization. This is the case of the Business looking for viability and the Technology Operations informing about the feasibility for shipping a product.


This is perhaps why many companies transitioned their UX roles and turned them into Product design. It implies that you, as a designer, on top of being the voice of the customer and advocating for their needs, also need to have a constructive dialogue with the other powers involved to reach an agreement and find balance.

Being that voice of the customer can also be tricky the longer you are in a position. Yes, you will learn more and more about the user's needs. But at the same time, you will be -naturally- building a bias with your own beliefs and with the information snippets you decide to retain or not.

Here are some strategies I've been collecting to keep you are your teams bias in check:

Another lens
Tarot cards of tech
Cognitive bias cheat sheet