The short answer
Credibility with stakeholders who don’t prioritise UX is not awarded on the basis of expertise, it is built over time through a series of small transactions. You solve a problem for someone. You give them information that proves accurate. You flag a risk that would have cost them later. Each transaction builds the political capital that you draw on when you need someone to support an uncomfortable recommendation or defend a decision under pressure. Most UX practitioners build their credibility inward — with other designers and researchers — rather than outward, toward the stakeholders who control budgets, scope, and delivery. That misdirection means that most organisational influence fails to build over time.
How credibility actually works in organisations
Credibility in an organisation is not a credential. It is not a title, a portfolio, or a track record that travels between contexts. It is a relationship-specific resource — something you have with specific people, built through specific interactions, over specific time.
The UX practitioner who is highly regarded within the design community — whose work is respected by other designers, whose research is cited, whose opinions carry weight in design discussions — may have zero credibility with the product director who controls the roadmap or the technology lead who approves the build scope. Those are different credibility hierarchies, governed by different standards, and they do not automatically convert from one to another.
This matters because influence over what gets built requires credibility with the people who decide what gets built. If that credibility is concentrated in the design community rather than distributed across the people with actual authority, the UX practitioner’s influence stops at the boundary of the design team.
The transaction model of credibility
Credibility with stakeholders who have other priorities is built through what might be called a transaction model: a series of small contributions that accumulate into a relationship the stakeholder values and draws on.
The transactions that build credibility tend to have consistent characteristics. They are useful to the person receiving them — not useful in a general sense, but useful specifically to what that person is trying to do and concerned about. They are accurate and they are timely. Accurate in terms of the information, the risk flag, the prediction about user behaviour turns out to be correct when tested against reality. Timely in that they arrive when the person can act on them, not after the relevant decision has been made.
Over time, a practitioner who has delivered a series of transactions with these characteristics builds something more durable than a single well-argued recommendation ever could: a relationship in which the stakeholder actively seeks their input rather than responding to it reactively.
Where most practitioners build credibility in the wrong place
Most UX practitioners build credibility inward rather than outward. They invest in relationships with other designers, with researchers, with content designers and service designers. Those relationships are valuable as they produce better collaborative work, more rigorous research, more coherent design decisions. They do not reach the stakeholders who control whether that work gets implemented in the way it was intended.
The product director, the technology lead, and the finance stakeholder have their own credibility hierarchies. Being well-regarded by a design team does not automatically register in those hierarchies. To build credibility with those people, the UX practitioner needs to engage on their terms, with the problems they are trying to solve, in the language they use to describe those problems, and with contributions that are useful to them specifically rather than to the design process generally.
Meeting stakeholders in their terms
What it means to meet a stakeholder in their terms varies by role and by person, but some consistent patterns apply:
- A product director cares about delivery risk and outcome quality: a practitioner who accurately identifies a delivery risk early, before it becomes a problem, is giving that director something genuinely valuable
- A technology lead cares about build complexity and maintainability: a practitioner who designs in ways that make implementation straightforward, and who communicates that clearly, builds a different kind of relationship than one who hands over designs without considering build implications
- A finance stakeholder cares about cost and return: a practitioner who can connect design decisions to cost consequences — the cost of rework, the cost of elevated support volume, the return on a specific design investment — is engaging in a language those stakeholders actually use
The practitioner who can engage on these terms, consistently and accurately, builds a relationship that is qualitatively different from the one built through user need arguments alone. The user argument still matters. The people who need to hear it are simply more likely to act on it when it comes from someone they already trust.
Instead of asking how to persuade stakeholders to care about UX, ask what they already care about, and where your work genuinely intersects with it.
Frequently asked questions
How do you build credibility with stakeholders who aren’t interested in UX?
Build credibility by making yourself useful to them in terms they value; not by making the case for UX in general, but by providing accurate information about specific risks, flagging problems they would have had to deal with later, and delivering things reliably when they expect slippage. Each of these transactions builds political capital that is specific to that relationship. Over time, a stakeholder who has found your input consistently useful will seek it out rather than receive it defensively.
Why do UX practitioners struggle to influence stakeholders?
UX practitioners often struggle to influence stakeholders because their credibility is concentrated in the design community rather than distributed across the people with authority over what gets built. Stakeholders with budget, scope, and delivery authority have their own credibility hierarchies, and they don’t automatically value expertise within the design community. Building influence with those stakeholders requires engaging on their terms, with their priorities, in their language, which is a different activity from building a strong design practice.
What is political capital in a UX context?
Political capital is the accumulated goodwill and trust that allows a practitioner to make requests, ask for resources, or advocate for uncomfortable decisions with a reasonable expectation of a positive response. In a UX context, it is built through small transactions — accurate risk flags, reliable delivery, useful contributions to problems the stakeholder cares about — and drawn on when a design recommendation requires the stakeholder to do something that has a cost for them: prioritise a design change, push back on delivery pressure, defend a decision under scrutiny.
How long does it take to build credibility with stakeholders?
Credibility is built incrementally and takes time that most practitioners underestimate. A single well-argued recommendation rarely builds it. A series of smaller, accurate, useful contributions over several months does. The practitioners with the most organisational influence have typically been investing in specific stakeholder relationships for a year or more before they need to draw on them in a high-stakes situation. This is why credibility-building needs to happen continuously, not just before an important recommendation is due.