making & taking informed decisions

Download Making & Taking Informed Decisions

Post on 20-Aug-2015

283 views

Embed Size (px)

TRANSCRIPT

  1. 1. Making & TakingInformed DecisionsJ. Boye Aarhus 14 @galimathies
  2. 2. Valuable lessons I havelearned from messing aroundwith A/B testing on one ofDenmarks largest e-commercewebsites for the past two years.J. Boye Aarhus 14 @galimathies
  3. 3. Mathies JespersenUser Experience Designer at Dansk Supermarkedsince 2012J. Boye Aarhus 14 @galimathies- A/B testing- Wireframing- Information architecture- Usability testing- Analytics
  4. 4. LessonHow-toJ. Boye Aarhus 14 @galimathies
  5. 5. Always havea clear hypothesisJ. Boye Aarhus 14 @galimathies
  6. 6. Always havea clear hypothesisBy changing ______into ______ I canincrease ______J. Boye Aarhus 14 @galimathies
  7. 7. If you cant measure it,you cant test itJ. Boye Aarhus 14 @galimathies
  8. 8. If you cant measure it,you cant test itAsk yourselfwhat success isJ. Boye Aarhus 14 @galimathies
  9. 9. Your numbers say morethan a 1,000 wordsJ. Boye Aarhus 14 @galimathies
  10. 10. Your numbers say morethan a 1,000 wordsYour boss prefers$$$ over essaysJ. Boye Aarhus 14 @galimathies
  11. 11. Get everyone tocontributeJ. Boye Aarhus 14 @galimathies
  12. 12. Get everyone tocontributeStart by askingwhy?J. Boye Aarhus 14 @galimathies
  13. 13. Let tests runas long as possibleJ. Boye Aarhus 14 @galimathies
  14. 14. Let tests runas long as possible200+ successesJ. Boye Aarhus 14 @galimathies
  15. 15. Keep it simpleJ. Boye Aarhus 14 @galimathies
  16. 16. Keep it simpleCan you actuallychange this?J. Boye Aarhus 14 @galimathies
  17. 17. Organize and prioritizea backlogJ. Boye Aarhus 14 @galimathies
  18. 18. Organize and prioritizea backlog1. Business value2. Technical setup3. Dev effortJ. Boye Aarhus 14 @galimathies
  19. 19. Learn from failureJ. Boye Aarhus 14 @galimathies
  20. 20. Learn from failureEverythingsa lesson learnedJ. Boye Aarhus 14 @galimathies
  21. 21. Dont break stuffJ. Boye Aarhus 14 @galimathies
  22. 22. Dont break stuffReview, presentand discuss your testJ. Boye Aarhus 14 @galimathies
  23. 23. - Have a clear hypothesis- Cant measure success? Dont test- Numbers speak louder than words- Involve people- Run tests for at least a month- Keep it simple- Use a backlog- Theres always something to test- Test your testsWhat makes yourinterface successful?J. Boye Aarhus 14 @galimathies

Recommended

View more >