What do we mean when we talk about data-driven products?
Neal Lathia

Recently we see many discussions like this: “Is this application data-driven or not?” , “Is he data scientist or data engineer or data analyst?” and many other similar discussions that try to show what some people do is not what they do and also what they do is not what other people do. I personally, do not think this type of discussions are as important as they look. What are we going to prove by showing that those examples are not data driven and some others are? In fact, by definition, when we add the data-driven adjective to something, it simply means the decisions and activities are made by “data” rather than by people experience and intuition. So, when you talk about an app that tells you the approximate arrival time of a bus or train, it could be data driven. Why? because it uses data. It gives you an information based on data. It actually even could go further and gives the estimate distance (time) from your location to the destination based on the average commute time of the vehicles in the past at the same time of the day. The thing is, sometime because we use data almost every day, we do not observe many things that are actually data-driven. So, when you get an information based on data, it is data-driven. Now, some may say it does not use machine learning algorithms to do some cool stuff on the data, but it does not matter. It is still data driven!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.