The short answer
Being right is necessary in UX practice, but it is not sufficient. Persuasive force — the capacity to make a recommendation that actually changes a decision — depends on the relationship between the person making the argument and the person receiving it, the timing of the argument relative to the decision, and the framing of the argument in terms the listener finds compelling. A well-evidenced recommendation from someone a stakeholder doesn’t trust lands differently from the same recommendation from someone they do. The reasoning may be identical, but the outcome is not.
The belief that evidence should be enough
There is a version of the UX profession that believes being right is enough. If the research is sound, the argument is clear, and the recommendation is well-evidenced, the decision should follow. This belief is understandable. It reflects a commitment to rigour, to user-centred thinking, to doing the work properly. It also fails in practice, consistently, across every kind of organisation.
The failure is not random, it has a structure: the quality of an argument and its persuasive force are two different things, and UX practitioners — trained to focus on evidence and reasoning — sometimes invest heavily in one while neglecting the other.
Why persuasive force is not just about the argument
Persuasive force is determined by the relationship between the argument, the arguer, and the audience, not by the argument alone.
A recommendation from someone who has built credibility with a stakeholder lands differently from the same recommendation made by someone that stakeholder does not yet trust. The evidence may be identical, but the history of the relationship is not. A stakeholder who has seen a practitioner’s previous recommendations prove accurate is more likely to act on a new one than a stakeholder who has no track record to draw on.
Timing matters in the same way. A recommendation made before a decision has been mentally closed is easier to act on than the same recommendation made afterward. Organisations make decisions in two stages: formally, in meetings and reviews; and informally, in the conversations that precede them. A recommendation that arrives after the informal consensus has formed is not competing on equal terms with recommendations that shaped that consensus.
Framing is the third factor. The same recommendation, expressed in terms of what the listener cares about, lands differently than it does when expressed in terms of what the UX practitioner finds significant. A recommendation framed around delivery risk lands differently with a product director than the same recommendation framed around user need — not because delivery risk is more important than user need, but because delivery risk is closer to what the product director is accountable for.
Why this is uncomfortable for UX practitioners
The idea that relationship, timing, and framing matter as much as evidence can feel like a corruption of the work. The UX practitioner’s job, in this view, should be to produce the best possible thinking and present it as clearly as possible. That it should also require navigating organisational relationships and adapting arguments to different audiences feels like politics, which is often viewed as something separate from and secondary to the work itself.
This discomfort is worth naming because it is real and because acting on it — treating influence as a secondary concern, something to worry about after the design work is done — produces predictable outcomes. Good work that is not advocated for effectively does not get implemented effectively. The absence of influence produces the same result as the absence of good work: a decision that does not reflect the best available thinking.
Influence is not separate from the work, more that it is a condition of the work having the effect it is intended to have.
What being heard requires
Being heard by the right people at the right moment is a skill, and it can be developed deliberately. It requires:
- Understanding whose support you need before a decision is made, not after. Identifying the people whose agreement is necessary for a recommendation be accepted, and investing in those relationships before you need to draw on them
- Knowing which stakeholders are persuadable and which are not, and directing effort toward the former rather than the latter
- Presenting recommendations in terms of what the listener cares about, not in terms of what the practitioner finds significant, but in terms of what the listener is accountable for and worried about
None of this means compromising the work. The recommendation remains what it is. What changes is when the groundwork for it is laid, who it is directed toward, and how it is framed when it arrives.
Instead of asking why your recommendations are not being acted on, ask whether the people who need to act on them have been given a reason to, in terms they find compelling.
Frequently asked questions
Why don’t good UX recommendations get acted on?
Good UX recommendations fail to produce action when they reach people who lack authority to act on them, arrive after informal consensus has already formed, or are framed in terms the listener doesn’t find compelling. The quality of the recommendation is necessary but not sufficient. It also needs to reach the right person, at the right moment, in terms that connect to what they are already accountable for and concerned about.
How do you build influence as a UX practitioner?
UX influence is built through credibility — a track record of accurate recommendations, useful contributions, and reliably delivered work — combined with deliberate investment in relationships with the people who have authority over what gets built. This investment happens before you need to draw on it. UX practitioners who build influence reactively, in response to a specific decision they need to win, are working at a disadvantage compared to those who have been building it steadily through smaller transactions.
Is stakeholder management a core UX skill?
Yes. Stakeholder management — understanding who has authority over design-related decisions, building credibility with those people, and communicating recommendations in terms they find compelling — is as important to the effectiveness of UX practice as research methods or design craft. In most organisations, the limiting factor on how much impact a practitioner has is not the quality of their thinking but their ability to get that thinking into the decision-making process at the right moment.
How do you frame UX recommendations for different stakeholders?
Frame recommendations in terms of what each stakeholder is accountable for and concerned with. A product director cares about delivery risk and outcome quality, so frame the recommendation around what could go wrong without it. A technology lead cares about build complexity, so frame it around what the design makes easier or harder to implement. A finance stakeholder cares about cost, so frame it around the cost of not doing it versus doing it. The recommendation is the same; the framing connects it to what each listener is already trying to manage.