Case study / Experimentation strategy and governance
From an A/B testing tool to a £50m global experimentation programme
An international B2B ecommerce business had the tools, the ideas and the appetite for optimisation. What it needed was ownership, experimental rigour and a repeatable way to turn activity into commercially useful decisions.
01 / The challenge
Testing activity is not the same as an experimentation programme
The business was already doing CRO, but there was no single owner bringing the work together. It had built a substantial backlog of ideas without an agreed way of deciding what to do first.
The A/B testing platform was sometimes being used like a shadow content management system to put short-term promotions live. That made it easy to launch activity, but launching activity was not the same as generating reliable evidence.
There were also gaps in experimental practice. Sample sizes and test durations were not consistently planned in advance, tests could be stopped early, and checks such as sample ratio mismatch (SRM) were not embedded in the process.
The business wasn't short of ideas or technology. It was short of a reliable way to decide what deserved testing, run those tests properly and act on the findings.
My remit: take ownership of the programme, introduce the necessary process and safeguards, and deliver measurable commercial value.
02 / Building the operating model
Make prioritisation provisional, then validate it with evidence
With a large backlog, the first task was to stop treating every idea as equally valuable. I introduced a weekly rhythm that combined the team's knowledge with subsequent analysis before committing to the next set of activities.
Tuesday
Review and shortlist
Discuss the ideas backlog with the team and make an initial, judgement-led assessment of opportunities worth investigating.
Between sessions
Gather the evidence
Look at the supporting data, interrogate the assumptions and adjust priorities where the evidence warrants it.
Thursday
Validate and commit
Return with a firmer prioritisation, agree the decisions with the team and plan the following week's work.
The initial shortlist was deliberately not the final decision. It gave the team a practical starting point while leaving room for evidence to overturn an early assumption.
Standardised experiment planning
Introduced a formal experiment document with predefined:
- Primary KPIs and other measures
- Sample-size requirements
- Planned test duration
- Guardrail metrics and evaluation criteria
These requirements were intended to prevent ad hoc evaluation and premature decisions.
Consistent learning and reporting
Established monthly reporting that brought together experiment results and what the team had learned.
The aim was to improve visibility, retain knowledge and make the programme accountable for decisions rather than the volume of tests launched.
03 / Operating internationally
One central programme, informed by local markets
The programme covered 43 countries, so running every experiment independently everywhere would have been impractical. We organised the work across three broad regions: North America, Europe and Asia.
Six priority markets were tested individually. For the remaining countries, we used results from the relevant leading market to inform rollout decisions. That was a pragmatic deployment model, not a claim that identical effects had been experimentally proven in all 43 countries.
The country marketing teams played an active role. They suggested opportunities, reviewed ideas for local relevance and helped translate experiment content. Experimental standards remained centralised; local knowledge influenced what was useful and appropriate to test.
What stayed central, and what was local?
Central programme
- Governance and prioritisation
- Test plans and quality standards
- Analysis and results reporting
- Programme-level commercial accountability
Country teams
- Market-specific ideas and context
- Review of proposed changes
- Language and translation support
- Feedback on local relevance
04 / Experimentation in practice
Fixing genuine customer dead ends
Two experiments from the programme illustrate the type of customer problem we prioritised. They will each have their own deeper case study; here, they show how the programme translated evidence into action.
Example one / On-site search
When a search returned no results
A substantial proportion of on-site searches returned no results, leaving customers who had actively expressed purchase intent at a dead end.
Optimising the no-results experience reportedly delivered a 14% uplift in orders. The original experiment documentation should be checked before adding further detail about the design or statistical analysis.
Example two / Product availability
When a product was unavailable or discontinued
Customers encountering out-of-stock or no-longer-stocked products needed a useful next step rather than a journey that simply stopped.
An experiment involving product alternatives delivered a reported 5.67% relative uplift in order conversion. The absolute conversion rates are withheld. This was an individual experiment result, not a separate addition to the programme’s headline revenue figure.
05 / Commercial impact
£50m attributed to experimentation, with benefits beyond the test programme
Partway through the engagement, an external management consultancy assessed the programme's contribution. Based on my recollection, its work drew on projected experiment uplifts and year-end business performance, and attributed approximately £50m in additional annual revenue to the experimentation programme.
This is a historical programme-level attribution, rather than an independently re-calculated figure from experiment-level data available today.
There was a further commercial effect. Improvements in conversion rate, average order value and margins helped support increased programmatic advertising investment in selected markets. The business reported around £50m of wider ecommerce revenue growth associated with that expansion.
That second figure should not be presented as another £50m directly caused by experimentation, or automatically added to the headline as a £100m experimentation outcome. Paid media investment was another contributor, and the figures may not be wholly independent.
~£50m
Annual additional revenue attributed to experimentation through a historical external assessment.
~£50m
Broader ecommerce growth associated with additional acquisition investment, enabled in part by improved trading economics.
06 / What mattered
The value was in better decisions, not more tests
There was no shortage of enthusiasm for testing at the start. The difference came from putting a repeatable system around it: a way to challenge priorities, plan experiments before they launched, protect against unreliable conclusions and share what was learned.
The international model mattered too. Central governance created consistency, but local teams helped ensure the programme remained connected to actual market conditions.
Perhaps most importantly, improved conversion performance had consequences beyond the experimentation team. It helped inform where the wider business could afford to invest for growth.
An A/B testing platform lets you run experiments. An experimentation programme helps you make better business decisions.
Evidence and transparency
A retrospective case study
How to interpret the figures
This case study is a retrospective account of a historical engagement and has been anonymised to protect client confidentiality. The £50m experimentation attribution and the further £50m ecommerce growth figure are recalled programme-level assessments; the underlying external consultancy calculations and original year-end reconciliation have not been provided for independent review.
The two example experiments are reported using results from the existing case-study inventory, pending verification against source experiment reports. Experiment-level effects should not be summed with programme-level attributions. Individual-market rollout does not establish that an experiment had the same effect in every country.
Measure → Trust → Understand → Experiment → Improve
Need a programme that produces evidence you can act on?
Conversions Matter helps organisations bring structure, measurement trust and commercial accountability to analytics and experimentation.
Discuss your experimentation programme

