How to Explain UX to Your Board (Without the Jargon)

Why do boards tune out UX presentations?

Because most of them answer a question nobody asked. “We need to improve the user journey” sounds like a preference. “Our signup flow loses 7 out of 10 customers who start it, worth roughly SAR 1.2M a year in lost revenue” sounds like a problem with a price tag — and boards are very good at solving problems with price tags.

The vocabulary is the first casualty. Words like heuristic, wireframe, empathy map, and delight mean nothing outside the design team. Worse, they signal that the request comes from a craft discipline asking for resources, not a business function returning them.

——————

You have twelve minutes in a board meeting to get a design budget approved. If you spend them explaining what UX is, you’ve already lost. The directors in that room don’t need to understand design. They need to understand what it returns.

Here’s how to run those twelve minutes.

What language do boards actually respond to?

Three buckets, and only three:

• Revenue. Conversion lift, retention improvement, higher average order value. A redesign of a money-making flow is a revenue project that happens to involve designers.

• Cost. Support ticket reduction, engineering rework avoided, faster onboarding of staff. In our audit work, confusing screens reliably turn out to be top ticket generators — every one of those tickets has a cost your CFO already tracks.

• Risk. Accessibility compliance, churn to competitors, failed launches. “We are about to spend nine months building something users may reject” is a risk statement, and research is the insurance.

If a design activity doesn’t fit one of these buckets, don’t bring it to the board.

How do you structure the ask?

One metric per slide, in this order:

1. The problem, priced. “Checkout abandonment costs us SAR X per month.”

2. The cause, shown. A 20-second clip of a real user failing the task beats any chart. Boards trust what they can see.

3. The fix, scoped. What you’ll do, how long it takes, what it costs.

4. The return, estimated. Payback period with conservative assumptions — claim 60% attribution and say so. Understated numbers survive scrutiny; inflated ones lose you the next budget.

5. The proof, if you have it. Results from your last design project: before and after numbers, not screenshots.

What mistakes kill the pitch?

• Asking for process instead of outcomes. “We need a research practice” gets a no. “We need to find out why renewals dropped 12%” gets a yes.

• Citing industry benchmarks as your case. Forrester’s $100-per-$1 UX return is fine as a footnote. Your own funnel data is the argument.

• Bringing mockups. Visuals invite taste debates from people whose taste isn’t the target market. Numbers close; screens open arguments.

What if they still don’t get it?

Run a pilot. One flow, one round of user testing, one measured result, SAR 25,000–50,000 instead of a full program. Boards that won’t fund a strategy will fund an experiment — and a single filmed session of a real customer failing to complete a purchase usually does what six slides couldn’t.

If you need the numbers and the evidence to make this case — baselined metrics, filmed user sessions, a priced problem list — that’s exactly what our UX strategy consulting produces. Book a strategy call →