If you are running a testing program, then you’ve more than likely had to think about what should go into a test you are running. This could include the problem statement, your hypothesis, how many variants, how different these variants will be, what your measures of success will be, screen captures, and more. It’s important to create a doc or some sort of accessible page/application for your teams to be able to reference this information. This helps to foster and open and collaborative culture of optimization. It will also help you as you look back to understand what your test objectives were and how the test did compared to those objectives. I track all of this via a Google Doc for each test I run. I used the same template for
Continue reading...