Gartner Blog Network

Big Data Tells Us What We Want to Hear

by Nick Heudecker  |  March 20, 2015  |  Submit a Comment

This is a guest post from Mark Beyer.

In the era of Big data, the theory goes that with more data, more inputs and more information, we can learn more, discover more and develop new insights. What if that is wrong?

A “theory of everything” is a complex physical theory that all things in the universe are somehow related to each other and interact with each other all of the time. General relativity and quantum field theory are frameworks that attempt to explain ToE. More recently, String theory proposes that there may actually be a single unifying theory based upon vibrational “strings” for preferred resonance and useful dissonance. In physics, that’s a grand theory. And, for some unknown reason, human beings have begun to interpret our theories (which are merely rationalized explanations we use to understand something) as actual facts. To quote everyone’s favorite science officer, we just “have a theory that happens to fit the facts.” It is actually a human interpretation of the real world that specifies physical data points—physics exists without us. The good news is, physics are mechanical. Unfortunately, it is far easier to evaluate the physical relative relationships of tangible objects than doing the same thing for logical concepts. And, that my friend, is the problem with data.

Data documenting business processes is merely a rationalized explanation of a logical theory that is proposed by humans from a distinctive perspective. In simple terms, ALL data is biased toward the creator. All data is captured from multiple perspectives and represents multiple points of bias. That means each new data point reflects the intent of the business process designer. This means it is not possible to actually assemble new analytics from existing data. Even more concerning, it is not possible to alter analysis with new data—you can only reinforce or refute the expected analysis. Any new analysis actually ALSO follows the data design at its creation. Since most new data is inserted into an existing model, it inherits the previous bias and is limited by those previous logical decisions. Human logic is inherently embedded in all business processes and all data capture is biased toward the expected outcome of those processes. And since all data is pre-existing immediately after it is designed, it will always be tainted by the original design which assumes both the business process and meaningful questions about that process.

When a business analyst performs their task, they create inferences between data points where no actual data exists. When that same analyst becomes dissatisfied with their own theories of inference, they should seek new data to fill in the gaps. Instead, most analysts resort to layering these inferences, all visibility into the underlying assumptions is lost and a data derivative is created. Adding more data does not necessarily support the analysis of new theories and often merely supports existing theory. (See, “Maverick* Research: How Big Data Causes Business Meltdown”, #G00268417, 26 September 2014.) Data derivatives are reinforced over time, because they represent highly complex layers of logical arguments. But, once again, logic is an interpretation of facts.

So, what are we to do? Over the past thirty-six months, Gartner has witnessed many data miners, data analysts, senior systems analysts and business intelligence professionals change their title to “data scientist”. It is not unusual for professionals to adhere to market hype and promote their prestige and incomes by doing so. But, what business strategists need is “real” data science. Real data science is the practice of building out competing interpretations of data, many multi-layered analytic theorems that intentionally challenge the inferences used by the others. True data science compares these theories along at least two axes.

First, how easy is it to trace the actual data used back to its originating business process? How many jumps or hops created the data? The number of assumptions and the complexity of the inferences between data points that are in use gives some idea of how reliable the data is. Second, how far removed from the physical process world is the data point? Meters that record electrical pulses are pretty accurate; however, the manner in which they are recorded, the record layout, even the decision to record “meaningful change” in the electro-static state of a device, is a form of bias. We record want we want to hear. Data science quantifies these distances and constructs models that test these assumptions, maybe fifty, maybe a thousand different ways. Then data science tests the veracity of the models. Now, don’t take this blog as instructions on how to pursue data science yourself or how to identify a data scientist—I said at LEAST two axes. But, the next time you decide to make a decision based upon data, remember it only tells you what the process designer thought of at the time of deployment and literally EVERYTHING else is only theory. You need data science to identify where the inferences are becoming extreme (and becoming derivative) and: either obtain integral data to fill those assumptions with facts; or, your data science team must build multiple models that constantly challenge those over-burdened assumptions (derivatives) with competing inference laden theory. And THAT, is how can start to actually listen to the data!

Category: big-data  

Tags: big-data  

Nick Heudecker
Research Director
4 years at Gartner
18 years IT Industry

Nick Heudecker is an Analyst in Gartner's Research and Advisory Data Management group. Read Full Bio

Leave a Reply

Your email address will not be published. Required fields are marked *

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.