CRO vs UX: Why You Need Both, Not One
Conversion Rate Optimisation and User Experience Design are often treated as competing disciplines. They're not — and the best results come when
The tension between CRO and UX is one of the most persistent misunderstandings in digital product practice. CRO teams want to optimise for measurable conversion outcomes. UX teams want to optimise for user needs and experience quality. Positioned as a competition, CRO wins in the short term and users — and ultimately the business — lose in the long term.
Positioned as a collaboration, CRO provides the rigour and measurement framework that UX needs; UX provides the human understanding that CRO needs. The combination produces results that neither discipline achieves alone.
The Dalata Case
On the Dalata Hotel Group project, the CRO programme wasn't a separate workstream from the UX design — it was the testing framework through which the UX redesign was validated and refined. The room selection flow, the booking funnel, and the loyalty member experience were all A/B tested against the existing designs before being fully rolled out.
This approach served two purposes. First, it provided commercial justification for design decisions that might otherwise have been contested on subjective grounds — if the redesigned room selection flow outperforms the existing one by a statistically significant margin, the argument for it is settled. Second, it surfaced refinements that wouldn't have emerged from UX research alone — specific interaction details that performed better in practice than the design team predicted.
The AA Ireland Programme
The AA Ireland digital programme was explicitly structured as a CRO programme from the outset — a 'test and adapt' cycle that ran continuously across the website's key conversion journeys. The UX design provided the hypotheses to test; the CRO programme provided the evidence for or against them.
The outcomes — 50% growth in car insurance conversions and 35% growth in AA Membership — weren't achieved through a single redesign. They were achieved through dozens of iterative improvements, each one validated before the next was built.
A Framework for Combined Practice
- UX research identifies problems and generates hypotheses. CRO testing validates which solutions work best.
- Set up testing infrastructure before you need it. The most common reason CRO programmes fail is that the testing infrastructure isn't in place when it's needed.
- Distinguish between optimisation and innovation. CRO is excellent at optimising existing journeys; it's a poor tool for discovering that the journey itself needs to be fundamentally rethought. That's UX research's job.
