Tuesday, 14 February 2012

moving to a new blogspot


To move on in my own ambitions, I am going to move this blogspot to:


Please update any settings you may have to do this

Speaking a different Language

Recently, I went on a long awaited holiday to a foreign country where English was not the predominate language. Majority of the time, I do not have that much of a problem because most of the people I dealt with were able to speak English, making my stay enjoyable. That was until I was alone with a person that did not understand English.

This man was trying to communicate with me but I said back that I did not speak Japanese. That is when we had to resort to the oldest language known to mankind; signing! I would like to mention, I am VERY horrible at any games like this, and this was no exception.

The man took his hand up and was twisting his hand in a counter clockwise motion. I made the "I understand" expression with the thumbs up and proceed to turn off the lights. He then proceeds to take his fingers and make a walking sign very low and took his thumb and went across his neck. Needless to say, I was scared at this moment. I hold up my hand and then held up one finger as I went to get my friend.

Now, I hope everyone thought the same thing I did.... this man was going to kill me. I later found out from my friend was he was telling me he was putting poison out to kill some rats. The signs were so clear after I knew what he was trying to tell me. But this got me to thinking; how do we bridge the language between the Analytics, Technology and the Business.

In a way, without thinking about it, we have created a language barrier between those that are in Web Analytics and those that are not. So much so, we have now create a Glossary of Web Analytics Terms. This is great for starting to standardize the industry since each tool has created its own definition (how is a visitor defined?). At times, these definitions are so confusing, we even question our own selves on what we are saying (now how is a pageview and instance different?)

We have no one to blame for this but ourselves. The business and Web Analytics feel the same way I did with the man on my holiday; lets draw a pretty picture and hope they understand what we mean. But who should change; should the business understand Web Analytics or should Web Analytics understand the business?

The bottom line is, the business does not care this page has a high bounce rate or we had an increase of 75% in visits to a particular site. This information is better for the developers, content team, and site specific owners. The business cares about conversion rate and the story of what is happening on the site; what can be done to make the KPI's go up. You can read more about this on another post: Avinash Kaushik tells a story

This means we as the analyst needs to learn to speak like the business. We should not use terms like "bounce rate", "click throughs", "page views" or "exit rate". Do not go and give them numbers and make them think with their left part of the brain. You do this, you have already lost them. Ensure they are always using their right side of the brain where the emotions are. The right side of their brain handles sensations, left side of the brain handles details.

I was at a conference, and a speaker asked which one of these are more effective:

  • 65% of the visitors were unable to complete an order due to an issue on the site.
  • My brother in law was trying to place an order on the site and could not complete the order due to an issue on the site.

If you are like me, the later is more powerful because you are referencing a specific person who was trying to place an order and failed. That was a lost sale due to technology on the company side. The former is just figures, you are not personalizing it. The business will remember the story, not what percentage of orders that could have been lost.

I normally deal with this language difference by presenting the business and developers two separate documents. When I deal with the business, I am allot more elaborate and fill the documents with stories. Now when I deal with the developers, they want the figures and nothing else. A simple excel sheet with the numbers is all that is needed.

Know your audience!!! Once you know what they want and how they want, ensure you deliver. The data is useless if the audience does not understand what you are trying to say

Now how do you handle the language barrier in your own company? Do you deliver different insight to the different groups? Do you have a single language when communicating, and if so, which language (business or analytics)?

Till next time. - John Andrews

Oh, and I still cannot speak Japanese.

image above came from undermuchgrace blogsopt.

Friday, 10 February 2012

My Blog, My Way

In the past, I have tried to mimic other well known Web Analytics / business blogs(Avinash Kaushik, Adam Greco, Seth Godin). I tried to follow their own pattern of writing, even follow the same format that they did. I have come to realize that while this works for these bloggers, it does not work for my own style.

I have always moved to the beat of a different drum than other people, and writing a blog is no different. While these people are successful, if I want to keep my blog updated, I need to follow my own style.

When I started this blog, I had two things in mind:

  • I wanted a source where people could see the A -> C process of Web Analytics
    1. The Issue
    2. The Solution
    3. Why it is the Solution
  • I wanted a community that communicates about the topic and requests topics to be written about

Essentially, I want this blog to be ruled by the audience that reads it. You have a question, and I show you my solution to your question. Will my solution always be the optimized solution; no. The beauty of Web Analytics is that there are multiple routes to the solution and none are the right or wrong way.

Now do not get me wrong, I follow these three blogs all the time. When there are new posts, I read them immediately. I highly recommend that if you are not following these people; start. Read their older posts, gather their greatness. What I feel is that these blogs are not the way I want to run this blog.

Avinash is great at telling you how to run a report in his own opinion. I do feel though that he is not telling you the reason why running a report in a different fashion has an issue or what the issue at hand is (not telling the whole story).

Adam is great at telling you the issue and partially telling you the solution. The reason I say it is partially is because he does not actually tell you how to get to the solution. He expects that you can communicate to the developers what you want and how you want it, but not technically how it is done.

Seth is a great business man and gives great words of wisdom. At times, I consider him a fortune cookie; every time you open up his blog, you do not know what he is going to write about. But I believe he is going for quantity, not quality. I feel at times that you need to wade through the nonsense posts to find that one gem (and when the gem comes, it is worth sharing).

Like I mentioned, these three blogs are worth reading and worth keeping up to date with. If you have an RSS feed, add them now. You will not be sorry.

Myself, I work on the more technical side of Web Analytics. I work directly with the business and technology to implement the solutions to answer the questions the business has. With this background, I have great experience using the tool to gain insight about the site. With this, I am in a unique place as not only can I explain the insight that was gained, I can explain how it was done.

Every day at work, someone from the insight team will come to me and ask how is it possible that "X" can be captured in "Y". With my own experience in the technical workings of how Web Analytics is implemented and how the Web Analytics tool works, I am able to explain this to them. This is what I want to do, I want to explain each process to give a full understanding of (A) the Issue (B) The solution (C) Why it is the solution.

Now is the part which I need your help. I have several topics that I want to cover on the blog, but I want this blog to be run by you. What do you expect to see on here? How often do you want a post? What topic would you like to see next? I have ran sessions in the past where the viewers would like me to cover a particular topic and this was a complete success. Now, I am trying the same format but as a blog.

Next post will cover communications: how do we bridge the language difference?