EN
Back to the archive

The archive · Work & Ways of Doing · Operational decision · 2007–2017

Booking.com wraps every product change in an A/B test — 1,000+ live at once

Booking.com made experiments the default decision system: every change ships inside a test, 1,000+ live at once, with a searchable history of wins and failures.

Booking.com

The ideaMake experimentation the default decision system: every change, even bug fixes, ships wrapped in an A/B test, and anyone can launch, read history and stop harmful tests.substantial

What it had to solve

As Booking.com grew into one of the largest travel marketplaces, product teams risked deciding features by opinion. The company had run online controlled experiments for more than a decade and wanted everyone, not just product managers, to validate ideas cheaply, safely and with trustworthy data.

How it works

At Booking.com, experimentation is not a tool some teams use — it is how the company decides. For more than ten years the travel platform has run evidence-based product development, and by 2017 its departments were running and analysing more than a thousand concurrent experiments on any given day, across mobile apps, hotelier tools, customer-service phone lines and internal systems.

The deliberate choice was democratization. The experiment platform acts as a searchable repository of every success and failure since the very first experiment, so anyone can consult history and form new hypotheses. Generic APIs abstract away recruitment, randomization and reporting, and each department has its own dedicated support team, so running a test does not require permission from product management.

Trust came from engineering discipline: two separately maintained pipelines compute the same metrics and are monitored against each other, a pool of A/A experiments validates the statistics, and safeguards such as pre-registration and peer review of successes curb p-hacking. Everyone in the company is empowered to stop a harmful experiment themselves.

The result was a company where 'every change, from entire redesigns and infrastructure changes to bug fixes, is wrapped in an experiment,' as the engineers wrote in a 2017 paper — turning product development into a stream of measured bets rather than a series of opinions.

Why it lands

  • Decentralizing experiments let thousands of people test ideas instead of waiting for product managers to prioritize them.
  • A searchable history of successes and failures lets teams revisit and build on each other's learnings.
  • Trustworthy infrastructure (dual pipelines, A/A pools, pre-registration) made evidence acceptable as the arbiter of decisions.
  • Keeping the experiment platform loosely coupled to business logic made shipping a winning change as simple as removing one API call.
  • Empowering anyone to stop a harmful experiment kept safety compatible with speed.

What it did

More than 1,000 experiments run concurrently across mobile apps, hotelier tools, customer-service phone lines and internal systems; every redesign, infrastructure change and bug fix is wrapped in a test, so product decisions moved from opinions to evidence and learnings are reused across teams.

Write-upRead the Booking.com paper

What you can take

You don't need consensus on an opinion if everyone can run a cheap, safe experiment: infrastructure plus an evidence culture turns decisions into tests, and failures into shared, searchable learning.

Since then

The in-house framework, written by Amsterdam engineers in the mid-2000s, has been extended but never rewritten; in 2026 Silicon Canals reported Booking.com still runs more than 1,000 concurrent tests on the live production booking page and tens of thousands of cumulative experiments per year, where a 0.1% conversion shift is an eight-figure sum. The pattern spread across the industry as 'experimentation culture' — vendor platforms, public playbooks and other tech companies adopted the same default-to-test model that Booking.com had pioneered.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe the brief you are staring at, and see who has been given the same problem.

Free account · 3 free questions · no card

Related cases