8 thought processes that can help you become a Data Scientists

A data scientist needs to be Critical and always on a lookout for something that misses others. So here is some advice that one can include in the day to day data science work to be better at their work:

1. Beware of the Clean Data Syndrome

You need to ask yourself questions even before you start working on the data. "Does this data make sense?" Falsely assuming that the data is clean could lead you towards wrong Hypotheses. Apart from that, you can discern a lot of important patterns by looking at discrepancies in the data. For example, if you notice that a particular column has more than 50 percent values missing, you might think about not using the column. Or you may think that some of the data collection instrument has some error.

Or let's say you have a distribution of Male vs. Female as 90:10 in a Female Cosmetic business. You may assume clean data and show the results as it is or you can use common sense and ask if the labels are switched.

2. Manage Outliers wisely

Outliers can help you understand more about the people who are using your website/product 24 hours a day, but including them while building models will skew the models a lot.

3. Keep an eye out for the Abnormal

Be on the lookout for something out of the obvious. If you find something you may have hit gold.

For example, Flickr started up as a Multiplayer game. Only when the founders noticed that people were using it as a photo upload service, did they pivot.

Another example is Fab.com started up as Fabulis.com, a site to help gay men meet people. One of the site's popular features was the "Gay deal of the Day". One day the deal was for Hamburgers - and half of the buyers were women. This caused the team to realize that there was a market for selling goods to women. So Fabulis pivoted to fab as a flash sale site for designer products.

4. Start Focussing on the right metrics

Beware of Vanity metrics. For example, number of active users by itself doesn't divulge a lot of information. I would rather say "5% MoM increase in active users" rather than saying "10000 active users". Even that is a vanity metric as active users would always increase. I would rather keep a track of percentage of users that are active to know how my product is performing. Try to find out a metric that ties with the business goal. For example, Average Sales/User for a particular month.

5. Statistics may lie too

Be critical of everything that gets quoted to you. Statistics has been used to lie in advertisements, in workplaces and a lot of other marketing venues in the past. People will do anything to get sales or promotions.

For example: Do you believe in Colgate's claim that 80% dentists recommend their toothpaste?

This statistic seems pretty good at first. It turns out that at the time of surveying the dentists, they could choose several brands - not just one. So other brands could be just as popular as Colgate.

Another Example: 99 percent Accurate" doesn't mean shit. Ask me to create a cancer prediction model and I could give you a 99 percent accurate model in a single line of code. How? Just predict "No Cancer" for each one. I will be accurate may be more than 99% of the time as Cancer is a pretty rare disease. Yet I have achieved nothing.

6. Understand how probability works

It happened during the summer of 1913 in a Casino in Monaco. Gamblers watched in amazement as a casino's roulette wheel landed on black 26 times in a row. And since the probability of a Red vs. Black is exactly half, they were certain that red was "due". It was a field day for the Casino. This is a perfect example of Gambler's fallacy, aka the Monte Carlo fallacy. This happens in real life, people tend to avoid long strings of the same answer, sometimes sacrificing accuracy of judgment for the sake of getting a pattern of decisions that looks fairer or probable.

For example, an admissions officer may reject the next application if he has approved three applications in a row, even if the application should have been accepted on merit.

7. Correlation Does Not Equal Causation

The Holy Grail of a Data scientist toolbox. To see something for what it is. Just because two variables move together in tandem doesn't necessarily mean that one causes another. There have been hilarious examples for this in the past. Some of the favourites are:

Looking at the firehouse department data you infer that the more firemen are sent to a fire, the more damage is done.
When investigating the cause of crime in New York City in the 80s, an academic found a strong correlation between the amount of serious crime committed and the amount of ice cream sold by street vendors!

Obviously, there was an unobserved variable causing both. Summers are when the crime is the greatest and when the most ice cream is sold. So Ice cream sales don't cause crime. Neither crime increases ice cream sales.

8. More data may help

Sometimes getting extra data may work wonders. You might be able to model the real world more closely by looking at the problem from all angles. Look for extra data sources.

For example, Crime data in a city might help banks provide a better credit line to a person living in a troubled neighbourhood and in turn increase the bottom line.

Source: HOB

Share This On

Previous Story Next Story

Latest News Feed