I've sat through plenty of meetings where someone made a genuinely good case for UX work and got precisely nowhere. On more than one occasion in the past that someone was me. I have found myself standing in front of a slide covered in personas while the finance director quietly lost the will to live. The work was solid, my arguments were rubbish. But over the years I have learned.
You see, most in-house teams lose this argument because they make the case for UX in the language of UX, to an audience that has never once been rewarded for caring about it. So senior managers nod politely, agree that it all sounds very interesting, and then fund the project that turned up with a number attached to it.
So I want to walk through how you build a business case for UX work based on my years of mistakes. I am not necessarily talking about a formal document with a cover sheet and an approvals matrix, but any argument solid enough to get the work you need signed off.
Nobody cares about UX as much as you do
And why would they? You don't care about health and safety, and you'd glaze over inside 30 seconds if the accounts team started walking you through their reconciliation process, however lovely their diagram. Everybody has their own patch and defends their own patch, and UX happens to be yours, which means the translating is your job rather than theirs.
That means selling UX rarely involves talking about users at all, which I admit feels like a small betrayal of everything we bang on about at conferences. Yes, talking about users is how we do the work. But, talking about business risk and opportunity is how you get permission to do the work in the first place.
Risk for the comfortable, opportunity for the hungry
A good business case leads with the risks and opportunities your proposal addresses, and the framing you pick depends enormously on the mood of the organization you happen to work for.
If you're in a big, established, comfortable business, the risk of doing nothing is your strongest card, because these organizations have plenty to lose and a deep institutional fear of losing it. Talk about customers drifting to competitors with a better signup process, or support costs climbing because the website can't answer a simple question.
If the business is newer and hungrier, flip it around and sell the upside, because nobody in a fast-growing company is lying awake worrying about protecting what they already have. There the conversation is about the sales you could win, the markets you could reach, and the growth currently leaking out of a checkout nobody has looked at properly.
Work out who you actually need to convince
Before you write a word, get clear on whose signature you need, what that specific person is measured on, and how your proposal makes their year easier. Business goals are useful, but personal goals are what get budget released, and the person approving your work has targets, a boss, and a nagging worry of their own.
The emphasis shifts depending on where you work, and in my experience it breaks down roughly like this:
Commercial businesses. Pick either customer acquisition or retention and build the case around one of them rather than gesturing at both.
Government and public sector. Focus on reducing risk, avoiding the sort of failure that ends up in the press, and improving the profile of the service.
Charities and non-profits. Talk about fundraising, supporter engagement, and building the profile of the cause.
But, cost savings work almost everywhere, and they're badly underused by UX people who would rather talk about delight. Fewer support calls, less staff time spent on manual workarounds, and fewer expensive rebuilds are all things a CFO understands without any translation from you.
Use numbers, even wobbly ones
Wherever you can, tie your case to hard figures, and don't let the fact that they're estimates stop you. Be honest that they're estimates, explain the assumptions behind them, and offer to do a more detailed analysis if the decision hinges on it. A rough number invites a conversation, while no number invites a polite no.
If the maths makes you nervous, I built an ROI calculator that does the heavy lifting for you, so you can walk in with something more persuasive than a strong feeling.
Beyond the numbers, get people excited about what's possible, because approval is an emotional decision dressed up in a spreadsheet. Vibe code a rough prototype, mock up the improved journey, or build something shiny that stakeholders can see and immediately want. I've watched a scrappy 2 day prototype do more for a business case than 40 pages of analysis ever managed.
What goes into the case
Strip away the formatting and every decent business case answers the same handful of questions:
The diagnosis. What's the problem or the opportunity, described in business terms rather than UX ones.
The work. What you're proposing to actually do.
The objective. What success looks like, and how you'll know you got there.
The evidence. What research, data, or experience supports your case.
The practicalities. What needs to happen, in what order.
The resources. What you need in people, time, and money.
The first step. One small, well defined thing you can start on now.
Ask for less than you want
Those last two points are where most business cases die, usually because they ask for too much in one go. Focus on reallocating resources you already have rather than requesting new money, especially at the start, because moving a designer onto a project for 3 weeks is a much smaller decision than approving a budget line.
Don't ask anyone to sign off on the whole plan either. Build momentum with a small first step, whether that's a prototype, a limited pilot, or a focused piece of research, and make sure it's something you can deliver quickly so people see progress while they still remember agreeing to it.
Then define, up front, what results would justify committing to the rest, so the next conversation becomes a matter of pointing at evidence everyone already agreed would be convincing.
None of this is as satisfying as being handed budget because the work is obviously the right thing to do, and I spent years waiting for that to happen. It never did, so I learned to talk about money instead, and the UX work finally started getting approved.
If you've got a case to make and no idea where to start with the figures, I can actually help with the process. You can learn more here.
No comments:
Post a Comment
Keep a civil tongue.