A practical operating model for conversion rate optimisation that turns customer evidence into prioritised tests, useful decisions and better website journeys.
Quick answer
Conversion rate optimisation works best as a learning system: define the customer job, diagnose the journey, choose one evidence-backed hypothesis, test it with an appropriate comparison and judge both the immediate action and its downstream quality. The objective is not more clicks at any cost; it is more useful progress with fewer avoidable barriers.
CRO is often reduced to button changes and landing-page ideas. That makes activity easy to produce but learning difficult to accumulate. A stronger programme begins with the decisions visitors are trying to make and the evidence that explains where those decisions break down.
This operating model is deliberately channel-neutral. It can be applied to organic, paid, lifecycle and direct journeys, while keeping the website experience and the quality of the resulting customer action in view.
Define the customer job and the business outcome
Start with the progress the visitor needs to make, then name the business outcome that would represent genuine value.
A pricing-page visitor may need to understand plan fit; a campaign visitor may need proof that the advertised promise is credible. Those are clearer starting points than a generic instruction to increase conversion rate.
Pair the immediate event with a downstream quality signal. A form submission can be useful, but qualification, attendance, activation or purchase may reveal whether the apparent improvement reached the right people.
- Customer job in plain language
- Primary outcome and downstream quality signal
- Experience guardrail such as errors, exits or support demand
Diagnose before adding ideas to the backlog
Use behavioural, qualitative and technical evidence to explain the barrier before proposing a treatment.
Review query or ad intent, page hierarchy, analytics events, recordings or feedback, mobile states and the hand-off after the primary action. One signal rarely proves the cause, but several aligned signals can justify a focused hypothesis.
Separate visibility, comprehension, motivation and completion. A CTA may underperform because people never see it, because the promise is unclear, because the offer is weak or because the next step fails. Each diagnosis needs a different change.
Run the smallest test that can change a decision
A good experiment isolates a meaningful uncertainty and states in advance what the team will do with each plausible result.
Google Ads recommends a clear hypothesis tied to a business goal and warns that changing multiple factors can make the result hard to interpret. The same discipline applies on-site: keep the treatment coherent and avoid bundling unrelated redesign work into one comparison.
Not every question needs an A/B test. Usability defects, broken links and inaccessible controls should be fixed directly. Controlled tests are most useful when reasonable people disagree and enough eligible traffic exists to inform the choice.
Turn every result into reusable knowledge
The value of a CRO programme is the quality of its next decision, not the volume of completed experiments.
Record the audience, evidence, hypothesis, treatment, primary metric, guardrail, result and limitations. A neutral result may still show that the assumed barrier was not important or that the test could not detect a useful change.
Review learning across page types and journeys. Patterns can guide prioritisation, but avoid turning one local result into a universal rule. Context remains part of the evidence.
Further reading
Sources
- Test with confidence with the Experiments page — Google Ads Help
- Set up events in Google Analytics — Google for Developers
- Web Content Accessibility Guidelines 2.2 — W3C
