40
Fail and Win: Why a Failed Test Isn’ Caleb Whitmore Founder & CEO Analy<cs Pros @CalebWhitmore

Fail and Win: Why a Failed Test Isn’t a Bad Thing

Embed Size (px)

Citation preview

Page 1: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Fail  and  Win:  Why  a  Failed  Test  Isn’  

Caleb  Whitmore  Founder  &  CEO  Analy<cs  Pros  

@CalebWhitmore  

Page 2: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Hi,  I’m  @CalebWhitmore  

Page 3: Fail and Win: Why a Failed Test Isn’t a Bad Thing

I  climbed  a  mountain…  once.  

Page 4: Fail and Win: Why a Failed Test Isn’t a Bad Thing

I  work  @Analy=csPros  

Page 5: Fail and Win: Why a Failed Test Isn’t a Bad Thing

And  get  to  work  with  some  awesome  clients!  

Page 6: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Why  Test?  

Page 7: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Why  Test?  

TESTING…    •  Should  focus  on  improving  an  outcome  •  Is  the  shortest  distance  between  you  and  improvements  •  Is  done  best  with  rapid  itera<on  and  lots  of  data  

Page 8: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Some  things  may  seem  obvious  to  test…  

Page 9: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Bad  Form  

Page 10: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Good  Form  

Page 11: Fail and Win: Why a Failed Test Isn’t a Bad Thing

But  you  should  s=ll  test  them!  

Page 12: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Tes=ng  depends  on  data  

Page 13: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Op=mizely  Data  

Page 14: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Google  Analy=cs  Data  

Page 15: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Not  all  tests  are  created  equally  

Page 16: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Some  tests  will  win  

Page 17: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Some  tests  will  fail  

Page 18: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Is  winning  a  success?  

Page 19: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Is  failing  a  loss?  

Page 20: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Tes=ng  is  a  Success  When:  

•  A  process  is  followed  

•  An  outcome  is  measured  

•  A  complete  picture  is  seen  

Page 21: Fail and Win: Why a Failed Test Isn’t a Bad Thing

When  Things  Shake,  What  Moves?  

Page 22: Fail and Win: Why a Failed Test Isn’t a Bad Thing

When  Things  Shake,  What  Moves?  

Page 23: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Crea=ng  a  360  Degree  View  

•  A  test  will  impact  more  than  what  you  intended  

•  You  must  measure  the  impact  across  your  spectrum  of  user  interac<on  

• Measure  your  test  with  your  exis<ng  infrastructure  

Page 24: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Crea=ng  a  360  Degree  View  

What  happens  to…  •  The  “key”  conversion  point  •  Engagement  on  the  test  page  •  Length  of  the  en<re  visit  •  Total  pageviews/interac<ons  in  the  visit  •  Secondary  conversion  goals  –  view  product,  view  content,  start  checkout,  download  a  file,  etc…  

Page 25: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Here’s  an  example  

Page 26: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Example  Experiment  

ASSUMPTIONS  •  Auto-­‐play  repels  visitors  – Audio  without  warning  

•  Thus,  bounce  rates  are  high  and  more  people  leave  •  Turn  off  auto  play  &  more  people  will  stay  and  engage  

Page 27: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Op=mizely  Shows  a  Winner  

Page 28: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Bounce  Rate  Improved  

Page 29: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Purchase  Rate  Tanked!  

Page 30: Fail and Win: Why a Failed Test Isn’t a Bad Thing

DO  THIS  

Page 31: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Setup  a  360  Degree  View  of  Tests  

•  Tip:  your  Digital  Analy<cs  plaXorm  has  this  view  already!  

Page 32: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Op=mizely  Automated  Integra=ons  

Page 33: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Pipes  data  straight  into  GA  

Page 34: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Is  this  a  good  outcome?  

Page 35: Fail and Win: Why a Failed Test Isn’t a Bad Thing

What  about  this?  

Page 36: Fail and Win: Why a Failed Test Isn’t a Bad Thing

See  the  full  picture  

Page 37: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Capture  Experiment  Data  

•  Tie  experiment  data  into  your  Tag  Management  and  Digital  Data  frameworks  

Page 38: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Leverage  Built-­‐in  Repor=ng  

•  Create  lots  of  Goals  in  Op<mizely  –  pages,  clicks,  revenue,  etc…  

Page 39: Fail and Win: Why a Failed Test Isn’t a Bad Thing

QUESTIONS?  

@CalebWhitmore  of    @Analy<csPros  

Page 40: Fail and Win: Why a Failed Test Isn’t a Bad Thing

Fail  and  Win:  Why  a  Failed  Test  Isn’t  a  Bad  Thing  

Caleb  Whitmore  Founder  &  CEO  Analy<cs  Pros  

@CalebWhitmore