Gathering Business Requirements – Part One

November 6th, 2008 by Debra Paynter

I want to thank @swcalise on Twitter who requested a post about gathering business requirements. Throughout my career as an SEO and analytics consultant, I have always considered the most important step with every client to be the business requirements gathering stage. In my next 2 posts you’ll learn more about my approach and I’ll share my thoughts on the process.

Consider Your Purpose – Pause for a moment, take a deep breath and turn your mind to what brought you here in the first place. Given the ever changing environment of life on the web, and now with the global financial climate full of uncertainty - applaud yourself for having good business insight. It was that business sense that made you decide to track your web traffic and engagement - but what now? Are you actually intending to utilize the information you gather?

That may seem like an irrelevant question at this point, after all you purchased the software and now you’re ready to implement it (implementation only is worthy of an extensive post). Too often companies collect but don’t utilize their data, so I encourage you to make that your first point of discussion with each and every stakeholder interview - What are you going to do with this information?”

Determine Your Stakeholders- Who are the stakeholders? From small businesses to large corporations, you should know the answer to ”Who is the intended audience to receive and digest this data?” A small business may have only one business user who wears multiple hats, but sometimes this audience can be more challenging to assist in determining their business requirements from, than that of a large enterprise.

How They Digest The Data- Once you have established who the intended audience is, and before you dig in to what it is they need to know, determine how each business user wants to receive their information. With WebTrends we can customize dashboards and set up automated reports so the Executive Team receives their reports every Monday morning (or any frequency). The Marketing Team may expect their reports delivered as a PPT or dynamic spreadsheet.

Teams may want their data combined with external data sources for a more complete and intregrated picture. Helping stakeholders understand and begin to think about deliverables encourages them from the very beginning to own the data and put it to work for them.

Start From A Scoped Document- WebTrends for reporting is significantly more than just profiles and reports. If you enter into an engagement with WebTrends, a Business Analyst or Technical Consultant will use your Statement of Work (SOW) as a blueprint. The SOW lays out pertinent information from the number of profiles to whether your requested reports are all out of the box or customized. We use the SOW as our guide moving forward. If your license choice is 5 profiles then you want to make sure that those five profiles are set up to gather all the data your stakeholders are expecting to receive.

What About Profiles? – When setting up profiles, you may want to consider though that once you go into your actual Requirements Gathering what you had thought you may need might change – so keep an open mind. Many companies set up a profile for each domain while others may want one profile that includes both their main domain and their ecommerce domain so they can easily track conversions. Your business may be set up to address different market segments so you may want a profile that will allow for reporting across each of those.

I’ve set up profiles where the main profiles filter out all internal company traffic with a separate profile that captures only internal traffic because they wanted to track how their technical support or call center are utilizing their site(s) to respond to clients. This level of detail for setting up these particular profiles comes at the end of a vigorous round of interviews.

Dig Deep – Consider the Marketing Department for a moment. Marketers naturally want to know how their campaigns or initiatives are working, how successful they are to bringing in visitors that convert regardless of what that conversion activity is. To set up successful campaign reporting you need to know very detailed information. Dig deep, ask lots of questions and then formulate a strategy around reporting that will help your Marketing Team learn from the present campaign so they can bring that information into the next campaign to make it even more successful.

In my next post - we’ll be diving into education, details, details, details and I’ll provide 13 helpful hints on gathering requirements yourself.

Tags: ,

4 Responses to “Gathering Business Requirements – Part One”

  1. Curtis Smith Says:

    In “Consider Your Purpose” in why did you buy (and are getting ready to install) an analytics tool. Sometimes you have to take a step back from that.

    A good starting point is “why do you have a website?” This really seems like an irrelevant question because at this point you already have the site, sometimes for years. But this is a good lead in to “what are the goals of your website”. What was the business reason you created the site for in the first place. Because everyone else has one isn’t a good answer. :-)

    The site reason is often the business goal that the analytics needs to support. Analytics is one of the tools to get you to the goal. Analytics is a hammer that helps builds the house. For the goal you want to concentrate on the house, not the hammer.

  2. Debra Paynter Says:

    I completely agree with your comments Curtis. There are so many questions to ask yourself and your business of course including, “How do you measure success?” Some businesses simply count new visitors as success while others look to returning visitors or time spent on site as the measures they count on to determine how successful the day or week or month was.

    Part 2 goes into more detail of course but still doesn’t cover the topic as completely as needed especially when it comes to all the questions. Depending on the size of the engagement I spend hours speaking with the stakeholders with my goal to dig in deep and find out as much as I can about the business and what it is they need from their analytics. Every question asked and answered will lead them to a deeper understanding of their data.

    Great point about the hammer, I’m glad you added that to this discussion.

  3. swcalise Says:

    thanks for the shout out and love the post about process. Too often a project gets started without all these aspects being considered or fully vetted out.
    I agree with your thoughts about having a scoped project so you think ahead of time “what can this project/product potentially do for me? what will it take in manpower and $$ to get it complete and is it then worth the effort?” I feel if this was done more a lot of projects would not make it to the next phase (sometime good, sometimes bad but at least you would have gone through the “process”)

    What I’d like to hear more about is how that process works internally at various organizations. At what point in the process is web analytics tracking and requirements discussed and with whom or with whom at diff points in the process. How do people spec out the analytics requirements for a project? I find we too often do things word of mouth or casual mtgs and have bare minimum in formal documentation for the analytics portion of a project.

    Debra, thanks for writing and starting this conversation. Hope to hear others insights as well.

  4. Debra Paynter Says:

    Thanks again for the idea for this blog swcalise and for your comments here. It’s an important implementation, establishing a set of guidelines and standards from which to build from. I’ve had some very recent experience with this so I think I can work up a post that would help provide some guidance. You are providing a wealth of blogging ideas, thanks.

Leave a Reply