Friday November 16, 2007 | Web Analytics Analyzed Strupp's Weblog |
|
All
|
General
We're working on redesigning our monthly Emetrics report. Every so often it needs to get pruned down, then built back up with the latest, greatest metrics. (I think that's a mixed metaphor.) Corporate and department goals and priorities change and evolve, and metrics reports need to do the same. As part of the redesign I've asked one of my senior analysts to propose some new metrics. Using best practices she's been very conscientious about including only "actionable" metrics. However, as we progress through the process, and think about the audience that will be reviewing the report (Directors and VPs) I wonder what "actionable" really means at that level? Online revenue is a great example. I can't imagine not having this metric in the report, but how actionable is it really? If revenue is down, you certainly want to take action, but I suspect the action would be "Paul, go figure out why revenue is down!". I think the right answer will be that some metrics are "bottom line" metrics and need to be included, but they should be surrounded by actionable metrics which tell me what to do if the bottom line (or top line in this case) slips. Comments:
Post a Comment: Comments are closed for this entry. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||