Why good UX work fails when stakeholders don't understand it
A design that nobody understands is not a design decision. It is a proposal waiting to be overruled by someone with a clearer story.
By Mike Newman · Updated
Designers tend to diagnose a rejected design as a taste problem, a politics problem or a stakeholder problem. Usually it is a communication problem, and communication is the part of the job most designers were never taught.
Why the reasoning matters more than the artefact
Stakeholders are rarely evaluating your craft. They are evaluating risk: what this costs, what it changes, what happens if it is wrong. If the reasoning behind a design is not visible in those terms, they fill the gap with their own reasoning, and their reasoning wins, because they are the ones deciding.
Practical shifts that work
- Lead with the problem and the constraint, not the screen.
- Say what you decided, what you rejected, and why: trade-offs make it a decision instead of an opinion.
- Use the language your audience already uses rather than design vocabulary.
- Ask for a specific decision at the end of the session, not general feedback.
- Build trust across a project, not one presentation at a time.
This gets more important as tooling gets faster
When more people in a team can produce something that looks finished, the person who can explain why one option is right has more influence than the person who made the most options. Communication is not a soft extra to design work. It decides whether the work survives contact with the organisation.