Leave a comment
Get the GH Bookmarklet

Ask GH

I got a question today from a client while talking about everything post testing (documenting, implementing, share insights). "Why document? Who ever reads documentation." I have my reasons but I would love your input on this. I think it is an interesting question based on the "who ever reads documentation" part. Do you ever revisit the old documentation on A/B-testresults? Why document?

  • AP

    Alex Pyatetsky

    over 3 years ago #

    What is your motivation for asking this question? "Why" is the question of poets and depressed people, as they say. What are you hoping to achieve/understand?

  • TM

    Tomi Mester

    over 3 years ago #

    I agree, documenting all your researches (not just A/B test results, but heatmaps, usability tests, etc.) is essential.
    The reasons are above mentioned.
    +1: if someone comes up with a great "new idea", you can just copy-paste, the link and say, we've already test it.

    My best practices to make people read the docs:
    1. Make one sentence summaries for every test. (So they don't need to read the whole doc, but they can if they want to dig deeper.)
    2. Make it short (top 5 min to read), clear (short and straight-forward sentences) and add lot of visuals.
    2. Present your results time-to-time. Even repeating yourself several time to time. I guarantee you, that not every people at the organization will understand everything for the 100th time, either.

    • JL

      joni lindgren

      over 3 years ago #

      Agree on all above and especially agree on talking about the results over and over. I usually have biweekly or monthly Insights workshop to dive deeper in what we´ve learned about the users during the latest period of time. Both from A/B-tests, the research that lead up to A/B-tests, and all other knowledge acquired by anyone attending the meeting. (Anyone is welcome)

  • NC

    Nge Chee Keen

    over 3 years ago #

    How documentation helped our team:

    - Knowledge transfer: Whenever a new team member joins our team, he/she can immediately grasp the A/B testing process we follow. Also, he/she would understand why our site is like this and how it came to be, really helps in our new member onboarding.

    - Review our past learnings: We often iterate our tests based on previous test data, in a few months it can lead to many branches of follow up tests, it's good to be able to review why we did the test in the first place, and also have a bird's eye view of all the tests we did so far.

    - Measure our progress towards our kpi over time: This is self-explanatory.

    Hope it helps

  • JM

    Juli Morris

    over 3 years ago #

    Because best practices is a real thing!

SHARE
12
12