Once you are done with understanding the problem statement and have your strategy in place, then only look into data. Never dive into the ocean without doing preparation. If you directly look into your data, you would try to find as many patterns possible in it and that process will never end. You won’t know when to stop and will get stuck instead.
Don’t worry, Hypothesis Generation is there to help you out!
As mentioned in this article,
Hypothesis generation is an educated “guess” of various factors that are impacting the business problem that needs to be solved using machine learning.
In short, you are making wise assumptions as to how certain factors would affect our target variable and in the process that follows, you try to prove and disprove them using various statistical and graphical tools.
This process will save a lot of time. Let me illustrate that with an example.
The Problem Statement that we are going to solve is-
“Being a Data Scientist in an E-Learning Platform, you have been employed to determine the Course Sales for the upcoming few months so that we find out what our Cash flow is gonna be. This will help us in the allocation of our resources to pay our instructors, for our operations and also, for our expansion.”
Ideally, before looking into the data, just spend one hour and understand the problem statement well. Think about all the factors that would affect the sales of our courses and then look into the data- this will help you in the feature engineering process.1
This is how the Dataset looks like–
There are 9 features (removing ID) and the target variable- Sales.
First, perform the Univariate analysis to understand each variable. I hope that’s pretty straightforward and not that much time-consuming?
But, the process of Bivariate and Multivariate Analysis which follows could take a lot of time if you try to take up all the possible combinations (⁹C₂=36 combinations for just bivariate) and try to find a relationship between them. Especially when you’re dealing with a hackathon dataset, this process should ideally be performed quickly!
Now, this is how I carried out Bivariate analysis-
While I was doing the Univariate Analysis, I compiled a set of questions which I would then try to prove and disprove using simple visual tools, you might want to choose another way.
So, these are the questions that would more or less cover our Bivariate Analysis. The visualizations have been made in Python using Matplotlib and Seaborn. They are pretty easy to build as well as interpret.
Yes, it is! We can see that there is a difference between Mean Sales when Courses were on Short Promotion and when they were not. You may use a t-test to statistically back your analysis as well rather than just visually doing it.
We can see that the Mean Sales on Non-Holidays is more than on Public Holidays. So, No! Public Holidays do not contribute to More Sales.
Again, the mean sales under Long Promotion is less than when it is not under long promotion. So, we can say that Long Promotions do not help increase our sales. Hence, No!
No! In fact, User Traffic is lesser on Public Holidays. People don’t visit prefer to buy courses on holidays xD
After looking at the scatter plot and obviously the correlation value, we can see that higher User Traffic leads to higher Sales. So, Yes! Higher User Traffic significantly affects our target variable.
No! Looking at the correlation value (-0.015), we can say that Competition_Metric hardly has any effect on Sales. Instead, it slightly decreases it.
Yes! The Bar Plot clearly shows that Degrees have much higher sales than Course and Programs.
Yes! Business courses have a much higher mean than others. So, Course Domain affects Sales. But, do you see that the black line going through Business is much bigger than the rest? This implies that the variance of Sales of Business courses is much larger. To further confirm whether Course Domains affect the Sales, you may perform ANOVA or T-test.
To answer this question we draw two line plots with Sales on the y-axis and Days on the x-axis in the first chart and Weeks in the second chart. We observe a bi-weekly pattern through the first plot and a yearly seasonal pattern through the second.
Voila! This is how our Analysis turned out to be-
Wasn’t it quick? Once we performed the Hypothesis generation, it hardly took any time to carry out further analysis.
And that is the beauty of planning, my friends. (Aha! I just gave you a life lesson! xD)
I am sure you would have some different ways of doing EDA and I would love to hear it from you. You can contact me on LinkedIn or we can discuss it in the comments below!
Thanks for staying till the end.
LinkedIn- https://www.linkedin.com/in/iasarthak/
GitHub- https://github.com/iasarthak
Top 10 Data Analytics Projects with Source Codes
Hypothesis Generation for Data Science Projects...
Solving Business Case Study Assignments For Dat...
Business Case Study Assignments For Entry Level...
7 Steps of Data Exploration & Preparation ...
Approach and Solution to break in Top 20 of Big...
The Key Concepts To Investigating Your Dataset
8 Charts You Must Know To Excel In The Art of D...
Top 10 AI Sales Assistant Tools
How Data Science and Business Intelligence Can ...
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s
Love this! Pretty well described, a lot of beginners struggle with it, more so on the time allocation part - thanks for this!