Making up words and stringing together phrases are responsibilities I have taken seriously since branching out on my own as a consultant nearly two years ago. In well under a fortnight, I’ll be speaking at eMetrics Chicago on “analytics hygiene”, for example.
Another example lives within the analytics hygiene principles: omnivision.
Not omnichannel, omnivision! From the principles post: “know the past, present and future. Organizationally. you know… fit it into an omnivision framework. Know the answers to questions like: Why are you doing things the way they are done today? What are the pain points? Where do you see the analytics team and software involved going over the next 1, 3, 5, 10 years?”
Don’t spend a ton of time on it if you don’t think there’s value, but give it 30-60 minutes every once in a while.
Omnivision requires collaboration (newly added principle #5!). You can’t see the future and the past of all things related to your analytics program without it. And, as much as omnivision requires close collaboration with colleagues, it is a tough thing to achieve without outsider input (internal and external outsiders)… yet another principle.
Perhaps most importantly, omnivision helps analysts and other data consumers understand the data they are using to inform decisions. A trend I’ve noticed is that “external factors”, some that may not be all that external, like major web site changes, shifts in markets, even basic seasonality are so frequently not cared about. Google Analytics allows for annotations, as do many other analytics platforms… but the input of this data is often manual, and covers few of the factors impacting data.
I’ve been working on a solution that will bring externalities to light within integrated datasets. I would love to know of any tools that are out there to help with this bridge… but for now, I will build!