{"id":15311,"date":"2022-01-27T06:54:07","date_gmt":"2022-01-27T11:54:07","guid":{"rendered":"https:\/\/www.invespcro.com\/blog\/?p=15311"},"modified":"2022-01-27T06:54:07","modified_gmt":"2022-01-27T11:54:07","slug":"why-and-how-you-should-document-your-experimentation-insights","status":"publish","type":"post","link":"https:\/\/www.invespcro.com\/blog\/why-and-how-you-should-document-your-experimentation-insights\/","title":{"rendered":"Why and How you Should Document your Experimentation Insights"},"content":{"rendered":"Reading Time: <\/span> 8<\/span> minutes<\/span><\/span>

Disclaimer: This section is a TL;DR of the main article, and it\u2019s for you if you\u2019re not interested in reading the whole article. On the other hand, if you want to read the full blog, just scroll down, and you\u2019ll see the introduction.<\/span><\/i><\/p>\n

    \n
  • The only way to continually learn is through rigorous experimentation and documentation.<\/span><\/li>\n
  • But all too often, small startups are disadvantaged by frowning upon the documentation part or viewing it as an optional formality.\u00a0<\/span><\/li>\n
  • Not documenting experimentation insights makes building a meaningful experimentation program challenging and impedes learning. Not to mention, it\u2019s also good practice.<\/span><\/li>\n<\/ul>\n

    What Is The Goal Of Documenting Experiments?<\/b><\/h2>\n
      \n
    • You can tell the maturity and culture of an organization by listening to why they document experiments.\u00a0<\/span><\/li>\n
    • it has everything to do with promoting continuous and efficient learning culture.\u00a0<\/span><\/li>\n
    • Insights and learnings should be the primary KPIs you use to track the value of documenting experiments.<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

      Why You Should Care About Documenting Experiments<\/b><\/h2>\n
        \n
      • If you have a high testing velocity, then it\u2019s critical to document your experiments.<\/span><\/li>\n
      • You want to keep track of every test you run \u2013 whether it wins or not \u2013 because those records will make your life down the line, and they can even help you achieve better results in your future tests.\u00a0<\/span><\/li>\n<\/ul>\n

        Benefits Of Documentation<\/b><\/h2>\n
          \n
        • Documentation facilitates education and cultural buy-in.<\/span><\/li>\n
        • Documentation helps prevent the duplication of tests.<\/span><\/li>\n
        • Documentation upholds your standards.<\/span><\/li>\n
        • Documentation saves money.<\/span><\/li>\n<\/ul>\n

          How To Document Experiments<\/strong><\/h2>\n
            \n
          • Each experimentation document should have these sections; introduction, problem, hypothesis, experimentation design, results, and conclusion.<\/span><\/li>\n
          • Write in first person active or 3rd person passive. Always document using past tense.<\/span><\/li>\n<\/ul>\n

             <\/p>\n

            Here’s A Longer And More Detailed Version Of The Article.<\/b><\/p>\n

            \n

             <\/p>\n

            Most of us in the conversion optimization<\/a> world know that we should always be learning.\u00a0<\/span><\/p>\n

            And as any experienced optimizer knows, the only way to continually learn is through rigorous experimentation and documentation.\u00a0<\/span><\/p>\n

            But all too often, small startups put themselves at a disadvantage by frowning upon the documentation part or viewing it as an optional formality.\u00a0<\/span><\/p>\n

            Unknown to them, not documenting experimentation insights makes building a meaningful experimentation program challenging and impedes learning.\u00a0<\/span><\/p>\n

            By documenting your A\/B testing<\/a> insights, you can ensure that you and your team constantly learn, improve, and can quickly reproduce results.<\/span><\/p>\n

            Not to mention, it\u2019s just good practice!<\/span><\/p>\n

            So without further ado, let\u2019s look at the benefits of documenting your A\/B testing insights and how you can do it.\u00a0<\/span><\/p>\n

            What is the Goal of Documenting Experiments?<\/span><\/h2>\n

            You can tell the maturity and culture of an organization by listening to why they document experiments.\u00a0<\/span><\/p>\n

            For some organizations, documenting experiments is an afterthought because it\u2019s a practice that can\u2019t be tied to revenue.\u00a0<\/span><\/p>\n

            But that\u2019s being myopic.\u00a0<\/span><\/p>\n

            Mature organizations that are pushing the needle understand that documenting experiments have nothing to do with revenue but it has everything to do with promoting continuous and efficient learning culture.\u00a0<\/span><\/p>\n

            Insights and learnings should be the primary KPI you use to track the value of documenting experiments.\u00a0<\/span><\/p>\n

            Why You Should Care About Documenting Experiments?\u00a0<\/span><\/h2>\n

            Tell you what, Although it might not look like it at the time, documenting your A\/B testing insights is one of the few things that you will be glad that you did.\u00a0<\/span><\/p>\n

            This process of documenting experiments is even more critical when you have a high-testing velocity program<\/a>.\u00a0<\/span><\/p>\n

            It can be challenging to keep track of what changed and why when running multiple tests simultaneously.\u00a0<\/span><\/p>\n

            Without good documentation, it will be very hard \u2013 if not impossible \u2013 to determine which changes led to success (or failure).<\/span><\/p>\n