Product managers make UX decisions every day. Most were never trained for it.

In the first two articles of this series we said that UX-PM is a product certification, and we explained how its three levels work. This week we look at UX for product managers, and at the problem that UX-PM wants to solve. It is a simple problem, and it is present in almost every product team.

Every product decision is also a UX decision

Think about a normal week for a product manager. You decide which features go into the next sprint and which ones wait. You cut scope because the deadline is close. You choose which customer complaints are important and which ones are noise. You approve a flow, a screen, maybe the text of an error message.

None of these decisions has “UX” in its name. However, every one of them changes the experience of the people who use the product. When you cut a step from onboarding, you change the experience. When you delay a bug fix, you also change the experience.

So the question is not whether product managers make UX decisions. They do, every day. The real question is whether they make them with the right knowledge.

Where product managers come from

Very few product managers studied product management. Most of them arrived from another place: engineering, business, marketing, sales, consulting, or their own startup. They are smart and experienced people. They learned the job by doing it.

This path gives them many strengths. They understand the business, the technology and the market. But it rarely includes formal training in user research, usability or interaction design. They learn UX in fragments: a workshop here, a book there, a conversation with a designer.

The result is predictable. Each person builds their own idea of what UX is, and these ideas are often very different inside the same team.

The gap is not talent

It is easy to think the problem is individual. It is not. In our experience, the gap is not talent. The gap is a shared language and a shared method across the product team.

Here is what this gap looks like in practice:

• A researcher presents findings from ten interviews. The product manager hears one more opinion.
• A designer talks about the mental model of the user. The engineer does not see how this affects the backlog.
• The team discusses a usability problem, but nobody agrees on how serious it is.
• In the end, the decision goes to the loudest voice, the most senior person, or the deadline.

Nobody in this story is doing a bad job. They simply do not speak the same language, and they do not follow the same method to go from evidence to decision.

What a shared language changes

When a product team shares basic UX concepts, the conversation changes. People can separate evidence from opinion. They can ask better questions before building, instead of after launch. They know when a problem needs research and which method fits, and when a quick test is enough. They can also rate the severity of a usability issue and compare it with other priorities in the backlog.

A shared language is not only vocabulary. It comes with a method: a common way to understand users, define the problem, test ideas and measure results. With a method, UX stops being a matter of taste. It becomes part of how the team makes decisions. This is even more important now that AI is entering product work, and teams need clear rules about who governs the decisions.

Train the team, not only the person

This is why UX-PM was designed for product and management profiles, not only for designers. And this is also why many organisations send the whole product team to Level 1 together. Product managers, designers, engineers, analysts and team leads sit in the same room and learn the same concepts with the same examples.

After the training, the value is not only in what each person knows. The value is in what the team can now discuss together. A designer does not need to explain the basics again. A product manager can challenge a research plan with good arguments, a skill that Level 2 develops in depth. And the organisation has a common starting point to grow its UX maturity.

A question for your team

If you manage a product, try this simple exercise. Ask three people in your team what “good user experience” means for your product. Then compare the answers.

If the answers are very different, you have found the gap. The good news is that it can be closed. You can check the upcoming UX-PM sessions in your country.

UX-PM is an international UX certification program operated within the UXalliance network. Learn more at ux-pm.com.