Experimentation and Testing: A Primer by Avinash Kaushik

Posted by Marshall on May 22, 2006 | Link It

Avinash Kaushik wrote a very good post on the different types of testing you can do to pull metrics from a website.  

Here’s my take -  Avinash thinks 80% of the time we are wrong about what a customer wants / expects from our site experience.  I think that’s true and my experience with customers suggests they have their own vision of what a site is for and how it should operate that does not conform with actual visitor behavior.

A/B Testing is the easiest to put in place but outside the simple AdWords ad rotation - I’ve not done it and it’s really hard to get large corporate clients to do it if they’re not thinking it’s important; that’s my experience.   Also, in a dynamic environment - with pages changing on a weekly basis web teams are pretty overworked anyway - and might not be set up to easily create two or three versions of the same page and test.

Multivariate Testing might be something that some of my clients can do, but none of them actually do it. 

"For example for my blog I can create “modules” of the core page content, the top header, and each element of the right navigation (pages, categories, links, search etc). In a multivariate test I could move each piece around and see which one worked best."

Experience Testing is what many corporations are being to do with large websites and adaptive portals where navigation is changed based on who the customer is.

"With experience testing you don’t actually have to create three or four websites, but rather using your site platform you can easily create two or three persistent experiences on your websites and see which one your customers react to best. Since any analytics tools you use collect data for all three the analysis is the same you do currently."

The amount of programming work involved is very large; also standard Metrics software is really not built, at this time, to handle different versions of the same page that only a few customers might see.  Imagine having a page that’s somewhat different for every customer - how do you decide how much traffic a page got when it’s different "home page" for everyone (or almost everyone who say, logs in and identifies themselves).

I haven’t yet seen any of  the more expensive analytics platforms actually contend with what personalization will mean in terms of metrics tracking. 

 

 



2 Responses

These are the current comments for "Experimentation and Testing: A Primer by Avinash Kaushik"

05/22/06 @ 11:13 pm

Marshall, great summary. I think you have described very well the challenges with testing in large companies. But my thought for them is what is the use of putting pages our repeatedly if you don’t know that you are actually giving the customers what they want. It is most definately a mindset change for most companies.

You should definately consider pushing multivariate more becuase it is cheap (with any vendor) you don’t have to create many many pages and you don’t even need IT. You can do it all by yourself from creating and putting the tests out to measuring them and recommending results. All IT needs to do is put a javascript on the site.

This can be a great and cheap way to prove value of testing to senior management.



05/24/06 @ 11:44 am

Hi Marshall,

you blogged:

“also standard Metrics software is really not built, at this time, to handle different versions of the same page that only a few customers might see.”

I wouldn’t entirely agree. Providing that you have a robust testing system in place (e.g., SiteSpect, Optimost and Offermatica are a few that Avinash mentioned), these systems can feed metrics and/or segmentation information into your standard 3rd-party web analytics tool. Thus, it isn’t actually so hard to slice overall visitor data based on which site variations(s) your visitors experienced.

-Dave from SiteSpect



Post a Response

Name (required)

Email (required, not published)

Website (optional)

Note: The following tags are approved for comments on this blog:
<a href=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <del> <strong>