A two-blog series on what data science can do, with real world examples.
Someone once asked me, “What does Data Science do?”
In my experience, there are essentially three work products:- Exploratory Data Analysis
- Decision Engines
- → $$$ (10x – 200x ROI)
The 1st is often a precursor to build and deploy the 2nd; both of these {1,2} drive the 3rd. In a two-blog series, I give two examples of my earlier work as reference.
EXAMPLE1: GARBAGE IN, PROFITS OUT!

My pricing engine generates close to $40MM per year in EBIT for the company. This work received national recognition in InfoWeek500 (2011) as “Garbage In, Profits Out” (and won the top spot for “No. 1 most innovative revenue generating idea” among the Fortune 500 rankings).

Once I developed a proof of concept that showed dramatic increases in yield in a few test markets, the CEO gave me the go ahead to hire an entire team. It took nearly 2.5 years of pitching and convincing multiple business units to adopt the algorithmic framework within the company, in order to get buy-in across the entire company to where all the regional pricing managers would trust the output of the model, and it became the default pricing engine behind the entire revenue management practice.
To date, it has generated over $0.5 billion in pure yield, having been active for more than a decade, undergoing some periodic model revisions. The underlying event space remains as it was when it was first conceived — and without that core piece of model engineering, it would have been impossible to create these models. Our CIO asked me to present my work at the quarterly all hands meeting to an audience of 5000 people, as an example of how data science might positively disrupt the enterprise.
I recall the appellation ‘data scientist’ became wildly popular just a year or two after I had completed this work, and it turns out, it was a perfect description of what I was doing, and now I had a name for it.
Around this same time, I coined the term ‘data engineering’, and when some consultants from one of the Big4 interviewed me in regards to my pricing work, I began using that terminology to describe what I was doing to construct a toy system that reflected the behavior of the real system I was modeling; later, coincidence or not, IT and the broader industry got a hold of that term and high-jacked it to mean something completely different. So, I now call it ‘event space engineering’ to reflect its statistical origins.
To read the next part of the blog, click here.
The author, “Prad” for short, is a senior analytics executive and experienced data science practitioner with a distinguished track-record of driving AI thought leadership, strategy, and innovation at enterprise scale. His focus areas are Artificial Intelligence, Machine/Deep Learning, Blockchain, IIoT/IoT, and Industry 4.0.