In Part 1, I mentioned that the Web Analytics team will look very different depending on company and business goals.  I identified three elemental constituents (business strategy, analytics, and technology) necessary to select a web analytics tool, and I divided them up into three different folks who fill those roles when you’re selecting an analytics technology.

Once the tool is selected, companies will want to create a structured team framework with defined roles and responsibilities in order to successfully deploy the tool.  What I’m describing is a suitable team-structure that enables you to successfully deploy a tool in your organization that finally gets you to a point where you are able to do web analysis. The team structure I describe below lets you get to the hub-and-spoke model that my good friend, Eric Peterson, described in these Part 1 and Part 2 of “what’s your web analytics communication strategy?”   What Eric excellently describes takes the team to the next level of actually doing Web Analytics.  It’s excellent stuff that I encourage you to read.

A formalized team structure for rolling out a web analytics tool may have the following constituents: 

• Executive Advisory Board.  Beyond the Executive Sponsor mentioned in Part 1, these board members are the ones who really control the budget and strategy at the highest level.  They may be your boss, your bosses’ boss, or board members at your company. Regardless, they are the analytics project champions at the highest level in your organization – often C-level executives.  They support the project structure and analytics strategy, confirm the scope of the project, and approve any budget allocation.

• Steering Committee.  You may be on the steering committee, Mr Web Analyst, or it may consist of very senior representatives of all the internal teams that the project touches.  These people work to define the strategic direction of the project, decide on how to resolve critical issues that come up during the rollout, and generally handle any escalations.

• Web Analytics Expert.  That’s probably you, fine reader.  You will provide analytics-based strategy and informed decision making across all aspects of the project. You’re obviously critical to the success of this project, and will ensure technical, tactical, procedural, functional, and financial adherence across the entire analytics program.   You are the chief evangelist, and will define the overall reporting and KPI structure.  In addition, you will be responsible for the overseeing the partnership with your vendor. Other things you may do will include managing costs, coordinating schedules, risks and resources, and reporting overall project status and important communications (often with the help of a project manager) to the steering committee and advisory board.

• Web Analytics Team.  If you are lucky enough to have a team, these folks will gather and document project and technology requirements, liason with business stakeholders, lead training, build awareness of and evangelize web analytics, and in general work with those who receive reporting and leverage the tool.  In many companies the solo web analytics expert will do all this stuff (and drink a lot of coffee or green tea too!).

• Project Manager.  A web analytics rollout can be complicated. While the solo web analytics team member may be expected to project manage, it may make sense to give that role to a formal project manager (y’know a PMP) who works with the Web Analytics Expert to manage the schedule, risks, resources, communications, change, and quality management plans.

• Business Partners.  Since web analytics will touch many different groups, you will need to ensure your analytics team communicates with them.  Business partner are critical stakeholders.  They can’t be neglected.  They will provide business requirements, test the technology, and work with analytics team to ensure the technology, reporting, KPI’s, and analysis you rollout helps drive business performance.

• Subject Matter Experts (SME).  Similar to business partners, these folks will probably be more technical in nature.  The Technology Expert you worked with when selecting the project will transition into a roll as a SME.  You may have one SME who oversees the overall technology architecture, another who coordinates BI resources, another who QA’s the system, another who creates interfaces to your data warehouse, and perhaps another who acts an IT contact covering issues across the operating system, database, security, and networks (especially if you are running an in-house tool).

• Vendor Professional Services Team Members.  Last, but certainly not least, are the folks sent from your vendor to do what you want them to do.  From installing the application (in a in-house environment), functional training, to advanced configuration, these people are critical to ensuring that you don’t make simple, avoidable mistakes that can thwart your efforts and delay the successful rollout, golive, and extension of the project.

In reality, you may not be able to effectively isolate all of these groups to support your analytics rollout.  To some degree I’ve presented big company structure above.  In smaller companies, one or only a few people may do all of the interlaced activities necessary to rollout a web analytics tool.  Regardless, I think the groupings I’ve presented above define the primary roles and responsibilities necessary for success when rolling out a web analytics tool (in fact I presented things in a general way to apply to other rollouts as well).  The next challenge comes once your up and running (make sure to read Eric’s posts)… You need to use the data to improve business performance and guide strategy, decision making, and online tactics that reduce expense and yield profitable revenue.


Image by Jim Sterne, from Emetrics 07 San Fran.

Add to the Conversation

Name:

Email:

Your email (required) will not be published.

Website:

Your Thoughts:

Please note that contributions are moderated and may take a little while to appear.