The Primary Analytics Practitioner
The field of Business Analytics can be very complex. Top level
analysts are experts; just like medical specialists, they have undergone years
of additional training and know their area of specialty (perhaps price
sensitivity, multivariate statistical modeling, survey analysis or mathematical
optimization) backwards. Keeping with this analogy, most business managers are as well informed as
to what business analytics can do for them as a patient heading in to see their
primary physician; perhaps less so.
Bringing your analytical guns to bear on Big Data – in-database analytics
I've blogged before about the need to use the right tools to hold and
manipulate data as data quantity increases (Data Handling the Right Tool for the Job). But, I really want to get to some value-enhancing analytics and as data grows it becomes increasingly hard to
apply analytical tools.
Let’s assume that we have a few Terabytes of data and that it's sat in an industrial-strength
database (Oracle, SQL*Server, MySQL, DB2, …) - one that can handle the data
volume without choking. Each of these databases has its own dialect of the querying
language (SQL) and while you can do a lot of sophisticated data manipulation, even a simple analytical routine like calculating correlations is a chore.
Cluster Analysis - 101
The current Wikipedia page on Cluster Analysis, excerpted below, is correct, detailed and makes absolute sense. Then again, if you do not have a background in statistical modeling, I'm guessing these two paragraphs leave you no wiser.
Cluster analysis or clustering is the task of assigning a set of objects into groups (called clusters) so that the objects in the same cluster are more similar (in some sense or another) to each other than to those in other clusters.
Clustering is a main task of explorative data mining, and a common technique for statistical data analysis used in many fields, including machine learning, pattern recognition, image analysis, information retrieval, and bioinformatics.
Wikipedia 4/2012
In this post I hope to provide a workable introduction for people that need to be educated consumers of cluster analysis.
Reporting is NOT Analytics
Reporting is about what happened; Analytics is about answering "what if" and "what's best" questions. Most of the materials that land on
a VP/Director’s desk (or inbox) are examples of reporting with no analytical
value added.
Data handling - the right tool for the job
Microsoft Excel must be the most
widely used analytic tool available today but, it’s not the only tool in my tool-bag and it should not be the only one in yours either.
It’s perfect for building small models, has broad embedded functionality, good charting capabilities, pivot-tables (a
superb tool worthy of its own post), comes with a programming language so
you can extend its capability even further and almost everybody has a copy already.
It’s awesome and I use it every day.
But...the data we analyze is getting much bigger and a lot more complex.
Even with newer versions of Excel allowing over 1 million records in a sheet, what can you do usefully in Excel with 1 million records? Certainly, you don’t want to print it, it’s
near impossible to chart or model against, bottom line you are using the wrong
tool for the job. To do the job well you
need to find, learn and use the right tool.
Don’t believe me? Try chopping
down a tree with a hammer!
Data Cleansing: boring, painful, tedious and very, very important
I've been working recently on a category management project and I'm reminded of just how essential clean, well-organized data is. We are working to group stores into 'clusters' of similar stores; later we will see what geographic and demographic data best helps us to predict cluster membership and optimize product assortment by cluster.
As a first pass, and under a severe time crunch, we took the data available, ran it through the model and while it processed, I was unhappy with the predictive power we found. Of course, this approach was ridiculously optimistic: so, back to look at the product characteristics we were using.
As a first pass, and under a severe time crunch, we took the data available, ran it through the model and while it processed, I was unhappy with the predictive power we found. Of course, this approach was ridiculously optimistic: so, back to look at the product characteristics we were using.
Subscribe to:
Posts (Atom)