Design Isn’t a Language Barrier

Working inside a large enterprise often means designers spend as much time defending their work as doing it. The rhetoric in business meetings is full of conquest metaphors — “capturing” mindshare, “targeting” customers, “hooking” users — while design teams talk about reducing friction, improving consistency, and developing empathy. These are not just different vocabularies; they are opposite ways of framing the same work.

When a designer says “consistency,” a manager may hear nothing that maps to a business objective. The design terms that feel precise internally are often ambiguous or meaningless to the rest of the organization. The gap isn’t in the quality of the work; it’s in the translation.

Speak Business, Not UX

One practical remedy is to drop UX vocabulary entirely when presenting to stakeholders. Instead of describing design work in its own terms, explain it through the lens of business goals. This means rehearsing the script in advance and choosing words carefully — not to be cynical, but to be understood.

The most effective way to bridge this gap is to tell a story that connects design initiatives directly to business outcomes: how the design team translated a business target into specific design steps, and how those steps will reduce costs, increase efficiency, or open new markets. The story should also make clear how the impact will be measured.

A useful way to structure such a narrative is in eight sequential parts:

  • Goals — the business targets and key results the work will achieve.
  • Translation — how those goals became concrete design initiatives and iterations.
  • Evidence — research data and observed pain points that justify the direction.
  • Ideas — prioritized options, ideally with an impact/effort matrix.
  • Design work — the actual flows, features, and user journeys produced.
  • Design KPIs — the metrics that will track and report success.
  • Shepherding — risk management, compliance, and governance concerns.
  • Future — recommended next steps based on what was learned.

This framing present design work as an investment with a measurable return, not an aesthetic preference. It also demystifies the process, which makes it easier for non-designers to support it.

Language Choices That Help and Hurt

Certain terms are counterproductive in a business setting. Avoid words like “consistency,” “empathy,” “simplicity,” “cognitive load,” and “universal design.” Skip process jargon such as “lean UX,” “agile,” “archetypes,” and “jobs to be done” (JTBD). Abbreviations such as HMW, IxD, PDP, and PLP only confuse the audience. Save “stakeholder management” and “UX validation” for internal conversations.

Instead, speak in terms the business tracks: value, retention, abandonment, cost reduction, efficiency, and growth. Frame risk management, compliance, and governance as natural parts of the design process, and present accessibility not as a compliance checkbox but as an industry-wide best practice. The language shift is not about distorting design work; it is about being deliberate in describing how the work serves the company.

Learned Patterns of Persuasion

There are a few consistent takeaways that will guide anyone about to walk into a significant meeting:

  • Business leaders rarely understand the impact of UX unless it is made explicit.
  • UX terminology is overloaded with terms that carry multiple meanings.
  • Projects that sound like initiatives without clear business outcomes rarely gain support.
  • Explaining UX work through business goals gets attention.
  • Showing how success will be measured builds credibility.
  • Stories about business value are stronger than stories about empathy or friction.

The path to being understood isn’t louder advocacy. It is carefully chosen language. Approaching design presentations with the same strategic rigor used for the actual research and interface work will eventually bring stakeholder support — because once the business sees how the design team makes everyone’s work more effective, the “fight” disappears.

Think about the language those in other departments use daily and use it where it applies. Directors, product managers, engineers, and finance will and value what they can finally see clearly.

There are useful starting points for those looking to how to frame design in business language. The book Business Thinking for Designers by Ryan Rumsey and the course Business For Designers (d.mba) by Alen Faljic are widely referenced for these conversations. Jared Spool’s “Five Things That Business Cares About” (on Twitter) and Jason Fried’s commentary on the language of corporate combat are also frequently cited. Andy Budd discusses the direct impact of design on Twitter, and Joe Natoli has argued for ending the dominance of UX terminology. For storytelling in research context, notably.ai hosts an article by Allison Grayce Marshall. Vitaly Friedman’s piece on defending design decisions continues the line of thought around presenting work to stakeholders.