"Oh Alec!" I hear you saying, "Are you feeling melancholy and wondering what life is all about?" No more than normal is the answer that you'll all be happy to hear. It is a new year, but there is no new whencanistop out there, I am afraid. Obviously speaking about my alter ego in the third person could be slightly new, but I'm going for the personal interpersonal touch. If you know what I mean. And I'm sure you don't , because I've lost it already and we're only on the first post of 2010 and already I'm drivelling in the opening paragraph. Oh wait - no, that is normal behaviour.
Actually what has really been going on with me is a little discussion that I eavesdropped on at the end of last year (that sounds so long ago, whilst actually only being last week!) that I didn't want to comment on until I had read some of the stuff that has been going on. So lets start at the beginning. Or the end, as the case may be. It started with me picking up a 'conversation' that Stéphane Hamel and Eric Peterson had been having on Twitter around 'models' (in the Business sense, not the entertainment sense :)). To cut a long story short, Stéphane has created a model (which you can download, read yourself and then pass back comment to Stéphane as I have) which describes how 'mature' or advanced a company is with its Web Analytics.
The model describes through six different 'pillars' how mature your organisation is on a scale of 0 to 5 (0 being not at all and 5 being brilliant - to paraphrase).
This also led me into reading Joseph Carrabis' "The unfulfilled Promise of Online Analytics" Part 1 and Part 2. They are lengthy reads - I'd recommend that you plan your dinner for a bit in the middle. Yes, I was researching this during my spare time and no I should probably not have been doing. Part 1, in case you are wondering ponders what the problem is and part 2 ponders what to do about it, using some of the methodology that is picked up by the Maturity model suggested by Stéphane (see there is a point to this).
Anyway, all the pondering led me to an epiphany and I stopped asking What is Web Analytics? and started asking: What is a Web Analyst? This should be something that is simple to answer for whencanistop given that it is in my job title. I even proclaim to be one in that little blurb at the top of the screen.
What is Web Analytics?
Stéphane proclaims to be able to define Web Analytics at the start of his Maturity model as:
“The extensive use of quantitative and qualitative data (primarily, but not limited to online data), statistical analysis, explanatory (e.g. multivariate testing) and predictive models (e.g. behavioural targeting), business process analysis and fact-based management to drive a continuous improvement of online activities; resulting in higher ROI.”Which is, as he quite rightly points out, a bit of an increase on what Wikipedia says about it (although the Wikipedia article looks a bit like it has been hijacked by someone from Nielson) . Really what we're talking about is collecting data about what people do on the site (by using a Web Analytics tool or by asking them in a survey) and then using it to improve the performance of the site.
What is a Web Analyst
So a Web Analyst (like yours truly) does stuff with that information. What sort of stuff? Well we take all that data from the tools, the surveys and any other source that we can find and we turn it into actionable insight (interestingly this last word doesn't appear anywhere in the Web Analytics page on Wikipedia).
So we take all that information and turn it into insight that the Business people can make their website better. Is that all we do? Well, no not at all. When those Business people implement it, we then tell them afterwards whether it has worked or not. In theory, you then use a continual improvement programme of measuring and providing insight and changing.
However actionable insight relies on a number of things. Any insight can be actionable. One of the insights I'd probably have made about this blog very early on is that I should have put it on Wordpress. So I should transfer it to Wordpress, copy all the content across, redirect all the links, etc, etc. But that isn't going to happen, because the effort and time it would take me to do it isn't worth my while. The benefits are there, but the pay back from it would probably take a long time to come into fruition. That means that not only do I have to come up with insights that are actionable, but the benefits have to outweigh the cost quickly.
Not only do I have to work out the benefits, but I have to work out what the cost is to work out if the ROI is there. How do I do that? I need to have a vague working knowledge of the systems that we are going to need to change. If we're making a change to a site, then we need to work out the Architecture of the IT, how competent the developers are (if there are any), whether it will have knock on effects, will there need to be lots of testing, etc, etc. This means I have to have a quite detailed knowledge of the IT systems (or at least access to someone who does).
Now, I've worked out that the change I'm suggesting has benefit, I've worked out when it has benefit, how much and how long it will take to do, then there is the next step. I have to persuade the Business that it is more important than any of the other projects that they are doing. Not least those pesky ones that nobody knows how long it will take, how much it will cost and what the benefits will be. When you're working with numbers, you can be very precise about the benefit. When you're suggesting that you turn your logo into a dancing hamster, you can make it up as you go along, because nobody will be able to argue with you through numbers.
So we've got to know:
- The information to provide the insight
- The IT infrastructure and how to alter it (plus all those processes that always go off in IT)
- The Business framework (how you can get funding)
- The current projects so that you can push your project
ps - would you have ever thought you'd see a picture of me and Kate Moss on the same blog post?