Big Data. Big Decisions
InformationWeek
Special Coverage Series


7 Deadly Sins Of Big Data Users

Sloth, negligence, gluttony...and that's just the beginning. Consider these common mistakes organizations make when assessing the meaning of large amounts of data.

We're swimming in a vast sea of data that's rising every year. And according to Josh Williams, president and chief science officer of Kontagent, a social and mobile analytics company, companies that collect, analyze, and interpret data accurately--and act upon it quickly--have a significant competitive advantage.

At the Kontagent Konnect user conference in late May, Williams made a presentation called the "7 Deadly Sins of Data Science," in which he outlined the common mistakes that organizations make when processing large amounts of data. There's a good chance you're familiar one or more of the Deadly Sins, which include Sloth, Negligence, Gluttony, Polemy, Imprudence, Pride, and, of course, Torpor.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

We've summarized each transgression below. If your organization has sinned, now is the time to repent.

1. Sloth: Lazy Data Collection. If your data-collection skills are bad, the data you acquire probably won't help your organization much. "We see a lot of times that faulty measurements lead to faulty management," Williams told InformationWeek. "It's a garbage-in, garbage-out problem."

[ If you had all the data that's available, where would you put it? See Big Data Means Big Storage Choices. ]

2. Negligence: Misapplied Analysis. It's easy to make analytical errors as data starts to filter through your organization. "Not everyone is a data expert, and they can draw the wrong conclusions," Williams said. You must analyze the data rigorously to create simple, easy-to-understand reports.

3. Gluttony: Too Many Reports. A glut of information and good visualization tools often lead organizations to produce too many reports, including those with vanity metrics (e.g., a website's number of registered users) that cause you to miss important facts about your business or industry. "Whether you're doing this in-house or with third-party vendors, it's easy to spit out a lot of reports, a lot of data," said Williams. "Too much information can cloud your judgment, and that makes it hard to make decisions."

4. Polemy: Data Definition, Use Disagreements. If the people in your organization don't agree about what a report means and how to act on it, you'll end up in conflict. Unclear definitions, personal interpretations of what the data means, or uncertainty on how to act on data, can hamper an organization's ability to make decisions. So make sure that different groups within your company aren't going in different directions based on the same data. "It's shocking how often that happens," Williams said.

5. Imprudence: Jumping To Conclusions. When you dig through data and read reports, it's not uncommon to see things that cause alarm. Companies may jump to conclusions without examining data sufficiently. They may even change their business model for the wrong reasons, such as relying on other people's conclusions, misinterpreting data, or reading an industry benchmark and deciding they need to follow a so-called best practice. "We encourage people to verify, run their own tests, and then decide if something that has become common knowledge really works," said Williams.

6. Pride: Decision-Driven Data Making. Rather than running tests and using data to confirm or deny assumptions, this Deadly Sin is where you dig through data to confirm your preconceived notions. "We see this happen a lot throughout organizations, both at the executive level and within teams," Williams said. "People try to confirm what they believe; they dig through data to find it." But the best data-driven cultures have mantras like: "Data wins arguments," he said. Let the data speak the truth.

7. Torpor: Learning And Acting Slowly. "A critical factor is how quickly you act on data, and how quickly you learn from it. This is where a lot of companies fall short," Williams said. You should interpret data methodically, of course. And you'll want to develop a process to ensure that people aren't jumping to conclusions based on the data, or using the data to confirm what they already believe. But once a decision is made, you must act on it right away.

Big data places heavy demands on storage infrastructure. In the new, all-digital Big Storage issue of InformationWeek Government, find out how federal agencies must adapt their architectures and policies to optimize it all. Also, we explain why tape storage continues to survive and thrive.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.