Why Design Still Loses in the Boardroom (and How to Change It)

Design often loses influence because it presents outputs, not business decisions. Here is a practical way to reframe design work in risk, revenue, and execution terms leaders can back.

I've sat in maybe two hundred boardrooms over the last fifteen years. CEOs in Bangkok, CFOs in Singapore, founders in London, product VPs in San Francisco. The pattern repeats with painful consistency. The design leader presents. The work is beautiful, the user research is rigorous, the slides are well-crafted. And then the CFO opens their mouth and asks one question that derails everything: "What's this worth to us?" The room goes quiet. The design leader, who has rehearsed every craft justification known to humans, suddenly has nothing to say. And in that silence, the budget gets cut, the headcount gets frozen, and the strategic seat at the table goes to someone else.

This isn't a craft problem. The work is usually fine. It's a translation problem. And it's the single biggest reason design teams stall at the same headcount year after year while engineering and product double every twelve months.

The boardroom doesn't care about your process

Here's the uncomfortable truth I learned the hard way at True Digital. Boards don't fund process. They don't fund double-diamonds, jobs-to-be-done frameworks, or atomic design. They fund outcomes that show up on the P&L. When a design leader walks in and explains how the team ran a six-week discovery phase, the CFO is already mentally calculating burn rate. When the same leader walks in and says "we lifted retention by eleven percent and that's worth roughly four million in annualised revenue," the conversation changes shape entirely.

The mistake most design leaders make is assuming the board needs to understand design to value it. They don't. They need to understand its impact in the same units they think in: money, time, and risk. Your job is to do that translation work before you walk in the room, not to teach the board to think like designers.

The three numbers every design leader should know cold

Before any board meeting, I make sure I know three numbers about every initiative I'm presenting. These are non-negotiable. If I can't answer them, I don't go in.

1. Cost of the current problem in annualised dollars, meaning actual lost revenue, support tickets, churn, and conversion drop, not abstract "poor UX".
2. Cost of doing the work, including design hours, engineering, research, and opportunity cost of what you're not building.
3. Confidence-weighted projected return, and what would have to be true for that return to materialise.

When I worked on the True VROOM platform, we didn't pitch it as "a better tool." We pitched it as "a tool that takes our internal sales team's process from forty-five minutes per quote to under five minutes, multiplied by twelve thousand quotes a year, valued at internal labour cost of $X per hour." That's a number an exec can act on. The fact that it ended up being award-winning was a bonus. The board approved it because the math made sense.

Stop saying "user-centred." Start saying "customer behaviour."

Language matters more than designers want to admit. "User-centred design" is a phrase that signals "design conference" to anyone outside our discipline. It instantly puts us in the soft-skills box. "Customer behaviour" signals revenue. "Conversion friction" signals lost money. "Time to first value" signals retention. Same concepts, completely different reception.

I made this swap deliberately about ten years ago and the difference in how execs respond is night and day. When I run my Design Leadership Mastery sessions, I have leaders rewrite their last three internal proposals using only language a CFO would use. Most of them are shocked at how much sharper their thinking becomes once the jargon comes out.

Bring a hypothesis, not a portfolio

Boards aren't impressed by craft. They're impressed by leaders who think commercially. Walk in with a hypothesis: "I believe we're losing about $2.4M a year to onboarding friction, and I want to test a fix in Q2 with a $180K budget. Here's how we'll know it worked." That positions you as a peer to the CFO, not a vendor. Beautiful screenshots can come later, in the appendix, where they belong.

When I helped reposition design at NBC Direct Brokerage, every initiative had a hypothesis card before it had a Figma file. The card had four lines: assumption, evidence, expected outcome, kill criteria. That single artefact moved us from "the design team" to "the team that moves the metric."

Make the cost of inaction visible

The most powerful slide I ever built was a single chart showing the cumulative cost of doing nothing: twelve months of compounding churn, support load, and lost opportunity if the board passed on the project. It wasn't a pitch. It was a forecast. The room went quiet for a different reason that day, and the work got funded inside a week.

If your design work matters, it matters in dollars. If you can't make that case, the work doesn't matter to the people writing the cheques, no matter how well-crafted it is. The good news is this is a learnable skill, not a personality trait. Start with one initiative, build one cost-of-inaction model, present it once, and watch the room shift.

One last warning from the trenches: don't outsource the financial framing to your finance partner once they're on side. The moment design stops doing the maths, finance starts doing it for you. And finance will always pick the conservative number. I've seen a single onboarding redesign at True Digital recosted three times across three quarters because nobody on the design team owned the model. By the time the project shipped, the projected uplift had been quietly halved and the bonus pool with it. Own the model, own the story, own the outcome. Hand it over only when the result is in the bank.

Where to start this week

Pick the one piece of work you most want funded next quarter. Spend two hours with someone in finance, not to ask permission, but to learn how they model value. Then rewrite your pitch in their language. Practise the three numbers out loud until you can say them without notes. Walk into your next board meeting and make a quiet bet with yourself: today, design speaks the language of the business. That's how the boardroom argument gets won. Not by being louder, but by being legible.

In short

Practical checklist

• State the commercial problem in revenue, cost, time, or risk.
• Present three numbers: current cost, intervention cost, projected return.
• Define success and kill criteria before requesting budget.
• Use board language, not design-process language.
• Close with the cost of inaction over 6–12 months.

When to use this approach (and when not to)

• Use this approach when decisions carry customer, revenue, or delivery risk.
• Use it when multiple teams need consistent quality standards.
• Use it when you need repeatable outcomes, not one-off output.

• Do not argue design quality alone when the room is deciding risk, revenue, and execution trade-offs.
• Do not enter finance conversations without naming at least one explicit trade-off and who owns the numbers.
• Do not mistake executive confidence for proof—bring assumptions, ranges, and sources into the open.

If this is the conversation you're stuck in

If this is the conversation your team is struggling with, start with one initiative and one finance-aligned model. If useful, I can help your leadership team build that translation muscle through a focused workshop.

Frequently asked questions

Why does design lose influence with senior leaders?

Because design is often presented as output quality rather than decision quality. Leaders back decisions tied to risk, growth, and execution outcomes.

What should design leaders change first?

Translate design proposals into business choices: what risk is reduced, what speed is improved, what customer or revenue impact is expected, and what trade-offs are involved.

What should go in a board-ready design proposal?

A clear commercial problem, intervention cost, expected return, confidence level, and downside if nothing changes.

How do I handle pushback from finance stakeholders?

Treat pushback as model calibration. Bring assumptions, sensitivity ranges, and evidence sources, then adjust transparently.

What is a good first step this week?

Reframe one active design initiative in business terms and rehearse it with a finance partner before your next leadership review.