During Emetrics San Francisco I had the opportunity to visit Google (I’ll blog about that in the coming days) and to have a look at the alpha version of Gatineau. This made me want to emphasize and explain our Code of Ethics as independent consultants.
But before I get into that let’s explain a little bit more:
As you might have read, our team had been testing the new version of Google Analytics for over a month before its release and we were very excited by the future launch. As I had signed an NDA, I haven’t talked to anybody outside OX2 about this release. Julien described GA version 2’s new features in two previous posts (first & second) and detailed where improvements have taken place.
Also during the conference, Ian Thomas offered Aurélie and I a demo of Gatineau, the code name for the upcoming Web Analytics tool that will be released by Microsoft around this summer – in beta version. As you might imagine, I have also signed an NDA before the demo, so I won’t be able to enter into specifics (sorry ;-)). But what I can tell you is that we are excited about this upcoming release as it will again allow the Web Analytics industry to go a step further and, hopefully, it will drive more businesses towards accountability (read my previous post about Microsoft and Web Analytics). What I can also tell you is that Gatineau is the code name, so expect a brand new name when it will be released. Through this post I want to wish Ian and his team good luck in the future release. If you’re interested in participating in the beta version of Gatineau, you can already apply by sending email to: firstname.lastname@example.org
Our Web Analytics Code of Ethics
That being said, you might wonder how can we work with so many different Web Analytics products and still have the confidence and trust of their management?
Well, this can be explained by our positioning, philosophy and code of ethics:
Our Web Analytics positioning regarding vendors:
We position ourselves as vendor-independent in the Web Analytics Industry. But don’t get me wrong, being independent is not the same as being agnostic. Being agnostic means that you don’t have any kind of preferred relationship with vendors whereas being independent, IMHO, means that you don’t work for vendors but with vendors.
Our objective is to best serve our clients. For this, we need to best understand the tools and this is why we partner with Web Analytics vendors. In order to provide the best advice, we need to understand and know the product in detail.
Let me give you an example of consultancy that we do more and more for our clients:
Corporations come to us and tell us that they want to acquire a Web Analytics product. We all know that just a product won’t solve any business question but, nevertheless, it is important to choose right depending on what kind of company you are, the people inside and many other factors. So we start by interviewing the client (in one or multiple meetings, depending on complexity and number of actors) in order to understand their needs, we also take a look at their history with Web Analytics. As I commented on Avinash’s post Web Analytics Tools Comparison: A Recommendation, you have to see if in your organisation there isn’t already a product or knowledge that could facilitate the Web Analytics Journey. Once we have all the information we need, we then preselect a few Web Analytics packages that match the needs of the clients. We contact the vendors in order to get some quotes and we provide the client with a final document in which we explain our methodology, what are the business and technical needs that we have highlighted in their company. Based on these needs we then present the selected products each with a description and a personalized SWOT analysis along with the pricing for the solution and an idea of implementation costs (this often includes also business KPIs and Dashboards implementation and some even include Processes). It is then the client that either chooses one tool or decides to invite vendors to learn more about their solution and maybe negotiate a POC (Proof of concept) in which we are very often involved.
Our Web analytics vendors relationship philosophy:
Regarding our philosophy towards vendors, we think that we need to work together, not in the sense that we work for them as I have expressed earlier, but in the sense that we need each other in the Web Analytics ecosystem. A company like OX2 needs WA tools in order to deliver to our clients the consultancy services we provide, and vendors need us in order to help their customers to use their tool at the maximum potential. So we encourage vendors not only to present us what they’re going to release and what are their plans to better serve our customers, we also encourage them to pick our brains. We are in the field, we work with many different clients and by being an interactive agency (not only a WA consultancy firm) we see the other aspects of the Web that might have consequences in a Web Analytics implementation process. But don’t get me wrong, picking our brains doesn’t mean that we will speak about other products, as we believe that it’s each vendor homework to understand his competition and adapt if needed their strategy, which leads me to our code of Ethics that Aurélie presented a few months ago here on our blog.
Our Web Analytics code of ethics principles:
- Don’t do product demos (or provide product information) to competitors as vendors should do their own home work;
- Respect leads: any lead coming from vendors will be solemnly respected;
- Respect the client: don’t support them to change solutions if it’s not in their best interest, short and long term.
If you are an independent consultant or Web Analytics agency and you subscribe to this code of ethics, please let me know and feel free to reuse it to explain you positionning. And if you have any comment, question or critique, please leave us a comment.