Defining Analytics: Analytics

Steve Bennett · 17th February 2010, 07:40 AM

Following-up to my blog 'Just Tell Me What I'm Doing', this is the third in a series of posts that define the key concepts and terms that make up my analytic world. Everything I do is coloured by my experience actually doing analytics in commercial organisations. So while I believe these posts will present practical definitions that will be actionable in the business world, I know that there are other worlds in academia and science where they are less relevant. At the very least, people in these areas will gain a better understanding of how business regards analytics. Data Warehouse puritans should perhaps stop reading, take a pill and lie down instead. Bennett's Analytica A Practitioner's Guide To Analytics Analytics The simplest definition of Analytics is "the science of analysis". A simple and practical definition, is that it is how a business arrives at an optimal or realistic decision based on existing data. Business managers may choose to make decisions based on past experiences or rules of thumb, or there might be other qualitative aspects to decision making. This is not analytics. When the decision is based on data, then this is analytics. Doug Lautzenheiser, a fellow blogger on the SmartData Collective recently gave us the following definition: “Business Intelligence isn't just about seeing how many cans of beans you sold last month. It's about figuring out how to sell even more in the future.” I like this, but even more when I swap out 'business intelligence' for 'analytics'. So, just like data warehousing and business intelligence, these are all terms used interchangeably in practice. Another favourite definition is: "analytics is reporting with an intent to inform a decision that you want to make." or even just: "analytics is reporting with intent." But I use this only when I am talking to someone who really doesn't understand much about the subject. Remember - my world is commerce. I haven't given much thought to other areas like academia and medicine, etc. where analytics is also used extensively. With that in mind, I define the analytic process as follows. Analytica IllustrationThe Analytic Process To me, it is the process you go through to analyse a problem and make a decision. Here are what I think are the common steps involved: Define the Problem. Example: "We need to improve by 20% the success of our Product X marketing campaigns." If you don't know what the problem is, then 99 times out of 100 you should stop the process and go and do something else that is useful! Generate Hypotheses. Use your experience and knowledge to guess ways in which you can use data to solve your problem. Often you will have several candidate hypotheses. These are 'educated guesses'. Example: "We can better predict which existing customers will buy more products if we can understand better what existing Product X customers have in common." Determine what information you need & gather it. Traditionally this information came from a data warehouse or some other sort...

Following-up to my blog 'Just Tell Me What I'm Doing', this is the third in a series of posts that define the key concepts and terms that make up my analytic world. Everything I do is coloured by my experience actually doing analytics in commercial organisations.

So while I believe these posts will present practical definitions that will be actionable in the business world, I know that there are other worlds in academia and science where they are less relevant. At the very least, people in these areas will gain a better understanding of how business regards analytics. Data Warehouse puritans should perhaps stop reading, take a pill and lie down instead.

Bennett's Analytica
A Practitioner's Guide To Analytics

Analytics

The simplest definition of Analytics is "the science of analysis". A simple and practical definition, is that it is how a business arrives at an optimal or realistic decision based on existing data. Business managers may choose to make decisions based on past experiences or rules of thumb, or there might be other qualitative aspects to decision making. This is not analytics. When the decision is based on data, then this is analytics.

Doug Lautzenheiser, a fellow blogger on the SmartData Collective recently gave us the following definition:

“Business Intelligence isn't just about seeing how many cans of beans you sold last month. It's about figuring out how to sell even more in the future.”

I like this, but even more when I swap out 'business intelligence' for 'analytics'. So, just like data warehousing and business intelligence, these are all terms used interchangeably in practice.

Another favourite definition is:

"analytics is reporting with an intent to inform a decision that you want to make."

or even just:

"analytics is reporting with intent."

But I use this only when I am talking to someone who really doesn't understand much about the subject.

Remember - my world is commerce. I haven't given much thought to other areas like academia and medicine, etc. where analytics is also used extensively. With that in mind, I define the analytic process as follows.

Analytica Illustration

The Analytic Process

To me, it is the process you go through to analyse a problem and make a decision. Here are what I think are the common steps involved:

Define the Problem. Example: "We need to improve by 20% the success of our Product X marketing campaigns." If you don't know what the problem is, then 99 times out of 100 you should stop the process and go and do something else that is useful!

Generate Hypotheses. Use your experience and knowledge to guess ways in which you can use data to solve your problem. Often you will have several candidate hypotheses. These are 'educated guesses'. Example: "We can better predict which existing customers will buy more products if we can understand better what existing Product X customers have in common."

Determine what information you need & gather it. Traditionally this information came from a data warehouse or some other sort of database or electronic file. In recent years unstructured textual data, multimedia and other sorts of data stores are being used.

Test sources. Run some basic reports to see if the data can support one (or more) of your hypotheses. If you are lucky, you have access to a Business Intelligence tool like Cognos, Business Objects, QlikView, etc. Often you don't and in these cases you can use SQL to extract data from their sources and import it into Microsoft Excel instead. Then test how good the source data is - or more precisely - determine how suitable the data is to our analytic purpose.

Test Hypotheses. Run further reports that are built to show how successful (or not) your hypothesis actually is. It is important to question your results and there are many way to do this. Here are a couple of the most common ways to do this:

- Find Root Causes. Look extra hard at the results that are the exceptions that do not support your hypothesis. Apply root cause analysis - this is analysis done in order to understand why the exceptions exist. Exceptions are often the data that do not fit your hypothesis. Example: "70% of the existing customers analysed had purchased a car in the 2 weeks before they purchased a tow bar [US: tow hitch]. But for 30% the towbar was their first purchase - but they only work in cars we sell". Concentrate on understanding the 30%. Example answer: "The tow bar purchaser for the exception 30% of customers, was 90% of the time either the spouse of the car purchaser or their employer".
- Experiment. Identify a set of customers with something in common but that haven't purchased Product X. Example: "30 - 40 year old women with 2 or more children under the age of 18". Also, randomly select a second group of customers (i.e. those with nothing in common) to be your control group. Then run the same test campaign using both groups and compare the results for both sets of customers.
Review the results with your peers to check that the result really is valuable. Is it fit for purpose? Is the effort worth the benefit gained? Can you identify enough customers meeting the criteria to meet the uplift target?

Package the process. If you regularly need to analyse the same or similar problems then you need to make the process repeatable by putting it into 'production' and packaging it with additional information about how it works, any known issues, its purpose, etc.

Get user feedback and evaluate the results by either tracking the decisions made based on the analysis or more informally. If you do the former, then congratulations - you are operating Decision Management. This is a holy grail for my work. More often you have to settle for informal feedback from the decision makers (or their colleagues). Example: "Analyst to Campaign Manager: So whadya think?"

Learn. Use this knowledge to improve the hypotheses, sources, data and process.

Repeat the process again until you get the result you want - or give it up as an unattainable goal.

Well that's how I see the process - at a very high level. I went looking online to see what other people thought and there was very little to find in the commercial context. Even wikipedia let me down although it does have interesting things to say about Analytic Hierarchy Processes and the Intelligence Analysis Process used by NSA and the like. There is an old discussion thread on LinkedIn that's relevant.

Analytic Techniques

There are a large number of statistical, mathematic and management techniques that can be used. These will be discussed in a future Analytica entry.

Common Uses of Analytics

Predictive Analytics

Predictive analytics encompasses a variety of techniques from statistics, data mining and game theory that analyse current and historical facts to make predictions about future events.

In business, predictive models exploit patterns found in historical and transactional data to identify risks and opportunities. Models capture relationships among many factors to allow assessment of risk or potential associated with a particular set of conditions, guiding decision making for candidate transactions.

Web Analytics

Web analytics is the measurement, collection, analysis and reporting of internet data for purposes of understanding and optimising web usage – not just measuring web traffic.

Related Terms and Concepts

Refer also to Data Mining

Comments? Via form below or send feedback to
analytica@tbig.com.au version 0.1 201002

Get More from the original blog...

17th February 2010, 07:40 AM	#1
Steve Bennett Member Join Date: Oct 2007 Posts: 386 Blog Entries: 26	Defining Analytics: Analytics Following-up to my blog 'Just Tell Me What I'm Doing', this is the third in a series of posts that define the key concepts and terms that make up my analytic world. Everything I do is coloured by my experience actually doing analytics in commercial organisations. So while I believe these posts will present practical definitions that will be actionable in the business world, I know that there are other worlds in academia and science where they are less relevant. At the very least, people in these areas will gain a better understanding of how business regards analytics. Data Warehouse puritans should perhaps stop reading, take a pill and lie down instead. Bennett's Analytica A Practitioner's Guide To Analytics Analytics The simplest definition of Analytics is "the science of analysis". A simple and practical definition, is that it is how a business arrives at an optimal or realistic decision based on existing data. Business managers may choose to make decisions based on past experiences or rules of thumb, or there might be other qualitative aspects to decision making. This is not analytics. When the decision is based on data, then this is analytics. Doug Lautzenheiser, a fellow blogger on the SmartData Collective recently gave us the following definition: “Business Intelligence isn't just about seeing how many cans of beans you sold last month. It's about figuring out how to sell even more in the future.” I like this, but even more when I swap out 'business intelligence' for 'analytics'. So, just like data warehousing and business intelligence, these are all terms used interchangeably in practice. Another favourite definition is: "analytics is reporting with an intent to inform a decision that you want to make." or even just: "analytics is reporting with intent." But I use this only when I am talking to someone who really doesn't understand much about the subject. Remember - my world is commerce. I haven't given much thought to other areas like academia and medicine, etc. where analytics is also used extensively. With that in mind, I define the analytic process as follows. Analytica IllustrationThe Analytic Process To me, it is the process you go through to analyse a problem and make a decision. Here are what I think are the common steps involved: Define the Problem. Example: "We need to improve by 20% the success of our Product X marketing campaigns." If you don't know what the problem is, then 99 times out of 100 you should stop the process and go and do something else that is useful! Generate Hypotheses. Use your experience and knowledge to guess ways in which you can use data to solve your problem. Often you will have several candidate hypotheses. These are 'educated guesses'. Example: "We can better predict which existing customers will buy more products if we can understand better what existing Product X customers have in common." Determine what information you need & gather it. Traditionally this information came from a data warehouse or some other sort... Following-up to my blog 'Just Tell Me What I'm Doing', this is the third in a series of posts that define the key concepts and terms that make up my analytic world. Everything I do is coloured by my experience actually doing analytics in commercial organisations. So while I believe these posts will present practical definitions that will be actionable in the business world, I know that there are other worlds in academia and science where they are less relevant. At the very least, people in these areas will gain a better understanding of how business regards analytics. Data Warehouse puritans should perhaps stop reading, take a pill and lie down instead. Bennett's Analytica A Practitioner's Guide To Analytics Analytics The simplest definition of Analytics is "the science of analysis". A simple and practical definition, is that it is how a business arrives at an optimal or realistic decision based on existing data. Business managers may choose to make decisions based on past experiences or rules of thumb, or there might be other qualitative aspects to decision making. This is not analytics. When the decision is based on data, then this is analytics. Doug Lautzenheiser, a fellow blogger on the SmartData Collective recently gave us the following definition: “Business Intelligence isn't just about seeing how many cans of beans you sold last month. It's about figuring out how to sell even more in the future.” I like this, but even more when I swap out 'business intelligence' for 'analytics'. So, just like data warehousing and business intelligence, these are all terms used interchangeably in practice. Another favourite definition is: "analytics is reporting with an intent to inform a decision that you want to make." or even just: "analytics is reporting with intent." But I use this only when I am talking to someone who really doesn't understand much about the subject. Remember - my world is commerce. I haven't given much thought to other areas like academia and medicine, etc. where analytics is also used extensively. With that in mind, I define the analytic process as follows. Analytica Illustration *The Analytic Process* To me, it is the process you go through to analyse a problem and make a decision. Here are what I think are the common steps involved: Define the Problem. Example: "We need to improve by 20% the success of our Product X marketing campaigns." If you don't know what the problem is, then 99 times out of 100 you should stop the process and go and do something else that is useful! Generate Hypotheses. Use your experience and knowledge to guess ways in which you can use data to solve your problem. Often you will have several candidate hypotheses. These are 'educated guesses'. Example: "We can better predict which existing customers will buy more products if we can understand better what existing Product X customers have in common." Determine what information you need & gather it. Traditionally this information came from a data warehouse or some other sort of database or electronic file. In recent years unstructured textual data, multimedia and other sorts of data stores are being used. Test sources. Run some basic reports to see if the data can support one (or more) of your hypotheses. If you are lucky, you have access to a Business Intelligence tool like Cognos, Business Objects, QlikView, etc. Often you don't and in these cases you can use SQL to extract data from their sources and import it into Microsoft Excel instead. Then test how good the source data is - or more precisely - determine how suitable the data is to our analytic purpose. Test Hypotheses. Run further reports that are built to show how successful (or not) your hypothesis actually is. It is important to question your results and there are many way to do this. Here are a couple of the most common ways to do this: Find Root Causes. Look extra hard at the results that are the exceptions that do not support your hypothesis. Apply root cause analysis - this is analysis done in order to understand why the exceptions exist. Exceptions are often the data that do not fit your hypothesis. Example: "70% of the existing customers analysed had purchased a car in the 2 weeks before they purchased a tow bar [US: tow hitch]. But for 30% the towbar was their first purchase - but they only work in cars we sell". Concentrate on understanding the 30%. Example answer: "The tow bar purchaser for the exception 30% of customers, was 90% of the time either the spouse of the car purchaser or their employer". Experiment. Identify a set of customers with something in common but that haven't purchased Product X. Example: "30 - 40 year old women with 2 or more children under the age of 18". Also, randomly select a second group of customers (i.e. those with nothing in common) to be your control group. Then run the same test campaign using both groups and compare the results for both sets of customers. Review the results with your peers to check that the result really is valuable. Is it fit for purpose? Is the effort worth the benefit gained? Can you identify enough customers meeting the criteria to meet the uplift target? Package the process. If you regularly need to analyse the same or similar problems then you need to make the process repeatable by putting it into 'production' and packaging it with additional information about how it works, any known issues, its purpose, etc. Get user feedback and evaluate the results by either tracking the decisions made based on the analysis or more informally. If you do the former, then congratulations - you are operating Decision Management. This is a holy grail for my work. More often you have to settle for informal feedback from the decision makers (or their colleagues). Example: "Analyst to Campaign Manager: So whadya think?" Learn. Use this knowledge to improve the hypotheses, sources, data and process. Repeat the process again until you get the result you want - or give it up as an unattainable goal. Well that's how I see the process - at a very high level. I went looking online to see what other people thought and there was very little to find in the commercial context. Even wikipedia let me down although it does have interesting things to say about Analytic Hierarchy Processes and the Intelligence Analysis Process used by NSA and the like. There is an old discussion thread on LinkedIn that's relevant. Analytic Techniques There are a large number of statistical, mathematic and management techniques that can be used. These will be discussed in a future Analytica entry. Common Uses of Analytics *Predictive Analytics* Predictive analytics encompasses a variety of techniques from statistics, data mining and game theory that analyse current and historical facts to make predictions about future events. In business, predictive models exploit patterns found in historical and transactional data to identify risks and opportunities. Models capture relationships among many factors to allow assessment of risk or potential associated with a particular set of conditions, guiding decision making for candidate transactions. *Web Analytics* Web analytics is the measurement, collection, analysis and reporting of internet data for purposes of understanding and optimising web usage – not just measuring web traffic. Related Terms and Concepts Refer also to Data Mining Comments? Via form below or send feedback to analytica@tbig.com.au version 0.1 201002 Get More from the original blog...

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Defining Analytics: Data Warehousing	Steve Bennett	Oz Analytics	0	10th February 2010 11:08 PM
Defining Analytics: Data, Information and Knowledge	Steve Bennett	Oz Analytics	0	8th February 2010 06:09 AM
Aussie: Custom web analytics implementation covering Google Analytics and Atlas ad s	admin	Presentation News Feeds	0	4th February 2010 05:26 PM
Analytics 3.0. - Designing an all-purpose analytics web server, offering API, SaaS, o	admin	Analytic News Feeds	0	21st December 2009 12:48 PM
IBM Furthers Investment In Business Analytics With Smart Analytics Cloud	Doug Heywood	IBM and Cognos Forum	1	17th November 2009 08:53 PM