{"id":111815,"date":"2014-07-28T12:16:20","date_gmt":"2014-07-28T12:16:20","guid":{"rendered":"https:\/\/staging.wingify.com\/blog\/define-ab-testing-roadmap\/"},"modified":"2014-07-28T12:16:20","modified_gmt":"2014-07-28T12:16:20","slug":"define-ab-testing-roadmap","status":"publish","type":"post","link":"https:\/\/wingify.com\/blog\/define-ab-testing-roadmap\/","title":{"rendered":"Before you Start A\/B Testing, Define your Roadmap"},"content":{"rendered":"

What tests should I launch? In what order? How do I stop several tests from interfering with each other? What risks are involved and how do I minimise these? Before you begin, these are the questions to ask. Follow our advice to establish your roadmap and get results from your A\/B tests<\/a>.<\/p>\n

Before you start testing, you must mark out your route. A roadmap is essential, not only for clearly defining your goals, priorities and risks, but also for setting out a timetable. With this, you can track the progress of your project, and keep all of your contributors informed.<\/p>\n

Your roadmap should,\u00a0in particular, consider the following 8 aspects:<\/p>\n

Test names<\/h2>\n

Be sure to give your tests precise, explicit names (preferably the same as you use in your Wingify tool). For example, a short name such as \u201c[HP]wordingCTA\u201d is preferable to an entire phrase such as \u201cTest on the wording of the CTA on the homepage\u201d.<\/p>\n

Test descriptions<\/h2>\n

So that all your contributors are in step with your testing procedure and can follow it as it evolves, write a short, explicit description. For example, \u201cReplace CTA wording \u2018Create an account\u2019 with \u2018Sign up now\u2019\u201d will allow anybody to understand the content and goals of the test.<\/p>\n

Test priority level<\/h2>\n

It is vital to rank your tests in the order of their importance in order to decide the order in which you will launch them. It is up to you to gauge:<\/p>\n