My struggle with metrics-driven analysis
As Marko and I triangulate on site search analytics from the bottom-up (exploratory analysis) and top-down (metrics-driven analysis), I've really struggled with the latter. Not surprising, as a designer of sorts, I'm much more of a bottom-up guy. I'm just not as experienced with the top-down approach, which has been one of the really valuable things I've learned from Marko.
But I still feel that there's a gap. In my take on top-down analytics, you start with a reasonable understanding of your organization's goals. Is it trying to sell widgets? Help people research retirement plans? Change the minds of voters? This is hand-waving Big Picture stuff, but obviously you shouldn't be in business if you can't describe what it is your organization is there to do.
Next part: come up with some concrete site search metrics for purposes of benchmarking and measurement. And there's the rub: getting from big goals to specific SSA metrics is really hard. Maybe not if you're trying to sell widgets, but definitely if you're trying to change voters' minds.
Marko describes some useful basic SSA metrics in his presentation (see slide #43), and there are many more here. But, based on both reading and direct experience, I still don't feel like the mapping process is obvious, and I'm not entirely sure what guidance to offer than 1) start with generic SSA metrics and 2) make the effort to customize them for your own organization's needs.
As an author, I feel like that's something of a cop-out: readers will surely want more guidance than that. But I'm not sure there's more out there other than "your mileage may vary". Does anyone have any advice on getting from broad goals to concrete site search metrics? Love to discuss it in the book (with full credit, natch).
Comments
Lou,
I'm not sure this is a problem specific to search analytics -- trying to figure out the ROI on political ads or a public relations campaign can be tough, too.
I think as with many things, this probably requires having a good, hard think about what success would look like. Is it simply more visitors to your site? Is it something like greater awareness of your company, which might be measured by an outside survey firm? Is it more sales? Better polling numbers?
As with many things related to marketing (which is what I think a Web site often is for a business), I think you've got to properly define those goals to figure out how to connect big picture to site search metrics -- for example, maybe you want to drive every single visitor as easily as possible to your shopping cart functionality, or you just want to measure how many times the phone rings in your sales department?
Maybe this is all stating the obvious but it seems to me too many people jump to choosing a tool without first deciding what it is they're building.
Best of luck.
Colleen
Posted by: Colleen Newvine | June 8, 2009 9:27 PM
So this is half-baked still but I've just started to read the Mental Models book. Indi Young's approach of mapping what people need to what you/the org has is starting green shoots in my brain about that very thing: top-down big goals identification (p'raps based on user analysis/metrics and business drivers) against the SSA metrics you can/are able to gather?
Hmm, half-baked. But, still early doors for me on applying the mental models approach to what I'm trying to do but I'm currently reading as much as I can looking for that brain spark/serendipitous ah-ha moment...
good luck in the hunt for yours anyway!
Posted by: Kate Simpson | June 9, 2009 2:06 AM
While this discussion is still fresh on my mind with Lou yesterday...
KPIs: The KPIs I have listed, (and all the others, which may be metrics not KPIs BTW depending on your needs), are meant to be starting points 'from the top', a place to begin if you will. They are meant to act as guides that lead you down a "structured path" to be able to perform data analysis. Now, what does that really provide? It provides you with boundaries to work within and think about. Why would you need such a thing? Because there is SOOOO much data out there that you have to be able to decipher the "signals through the noise" and having these structured paths (KPIs) 'to walk down' provide you with those ways of doing just that. REMEMBER all data is valuable, not all of it is useful. You need ways to cut through the clutter.
Mapping: Now is a perfect simple world I/we could take your business model, a set of associated KPIs, your business goals, and deliver you actionable insights. Now, I emphasize the word 'simple' here, because in essence that is what I do for my clients, but here's the kicker... each and every company / client / etc are unique and that means I would have to create a cookie-cutter template that everyone would have to abide by. Now, to a degree I/we will be doing just that in the book and Lou has been pestering me to put some of that on the blog as well, but again it is only a starting point. What you must do after this is look at your individual business model, business goals, time, money, resources, technology, processes, and more to determine which KPI(s) will produce the best results for you.
Example: While giving my talk in Spain last week a person from the audience said (referring to slide 43 of my presentation) that for them "Zero /Null Results" was their number one KPI for search analytics. For them it was a very simple way to understand what content people were looking for in comparison to what content there was or wasn't on the website. And for them that works, and they are happy and it produces great insights that they can take action on. And that is the ultimate goal of what we are trying to accomplish with data analysis: some 'nugget' of information (an insight) that can be applied (action) to achieve better results (business & user).
Colleen's comments above: You make a couple of great points and that this issue is not limited to search analysis.
"trying to figure out the ROI on political ads or a public relations campaign can be tough, too."
-- I disagree with this as a blanket statement for ROI, but I'm not saying it's easy either. It's a multifaceted issue that we are not entirely equipped for today and that is the ability to measure & track to a degree we'd like between channels (multichannel metrics). That being said, if it's online it can be tracked, measured, and monetized.
"this probably requires having a good, hard think about what success would look like"
-- Couldn't agree more! I did a talk at the NY UPA in February on something I created called "Designing Outcomes". What is does it breaks down the process into 3 major areas: Business Goals, UX, & Analytics and 'forces' you to think about how to use the data from each to "design the desired outcome". The easiest way of doing this is to start at the end (desired result) and work backwards.
"too many people jump to choosing a tool without first deciding what it is they're building."
-- Oh indeed they do! The way it should be is as follows: Choose your people first. Then define you processes based upon your time, money, people. Then based upon all that ONLY THEN should you choose your technology. I am such an advocate or this method that there is simply no argument whatsoever. To prove this point to clients I have previously challenged their existing team who usually has Omniture or CoreMetrics, and I will use only myself and Google Analytics to get the best results on "X & Y". To date I've never lost. Technology only comes into play when you have maximized your internal resources (people & processes).
Posted by: Marko Hurst | June 9, 2009 9:39 AM
As a novice in this area, I sure don't have the answer -- but I do know that a case study would go a long way to showing what a successful process looks like. When you can't adequately describe it... show it.
Posted by: Andrea | June 9, 2009 12:22 PM
Lou,
I'll be discussing metrics-driven research in my upcoming talk at DRC (http://trex.id.iit.edu/events/drc/2009/speakers/tomer-sharon.html).
I will describe a 4-step model for measuring the user experience success (or failure) of a new Google product.
1. The process involves defining user experience goals for the product, that are separated from its business goals but are very relevant to its success or failure.
2. Next, UX goals are translated to signals in the interface that would tell whether success is achieved or not.
3. Then, signals are translated into specific metrics. For example, a UX goal would be "Efficiency", a signal for that goals is a measure of how lost users are when they complete a certain task, and a metric would be a "Lostness" score (that is calculated by a lostness formula).
4. The last step of the process is working with the product team (designers, engineers, and product managers) to make it happen.
I'd love to talk more about it (I'm currently at UPA 2009. Are you?).
Tomer
Posted by: Tomer Sharon | June 9, 2009 5:25 PM