Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel1

...

 

All of the online tools let you us name your our tree test, so you (or a colleague) we can find it later. There’s no special magic here, but we do recommend that you identifyidentifying: 

  • The site you’re we’re testing

  • Which variation of the tree you’re we’re testing (if you’re we’re testing more than one)

  • Which revision of the test you’re we’re working on

...



For example, suppose we’re helping the Acme Supply company reorganize their website. We’re testing their current site structure (to get a baseline score to compare against) and two new trees – one grouped by topic, and the other by audience. So we create 3 tree tests with the following names: 

  • Acme current
  • Acme topic
  • Acme audience

 In Chapter ~10 - Piloting the test, we’ll see that it’s a good idea to pilot do a dry run of each test, revise it, and launch the second (or third) version. So really, the list of tests will may eventually look something like this: 

  • Acme current – draft 1
  • Acme current – final
  • Acme topic – draft 1
  • Acme topic – draft 2
  • Acme topic – final
  • Acme audience – draft 1
  • Acme audience – final

 Any name will work, of course, but if you we do more tests over time, it does pay to be systematic now so you we can make sense of your our tests later.

 

...

Next: Disguising the test address

...