Growth8 min read
The hidden cost of a bad user experience
Poor UX rarely appears as a line item. It hides inside support costs, sales cycles, training budgets and churn, which is exactly why it goes unfixed for so long.
By Strategy Practice, Brand, strategy & AI
Ask a finance team what bad UX costs and you will usually get a blank look. Not because the cost is small, but because it never appears in one place. It is distributed across support, sales, customer success, training, engineering and operations, a little in each, owned by nobody.
That distribution is the reason poor experiences survive for years. Each team absorbs its share as a normal cost of doing business. The total is never added up, so it never competes for budget against things that are.
Where the cost hides
| Area | How bad UX shows up | What to count |
|---|---|---|
| Support | Tickets asking how to do things the product should make obvious | How-to tickets per month and handling time |
| Onboarding | Long implementation, hand-holding, training sessions | Hours per new customer |
| Sales | Longer demos, more objections, more proof required | Average deal length and stage drop-off |
| Operations | Internal staff working around clumsy tools | Time per task and error rework |
| Retention | Customers leaving for an easier competitor | Churn reasons mentioning usability |
Internal tools are the quietest cost of all
Customer-facing products at least get complaints. Internal tools get workarounds. A claims handler who spends extra minutes per case fighting a clumsy screen will not file a ticket. They will build a spreadsheet, ask a colleague, or simply be slower, every day, for years.
Multiply a small daily friction by the number of people doing it and the number of working days in a year, and internal UX often turns out to be among the larger operational costs in the business. It is just never labelled as such.
Estimating the cost with data you already have
You do not need a research programme to put a first number on this. Most of the inputs already exist.
- Pull a quarter of support tickets and tag the ones caused by the product being unclear rather than broken.
- Multiply by average handling cost.
- Add onboarding and training hours per customer that exist only because the product is hard to learn.
- Add internal time lost to workarounds, sampled from a few days of observation.
- Add churn where usability is named as a reason, valued at lifetime revenue.
What changes once the cost has a number
Design discussions without numbers become debates about taste, and taste debates are won by seniority. Once poor UX has an annual cost attached, the question changes from 'do we like this?' to 'is fixing it worth more than it costs?' That is a question finance teams are very good at answering.
Bad UX is rarely cheap. It is just paid for in instalments, by people who do not know they are paying.
Strategy Practice
Brand, strategy & AI
The strategy practice covers positioning, product strategy, UX diagnosis and AI opportunity work. It writes about the commercial reasoning behind design decisions, and the organisational conditions that make good products possible.
