Your weekly source of sales, marketing, customer service, and management insight - compliments of ETE REMAN

With Great Data Comes Great Responsibility

June 25, 2020 BY The Rhythm Of Reman Leave a comment

Insights are often born out of frustration.  I routinely urge my colleagues to pay attention to those moments of repetitive frustration and annoyance and use them to identify opportunities for improvement.  Not all are actionable, but I find that most are, and the solutions can be simple. 

I’ve recently felt a growing disdain for the manner in which information is presented.  Ever opened a spreadsheet someone has sent you and spent a few minutes guessing at what the header abbreviations mean and how the data relates? Have you ever asked yourself, “What am I looking at here? Do I need a secret decoder ring?!” Worse yet, is the data used to deliberately mislead? (Watch a few commercials, you’re bound to see it).

Here are the problems I see regularly with the data the world presents to me:

  • Bias – A lot of the data we see is architected purposely to make us think the way the creator wants us to. Beware of the objectives and motives of the content creator and pay special attention to the exact way the statistics are described.
  • Sourcing/Quality of Data – Bad data equals bad intelligence and faulty conclusions. This often happens by accident because of combining different data sets or working with data sets you don’t know well. 
  • Poor Labeling – Use of abbreviations, unique terminology and proprietary metrics all add confusion. If you need an extensive data dictionary to read reports, chances are good that your data is too complicated.
  • Assumptions – When the people gathering the data think they know what it will mean before it’s collected, they tend to see the data they want to. Even with the best intentions, data can be explained as meaning something it doesn’t.

There is a common theme in these problems, the intentional or accidental misrepresentation of what the data says. This is particularly dangerous when it’s based in numeric, objective data. People tend to see precision as the same as correctness. I can tell you that 1.2% of people eat their ice cream cones from the bottom up and many would be inclined to believe me because the number is just so exact. But, what if that’s just my way of interpreting that, when surveyed, 98.8% of people say they eat their ice cream cones from the top down?*

As a member of our BI (Business Intelligence) team I know how difficult it is to avoid these pitfalls.  Even when trying diligently to seek truths from the numbers, our preconceived notions have an effect on our interpretations.  It’s a slippery slope.  When asking questions that have never been asked before, there are seldom the exact data sets you’d need to answer them neatly. That forces some compromise, assumption, and interpretation.  But, none of us can afford to wait for ideal conditions and perfect data in order to make our decisions (we’d be waiting forever).  To help offset these inevitable challenges, here are some things I wish everyone who shares information with the world would consider:

  • Be transparent
  • Use Visual Representation
  • Summarize Findings and Insights
  • Expose Weaknesses in Inputs

There’s a common theme to these, too – namely, be transparently honest with your data and presentation. As the world creates and collects more and more data, we’ll all get better at spotting and calling out mistakes. Our responsibility as data aggregators and interpreters is to be good stewards of the data. We must ensure we are wary of the mistakes people can make with (with good intentions or otherwise) and to provide our method so that our results can be reviewed as needed. Get ahead of the curve and give people what we really need, well-presented information in concise and transparent form – and be prepared to adjust your interpretations.   

* First, I assumed that if people don’t eat their ice cream from the top down, then they must eat it from the bottom up – but that wasn’t what the statistic said. And second, where did that data come from? For all we know, some blogger could have just made it up-

Related Articles