Fast garbage is still garbage: The true cost of skipping UX

In 2026, generative AI has given us the remarkable ability to build the wrong product faster than ever before. We can spin up code and deploy features instantly, entirely skipping the supposedly “slow” work of actual user discovery.

“Why would we pay for user research? The AI already generated the personas and the wireframes.”

– A budget-conscious stakeholder, somewhere

Why are companies so desperate to avoid talking to their users? Is it because they think an algorithm has magically developed human empathy? Is it because they don’t want to hear that their brilliant idea is actually quite dodgy? Because neither of those issues will be fixed by shipping code faster.

When you skip UX research, you aren’t saving money. You are just deferring the cost until after the product launches.

The cost of moving fast

Development hours are incredibly expensive. Throwing a highly paid engineering team at an unvalidated problem is a fantastic way to burn through your budget while delivering absolutely zero value to the customer. Even if you’ve equipped your team with Claude, you’ll be burning tokens building the wrong thing.

We like to pretend that shipping quickly mitigates risk. If we build the wrong thing, we just pivot in the next sprint, right? Right??

Except we very, very rarely do. We move onto the next thing, the next shiny feature to tantalise customers with, and it’s an incredibly expensive way to run a business.

Failing when it’s cheap

Pivoting code is hard. You have to untangle technical debt, rewrite backend logic, and somehow explain to the board why the last three months of development were essentially a waste of time.

“We’ll just fix the usability issues in phase two.”

– A product manager about to learn a very expensive lesson

Why do we accept this? Why is it perfectly acceptable to spend fifty grand on development just to find out a feature is useless, but it’s “too expensive” to spend a fraction of that on a UX researcher to validate the idea first?

Good UX is the ultimate risk mitigation tool because it allows you to fail when it’s cheap. We can scrap a dodgy wireframe in ten minutes. We can pivot a prototype after a handful of user interviews.

By the time a developer even looks at a Jira ticket, we already know the solution passes the sniff test. UX ensures you make the right thing, rather than just making a broken thing incredibly quickly.

AI as a sidekick, not a replacement

There is a massive misconception that AI is here to replace the UX team. It isn’t.

AI is here to handle the noise. For years, researchers have been bogged down by the administrative nightmare of our own profession. We spent weeks transcribing interviews, colour-coding sticky notes, and trying to pull common threads out of chaotic user ramblings. Not to mention the faff of handling recruitment and creating well-balanced user pools.

It was a massive waste of specialist talent. But now, we can feed hours of qualitative data into an LLM and run AI-assisted thematic analysis in a fraction of the time. We can create AI skills to find potential participants by looking through Salesforce, rather than us cold calling stale customers.

Tools like Dovetail or Conveo can instantly auto-code existing interview data, run sentiment analysis, and group messy qualitative data into initial thematic clusters. You don’t have to manually tag fifty transcripts just to figure out that users find the checkout process confusing. The AI highlights the pattern, links it back to the timestamped source clips, and lets you focus on what actually matters.

Doing better research

When you let AI handle the admin, you buy your staff capacity.

Capacity to run longer research projects, run workshops with customers and internal stakeholders, ask deeper and more probing questions because we know that we’ll have a little buddy on the other side helping us with the analysis.

In 2026, the value of UX staff isn’t in data processing. It’s in strategic thinking, human connection, and making sure the business actually builds the right thing.

Scroll to Top