Opinion and commentary about Mac and iOS applications, publishing and content consumption behavior, web and cloud architectures
October 14, 2009

On A/B testing and actionable metrics

Applying ☞ A/B testing is not as easy as one would think and the results are heavily depending on having a correct, well thought set of metrics. Even more important: these metrics should be actionable metrics

  • Any team can create a true split-test experiment that affects only the sandboxed parts of the product, however:
  • One team must see the whole experiment through end-to-end.
  • No experiment can run longer than a specified amount of time (usually a few weeks).
  • No experiment can affect more than a specified number of customers (usually expressed as a % of total).
  • Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics.
  • Any team that creates an experiment must monitor the metrics and customer reactions (support calls, forum threads, etc) while the experiment is in-progress, and abort if something catastrophic happens.